Tree-inventory developers spend the iteration polishing internal code structure while residents still cannot use the public tree map named in the PI Objectives. What should the SM/TC emphasize?
Select an answer to reveal the explanation.
Short Explanation
Polishing the filing cabinet while the park map stays locked in the drawer is local craft, not a mission. The PI already named a public tree map for residents. Point the team at that shared outcome, then improve the internals on the way.
Full Explanation
High-performing teams align to a common mission and PI Objectives rather than optimizing local technical beauty. Internal refactoring can support Built-in Quality, but not when it displaces the resident-facing increment the ART committed to. The SM/TC should reconnect the tree-inventory team to those outcomes. Protecting the refactor as the only craft measure, hiding the map from objectives, or rewarding module elegance without delivery all license local optimization over alignment.