The short-term-rental registry team ships slices quickly, but nobody can explain the Product Goal or PI Objectives. What is missing?
Select an answer to reveal the explanation.
Short Explanation
A rental-registry team that cannot name the Product Goal is a fast boat with no harbor. Speed without a shared why just piles up the wrong slips. High-performing teams can point at the same PI Objectives, then move.
Full Explanation
Shared purpose and alignment to Product Goal and PI Objectives matter more than throughput alone. A short-term-rental registry team that ships slices quickly but cannot explain those goals is optimizing motion without mission—risky for hosts, neighbors, and enforcement staff who need coherent civic outcomes. The Scrum Master/Team Coach should restore goal literacy and alignment conversations.
Raising story-point targets to prove purpose through speed fails by concept: speed without shared purpose is still misaligned. A dashboard of commits instead of goals fails by concept by substituting activity metrics for intent. Letting each developer pick a personal product goal fails by concept because fragmented goals destroy team alignment.
Exam caveat: SAFe high-performing teams connect daily work to Product and PI goals; throughput without that alignment is incomplete performance. Coaches facilitate understanding—they do not replace the Product Owner’s goal stewardship for the rental registry.
Operational check: review Product Goal and current PI Objectives in planning and syncs, map in-flight stories to those goals, remove or renegotiate orphan work, and spot-check that teammates can explain why a slice matters.