Common Scrum Myths and Misconceptions (and What the Scrum Guide Really Says)
Scrum is easy to describe and hard to do well, and that gap breeds myths. Many of them are repeated by well-meaning managers, job adverts and even training slides. Part of a Scrum Master's job is to gently correct these misunderstandings, so it helps to know them thoroughly. Below are twelve of the most common, with what actually applies according to the Scrum Guide (2020 edition, the current edition at the time of writing) and common practice.
Myth 1: The Scrum Master is the team's manager or project manager
Reality: The Scrum Master is accountable for the team's effectiveness and for establishing Scrum, as a true leader who serves the team and the organisation. They do not assign tasks, approve work or manage people. See Scrum Master vs Project Manager vs Product Owner.
Myth 2: Scrum means no planning and no documentation
Reality: Scrum has planning at several levels: a Product Goal, a Product Backlog, Sprint Planning and a Sprint Goal. Documentation is produced when it adds value. What Scrum rejects is planning that pretends to know the future in detail.
Myth 3: The Sprint Backlog is fixed once Sprint Planning ends
Reality: The Sprint Goal is the commitment. The Sprint Backlog is a plan that the Developers update throughout the Sprint as they learn more. Scope can be clarified and renegotiated with the Product Owner without endangering the Sprint Goal.
Myth 4: The Product Owner writes every user story
Reality: The Product Owner is accountable for the Product Backlog, including its clarity and ordering, but may delegate the work of writing items. Good stories usually emerge from collaboration between the Product Owner, Developers and stakeholders. See User Stories in Scrum.
Myth 5: The Daily Scrum is a status meeting for the Scrum Master
Reality: The Daily Scrum is for the Developers to inspect progress toward the Sprint Goal and adapt the plan for the next 24 hours. The Scrum Master ensures the event happens and is productive but need not attend, and nobody should be "reporting" to the Scrum Master. See Daily Scrum Explained.
Myth 6: The Daily Scrum must use the "three questions"
Reality: The three questions (what I did yesterday, what I'll do today, any blockers) were removed from the Scrum Guide in 2020 and are one optional technique. Teams may use any structure that focuses on the Sprint Goal.
Myth 7: A Sprint can be extended if we are not finished
Reality: Sprints have fixed length. If work is not finished, it returns to the Product Backlog and is re-evaluated. Extending a Sprint defeats the purpose of regular inspection and adaptation, and hides the team's real capacity.
Myth 8: Velocity measures productivity and should be compared across teams
Reality: Velocity is a planning aid for one team and is based on that team's own story point scale. Comparing velocities across teams is meaningless and encourages inflation of estimates. For better measures, see Scrum Metrics Explained.
Myth 9: The Scrum Guide requires story points, user stories and a burndown chart
Reality: The Scrum Guide mentions none of them as mandatory. They are popular practices. Teams may use other ways to size or visualise work as long as they remain consistent with Scrum's purpose.
Myth 10: Scrum only works for software
Reality: Scrum was designed for complex work in general. Marketing, HR, research and operations teams use it with adaptations. See Scrum Beyond Software Teams.
Myth 11: The Scrum Master must be technical, or must be a former project manager
Reality: Technical understanding helps, but the core skills are facilitation, coaching, teaching and conflict navigation. Good Scrum Masters come from varied backgrounds: development, testing, business analysis, project management, HR and operations.
Myth 12: Once we have the events and roles, we are "doing Scrum"
Reality: Scrum is a framework, and its purpose is to enable empirical process control through transparency, inspection and adaptation. If the Sprint Review never changes the backlog and the Retrospective never changes the process, the team is performing rituals, not doing Scrum. Read Scrum Master Anti-Patterns for the common failure modes.
How to Correct a Myth Without Being a Pedant
- Ask first. "What problem are you hoping that practice will solve?" often reveals the real need.
- Point to the purpose, not just the rule. People accept the reason more readily than a quote.
- Offer an experiment. "Let's try it for two Sprints and compare."
- Keep the tone curious. Most myths come from earlier experience with poor implementations, not from bad faith.
- Many "rules" people quote, such as the three questions or story points, are practices, not requirements.
- Scrum Masters lead through teaching and coaching, not management.
- Sprints are time-boxed and the Sprint Goal, not the plan, is the commitment.
- Always correct myths by explaining the purpose behind the practice.