Your SlideShare is downloading. ×
The 5 Levels Planning in Agile
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

The 5 Levels Planning in Agile


Published on

​Agile is a philosophy for delivering solutions that embraces and promotes evolutionary change throughout the life-cycle of a product. Many teams and organizations have been using Agile to, deliver …

​Agile is a philosophy for delivering solutions that embraces and promotes evolutionary change throughout the life-cycle of a product. Many teams and organizations have been using Agile to, deliver software more timely, increase quality, and ultimately increase customer satisfaction.

These planning levels were originally described by Hubert Smits in the whitepaper "5 Levels of Agile Planning: From Enterprise Product Vision to Team Stand-up".

  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. The 5 Levels of Planning
  • 2. About Dimitri Ponomareff Agile Coach ● Finance: American Express, Charles Schwab, Morgan Stanley, Bank of America ● Healthcare: Mayo Clinic, Phoenix Children's Hospital, Wolters Kluwer ● Hospitality: Choice Hotels International, SkyTouch Technology ● Software: JDA Software Group, Apriva Mobile ● Security: LifeLock ● Energy: First Solar ● State of Arizona - First Things First, ADOT, ADE ● Insurance: AAA Insurance Facilitator of “The 7 Habits of Highly Effective People” Certifications ● Project Management Professional (PMP) ● Agile Certified Practitioner (PMI-ACP) ● Certified ScrumMaster (CSM) ● Certified Scrum Practitioner (CSP) IT Professional ● CIO - Concord Servicing Corporation Software ● Vice President Communications - PMI Phoenix ● Director of Web Technologies - I-ology
  • 3. The Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Source:
  • 4. Planning Process Vision Roadmap R1 R2 R3 Rn Release 1 SP1 Iteration 1 SP2 SP3 SPn ST1 ST2 ST3 STn Iteration n ST1 ST2 ST3 STn Story 1 T1 T2 T3 Tn Story n T1 T2 T3 Tn Release n SP1 SP2 SP3 SPn
  • 5. Let’s play Plinko...
  • 6. L1 - Vision ● Communication ● Elevator Pitch ● Voices of Why, What and How ● PDCA
  • 7. Project Management is all about communication People who want IT must communicate with people who can build IT.
  • 8. Elevator Pitch FOR (target customer) WHO (statement of the need or opportunity) THE (product name) IS A (product category) THAT (key benefit, compelling reason to buy) UNLIKE (primary competitive alternative) OUR PRODUCT (statement of primary differentiation) Source: Geoffrey Moore’s template from Crossing the Chasm
  • 9. Why, What & How ●WHY are we doing this? Voice of the stakeholder (Stakeholders) ●WHAT needs to be done? Voice of the user (Product Owner, Subject Matter Expert) ●HOW do we build it? Voice of the developer (Scrum Team)
  • 10. PDCA - Plan, Do, Check, Act PLAN DO ACT PDCA Cycle CHECK Continuous Improvements
  • 11. L2 - Roadmap ● What is a Roadmap ● External Facing Roadmap
  • 12. Roadmap ● a roadmap is a planned future, laid out in broad strokes ● intentions for the future given what we know and believe today - they are not commitments ● should be formulated by first understanding the target users, the market, and the underlying technologies ● a good product roadmap should invariably deliver the right products with the right features at the right time to the right customers
  • 13. Client Facing Roadmap
  • 14. L3-L5 Levels of planning Release Plan (months) Iteration Plan (weeks) Daily Plan (days) Product Backlog Sprint Backlog Stories Tasks AAcctitvivitiiteiess Activities
  • 15. L3 - Release Planning ● Product, Epics & Stories ● Feature Driven Development (FDD) ● Feature Breakdown Structure (FBS) ● Parking Lot Charts ● Stories and Acceptance Criteria ● Estimation ● Release Burndown
  • 16. Product, Epics & Stories Story Story Story Story Story Story Story Story Story Story Story Story Story Story Story Story Story Story Product Epics Stories
  • 17. Feature Driven Development (FDD)
  • 18. Alternative to Work Breakdown Structure (WBS) WBS or traditional projects Activity Functionality Analysis Design Coding Testing Feature Feature Feature Module Module Module Feature Breakdown Structure Functionality Activity Story Story Story Story Analysis Design Coding Testing Define the project plan in terms of what will be delivered rather than what work steps will be performed.
  • 19. Parking Lot Charts
  • 20. Story form As a < role > I can < activity > so that < business value > ● Role - represents who is performing the action. It should be a single person, not a department. It may be a system if that is what is initiating the activity. ● Activity – represents the action to be performed by the system. ● Business Value – represents the value to the business. Why is this story important?
  • 21. Acceptance criteria ● like stories it's written in simple language ● define the conditions of success/satisfaction ● provide clear story boundaries ● remove ambiguity by forcing the team to think through how a feature or piece of functionality will work from the user’s perspective ● checklist or template of things to consider for each story ○ list of impacted modules and/or documents ○ specific user tasks, business process or functions ● establish the basis for acceptance testing ○ steps to test the story (given-when-then scenarios) ○ type of testing (manual vs. automated)
  • 22. The Cone of Uncertainty
  • 23. Estimation tools: T-shirts, Points & Hours Cone of Uncertainty XS S M L XL 0 1 2 3 5 8 13 20 ? Hours
  • 24. Release planning ● Overall context and prioritization for a specific period of time ● Product Owner ○ Creates a goal for the release ○ Selects a number of user stories from the product backlog ○ Works with the team to decompose and estimate the user stories ● The outcome of the release planning process is ○ Release Data Sheet ○ Release Backlog ○ Release Burndown Chart
  • 25. L4 - Iteration Planning ● Iteration planning ceremony ● Iteration Burndown
  • 26. Iteration Planning Ceremony As a vacation planner, I can see photos of the hotels, so that ... 8 points Tasks Hours Code the middle tier 8 Code the user interface 4 Write test fixtures 4 Code the foo class 6 Update performance tests 4 ● Team selects stories from the product backlog they can commit to completing ● Sprint backlog is created ○ Tasks are identified and each is estimated in hours ○ Tasks and estimates are done collaboratively ● High-level design is considered
  • 27. Iteration Burndown
  • 28. L5 - Daily Stand Up ● Plan your day...
  • 29. Daily Planning Parameters ● Daily ● 15-minutes ● Stand-up ● Not for problem solving Three questions for each scrum team member 1. What did you do yesterday? 2. What will you do today? 3. Is anything in your way? These are not status for the Agile Project Manager, they are commitments in front of your peers
  • 30. Big Picture ● Scaled Agile Framework (SAFe) ● Agile Testing Framework (ATF) ● The 5 Levels of Planning in Agile
  • 31. SAFe
  • 32. Agile Testing Framework (ATF)
  • 33. The 5 Levels of Planning in Agile
  • 34. Agile Coaching, Staffing and Training. Learn more at
  • 35. PMI-ACP Agile Certified Practitioner Prep Workshop (3 days - 21 PDUs) Phoenix AZ Agile Exams will be included in your PMI-ACP Prep Workshop.
  • 36. Thank You
  • 37. Resources and References ● ● ● ● ● ● The 5 Levels of Planning: From Enterprise Product Vision to Team Stand-up by Hubert Smits ● Agile Estimating and Planning by Mike Cohn ● Agile Project Management with Scrum by Ken Schwaber ● Agile Retrospectives by Esther Derby and Diana Larsen ● Agile Software Development Ecosystems by Jim Highsmith ● Agile Software Development with Scrum by Ken Schwaber and Mike Beedle ● Scrum and The Enterprise by Ken Schwaber ● User Stories Applied for Agile Software Development by Mike Cohn
  • 38. This presentation was inspired by the work of many people and we have done our very best to attribute all authors of texts and images, and recognize any copyrights. If you think that anything in this presentation should be changed, added or removed, please contact us.