Transparency
· Implications: Scrum processes and artifacts must be transparent. In other words, it is necessary to make it easy for those involved to understand the situation.
· Examples: Artifacts and tools such as product backlogs, sprint backlogs, and burndown charts are published to give teams and stakeholders a clear understanding of the current project state and progress.
· Purpose: Reduce misunderstandings and ambiguity and support better decision-making by providing all stakeholders with the same understanding of project status.
Inspection
· Implications: Scrum teams regularly inspect their artifacts and processes to identify problems and areas for improvement.
· Specific Examples: Confirming deliverables during daily scrums and sprint reviews, reflecting on processes during sprint retrospectives, etc.
· Purpose: To efficiently develop high-quality products, evaluate intermediate results and processes, and make corrections and improvements as necessary.
Adaptation
· Meaning: Based on inspection results, quickly make necessary improvements and corrections to continuously optimize processes and products.
· Examples: working on improvements in sprint retrospectives, introducing new techniques and methods, changing priorities in the product backlog etc.
· Purpose: To respond to changing requirements and environments and maximize team productivity and product value.
When these three principles work well, Scrum teams can respond flexibly to change and efficiently develop high-quality products. It’s important to maintain the spirit of Scrum by constantly ensuring that there is a balance between transparency, inspection, and adaptation.
