Introduction
- The Agile Release Planning workshop
- Planning, Not Plans
- Emerging
- Final Version
- About this book
- Warnings
Comments on the ‘no estimates’ idea
Why Agile Release Planning?
The Story Begins
- Next steps
- What Happened
- What Happened Next?
My Approach — Summary
- The People
- The Process
- Product Backlog Refinement
- Comments on initial Agile Release Planning
My Approach - The Details
The People
Vision
Product Backlog
- Roles
- User Story Workshop
Business Value
- Business Drivers
- Completing the Drivers
- Priority Poker
Effort
- Definition of Done
- Planning Poker
The R Factor
Ordering by R Factor
Risks, Dependencies, Learning, MMFS, Other
Completing the Plan
- Estimating Velocity
- Finishing the Plan
- Communicating the Plan
- The Fix-It Plan
- ‘Finalizing’ the Plan
The ‘OTHER’
- Other steps or activities we might add to the ARP Day
- I-A-D (Infrastructure, Architecture, Design)
Closing Up
- When is the Initial Release Planning completed?
- What do you have ‘in hand’ at the end?
The Real Value
Product Backlog Refinement
- What’s Next?
The Steering Committe (and the Team)
- My key point
Key Ideas
- Suggested, not Prescriptive
- About people and common sense
Reminder
Appendices
- The Agile Release Planning workshop
- FAQ
- Note on the Author
- Glossary