Module 05 of 10

Planning & Delivery

Lessons

About This Module

A healthy team still needs a plan. As a manager you are the person who turns a team's effort into work that actually ships, and who tells the rest of the company honestly when. Doing that well takes more than a deadline and good intentions.

You'll start with estimation and planning: why estimates go wrong, what they are good for, and how to plan without treating guesses as promises. From there the module looks at predictable delivery, including how flow, capacity and the difference between a roadmap and a release plan help you commit to less and finish more.

Once you can plan and deliver reliably, you'll be ready for the next module, Technical Strategy & Quality, which looks at how to keep the codebase healthy while the team keeps shipping.

Lessons

3 videos
01

Agile Estimating Explained: Story Points and Planning Poker (Mike Cohn)

Mike Cohn's conference talk on how agile teams estimate and plan, covering what makes a plan agile, why story points work, and how Planning Poker helps teams size work.

02

Estimating Software Delivery Time Doesn't Work: Allen Holub & Dave Farley

Two experienced engineers discuss why accurate delivery estimates are so hard to give, and what to do when you are still under pressure to provide dates.

03

Get the Elephant off the Road: Flow and Predictable Delivery

A conference talk that uses a traffic-jam metaphor to show why team flow matters, and how to move from estimation-driven planning to data-driven forecasting.