Embed Size (px)
Citation preview
Step by Step
Release Planning
Share Vision & Roadmap
Product Owner
Team
Scrum Mater
Business, SME & Architect
Output
Release planning creates a common vision about what need to be delivered & when in terms of commitment to a product value increment.
StepsInput
Agenda, Meeting Rooms, Travel, Tools, stationeries
Plan Meeting & Logistic
Product Backlog
Vision & Release Goal
Velocity & availability
Business & architect inputs
Release Theme, Schedule, Iterations
Dependencies, Assumptions, Adjustments
Release Schedule
Release backlog
Risk, issues, Assumptions & Dependencies
Feedback
Definition of done, Sizing, Story Mapping, Review
Commit, Action plan, Retrospect, Close
Plan Meeting & Logistic
Product Owner
Team
Scrum Mater
Business, SME & Architect
Next
•Release planning meeting is attended by product owner, business sponsor, delivery team, facilitator like SME & architect, Scrum master and all the stakeholders impacted by the release.
•Scrum Master facilitates the release planning meeting.
StepInput
Agenda, Meeting Rooms, Travel, Tools, stationeries
Plan Meeting & Logistic•Create an Agenda•Book meeting rooms•Send invite•Plan travel & logistic•White Board, maker•Sticky notes, flip chart•Computer & laptops
Product Backlog
Vision & Release Goal
Release Meeting Starts•Welcome & review agenda•Purpose of meeting•Business sponsor’s introduction•Sponsor speaks
Vision, Roadmap & Theme
Vision & Roadmap•Share vision & larger picture•Roadmap to the goal•How & where this release fits in roadmap
Product Owner
Team
Scrum Mater
Business, SME & Architect
Next
•Shares vision, larger picture, discuss roadmap & release goal. Product owner owns this activity.
•Release theme, schedule and number of iterations are derived through collaboration
StepsInput
Meeting Rooms, Tools, stationeries
Product Backlog Vision & Release Goal
Velocity & availability
Business & architect inputsRelease Theme, Schedule, Iterations•Decide release name & theme•Present velocity•Review key milestones•Discuss time-boxes & number of iterations
•Definition of done •Product backlog sizing •Story Mapping
•Dependencies, •Assumptions, •Adjustments
Definition of Done, Story mapping
Product Owner
Team
Scrum Mater
Business, SME & Architect
Next
•This is the most critical step of release planning which requires active participation of all the participants
•Team should resolve most of their ambiguities, queries around the backlog item, sizing and dependencies
StepsInput
Meeting Rooms, Tools, stationeries
Product Backlog
Business & architect inputs
Vision & Release Goal Dependencies, Assumptions, Adjustments•Check dependencies •Review assumptions•Make necessary adjustments
•Commit release plan •Create action plan, •Retrospect the meeting
Definition of done, Sizing, Story Mapping, Review•Review & updated definition of done•Size product backlog items•Map stories to iterations•Review issues
Commit Release Plan
Product Owner
Team
Scrum Mater
Business, SME & Architect
Output
Release plan is committed once delivery team and product owner agrees the plan with its backlog items and schedule.
StepsInput
Meeting Rooms, Tools, stationeries
Product Backlog Vision & Release Goal
Velocity & availability
Business & architect inputs
Release Schedule
Release backlog
Risk, issues, Assumptions & Dependencies
Feedback
Commit, Action plan, Retrospect, Close•Commit release backlog•Commit release schedule•Derive action plan•Retrospect release planning meeting•Close the meeting
DevOps & Scaled Agile
Release planning in DevOps practice is more or less similar to extreme programming release planning with
smaller sprint durations.
SAFe
Release planning in SAFe is program increment planning with projects being part of a program. Program increments are delivered by agile release train(s). A Project executed using Kanban or XP scrum methodology.
