Facilitated by TJ Badru.

Shipping one feature is hard. Shipping ten features across multiple sprints, on a date stakeholders are already counting on, is a different skill entirely. This session covers how to plan releases, forecast realistically, and communicate progress without over-promising.

We’ll cover release planning fundamentals, forecasting techniques based on historical velocity and throughput, and how to communicate uncertainty to stakeholders without sounding like you don’t have a plan.

Learning Objectives

Understand the difference between sprint planning and release planning.
Learn forecasting techniques that use real historical data instead of optimism.
Practice communicating a release forecast, including its uncertainty, to stakeholders.
Build a release plan that survives contact with reality.

Who Should Attend?

Product Owners, Scrum Masters, and Project/Program Managers responsible for communicating delivery timelines to stakeholders.

Key Takeaways

A release planning template adaptable to any team.
Forecasting techniques grounded in actual team data.
Language for communicating delivery dates honestly, with built-in uncertainty.