Plan-review comments on a civic permitting workflow are written only after code is called complete, causing late rework. What should the Scrum Master/Team Coach coach the team to do?
Select an answer to reveal the explanation.
Short Explanation
Writing plan-review notes after the permit workflow is coded is like redlining the blueprint after the concrete is poured. Get examples and acceptance tests in first. That is shifting learning left, not adding another inspection week.
Full Explanation
Shifting learning left means agreeing examples and acceptance tests before building civic permitting workflows, so discovery happens when change is cheap. Comments after code is complete create late rework that interrupts flow. Final-only meetings and extra inspection weeks keep learning at the end. The Scrum Master/Team Coach should coach test-and-example-first collaboration with reviewers.