8.1 Common Misconceptions & PSM I Traps
Key Takeaways
- The Scrum Master is accountable for the Scrum Team's effectiveness and is a true leader who serves — not a manager who assigns or tracks work.
- The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal — not a status report delivered to the Scrum Master or Product Owner.
- Only the Product Owner has the authority to cancel a Sprint, even when the request originates elsewhere.
- The 2020 Scrum Guide defines three accountabilities (not roles) inside one Scrum Team with no sub-teams or hierarchies.
- Scrum mandates no estimation technique — story points, hours, and t-shirt sizes are all optional choices the Developers make.
Why Misconceptions Decide This Exam
PSM I rarely fails candidates on facts they have never seen. It fails them on familiar workplace habits that contradict the 2020 Scrum Guide. The exam writers know that years of "agile-ish" practice teach people the wrong defaults: stand-ups as status meetings, the Scrum Master as a delivery manager, velocity as a productivity score. Every distractor below is something that sounds normal in a real office and is still wrong against the Guide.
Read each trap as a pair: the Myth (what most teams do or assume) and the Reality (the Guide's exact stance). On exam day, when an option matches a Myth, eliminate it even if it describes your own workplace. The Guide is only about 13 pages; the exam tests whether you internalised its model, not the messy hybrid most companies run. Distrust any option that adds a role, a meeting, an approval, or a phase that the Guide does not name.
The Core Myth ≠ Reality Table
| # | Myth (wrong answer pattern) | Reality (2020 Scrum Guide) | Why the wrong answer fails |
|---|---|---|---|
| 1 | The Scrum Master manages the team and assigns tasks. | The Scrum Master is accountable for the Scrum Team's effectiveness and is a true leader who serves. | The Guide never grants the Scrum Master authority over people or work; teams are self-managing. |
| 2 | The Daily Scrum is a status report to the Scrum Master/Product Owner. | The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. | It is owned by Developers; reporting upward is not its purpose. |
| 3 | Anyone (SM, stakeholders, management) can cancel a Sprint. | Only the Product Owner has the authority to cancel the Sprint. | Cancellation authority is exclusive and singular. |
| 4 | Scrum has roles: SM, PO, Dev Team. | Scrum has three accountabilities within one Scrum Team; there are no sub-teams or hierarchies. | "Roles" and a separate "Development Team" entity are pre-2020 framing. |
| 5 | Scrum requires story points / velocity. | Scrum mandates no estimation technique; forecasting tools like burn-downs are optional. | Any answer asserting a required estimation method is false. |
| 6 | The Product Owner can be a committee. | The Product Owner is one person, not a committee. | One person remains accountable even if work is delegated. |
| 7 | The Scrum Master decides Sprint length / how much work the team takes. | The Developers select how many items to pull into the Sprint through discussion with the Product Owner. | Capacity decisions belong to the people doing the work. |
| 8 | An Increment can ship even if it does not meet the Definition of Done. | Work cannot be considered part of an Increment unless it meets the Definition of Done. | "Done" is the quality gate for being an Increment at all. |
| 9 | Sprint Review is a sign-off gate before release. | The Sprint Review should never be considered a gate to releasing value; an Increment may be delivered before the Sprint ends. | Release timing is decoupled from the Review. |
| 10 | Product Backlog refinement is a mandatory Scrum event. | Refinement is an ongoing activity, not one of the five events. | Treating it as a fixed event misstates the framework. |
| 11 | A new Sprint waits for planning, approvals, or a gap. | A new Sprint starts immediately after the conclusion of the previous Sprint. | There is no buffer Sprint or hardening Sprint in Scrum. |
| 12 | The Sprint Goal is optional or written after the Sprint. | The Sprint Goal is created during Sprint Planning and added to the Sprint Backlog. | Every Sprint has a single Sprint Goal set at planning. |
| 13 | The Scrum Master must attend and run the Daily Scrum. | The Daily Scrum is for the Developers; the Scrum Master ensures it happens but Developers run it. | Ownership, not attendance, is the tested point. |
| 14 | Managers approve Developers' work assignments. | The Scrum Team is self-managing — they internally decide who does what, when, and how. | External assignment violates self-management. |
| 15 | Scrum only works for software. | The Scrum Team is responsible for all product-related activities; Scrum is a general framework for complex problems. | Domain-restriction answers contradict the definition. |
Exam tip: If an option uses manager vocabulary (assign, approve, report to, sign off, mandate), suspect it. The Guide's vocabulary is serve, enable, self-managing, inspect, adapt, accountable.
Subtle Traps That Catch Strong Candidates
- "The whole team is accountable" vs. a single accountability. The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint, yet the Product Owner alone is accountable for maximizing value and the Scrum Master alone for effectiveness. Watch which scope the question asks about.
- Self-managing ≠ unmanaged. Self-management means the team decides internally; it does not abolish the Definition of Done or organizational standards.
- Cross-functional ≠ everyone does everything. It means the team collectively has all skills needed each Sprint, not that each Developer is a generalist.
- Shorter Sprints reduce risk. The Guide says shorter Sprints generate more learning cycles and limit risk — a frequent "best answer" option.
- The Daily Scrum is not the only adaptation point. Developers may adjust the plan any time; an option claiming changes can only happen at the Daily Scrum is wrong because of the absolute.
- The Sprint Backlog can change during the Sprint. As more is learned, the Developers add, remove, or reorder work; only the Sprint Goal stays fixed while scope is renegotiated with the Product Owner.
- Scope can be renegotiated, the Goal cannot be diluted. If the Sprint Goal becomes obsolete, the Sprint may be cancelled — but everyday learning leads to scope adjustment, not goal abandonment.
- The Scrum Master serves three audiences. The Guide lists service to the Scrum Team, the Product Owner, and the organization — an answer that limits the Scrum Master to "just the team" is incomplete.
Mid-Sprint, a senior stakeholder tells the Scrum Master the market shifted and the Sprint Goal is now worthless, demanding the Sprint be stopped today. What is the correct response under the 2020 Scrum Guide?
A newly hired delivery manager reframes the Daily Scrum so each Developer reports yesterday's tasks to the Scrum Master, who then updates an executive dashboard. Which statement best identifies the problem?
Which of the following statements contradict the 2020 Scrum Guide? (Select all that apply.)
Select all that apply
An organization tells a coach that Scrum cannot be used for their hardware-and-services product because "Scrum is only for software development teams." Which response is consistent with the 2020 Scrum Guide?