A civic 311-app team integrates once per PI, and each merge becomes a multi-day firefight. What should the Scrum Master/Team Coach coach as a flow practice?
Select an answer to reveal the explanation.
Short Explanation
Merging 311 code once a PI is like opening every hydrant on the same afternoon; the flood is the batch. Integrate small and often so conflicts stay tiny. Heroes and IP-only merges just schedule the firefight.
Full Explanation
Continuous integration is a flow practice that shrinks merge firefights. Integrating a civic 311-app once per PI turns each merge into a multi-day interrupt; frequent integration keeps quality feedback close to the change and protects ART flow. The Scrum Master/Team Coach should coach CI so infrequent-merge crises stop defining the team’s calendar.
Keeping one integration per PI so conflicts arrive in a single batch fails by concept: batching integration maximizes conflict cost. Integrating only on the IP iteration fails by concept by postponing integration risk and interrupting innovation/planning time with deferred firefights. Assigning one integration hero after every PI fails by concept because it creates a specialist bottleneck and leaves the team unskilled at keeping the mainline healthy.
Exam caveat: SAFe built-in quality and DevOps guidance treat CI as foundational to predictable flow; PI-end integration is a classic exam anti-pattern. CI includes automated verification, not merely merging branches without checks.
Operational check: establish at least daily integration to the mainline with automated checks for the 311 app, track merge conflict and integration-fix hours per iteration, and show the decline versus the old once-per-PI firefight.