To Deliver, Discover We Must - A value-driven approach to agile planning
- 1. Raj Indugula raj.indugula@lithespeed.com Twitter: @lithespeed, @raj_indugula, To Deliver, Plan We Must Discover A value-driven approach to agile planning
- 2. Enable business strategies by fundamentally shifting the way we deliver technology to become the uncontested market leader in … Customer- centricity Speed to market Productivity Innovation Teams will adopt agile methods to execute against their mission OrganizationalContext 2
- 3. Agile, But… SprintsRequirements & Planning Controlled Acceptance, Release and Operations Sprint Planning & Backlog Daily Standup Sprint Review Idea Requirements & Specifications Acceptance Operations The fuzzy front end The last mile • Teams not aligned to business goals • Lack of sufficiently ready work items • Long requirements lead time • Lack of clarity, line-of-sight Build to spec, not need Lack of Engagement, transparency 3
- 5. “The narrower the view, the wider the ignorance” Solely focused here 5
- 6. From Shared Vision to Reality… STORIES FEATURES EPICS GOALS/ROADMAP SHARED VISION What do you want to achieve? What will the business get out of it and what is the line of sight? What do users and stakeholders need to achieve the goals? What need can the application fulfill? ACCEPTANCE CRITERIA Scenarios/Examples Executable Specs TASKS What specifically do we do to complete the story? What need delivers user value? How do we know we answered the need properly? Help clarify by breaking the feature into smaller user stories Example Technique: Story Mapping Concrete examples are easier to grasp and test Provides focus for delivery by putting deliverables in the context of impacts they are supposed to achieve Example Technique: Impact Mapping (What, Why, Who) (How)Example Technique: Example Mapping Connecting the work of the teams with business goals Delivery Team Bus. Sponsor & Product Owner Product Owner & Delivery Team Product Owner & Delivery Team Product Owner & Discovery Team 6
- 7. 1. Identify and Understand the Business Needs • What is the product vision & goals? • Understand user journey(s); pains and gains • What are the success criteria?
- 8. How we capture our product vision & goals XXXXXXX XXXXXX (1 Program, 2 Customer Experiences) Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation Program Goals • Highly-available, secure, fit-for- purpose solutions that meet/exceed performance service levels • Predictable flow of value matched to customer needs • High quality product solutions as perceived by our customers • Engaged and happy team members Target Group Goals Team / Roles Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque Real-Time Execution Data Analytics & Intelligence Finibus Bonorum et Malorum • ugit, sed quiaC • magni dolores eos • umquam eius modi tempora • minus id quod maxime placeat facere possimus • sed quia consequuntur magni dolores eos qui • 1 PO / team • 1 SM / team 9 Delivery Team Members • Tech Lead • Analysts • Developers • Operations • 1 CPO • 1 RTE • 2 Teams (11 people per team) System & Shared Services • 1 PO • 1 SM 10 Delivery Team Members • Tech Lead • Analysts • Developers • Operations • System upgrades & optimization • Infrastructure maintenance • DevOps • System / Performance Testing • All customers CPO & RTE support from Data Analytics 1 Team (15 people) • 1 PO • 1 SM 13 Delivery Team Members • Tech Lead • Analysts • Developers • Operations • Production support & triage • Break-fixes / emergency changes • 1 CPO • 1 RTE • 1 Team (12 people) Vision Goals & Outcomes Product Canvas 8 Finibus Bonorum et Malorum • ugit, sed quiaC • magni dolores eos • umquam eius modi tempora • minus id quod maxime placeat facere possimus • sed quia consequuntur magni dolores eos qui • What are we trying to accomplish, and for whom? • Why are we doing this? • What are we hoping will happen by doing this work?
- 9. Howwegaininsightintocustomer painpoints Customer Journey Customer Journey Map Template 9 Highlight development priorities, by exposing gaps in desired customer experience
- 10. How we create alignment Objective: Create an awesome customer experience Key Results: -> Improve Net Promoter Score from X to Y. -> Increase Repurchase Rate from X to Y. “If it does not have a number, it is not a key result.” OKRs OKRs 10 • Set, tracked, & re-evaluated quarterly • Simple • Transparent • Supports nested cadence
- 11. 2. Find the Opportunities • Identify opportunities (how might we achieve identified product goals?) • Create high-level actionable plan with current, near-term and directional time horizons
- 12. Howwedostrategicplanning ACTORS IMPACTS DELIVERABLES RISKS & ASSUMPTIONS GOAL(S) https://www.impactmapping.org/ 12 • Discourages solution-first thinking • Leverages wisdom of crowds • Provides big-picture view • Fosters shared understanding Impact Map
- 13. BusinessMilestonesacrossTimeHorizons AUG NOV JAN ORION DRACO PEGASUS Purpose: Test and Learn Outcome: • Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi • Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur • At vero eos et accusamus et iusto odio dignissimos ducimus qui blanditiis praesentium voluptatum deleniti atque corrupti quos dolores Purpose: Launch and Learn Outcome: • At vero eos et accusamus et iusto odio dignissimos ducimus qui blanditiis • Ut enim ad minima veniam, quis nostrum • Quis autem vel eum iure reprehenderit qui in ea voluptate 20202019 Purpose: Release and Earn Outcome: • Et harum quidem rerum facilis est et expedita distinctio. • Nam libero tempore, cum soluta nobis est eligendi optio cumque nihil impedit quo minus id quod maxime • Itaque earum rerum hic tenetur a sapiente delectus, ut aut reiciendis voluptatibus Current Goals Flexible Directional Feature Feature Story Feature Feature Epic Epic Feature 13 • Continuity of purpose • Stakeholder collaboration • Prioritization & budgeting Roadmap
- 14. 3. Decide What Features to Build • Identify Features • Prioritize & Estimate
- 15. GOAL ACTIVITIES (FEATURES) TASKS (USER STORIES) Minimum Viable Product Or Earliest Usable Product CUSTOMER EXPERIENCE / WORKFLOW OPTIONALITY 15https://jpattonassociates.com/the-new-backlog/ Howwebuildourproductbacklog Story Map
- 16. How we prioritize our features Example of t-shirt sizes for job size being mapped to time Assign relative numbers to urgency and value (low to high) Consider implementing features with higher WSJF sooner Value * Urgency WSJF = Size 16 http://blackswanfarming.com/cost-of-delay-divided-by-duration/
- 18. 4. Flow the work • Discovery + Delivery • Interactive layers of planning, collaboration & feedback
- 19. Initial Ideas / Initiatives Prioritized for Implementation Steering Committee Program Team Demand management & alignment Implementation Go/No-Go Decision Analyzed & Refined Ready to Implement Epics / Features User Stories Delivery Teams Team 1 Team 2 What are the sources of Ideas? Epics / Feature flow Story flow 19
- 20. How we foster shared understanding of the boundaries of a user story …password that is not easy to crack Is there a maximum length constraint? Minimum of 8 characters Alphanumeric, mixed case, with at least one special character Repeating pattern (Less than 3 consecutive) foobar Invalid – Too short f00bargobble! Invalid – not mixed F00bargobble! 1AaaaaaaA! Invalid - repeating 1AaByzdbAxt! The case where… No number No letter No special character User Story under discussion Rules to satisfy story, or express other constraints about the story scope Concrete examples that illustrate a rule Questions about scenarios where we don’t know the right outcome Acceptance Criteria Acceptance Scenario 20https://cucumber.io/blog/bdd/example-mapping-introduction/ Example Map
- 21. Release Planning (<= 3 mths)Sprint Planning Retrospective Sprint Demo Daily Scrum Code Review Design SessionCore Team Tech Sync PO Sync Refinement Integrated Demo Product & Technical Discovery Inspect & Adapt Major Release Minor Release Major Release Minor Release Product & Technical Discovery Scrum of Scrums Product & Technical Discovery Minor Release Closed loop system of feedback and collaboration 21 Extended Team
- 22. Program Metrics “You can't manage what you can't measure.” 22
- 23. In Summary
- 24. Delivering the Right Product Requirements at the Right Time Planning Level Planning Frequency Planning Estimates Planning Precision Artifact(s) Product Planning Kickoff; updates as needed throughout project duration T-shirt size Relative size (Fibonacci) Hours Epics, Features Product Roadmap, Product Backlog Release Planning Each incremental bucket of value; rolling wave (2-3 months) Features, Stories Updated Product Backlog, Release Plan Sprint Planning Every 2 weeks Stories, Tasks Sprint Backlog Daily Scrum Daily Tasks Updated Sprint Backlog § Multi-level § Less upfront, but frequent § Just enough, Just in-time Interactive Layers of Planning 24
- 25. Same direction Clear priority Coordinated rhythm 25
- 26. Identify the Needs • What is the product vision & goals? •Understand user journey(s) •What are the success criteria? Find the Opportunities • How might we achieve identified product goals? •Create high-level actionable plan with current, near-term and directional time horizons Decide What to Build •Identify Features •Prioritize & Estimate Flow the Work •Interactive layers of planning, collaboration & feedback •Discovery + Delivery 1 2 3 4 26