Public-housing maintenance leadership wants AI-estimated story points treated as the team’s forecast. What should the SM/TC coach?
Select an answer to reveal the explanation.
Short Explanation
A housing work-order bot can guess hours the way a vending machine guesses your snack. That guess is not the team's forecast. Empiricism still lives in the people who did last PI's roofs and boilers.
Full Explanation
Public-housing maintenance leadership may want AI-estimated story points treated as the team's forecast, but the SM/TC should keep the team's empirical forecast; AI estimates are not a substitute for that conversation. A work-order bot can guess hours the way a vending machine guesses a snack—that guess is not the commitment of people who delivered last PI's roofs and boilers. Empiricism still lives in the Agile Team's inspection of prior delivery and current capacity.
Publishing AI points as the official PI forecast fails because it creates fake precision leadership will treat as fact. Averaging the model's points with last PI's velocity and freezing the result fails because blending invents a number nobody empirically owns. Asking the Product Owner to replace Planning Poker with the model's output fails because estimation and forecasting remain a team conversation, not a PO-run oracle.
Exam caveat: AI estimates can start a discussion; they cannot own the forecast. Operational check: allow model numbers only as optional input, run the housing team's empirical forecast conversation, publish the team's forecast—not the bot's—and coach leadership on why citizen-facing predictability comes from team empiricism.