How to Measure PI Progress with Nesma Easy Functional Sizing

A PI forecast is only useful if you can tell, sprint by sprint, whether you're actually on track to hit it. This guide picks up exactly where the forecast leaves off, using the same CityConnect case study and teams, and shows how to track real delivered functionality against a Program Increment commitment as it happens — not just at the end.

It walks through managing scope as Features get refined into user stories without losing the size they were forecast against, measuring progress after every completed sprint in function points rather than story points, and what to do when delivered functionality starts falling behind plan. Four worked visuals show how a team can get quietly buried by work that isn't building functionality at all, and why story points can mask that problem while function points expose it immediately.

This guide covers:

• Managing scope during refinement so a Feature's size survives its breakdown into stories

• Measuring real progress after every sprint against the original PI forecast

• What to do — and when to flag it — when delivered functionality falls behind expectations

• Why story points can hide the true impact on delivered functionality, and how function points reveal it

• A full worked example tracking CityConnect's PI, sprint by sprint, against the Low/Likely/High forecast

Part of the Nesma EFS series, which carries one consistent function-point measurement from a product's total functionality down to a single sprint, up to a full Program Increment forecast, and through to tracking that forecast to completion. Also available in the Complete Series bundle.