Cracking the PSM I: 7 Sneaky Topics That Trip Up Candidates
The PSM I exam is famous for its trick wording. Here are the 7 most common "traps" and how to spot them before you click the wrong answer.
You’ve read the Scrum Guide. You’ve taken open assessments. But when you sit for the real exam, you see a question where two answers look correct.
This is by design. Scrum.org tests for "Mechanical Scrum" vs "Professional Scrum." Here is how to spot the difference.
1. The "Manager" Trap
The Trap: Questions often ask who is responsible for "assigning tasks," "hiring," or "performance reviews."
Common Mistake
Thinking the Scrum Master or Product Owner assigns work.
The Truth
No one assigns work to Developers. Not even the CTO. Developers pull work themselves.
2. The "Sprint Zero" Trap
The Trap: "Should we have a Sprint 0 for architecture and design?"
3. Who Attends the Daily Scrum?
This seems easy, but the wording often tricks people.
| Role | Required? | Why? |
|---|---|---|
| Developers | YES | They are the ones doing the work. |
| Scrum Master | NO | Only ensures it happens; does not need to be there. |
| Product Owner | NO | Optional. Can attend as a silent observer or to answer questions if asked. |
4. The "Sprint Cancellation" Trap
This is a favorite exam topic because it is so rare in real life.
ONLY the Product Owner. Not the Scrum Master, not the CEO.
ONLY when the Sprint Goal becomes obsolete. Not because we are "behind schedule."
5. Capacity vs. Velocity
The Trap: "How do we calculate Velocity?"
The Fix: Scrum does not mandate Velocity. It does not mandate Story Points. If an answer treats "Velocity" as a required metric, it is wrong. Look for answers focused on value and flow.
Test Your "Trap Detection"
Our Simulator includes a "Hard Mode" specifically designed to test these edge cases.
6. The "Definition of Done" vs. "Acceptance Criteria"
They sound similar, but confusing them guarantees a wrong answer.
Definition of Done
Global. Applies to ALL items (e.g., "Code Reviewed," "Unit Tests Passed"). If not met, it's not an Increment.
Acceptance Criteria
Specific. Applies to ONE item (e.g., "Login button is blue"). Defined by the Product Owner.
7. The "Burn-down Chart" Myth
Similar to Velocity, the Burn-down chart is a complementary practice. It is not part of core Scrum. You can use a burn-up chart, a flow diagram, or just a conversation.
Exam Tip: If a question asks "Which report MUST the team use?", the answer is usually "Whatever they choose."
Ready to Ace the Exam?
Don't get tricked by the wording. Practice with 800+ realistic questions.