From an observation to a useful decision
Scrum addresses complex problems through experience and observation rather than assuming that a detailed initial prediction is certain. Transparency, inspection and adaptation work together. A visible artifact gives people something meaningful to inspect; inspection helps reveal whether the current understanding still fits; adaptation changes a decision or plan when the evidence calls for it. Holding many meetings is not enough if the information being inspected conceals unfinished work. Likewise, collecting accurate observations without reconsidering a disproven plan does not complete the learning process. Start by naming the decision and asking what evidence could reasonably inform it.
Transparency includes limits and uncertainty
A useful representation should make relevant work and its actual state understandable to the people performing and receiving that work. A dashboard can look precise while obscuring an important condition. For example, a completion total may include items that have not met the Definition of Done. The number is then a poor basis for interpreting delivered value. Explain how the measure is produced, what it includes and what remains uncertain. Transparency does not require every detail to be distributed to everyone without regard to context; it requires a sufficiently shared understanding for the decisions people need to make.
Worked example: a misleading success trend
Fictional case: a museum team reports a rising number of completed booking improvements. Staff still cannot use several changes because required integration checks have not finished. The museum uses the trend to decide whether to expand the rollout. First, identify the mismatch between the reported label and usable work. Second, make the actual state and missing evidence visible. Third, inspect what the corrected picture means for the rollout, then adapt the next step. Adding a second weekly reporting meeting without correcting the data would repeat the same problem more often. A beautiful chart cannot compensate for a misleading completion boundary.
Values shape the conversation around evidence
Scrum names commitment, focus, openness, respect and courage. These values support the way people work together; they are not a diagnostic quiz in which every workplace symptom identifies exactly one value. Reporting a failed assumption may involve courage, openness and respect at the same time. Commitment does not mean defending a prediction after evidence contradicts it. Respect does not require concealing a problem to protect a colleague from all discomfort. Discuss the observation and its implications clearly, acknowledge uncertainty and avoid turning the conversation into a search for blame. Several values can guide the same constructive action.
Transfer check: change the evidence, then the plan
Try this case: a small usable reminder feature is delivered, but the team has only two days of customer observations. Should it declare the entire product direction proven? No. The observations may inform a next decision, but the time period and the people observed limit the conclusion. Choose what to investigate next and explain why. Conversely, ignoring the observations because they are not perfect would also lose a learning opportunity. Use the four practice tasks to distinguish misleading input, a hidden problem, a bounded learning step and a difficult evidence conversation. Record the reason for a choice before looking at its explanation.
A delivery team holds frequent inspection meetings, but its dashboard counts work as complete before the required quality checks finish. Stakeholders use that dashboard to choose the next investment. Which action most directly repairs the empirical decision process?
- Inspection depends on a sufficiently transparent account of the work. A completion figure that includes work failing the quality boundary can make a frequent meeting produce a misleading conclusion. Make the actual state and its limitations visible, then inspect and adapt decisions using that evidence. Historical comparisons can be explained rather than protected by preserving a misleading definition. The objective is not perfect information; it is an honest basis for an appropriate next decision.
Compare the other answer choices
Increasing meeting frequency does not correct misleading input; the same incomplete work would still appear finished.
Comparable numbers are not useful if their meaning conceals unfinished quality work. Explain the changed interpretation transparently.
Empirical decisions use observed evidence and acknowledged uncertainty; waiting for certainty or following an obsolete plan avoids adaptation.
Try it, then explain it.
Complete a short set without looking at the example. After each answer, explain which evidence or rule supports your decision and why the alternatives do not fit.
Sources & authorship
Original OpenExam explanations and examples. References support the concepts; they are not the source of copied questions. Independent educator review is pending.
The Scrum Guide — November 2020