06The visible tip

Ask a Scrum-in-name-only team what Scrum is, and the answer usually comes down to three practices: a daily meeting, a sprint backlog and a demo at the end of the sprint. These are the visible tip of the framework. Most of what gives them meaning sits below the waterline.

The three practices that survive are the most visible ones, the practices a manager can observe from the outside. What tends to disappear is less visible and more demanding: the Product Goal and the Sprint Goal, a Definition of Done that actually constrains the work, continuous backlog refinement, an increment someone could really use, and the retrospective, the loop through which a team improves its own way of working.

This pattern is not random. Organisations kept the parts of Scrum that produce visibility for management and dropped the parts that produce learning and change.

The rituals lost their meaning because the commitments sank

Every Scrum event is an inspection point, and an inspection needs a reference. The 2020 Scrum Guide made this explicit by pairing each artifact with a commitment: the Product Backlog with the Product Goal, the Sprint Backlog with the Sprint Goal, and the Increment with the Definition of Done. Remove the commitment and the event has nothing to inspect. It falls back on the only thing left, which is reporting activity.

This is why so many people cannot explain the purpose of their daily meeting. Without a Sprint Goal, there is no purpose to find.

A real Sprint Goal is an increment that makes business sense to the people who will use the product, such as "a collection nurse can register a first-time donor and record the donation". The stories selected for the sprint are the steps that build it. The 2020 Guide makes the distinction explicit: the team commits to the Sprint Goal, while the selected stories are a forecast of how to reach it. A sprint succeeds when its goal is met, not when every story is ticked off. A goal that reads "finish stories 12, 15 and 18" describes activity, not an increment, and leaves the daily meeting with nothing to inspect.

Table 3 · The three surviving rituals, traced down to their purpose.

The 2020 revision of the Scrum Guide contains two telling corrections. It dropped the three standard daily questions (what I did yesterday, what I will do today, what is blocking me), which had turned the daily into individual status reporting. And it states that the Sprint Review is a working session that should not be limited to a presentation. The everyday word "demo" is itself a symptom: a review produces decisions, a demo produces approval.

The lower layers explain why the decay is cultural

The pillars rest on the values. Transparency requires openness and courage. In an organisation where bad news is punished, the daily and the review turn into theatre, and every indicator stays green until the release fails. Deming's principle of driving out fear applies directly: no amount of ceremony produces honest inspection in a climate of fear.

The values, in turn, rest on the foundations. If leadership still thinks in terms of a defined process, where the plan is executed and variance is controlled, the values look like soft extras and the pillars become reporting tools. The organisation ends up running Scrum on the assumptions of the predictive model while dropping the discipline that made the predictive model work. It gets the weaknesses of both and the strengths of neither.