The PDCA cycle, or Plan-Do-Check-Adjust, is a cycle of continuous improvement that helps teams identify problems, make changes, and continually improve their processes. It is also known as the Deming cycle or the continuous improvement cycle.
In the context of Scrum, the PDCA cycle is recognized as a key element that underlies the framework's empirical nature. Scrum relies on inspection and adaptation, which aligns directly with the iterative steps of the PDCA approach. By repeatedly cycling through planning, execution, inspection, and adaptation, Scrum teams continuously refine their work processes, improve their collaboration, and enhance the quality of their product.
The Four Phases of PDCA and Their Relation to Scrum
The PDCA cycle consists of four distinct phases that are integral to driving continuous improvement. These phases map closely to various events and practices within the Scrum framework:
- Plan: This phase involves defining the problem, identifying potential solutions, and establishing a plan for action. In Scrum, this aligns with activities like Sprint Planning, where the team defines the Sprint Goal and plans the work for the upcoming Sprint. It also relates to Product Backlog Refinement, where upcoming work is understood and planned at a high level.
- Do: In this phase, the planned actions are implemented. Within Scrum, the Sprint itself is the "Do" phase. The Development Team works on the selected Product Backlog items to create an Increment. This is where the plans made during Sprint Planning are executed.
- Check: This phase involves inspecting the results of the "Do" phase and comparing them against the desired outcomes defined in the "Plan" phase. In Scrum, inspection happens during events like the Sprint Review, where the Increment is inspected and feedback is gathered, and the Sprint Retrospective, where the team inspects their process and teamwork. The Daily Scrum also serves as a daily checkpoint for inspecting progress towards the Sprint Goal.
- Adjust (or Act): Based on the findings from the "Check" phase, adjustments are made to improve the process, the product, or the plan. The Sprint Retrospective is the primary Scrum event for identifying improvements to the process. Actions decided in the Retrospective are then incorporated into the next Sprint's "Plan" and "Do" phases. Adjustments also happen continuously during the Sprint, for example, by adapting the Sprint Backlog based on the Daily Scrums.
Why is PDCA Important in Scrum?
The PDCA cycle reinforces Scrum's core principles of transparency, inspection, and adaptation. It provides a structured approach for teams to:
- Systematically identify areas for improvement in their process or product.
- Experiment with changes in a controlled manner.
- Evaluate the effectiveness of those changes.
- Implement successful changes and discard ineffective ones.
By embedding this cycle of continuous improvement, Scrum teams are empowered to become more effective, predictable, and sustainable over time, delivering greater value to stakeholders.
