Standardizing without dogma in a regulated product group
Northwind Devices has six product teams: three use Scrum, two use Kanban for interrupt-driven support work, and one uses an XP-style approach with pair programming and test-driven development. The product group is regulated under ISO 13485, and audits require traceability from requirement to verification evidence. A new VP of Engineering says, “Agile means Scrum,” and wants one mandatory Agile playbook for all six teams by Q3. Team dashboards show different cadences, inconsistent definitions of done, and weak retrospectives in two Scrum teams. The Kanban teams handle roughly 40% unplanned support requests and have the shortest cycle time. The XP team has the lowest defect escape rate but does not run two-week sprints. You are the Agile coach asked to lead the playbook effort while preserving the VP’s confidence and the audit position.
1. The VP asks you to make Scrum mandatory for all six teams by Q3. Using an Agnostic Agile stance, how do you respond and what decision criteria do you propose?
Read the worked answer
Start by separating the goal from the framework. Ask what the VP needs: predictable delivery, audit evidence, faster customer feedback, or fewer defects. Those outcomes can be met by different practices. Build a decision matrix with criteria such as work type, interrupt rate, regulatory evidence, dependency load, team maturity, and cycle-time data. The support teams’ 40% unplanned work is evidence that a fixed two-week sprint may create batch delays; Kanban with explicit policies may fit better. The XP team’s low defect escape rate suggests retaining technical practices even if cadence changes. Propose a playbook with non-negotiable boundaries, such as traceability and a definition of done that includes verification, plus optional practices selected by context. Do not simply reject Scrum; offer Scrum where empirical planning and a stable cadence add value. Pilot the playbook with two teams, review evidence at Q3, and document why each team uses its chosen practices.
2. What belongs in the playbook as mandatory, what should remain team-owned, and how do you protect both compliance and empiricism?
Read the worked answer
Make mandatory only what the organization genuinely cannot vary: regulatory traceability, verification evidence, a definition of done that includes quality gates, an explicit review of outcomes, and a documented path for deviations. Keep team-owned the board design, estimation method, ceremony format, WIP limits, and how work is sliced, because these depend on context and should be inspected and adapted. Write the playbook as a living guide with decision records, not a rulebook. Map each mandatory item to audit evidence so compliance is demonstrable rather than ceremonial. Protect empiricism by requiring teams to review flow, quality, and customer feedback at a fixed cadence and to change practices based on evidence. Include an exception process: a team can use Kanban or XP practices if it shows how the mandatory boundaries are met. This prevents standardization from becoming ritual compliance and gives auditors a clear, consistent evidence trail.
3. A Kanban team is told to adopt Scrum next month. What do you do?
Read the worked answer
First, clarify the reason for the mandate. If the purpose is audit consistency or predictable planning, test whether Scrum is the only way to achieve it. Compare the team’s current flow metrics with the Scrum teams: cycle time, blocked time, support interrupt rate, and defect escape rate. Show the VP the likely cost of forcing a two-week cadence on a team with 40% unplanned support work, such as longer queues and hidden work. Propose a bounded experiment: keep Kanban flow and WIP limits, add a short planning cadence and a review of outcomes, and use the same definition of done and traceability evidence. Set a 6–8 week review with explicit success measures. If the VP still mandates Scrum, negotiate safeguards: protect support capacity, limit work in progress, and review the impact on cycle time. Document the decision and risks rather than silently resisting.