The Release Plan forecasts future velocity based on historical data. It’s created by the Product Owner who usually waits 2-3 sprints until some historical data has been generated. The input is the total effort in the product backlog, the team’s availability, sprint length and velocity. From this you can determine how many sprints are needed in total to complete the backlog. The Product Owner uses this information to update the backlog items so they will get assigned to Sprints according to priority, capacity and building shippable increments.
The Product Owner updates the Release Plan at the end of each Sprint to include current velocity, changes in capacity or capability, and changes in the Product Backlog. The data can also be shown as a Release Burndown Chart plotting the effort left in the Product Backlog vs time.
The Release Plan should show:
Sprint numbers
Start and End Dates
Velocity (guess)
Comments
Tags: scrumNo Comments
0 responses so far ↓
There are no comments yet...Kick things off by filling out the form below.