So you have read the Scrum Guide and you understand the theory, but you keep getting practice questions wrong because the "professional-sounding" answer feels right even when it violates Scrum.. If you searched for PSM I anti-patterns, you're in the right place Welcome to the PSM I experience. The exam loves to present anti-patterns: practices that sound legitimate but fundamentally contradict Scrum. If you cannot spot them, you will fail. Let us fix that.
Why Anti-Patterns Matter
The PSM I exam tests whether you can distinguish Scrum from traditional project management dressed up as Scrum. About 30 to 40% of the questions include at least one answer that represents a common anti-pattern. If you select it, you lose the point. Spotting anti-patterns is not optional: it is essential.
| Anti-Pattern | Wrong Role Action | Correct Scrum Behavior |
|---|---|---|
| SM as team lead | Assigns tasks, manages capacity | Coaches, facilitates, removes impediments |
| PO as business analyst | Writes detailed requirements | Orders Product Backlog for value |
| Daily Scrum as status | Reports to SM or stakeholders | Developers plan their own work |
| Sprint Review as gate | Formal stakeholder approval | Collaborative feedback session |
| Hardening Sprint | Testing in separate Sprint | Done Increment every Sprint |
The 15 Anti-Patterns You Must Know
1. The Scrum Master as Team Lead
The anti-pattern: The Scrum Master assigns tasks, manages the team's capacity, runs Sprint Planning like a project kickoff, and reports team performance to management. Why it is wrong: The Scrum Master is a servant-leader who coaches the team toward self-management. They do not lead the team in the traditional sense. PSM I clue: If the Scrum Master "manages" or "directs" the Developers, the answer is wrong.
2. The Product Owner as Business Analyst
The anti-pattern: The Product Owner gathers requirements from stakeholders, writes detailed specification documents, and hands them to Developers as a Sprint Plan. Why it is wrong: The Product Owner maximizes value through Product Backlog ordering. They do not write specifications or manage Sprint work. Developers decide how to build what the Product Owner prioritizes. PSM I clue: If the Product Owner "writes requirements" or "tells Developers what to build in detail," the answer is wrong.
3. The Daily Scrum as Status Meeting
The anti-pattern: Developers take turns reporting what they did yesterday to the Scrum Master, who takes notes and follows up on action items. Why it is wrong: The Daily Scrum is a 15-minute planning meeting for Developers. They inspect progress toward the Sprint Goal and adapt their plan for the next 24 hours. It is not a status report for anyone outside the Developers. PSM I clue: If anyone other than Developers "receives" or "listens to" the Daily Scrum report, the answer is wrong.
4. Sprint Review as Gate Review
The anti-pattern: Stakeholders formally review the Increment and give approval (or rejection) before it can proceed. Why it is wrong: The Sprint Review is a working session to inspect the Increment and adapt the Product Backlog based on feedback. There is no formal approval process. PSM I clue: If the Sprint Review involves "approval," "sign-off," or "acceptance" by stakeholders, the answer is wrong.
5. The Hardening Sprint
The anti-pattern: The team runs a "hardening Sprint" at the end of every few Sprints to fix bugs, complete testing, and stabilize the product. Why it is wrong: Every Sprint must produce a Done Increment that meets the Definition of Done. If testing is not happening during regular Sprints, the Definition of Done is too weak. PSM I clue: If a Sprint is dedicated to testing, bug fixing, or "stabilization," the answer is wrong.
6. The Scrum Team Has Sub-Teams
The anti-pattern: The Scrum Team is divided into specialized sub-teams: frontend, backend, QA, and DevOps. Why it is wrong: A Scrum Team is cross-functional: it has all the skills needed to create a Done Increment without depending on others. Sub-teams create handoff delays and reduce accountability. PSM I clue: If Developers are organized by specialty within the Scrum Team, the answer is wrong.
7. Specialized Developer Roles
The anti-pattern: Within the Scrum Team, one person is "the database person," another is "the UI person," and they only work in their specialty. Why it is wrong: Developers in Scrum are not titled by specialty. They collectively have all the skills needed to build the Increment. While individuals may have specialties, the team works together. PSM I clue: If Developers are permanently assigned to specialty areas, the answer is wrong.
8. The Sprint Goal Changes Every Week
The anti-pattern: When a stakeholder requests a new feature, the Product Owner updates the Sprint Goal to include it, and Developers adjust their plan. Why it is wrong: The Sprint Goal provides stability and focus. It should not change unless the Sprint becomes obsolete. PSM I clue: If the Sprint Goal is "adjusted" or "updated" to accommodate scope changes, the answer is wrong.
9. Management Sets the Sprint Goal
The anti-pattern: A functional manager or senior stakeholder tells the Scrum Team what the Sprint Goal should be. Why it is wrong: The Sprint Goal is created collaboratively during Sprint Planning by the Scrum Team. While the Product Owner proposes the goal, the Developers commit to it. PSM I clue: If anyone outside the Scrum Team dictates the Sprint Goal, the answer is wrong.
10. Velocity as a Performance Target
The anti-pattern: Management uses velocity to measure team performance and holds the team accountable for meeting velocity targets. Why it is wrong: Velocity is a planning tool for the Scrum Team. Its purpose is to help forecast Sprint capacity, not to compare teams or set performance expectations. PSM I clue: If velocity is used as a target, KPI, or comparison metric across teams, the answer is wrong.
11. Developers Wait for Task Assignment
The anti-pattern: Developers wait for the Scrum Master or Product Owner to tell them what to work on each day. Why it is wrong: Developers are self-managing. They pull work from the Sprint Backlog based on the Sprint Goal and their own capacity planning. PSM I clue: If Developers "wait for assignments" or "receive tasks from" someone else, the answer is wrong.
12. Skipping Sprint Retrospective When "Things Are Good"
The anti-pattern: The team skips the Sprint Retrospective because the Sprint went well and there is nothing to improve. Why it is wrong: The Sprint Retrospective is a mandatory Scrum event. Even when things go well, there are always opportunities to improve quality, collaboration, or engineering practices. PSM I clue: If any Scrum event is skipped for any reason, the answer is wrong.
13. The Product Attends Sprint Planning as a Standby Decision Maker
The anti-pattern: Stakeholders attend Sprint Planning to answer questions and approve the plan. Why it is wrong: Sprint Planning is for the Scrum Team. The Product Owner represents stakeholder interests through the Product Backlog, not by having stakeholders present. PSM I clue: If stakeholders attend Sprint Planning as decision-makers, the answer is wrong.
14. Changing the Definition of Done to Meet Sprint Deadlines
The anti-pattern: When the team cannot complete all planned work, they lower the Definition of Done to make the remaining items meet the bar. Why it is wrong: The Definition of Done is a quality standard. Lowering it to fit more work into a Sprint undermines transparency and quality. PSM I clue: If the Definition of Done is weakened to accommodate Sprint scope, the answer is wrong.
15. The Scrum Master Cancels the Sprint Unilaterally
The anti-pattern: The Scrum Master decides the Sprint is not working and cancels it without consulting the rest of the Scrum Team. Why it is wrong: Only the Product Owner has the authority to cancel a Sprint. The Scrum Master can coach and recommend, but the Product Owner makes the decision. PSM I clue: If anyone other than the Product Owner cancels a Sprint, the answer is wrong.
How to Use This Guide
When you see a PSM I practice question, run each answer through this checklist:
- Does any answer give a non-Scrum role power over the team?
- Does any answer delay feedback or reduce transparency?
- Does any answer violate Scrum accountabilities?
- Does any answer involve formal approvals or gates?
- Does any answer skip or modify a Scrum event?
- Does any answer change the Sprint Goal casually?
- Does any answer separate testing from development?
If you find one match, you have found your wrong answer. Eliminate it.
FAQ
What happens if the Sprint Goal becomes obsolete?
If the Sprint Goal becomes obsolete during the Sprint, the Product Owner can cancel the Sprint. This is rare and should not be done lightly.
Can the Sprint Backlog change during the Sprint?
Yes. Developers modify the Sprint Backlog throughout the Sprint as they learn more about the work. This is expected and healthy as long as the Sprint Goal is not endangered.
Who can cancel a Sprint?
Only the Product Owner has the authority to cancel a Sprint. The Scrum Master, Developers, or stakeholders cannot unilaterally cancel it.
What if the Definition of Done is not met by the end of the Sprint?
The incomplete work does not count as part of the Increment. It returns to the Product Backlog for future Sprint Planning. The team should inspect why the Definition of Done was not met during the Sprint Retrospective.
Is it okay to have a Scrum Master and a Project Manager in the same team?
Scrum does not define a Project Manager role. If someone is performing project management tasks (assigning work, managing timelines), they are taking on Product Owner or Developer accountabilities, not adding a new role.
Should the Daily Scrum always follow the three-question format?
The three-question format ("What did I do? What will I do? Are there any impediments?") is a suggested technique, not a requirement. The Scrum Guide says Developers can use any structure that works for them, as long as the Daily Scrum focuses on progress toward the Sprint Goal.
Study these anti-patterns, and you will spot 30 to 40% of the PSM I questions immediately. Practice at cert-pass.com/exams/scrumorg-professional-scrum-master-i/take. Full prep with 1000+ questions starts at EUR 29.
