Stakeholders want story-point estimates for a hundred housing-portal ideas before anyone has refined them or discussed meaning with Developers. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
Asking "how big is it?" before "what is it?" is how you get confident numbers about fog. Estimates without a shared picture are decorative. The Product Owner gets the conversation first, then a forecast that might actually mean something.
Full Explanation
Sizing without shared understanding produces confident numbers about fog. When stakeholders want story-point estimates for a hundred housing-portal ideas before anyone has refined them or discussed meaning with Developers, the Product Owner should pair sizing with shared understanding and refuse precise estimates of unreined items. Demanding exact hours for every idea this week so the housing budget can lock invents false certainty for Finance and freezes learning. Using stakeholders’ T-shirt sizes as the Developers’ forecast misassigns estimation and skips the team understanding that makes forecasts useful. Skipping refinement and letting Sprint Planning invent meaning for the numbers later postpones the only work that makes estimates meaningful. Exam caveat: very coarse portfolio ranges can inform budgeting conversations, but they are not Sprint forecasts and must not be treated as commitments on PSPO II exams. Operational check: refine a thin slice of housing ideas with Developers first, size only what is understood, communicate uncertainty bands to budget staff, and refuse a hundred-point spreadsheet as a substitute for Product Backlog readiness on the civic housing portal. Prefer relative ordering and thin spikes over false precision when housing ideas are still ambiguous to the people who will build them.