BC1-Stable Throughput

  2. /
  3. Basecamp 1
  4. /
  5. BC1-Stable Throughput

Why

​​​The Program Owner, Product Owner and Product Category Teams know how to stabilize demand so that the overall System of Delivery can make and meet commitments. The Delivery Teams are sprinting and continuing to improve. Releases are planned with capacity as input with higher confidence in the ability to make and meet commitments. Teams are focused on balancing capacity and demand, scheduling work to completion and getting discipline around flow.

How

Now that the Delivery Teams have a few sprints under their belts, we can understand both the capacity (the maximum amount of work the team can take on) and the velocity (how much work can be delivered in an iteration) of the teams. This information is what the Product Category Team will use Release Targeting and Product Line Team does Release Planning.

The backlog of work has been built up and Delivery Teams are able to have backlogs ready further out than the next Sprint. The number of Story Points is also stabilized and teams are tracking this and usually within a small margin each Sprint.

Success Criteria

  • 2 sprints of ready Backlog and a minimum of 3 sprints of data
  • The business value of Roadmap items is clearly understood by the Program Owner, Product Owner and Delivery Teams

Supporting Material 

Coaching Activities

 

Baseline Throughput, Velocity, and Capacity

Using at least 3 sprints of prior data, establish a baseline for Velocity and Throughput across the System of Delivery

 

 

Basecamp 1 Outcomes

Form Teams     |     Establish Flow of Work     |     Make & Meet Commitments   |     Improve the system     |     Stable Throughput     |     Road Map     |     Release Plan     |     90 Day Rolling Backlog