Building Solutions with Agile Product Delivery Flashcards
What is Design Thinking?
Clear and continuous understanding of the target market, Customers, the problems they are facing, and the jobs to be done
Design Thinking tools (6)
- Gemba Walks
- Personas
- Empathy Maps
- Journey Maps
- Story Mapping
- Prototyping
Customer Centricity is a Mindset
- Think like the customer
- Focus on the customer
- Understand the customer’s needs
- Build whole product solutions
- Know customer lifetime value
- EVERYTHING IS ABOUT THE CUSTOMER
Program Backlog
Holding area for upcoming Features that will address user needs and deliver business benefits for a single Agile Release Train (ART)
Features
Represents the work for the Agile Release Train (ART)
► The Feature benefit hypothesis justifies development cost and provides business perspective for decision-making
► Acceptance criteria are typically defined during Program Backlog refinement
► Reflect functional and nonfunctional requirements
► Fits in one PI
Stories
Features are implemented by Stories
► Stories are small increments of value that can be developed in days and are relatively easy to estimate
► Story user-voice form captures role, activity, and goal
► Features fit in one PI for one ART; Stories fit in one Iteration for one team
Story Points
Singular number that represents:
– Volume: How much is there?
– Complexity: How hard is it?
– Knowledge: What do we know?
– Uncertainty: What’s not known?
Weighted Shortest Job First (WSJF)
Give preference to jobs with shorter duration and higher cost of delay (CoD)
Cost of Delay Components (3)
- User Business Value
- Time Criticality
- Risk Reduction & Opportunity Enablement
WSJF Calculation
User Business Value + Time Criticality + Risk Reduction & Opportunity Enablement / Job Size
Program Increment (PI) Planning
Cadence-based event that serves as the heartbeat of the Agile Release Train (ART), aligning all teams on the ART to a shared mission and vision.
► Two days every 8 – 12 weeks (10 weeks is typical)
► Everyone plans together
► Product Management owns Feature priorities
► Development teams own Story planning and high-level estimates
► Architect/Engineering and UX work as intermediaries for governance, interfaces, and dependencies
Program Increment (PI) Planning Activities
- Product Solution/Vision
- Architecture Vision & Development Practices
- Planning Context
- Draft Plan Review
- Management Review & Problem Solving
- Planning Adjustments
- Final Plan Review
- Program Risks
- PI Confidence Vote
- Plan Rework (if necessary)
- Planning Retrospective & Moving Forward
Program Increment (PI) Objectives
► Objectives are business summaries of what each team intends to deliver in the upcoming PI
► They often directly relate to intended Features in the backlog
Uncommitted Objectives
Low confidence in meeting PI objective
► They are planned and aren’t extra things teams do ‘just in case you have time’
► They are not included in the commitment, thereby making the commitment more reliable
► If an objective has many unknowns, consider moving it to uncommitted and put in early spikes
► Uncommitted objectives count when calculating load
Program Risks (ROAM)
RESOLVED - Has been addressed. No longer a concern.
OWNED - Someone has taken responsibility.
ACCEPTED - Nothing more can be done. If risk occurs, release may be compromised.
MITIGATED - Team has plan to adjust as necessary.
