What is Scrum Release Planning

What is Scrum Release Planning?

5-6 minutes

The goal of Release Planning is to when various sets of usable functionality or products will be delivered to the customer which to enable the Scrum Team to have an overview of the releases and delivery schedule for the product being developed. With a longer-term plan, the team can align with the expectations of the Product Owner and relevant the project sponsor and provides us some answers for questions such as:

• When will we be done
• Which features can I get by the end of the year
• How much will this cost
• Discover critical dates and milestones
• Coordinate development plans of the dependent systems.
• Help us to balance business value and overall quality against the constraints of scope, schedule, and budget

Patterns of Release Planning

Many organizations have its own cadence regarding release of products to its customers. Some choose to release every sprint . Others group the results of multiple sprints into one release as shown in the Figure below. Still others release as soon as each feature is completed, a practice often referred to as continuous deployment or continuous delivery.

Definition of Ready

A release plan is a roadmap that reflects expectations about which features will be implemented and when they are completed. Depending on the development strategy, it may either be driven by functionality, in which the objective is to deliver a release once a predetermined set of functionality has been developed; or the planning may be driven by date, in which the release happens on a predefined check point. If the project is feature-driven, the sum of all features within in a release can be divided by the expected velocity .This will then result in the number of sprints needed to complete the requested functionality.

Do you need an “upfront” Release Planning?

Release planning is a controversial topic in Agile . While we are often asked to provide some up-front estimation on cost and time in the business world, Scrum does not suggest up-front planning. Here are some arguments of not have a release planning:

• The customer sees no value in Release Planning and often considered to be a kind of waste
• The rapidity of change in many areas substantiates the “You Aren’t Going to Need It”(YAGNI) principle implies that the up-front release planning should not be required
• Thus, the only value from the release plan could be just simply consists of the initial date and budget and nothing more than that

Why We Need A Release Planning Anyway?

Although, the actual dates of engagement in the agile world may have less precision as far as committed targets. However, a general delivery roadmap of releases could establish trust and expectation between your team and other stakeholders. Furthermore, Releases should take into account all the additional work that must be accomplished, such as updating the public website and training the customer support team. Here is the main reasons for having a Release planning in Scrum your project:

A communication device

Planning tool

Validates value versus cost

Sets the overall context

Release Planning Example:

Release Planning vary in their format. I provided an examples here for both feature /data driven:

Release planning example

If the project is date-driven we can simply multiply the velocity by the number of Sprints and we’ll get the total work that can be completed within the given timeline.