Self-management has a shared purpose
A Scrum Team internally decides who does what, when and how. Those decisions support the product work within Scrum accountabilities and applicable constraints. Self-management does not mean that everyone follows an unrelated preference or that external requirements no longer matter. It changes where work decisions are made and how the team learns to coordinate them. When reviewing a case, look for who actually controls the decisions rather than the title attached to that person. An external dispatcher renamed as a coach still controls assignments if nothing about the decision process changes. A useful change makes internal decisions real and understandable.
Cross-functionality is a team capability
A cross-functional Scrum Team collectively has the skills needed to create value in each Sprint. It does not require every person to possess identical expertise. Different specialists can work together while avoiding a pattern in which nobody is responsible for the usable whole. Dependencies deserve inspection when they repeatedly prevent usable Increments. The Scrum Master can coach the team to examine its way of working and strengthen its collective capability. Pairing, sharing knowledge or reorganizing work can be useful options in a particular context; none is automatically the required answer to every team problem. Keep an intervention connected to the observed obstacle.
Worked example: a dependency between specialists
Fictional case: a data specialist completes changes that an interface specialist cannot integrate until the following week. Both report being busy, but the product rarely gains a usable Increment. First inspect the shared outcome rather than blaming either occupation. Ask how work selection, handoffs and verification create the delay. Coach the team to choose an improvement and observe whether it helps produce usable work. Do not solve the apparent reporting problem by giving each specialist a different quality boundary. Two individually completed fragments do not become a usable Increment merely because each person can point to a finished task.
Coach observations without overdiagnosing
Silence during a Retrospective can have several explanations: the question may be unclear, the format may be ineffective, members may need time, or conditions may discourage contribution. Silence alone proves neither excellent performance nor a definite psychological-safety diagnosis. The Scrum Master can explore respectfully and try a different approach while ensuring the event remains productive and timeboxed. Such techniques are contextual teaching examples, not a list mandated by the Scrum Guide. Use an observation to open an investigation. Avoid turning a plausible explanation into a certain claim before the supporting evidence exists.
Transfer check: test the boundary of coaching
Developers want a new Daily Scrum format. Would self-management mean accepting any format even if it only produces individual approval requests? No. Developers can choose techniques, but the event still serves progress inspection and adaptation toward the Sprint Goal. Coaching can clarify that purpose without assigning their next technical tasks. Next consider a manager who wants all assignment decisions to remain external. Explain the difference between a legitimate organizational constraint and replacing the team’s internal work decisions. In practice, record the observation, the constraint and a possible intervention; then compare the alternatives using the four linked questions rather than a memorized slogan.
A newly formed Scrum Team is told that a department manager must decide who performs each task and how to perform it. The team already understands its product objective and applicable constraints. Which change best supports Scrum self-management?
- A Scrum Team is self-managing: its members internally decide who does what, when and how. This does not remove product direction, quality obligations or the different Scrum accountabilities. The appropriate change is to allow internal decisions rather than preserve external task control under another title. Supporting the team may still require organizational coaching and clarity about legitimate constraints; self-management is not an absence of coordination.
Compare the other answer choices
Changing a title does not change the external control over decisions that should be made within the team.
Self-management operates with shared purpose and accountabilities; it is not unrelated individual work without a goal.
Value accountability does not make the Product Owner the dispatcher of every technical task or implementation method.
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