Agile

ReleasePlanner

Plan and track software releases across multiple sprints. Manage features, dependencies, and forecast delivery dates.

Total Features

47 pts

4 features

Completion Rate

28%

Avg Velocity

36

pts per sprint

Sprints Needed

1

for 26 pts backlog

Releases

Version 2.0 Launch

v2.0.0

In Progress

Release Details

Features

Critical
Pts:
High
Pts:
High
Pts:
Medium
Pts:

Feature Status

Sprint Velocity

Guide

A Release Planner is an essential tool for agile teams to plan and track software releases across multiple sprints. It helps teams visualize what's being delivered, when, and how features fit together.

Understanding Release Planning

Release planning involves deciding which features to deliver in a specific timeframe. Unlike sprint planning (2-4 weeks), release planning looks at longer horizons (3-6 months) to coordinate larger initiatives.

Key Concepts

Release: A bundle of features delivered together. Has a target date and version number.

Feature: A user-facing capability with story points and priority. Can have dependencies on other features.

Sprint Capacity: How much work (in story points) a team can complete in one sprint.

Velocity: Average story points completed per sprint. Used to forecast release dates.

Feature Dependency: When one feature requires another to be completed first.

How to Use This Tool

  1. Create releases with target dates and version numbers
  2. Add features to each release with story points and priorities
  3. Define feature dependencies
  4. Set sprint capacity and velocity
  5. Assign features to sprints automatically or manually
  6. Track progress and adjust plans as needed

Glossary

Release
A version of the software shipped to customers. Contains multiple features delivered together.
Feature
A distinct capability delivered to the user. Has story points, priority, and status.
Story Points
A unit of measure for expressing the overall effort required to fully implement a product backlog item.
Velocity
The amount of work (in story points) a team completes during a sprint. Used for forecasting.
Sprint Capacity
The maximum amount of work a sprint team can complete, accounting for availability and holidays.
Feature Dependency
A relationship where one feature requires another feature to be completed first.
Release Window
The time period allocated for a specific release, typically aligned with business cycles.
Feature Freeze
A milestone where no new features are added to a release, only bug fixes are allowed.
Code Complete
A milestone where all coding is finished; only testing and stabilization remain.
Release Candidate (RC)
A version of the software that is complete and ready for final testing before release.