The traditional release plan asks a simple question: what should be built within a given timebox? While that defines the scope, it does not guarantee feasibility. Capacity planning extends the concept by asking whether the selected work can actually be delivered in the allotted period. By integrating data on team size, historical velocity, and other flow metrics, the capacity plan provides a reality check before commitments are made.
What capacity planning adds to a release plan
Unlike a basic release plan that merely lists the desired features, a capacity plan quantifies the effort required and matches it against the collective capability of the involved teams. It answers the crucial question, “Can we deliver this within the specified timebox?” The answer emerges from a comparison of estimated work size with the measured capacity of each team, allowing product managers to adjust scope, re-allocate resources, or extend timelines based on concrete data rather than gut feeling.
How Rally calculates team capacity
Inputs that drive the calculation
Rally gathers several data points to compute capacity. First, it records the number of teams and the size of each team in terms of available personnel. Next, it pulls the historical velocity of each team—how many story points they have traditionally completed per iteration. Additional flow metrics such as cycle time and throughput are also considered to fine-tune the estimate. By combining these inputs, Rally produces a capacity figure that reflects both the scale and the proven performance of the workforce.
Comparing capacity with work size
Once capacity numbers are available, the next step is to align them with the estimated size of the backlog items slated for the upcoming program increment (PI) or release. Rally presents a side-by-side view where the total capacity of all teams can be directly juxtaposed with the total effort required for the selected portfolio items. If the work size exceeds capacity, the tool highlights the gap, prompting stakeholders to prune scope, add resources, or re-schedule items to maintain realistic expectations.
Using the Capacity Planning page in practice
Experimenting with scenarios
The Capacity Planning page serves as a sandbox for exploring “what-if” situations without altering the underlying artifacts or execution data. Users can adjust team composition, modify historical velocity assumptions, or add and remove backlog items to see how each change influences overall feasibility. This flexibility enables product owners to test multiple execution scenarios, identify the most viable approach, and communicate the rationale behind decisions to stakeholders.
Transitioning to team-level planning
After a capacity plan is finalized and published, individual squads move to the Team Planning page to break down portfolio items into concrete user stories. Here, teams schedule stories into specific iterations, ensuring that the work fits within the capacity previously validated at the portfolio level. This two-tiered approach—first validating capacity at a high level, then detailing tasks at the team level—helps maintain alignment between strategic goals and day-to-day execution.
Learning resources and next steps
Rally offers two YouTube playlists that walk users through the capacity planning workflow. One series, presented by product manager Nate Bever, focuses on leveraging the Capacity Planning feature to its fullest. The other provides an end-to-end overview of Rally’s planning capabilities, suitable for both single-team projects and multi-product release trains. Watching these short videos equips teams with the knowledge needed to create realistic, data-driven plans for any timescale.
