Agile Release Manager:
- Create a report or list in the tracker that filters epics by the field you use to designate the “minimally releasable product”—everything that absolutely must be in the next major version of the project—showing both:
- Negotiate a deadline by which the Release Planners will draft all of the epics desired for the version.
Notes: Remind them:
- How to label the epic as part of the MRP or an “Extra.”
- That only the “story statement” is required for this purpose, and only MRP epics.
- After the deadline, add any business requirement epics you think are missing.
- Schedule a meeting of the Release Planners and the Team Guides to revise the list, as soon as most are available after the deadline.
- If the team or set of teams has been through three Planning Releases, determine or update the “Epic Velocity”—the number of epics the program reliably delivers in a release.
Details: “Create a Version Backlog.”
Agile Release Manager, during the meeting:
- Show the Product Backlog filtered by “MRP.”
- If you have an epic velocity:
- Count the number of “MRP” epics.
- Divide the total by the epic velocity and round up to find the number of Planning Releases required to complete that amount of work.
- Otherwise, help attendees:
- Estimate the number of calendar months required to deliver that total number of epics, assuming “normal” problems and that the teams remain 100% on the current project.
- Divide the result by the number of months in your release cycle, and round up.
Example: For quarterly Planning Releases:
11 (months) ÷ 2 (months per release) = 5.5 (releases, rounded up to 6).
Details: “Estimate the Releases.”
Share this page