What is Release Planning? How does it help in agile methodology?
The release planning is a collective effort of scrum master, product owner and delivery team in order to create a plan to deliver an increment to the product. It is done after every 2 to 3 months. It cannot lasts up to one year. Release planning is made up of short iterations.
Who is Involved?
Scrum Master − The scrum master acts as a facilitator for the agile delivery team.
Product Owner − The product owner represents the general view of the product backlog.
Agile Team − Agile delivery team provides insights on the technical feasibilities or any dependencies.
Stakeholders − Stakeholders like customers, program managers, subject matter experts act as advisers in release planning and make out decisions that are made around the release planning.
Prerequisites of Planning
The prerequisites of release planning are as follows −
Consists of ranked product backlog, managed by the Product Owner. Generally five to ten features are taken into consideration where the product owner feels that it can be included in a release
Every software project, whether a minor feature or new product launch, includes lots of inputs. So, team's input about capabilities, known velocity or about any technical challenge that need to be considered.
Market and Business objective
Acknowledgement whether new product backlog items are needed
The list of materials required for release planning is as follows −
Posted agenda, purpose
Flip charts, whiteboards, markers
Projector, way to share computers having data/tools required during planning meeting
The list of data required to do release planning is as follows −
Need previous iterations or release planning results
Get feedback from various stakeholders on product, market conditions, and deadlines
Need action plans of previous releases / iterations
Features or any defects are taken into consideration.
Velocity from previous releases/ estimates.
Organizational and personal calendars
Inputs from other teams and subject matter experts to manage any dependencies
The output of a release planning can be the following −
Issues, concerns, dependencies, and assumptions which are to be monitored
Suggestions to improve future release plannings
The agenda of a release planning can be −
Opening ceremony − Welcome message, review purpose and agenda, organizing tools and introduction to business sponsors.
Product Vision, Roadmap − Show the large picture of the product.
Review previous releases – need discussion on any item which can impact the plan.
Release name / theme − Inspect the current status of roadmap themes and do the required adjustments, if any.
Velocity − Present the velocity for the current release and of previous releases.
Release schedule − Review key milestones and decision on time boxes for release and iterations within release.
Issues and concerns − Check any concerns or issue and record them.
Review and Update the Definition of Done − Review the definition of done and make necessary changes based on technology, skill, or changes in team members since the last iteration / release.
Stories and items to be considered – need to present the user stories and features from the product backlog that is to be considered for scheduling in the current release.
Determine sizing values − If in case the velocity is unknown, then you need to plan the sizing values that is to be used in the release planning.
Coarse the size of stories − The delivery team constitutes the definite size of the stories under consideration and these stories can split into multiple iterations if a story is said to be too large. The product owner and the subject matter experts clarify the doubts, elaborate the acceptance criteria, and make proper story splits. The scrum master facilitates the collaboration.
Map stories to iterations − The delivery team and the product owner move the stories/defects in the iterations based on the size and velocity. The scrum master facilitates the collaboration.
New concerns or issues − Check any new issues concerned based on previous experience and record the same.
Dependencies and assumptions − Check any dependencies/assumptions planned during the release planning.
Commit − The scrum master is the head for calling, so he calls for the planning. If the delivery team and Product owner gets satisfied it as the best plan, then commit to move to the next level of planning, that is, iteration planning.
Communication and logistics planning − Review/Update the communication and logistics planning for the release.
Parking lot − Process parking lot means all items should be either resolved or set as action items.
Distribute Action items and action plans − Distribute the action items among their owners, process the action plan.
Retrospect −Get feedback from participants to make the meeting successful.