Transparency
• Meaning: Scrum processes and artifacts must be transparent. In other words, their status must be easy for stakeholders to understand.
• Example: Artifacts and tools such as the Product Backlog, Sprint Backlog, and burndown charts are made available so the team and stakeholders can clearly understand the project's current status and progress.
• Purpose: Giving every stakeholder the same understanding of project status reduces misunderstandings and ambiguity and supports appropriate decision-making.
Inspection
• Meaning: The Scrum Team regularly inspects artifacts and processes to identify problems and areas for improvement.
• Example: Examples include reviewing artifacts in the Daily Scrum and Sprint Review, and reflecting on processes in the Sprint Retrospective.
• Purpose: To develop high-quality products efficiently, interim results and processes are assessed and corrected or improved as necessary.
Adaptation
• Meaning: Based on inspection results, necessary improvements and corrections are made quickly to optimize processes and products continuously.
• Example: Examples include acting on improvements identified in the Sprint Retrospective, introducing new technologies or methods, and changing Product Backlog priorities.
• Purpose: To respond to changing requirements and environments and maximize team productivity and product value.
When these 3 principles function effectively, the Scrum Team can respond flexibly to change and develop high-quality products efficiently. It is important to continually check that transparency, inspection, and adaptation remain balanced and to preserve the spirit of Scrum.
