LEARN. PRACTICE. GROW.Concept and mechanism
A file-reconciliation team shows every task as green although it cannot yet recover partially processed files. The dashboard describes activity but cannot establish whether the increment is usable. Decisions based on it may lead the business to announce a capability that does not yet exist. The Scrum Master should help the team expose actual state and use shared criteria. Commitment to a goal does not require hiding difficulty; openness enables adjustment while options remain.
Guided application
In the exercise, compare “development 100% complete” with “normal processing available; partial recovery still lacks evidence.” The second enables discussion of risk, remaining work, and options. Ask participants which observation could change their decision. If the team inspects weekly but may never adapt a choice, adding reports does not resolve the issue. Work with those setting the boundaries so learning can have practical consequences.
An operator identifies a duplicate file the demonstration did not cover. The team records the limitation and adapts work rather than treating feedback as a deviation from plan.
Common pitfalls
Confusing task completion percentages with a usable increment; inspecting without room to adapt.
Related topics: Self-management with clear accountabilities · Goals and artifacts that guide choices
Transparency enables decisions about actual state, including what remains unknown.
Reference: The Scrum Guide, November 2020 · PSM I; Scrum Guide November 2020; no public numbered exam revision