the 5 levels planning in agile
DESCRIPTION
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".TRANSCRIPT
About Dimitri PonomareffAgile Coach
● American Express● Charles Schwab● JP Morgan Chase● Bank of America● LifeLock● First Solar● Mayo Clinic● CSAA Insurance● Phoenix Children's Hospital● Choice Hotels International● State of Arizona - First Things First, ADOT, ADE● Wolters Kluwer ● Apriva● JDA Software Group
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 Software● Vice President Communications - PMI Phoenix● Director of Web Technologies - I-ology
www.torak.com
www.linkedin.com/in/dimka5
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: www.agilemanifesto.org
www.torak.com
Planning ProcessVision
Roadmap
R1 R2 R3 Rn
Release 1
SP1
Iteration 1
ST1 STnST3ST2
Iteration n
ST1 STnST3ST2
Story 1
T1 TnT3T2
Story n
T1 TnT3T2
SPnSP3SP2
Release n
SP1 SPnSP3SP2
www.torak.com
L1 - Vision
● Communication● Elevator Pitch● Voices of Why, What and How● PDCA
www.torak.com
Project Management is all about communication
People who want IT must communicate with people who can build IT.
www.torak.com
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
www.torak.com
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)
www.torak.com
PDCA - Plan, Do, Check, Act
ACT
PLAN DO
PDCACycle
CHECK
Continuous Improvements
www.torak.com
L2 - Roadmap
● What is a Roadmap● External Facing Roadmap
www.torak.com
Roadmap
www.torak.com
● 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
L3-L5 Levels of planning
Release Plan (months)
Iteration Plan (weeks)
Daily Plan (days)
Product Backlog
Sprint Backlog
Stories
Tasks
ActivitiesActivitiesActivities
www.torak.com
L3 - Release Planning
● Product, Epics & Stories● Feature Driven Development (FDD)● Feature Breakdown Structure (FBS)● Parking Lot Charts● Stories and Acceptance Criteria● Estimation● Release Burndown
www.torak.com
Product, Epics & Stories
Story Story Story
Story Story Story
Story Story Story
Story Story Story
Story Story Story
Story Story Story
Product
Epics
Stories
www.torak.com
Alternative to Work Breakdown Structure (WBS)
Activity
Functionality
Analysis Design Coding Testing
Feature Feature Feature Module Module Module
WBS or traditional projects
Functionality
Activity
Story Story Story Story
Analysis Design Coding
Feature Breakdown Structure
Testing
Define the project plan in terms of what will be delivered rather than what work steps will be performed.
www.torak.com
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?
www.torak.com
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)
www.torak.com
Estimation tools: T-shirts, Points & Hours
Cone of Uncertainty
13853210 20 ?
Hours
XS S XLLM
www.torak.com
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
www.torak.com
L4 - Iteration Planning
● Iteration planning ceremony● Iteration Burndown
www.torak.com
Iteration Planning Ceremony
● 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
As a vacation planner, I can see photos of the hotels, so that ...
8 points
Tasks Hours
Code the middle tier 8Code the user interface 4
Write test fixtures 4
Code the foo class 6
Update performance tests 4
www.torak.com
Daily Planning
Parameters● Daily● 15-minutes● Stand-up● Not for problem solving
Three questions for each scrum team member1. 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
www.torak.com
Big Picture
● Scaled Agile Framework (SAFe)● Agile Testing Framework (ATF)● The 5 Levels of Planning in Agile
www.torak.com
www.torak.com
Agile Testing Framework (ATF)
www.torak.com
PMI-ACP
Agile Certified Practitioner Prep Workshop (3 days - 21 PDUs)
Phoenix AZ
Agile Exams will be included in your PMI-ACP Prep Workshop.
Resources and References● www.scrum.org● www.scrumalliance.org ● www.scaledagileframework.com ● www.mountaingoatsoftware.com ● www.agiletestingframework.com
● 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
www.torak.com
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.
http://creativecommons.org/licenses/by-nc-nd/3.0/
www.torak.com