Lesson 4: Building Solutions with Agile Product Delivery (10 questions) Flashcards
What is ‘Customer Centricity’?
Customer Centricity is a mindset that focuses on creating positive experiences for the customer.
It is designing whole-product solutions with a deep understanding of the customer’s needs.
Customer-centric enterprises apply empathic design throughout the product lifecycle.
What is Design Thinking?
Design Thinking is a customer-centric development process that creates desirable products that are profitable and sustainable over their lifecycle.
Design thinking represents a profoundly different approach to product and solution development, in which divergent and convergent techniques are applied to understand a problem, design a solution, and deliver that solution.
Two Diamonds: Problem Space < > Solution Space
Problem Space: Understand the problem
Solution Space: Design the right solution
Each diamond focuses on divergent thinking (understanding and exploring options) followed by convergent thinking (evaluating options and making choices).
< Problem Space > < Solution Space>
<>Discover (diverge) <> Devleop (diverge)
<> Define (converge) <> Deliver (converge)
Hint: 4’D’s
Builds a solution that is:
- Desirable
- Freasable
- Sustainable
- Viable
(Hint: Do For Sweet Vixen)
What are Personas and how are they used?
Personas are used to understand the customer and focus our designs:
- They help convey the problems that the end-user is facing and provide key triggers for using the product.
What are Empathy Mapping?
Empathy maps are a design thinking tool that promotes customer identification by helping teams develop a deep, shared understanding of others.
They enable teams to imagine what a specific persona is thinking, feeling, hearing, and seeing as they use the product.
- Goal: Who are empathizing with?
- Goal: What do they need to do?
- What do they see?
- What do they hear?
- What do they do?
- What do they say?
- Pain/Gain: What do they think
- Pain/Gain: What do they feel?
The greater the degree of empathy a team has for its customers, the more likely it will be able to design desirable solutions.
What is the primary purpose of a Journey Map?
A Customer Journey Map captures the user’s experiences as they interact with a company’s operational value stream, products, and services.
Journey mapping is a visual representation of the customer experience, including all of the interactions and touchpoints they have with a product or service.
The important goal of Journey Mapping is to know a deep understanding of the customer’s perspective and identifies the areas needed for improvement.
Journey mapping provides teams with a comprehensive view of the customer experience, including both the customer’s needs and their pain points, which can be used to inform the development of an implementation plan.
What is a Benefit-Feature Matrix? How is it used?
For a benefit-feature matrix the intended customer benefits are identified first, and then the teams determine what features might satisfy their needs. This approach helps agile teams explore better and faster ways to deliver the desired benefits.
When should teams use ‘story maps’?
Story maps capture user workflows. They help teams ideate, plan, and group activities in a workflow or user journey. They allow teams to identify and address the most critical steps before improving existing steps or adding new functionality
i.e., ID the set of stories that are essential to the current release (while others can be marked a future stores).
What are Features and when are the Acceptance Criteria associated with Features defined?
Features represent work for the ART and typcially fit in a single PI. ACs are typically defined durning ART backlog refinement.
Features provide benefit hypotheses statement (the what) that can be used to justify development costs and provides business perspective for decision making.
Features are implemented by stories.
Workbook 4-16
True of False
Story points at some point in time must represent a unit of time measurement.
False
Story points are relative and are not connected to any specific unit of mesurement.
If you only quantify one thing quantify the < blank> < blank> < blank >
Cost of Delay
True of False
Give preference to jobs with shorter duration and higher COD.
True
Considering the formula for WSJF is COD/Duration. What are the components of COD?
- User-buisness value (UBV)
- Time criticality (TC)
- Risk Reduction and/or Opportunity Enablers (RROE)
COD = UBV + TC + RROE
3 features were evaluated using WSJF the values are as follows:
Feature A WSJF = 12.2
Feature B WSJF = 10.2
Feature C WSJF = 8
Which feature do I do first, second and third?
Do A, then B, and then C
What is the purpose of PI Objectives?
PI Objectives are business summaries of what each team intends to deliver in the upcomming PI.
PI Objectives often directly relate to intended feature in the backlog. PI objective are used to engage business owners. PI Objectives are written in a language that is understood by the business.
PI Objectives (committed) also help build trust with BOs. Trust allows all stakeholders to move forward confidently and base decisions and plans on what is ‘very likely to be true very soon.’
What are the inputs and outputs of PI planning?
Inputs to PI Planning:
- Business context
- Roadmap and vision
- Highest priority Features of the ART Backlog
Output of PI Planning:
- Committed PI objectives – Each team creates a set of SMART objectives with the business value assigned by the Business Owners.
- ART planning board – Highlighting the new feature delivery dates, feature dependencies among teams, and relevant milestones
PAH: ART RISK ROAM boards could also be an output of PI planning.
With regards to SMART objectives. What does the ‘R’ stand for?
Realistic
Specific – States the intended outcome as concisely and explicitly as possible. (Hint: Try starting with an action verb.)
Measurable – It should be clear what a team needs to do to achieve the objective. The measures may be descriptive, yes/no, quantitative, or provide a range.
Achievable – Achieving the objective should be within the team’s control and influence.
Realistic – Recognize factors that cannot be controlled. (Hint: Avoid making ‘happy path’ assumptions.)
Time-bound – The time period for achievement must be within the PI or sooner, so all objectives must be scoped appropriately.
True or False
Uncommitted objectives count when calculating team load.
True
Student workbook 4-37
In order to be a successful PI planning event readness needs to be accomplished in what three areas?
Organizational readiness
Content readiness
Logistics readiness
With regards to content readness what three briefing are addressed in day 1 of PI planning?
Executive briefing – A briefing that defines the current business context
Product vision briefing(s) – Briefings prepared by Product Management, including the top 10 features in the ART Backlog
Architecture vision briefing – A presentation made by the CTO, Enterprise Architect, or System Architect to communicate new enablers, features, and Nonfunctional Requirements (NFRs)
With regards to PI planning what is required for organizational readiness
Planning scope and context – Is the planning process’s scope (product, system, technology domain) understood? Do we know which teams need to plan together?
Business alignment – Is there reasonable agreement on priorities among the Business Owners?
Agile teams – Do we have Agile teams? Are there dedicated team members and an identified Scrum Master/Team Coach and Product Owner for each team?