When release planning happens
This picture shows that release planning is not a one-time, upfront activity. Instead is an activity that occurs every sprint.
Resources
Related Content:
Blog
- Burn Charts for Communicating Progress Through a Scrum Release
- Fixed-Scope Release Planning in Scrum
- Fixed-Date Release Planning in Scrum
- How Long Should the Sprint Review Last?
- Stakeholders Missing at Sprint Reviews – Part Three: Simple Misunderstanding
- Stakeholders Missing at Sprint Reviews – Part Two: Too This and Too That
- Stakeholders Missing at Sprint Reviews – Part One: Nothing to See Here
- Surprising Stakeholders is Almost Never a Good Thing!
- How To Determine Sprint Start and End Days
- Changing the Definition of Done
- Scrum in Pictures: How to Interpret the Visual AGILExicon®
- Who Should Attend Scrum Meetings?
- The Math of Fixed-Scope Multi-team Release Planning
- It’s a Sprint Review Not a Sprint Demo!
- Scrum: First Establish a Firm Foundation
Chapters
Visual AGILExicon
- Scrum framework—Refinement
- Sprint review activity—refined
- When sprint retrospective happens
- Sprint review activity
- When sprint review happens
- When sprint execution happens
- When sprint planning happens
- Release-planning activity
- Incremental / provisional funding
- Envisioning is an ongoing activity
- Release line in product backlog
- Different levels of planning
- Scrum of scrums
- Development team responsibilities
- Product owner day in the life
- Definition of ready
- When grooming happens
- Product backlog (in context)
- Sprint skeleton
- Sprint review (in context)
- Potentially shippable product increment (in context)
- Scrum framework
- Scrum practices
- Release planning
- Sprint review