Skip to content
BENIBIX Learn

Release Planning

Business📋 Agile DeliveryPlanning

Also known as Release Plan, Agile Release Planning

Deciding what goes in a release and about when it ships. It is updated each sprint.

Think of it like

It is like planning a road trip by how far you drive each day. Then you can guess the day you get there.

Example

A release holds 120 points of stories. The team finishes about 20 points a sprint, so it plans for six two-week sprints, about three months.

Why it matters

It gives the business a date range it can plan around. It also shows early when the scope will not fit.

Definition

Release planning is deciding what goes into a release and about when it will ship. The team adds up the size of the items in the release. It divides that by its velocity to get a number of sprints. If the date is fixed, the scope bends, and the other way round. The plan is checked again every sprint as things change.
Each slice across the map is one release. The plan says which slice ships first, and about when.

Common mistake

Treating the first release plan as a promise. It is a forecast, and it should change as the team learns.

Key takeaways

  1. 1
    Size over pace. Total points divided by velocity gives sprints.
  2. 2
    Fix one side. Hold the date or the scope, not both.
  3. 3
    Plan again each sprint. New facts update the forecast.

Learn it properly