Iterations
Understand how Tracker Boot uses delivery history to project upcoming work and Release timing.
An Iteration is a recurring planning and delivery cycle used to understand how work progresses over time.
Rather than committing a fixed set of Stories to a sprint, Tracker Boot uses the order of the Backlog, Story Point estimates, and the team’s historical Velocity to project how work may fall across upcoming Iterations.
As priorities change or the team’s delivery pace changes, these projections can change as well.
How Iterations work
Stories remain ordered by priority in the Backlog.
Feature and Design Stories are estimated using Story Points, which represent relative complexity rather than time.
As the team works, Stories move through the delivery workflow:
Started → Finished → Delivered → Accepted
When estimated Stories are completed and accepted, their Story Points contribute to the team’s delivery history.
Tracker Boot uses this history to understand how much work the team can typically complete in an Iteration.
Velocity
Velocity represents how many Story Points the team can typically deliver in an Iteration.
Tracker Boot calculates Velocity using the average accepted Story Points from the team’s most recent three completed Iterations.
For example, if the team accepted:
- Iteration 1: 18 points
- Iteration 2: 24 points
- Iteration 3: 21 points
the team’s Velocity would be:
(18 + 24 + 21) ÷ 3 = 21 points
This means the team has recently been delivering about 21 Story Points per Iteration.
Velocity is based on completed work, not planned work. Estimates alone do not create Velocity.
As the team completes more estimated Stories, Tracker Boot builds a more useful delivery history.
Projecting upcoming Iterations
Tracker Boot uses the team’s Velocity together with the estimated Stories in the Backlog to project upcoming Iterations.
For example, if the team’s Velocity is approximately 20 points, Tracker Boot uses that delivery capacity together with Backlog priority to estimate which Stories may fall into the next Iteration.
The following Stories then flow into later projected Iterations based on their Backlog order and remaining estimated points.
These Iterations are projections, not fixed commitments.
If Stories are reordered, estimates change, or the team’s Velocity changes, the projected Iterations can adjust accordingly.
This allows the team to keep the Backlog flexible while still having visibility into what may be delivered next.
Release Projection
Tracker Boot can also use Velocity and the remaining estimated work in the Backlog to estimate how long that work may take.
The basic relationship is:
Remaining estimated Story Points ÷ Velocity = projected number of Iterations
For example, if the Backlog contains 100 estimated points and the team’s Velocity is approximately 20 points per Iteration, the remaining work represents roughly five Iterations at the team’s recent delivery pace.
Tracker Boot can use this projection to estimate when upcoming work or Release milestones may be reached.
A Release Projection is not a guaranteed delivery date.
It can change when:
- Backlog priority changes
- Stories are added or removed
- Story Point estimates change
- Team Velocity changes
The goal is to give the team a realistic projection based on actual delivery history rather than a fixed long-term commitment.
Velocity and delivery consistency
Velocity shows the team’s recent delivery capacity.
A separate metric, Volatility, shows how consistently that capacity changes across recent Iterations.
Velocity is used to help project upcoming work and Release timing, while Volatility is used to understand how stable or variable the team’s recent delivery has been.
Detailed Volatility calculations and delivery analysis are covered in Iteration Insights & Reports.