Task: Release Planning
At the beginning of a project the team will create a high-level release plan
Disciplines: Scrum Activities
Purpose
To level-set expectations (internal and external) and to proactively uncover needs and dependencies
Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory:
    Optional:
    • None
    Main Description

    At the beginning of a project the team will create a high-level release plan.  The team cannot possibly know everything up front so a detailed plan is not necessary.  The release plan should address:

    • The number and duration of the sprints
    • How many people or teams should be on this project
    • The number of releases
    • The value delivered in each release
    • The ship date for the releases

    Key inputs to release planning are:

    • The prioritized Product Backlong
    • The estimated velocity
    • Any hard and fast to-market dates the Product Owner must satisfy