Software Project Estimation & Agile Metrics

What you'll build

What you will be able to do

Each lab ends with a concrete result that you build yourself and the checker confirms, cell by cell.

• Turn eight sprints of Team Orca's history into a say/do ratio, an average velocity and a low/high velocity range for planning.
• Work out how many focus hours Team Orca really has in sprint 9 and turn them into a capacity forecast in story points.
• Turn the remaining Harbor 2.0 backlog and the velocity range into a number of sprints and a release date for the expected, worst and best case.
• Build the burndown data of sprint 9 (ideal line, actual remaining work, cumulative done) and chart the burndown.
• Measure the cycle time of 12 finished items, the 85th percentile, the weekly throughput, and use Little's law to find the average work in progress.
• Score eight Harbor features by cost of delay, divide by job size and rank them, so the backlog starts with the best value per sprint.
• Turn optimistic, most likely and pessimistic estimates for release 2.1 into PERT estimates, one shared buffer at 90% confidence and a number of sprints.
• Put a dollar figure on one Team Orca sprint, on one story point and on the rest of the Harbor 2.0 backlog.