Final Review and PSM I Exam Tactics

Module Map: How To Use This Final Review

Domain 1: Scrum Theory, Values, and Empiricism

Domain 2: Scrum Roles, Self-Managing Teams, and the Scrum Master

Domain 3: Events and Flow – Sprints, Planning, Daily Scrum, Review, Retro

Domain 4: Artifacts, Commitments, Definition of Done, and Transparency

Domain 5: Product Backlog Management and the Product Owner

Spot the Trap: Common PSM I Question Patterns

Use this thought exercise to train your “trap radar”. For each mini‑scenario, decide silently which option sounds Scrum‑consistent, then reveal the guidance.

1. Scenario: Daily Scrum

Developers attend a 30‑minute Daily Scrum where each person reports status to the Scrum Master, who then assigns tasks.

• Ask yourself: Which parts conflict with Scrum?
• Check: Daily Scrum is 15 minutes, for Developers, to inspect progress toward the Sprint Goal and adapt their plan. It is not a status report to the Scrum Master, and the Scrum Master does not assign tasks.

1. Scenario: Changing scope mid‑Sprint

Mid‑Sprint, the Product Owner discovers a more valuable item and tells Developers to drop some current work and start the new item.

• Ask: Is this allowed? Under what conditions?
• Check: Scope can be renegotiated between Product Owner and Developers if it does not endanger the Sprint Goal. The Product Owner cannot unilaterally command scope swaps that break the Sprint Goal.

1. Scenario: Definition of Done

A manager wants a “lighter” Definition of Done for urgent items so they can be released faster.

• Ask: What happens to transparency and quality?
• Check: Definition of Done is a formal description of the state of the Increment when it meets required quality. Having multiple Definitions of Done for the same product at the same time weakens transparency and is not aligned with Scrum.

As you continue in the module, keep asking: “Is this preserving self‑management, transparency, and empiricism, or undermining them?”

Quick Check 1: Roles, Events, and Artifacts

Answer this representative PSM I‑style question. Focus on the exact wording.

Quick Check 2: Transparency and Definition of Done

Another PSM I‑style question to reinforce artifacts and quality.

Time Management: 80 Questions in 60 Minutes

Guessing, Elimination, and Handling Tricky Wording

Stress Management and Focus During the Exam

Flashcards: Must-Know Scrum Definitions

Flip these cards mentally and make sure you can recall each definition word‑for‑word or very close. These are high‑value for PSM I.

Build Your Last-Week and Exam-Day Plan

Use this guided exercise to create a concrete plan tailored to you.

1. Score your domains (1–5)

For each area, rate your confidence:

• Scrum theory and values
• Roles and self‑managing teams
• Events and timeboxes
• Artifacts, commitments, Definition of Done
• Product Backlog management and Product Owner

1. Pick your top 2 weak areas

Circle the two lowest scores. These will get extra focus in the last week.

1. Design your last-week schedule

Example structure:

• Days 1–2: Rewatch/review Skarp lessons on your weakest domain; do 15–20 targeted questions.
• Days 3–4: Second‑weakest domain; do another 15–20 questions.
• Day 5: Full Skarp mock exam under real timing; review the gap guide.
• Day 6: Spaced review queue and flashcards (definitions, events, roles).
• Day 7: Light review only; no heavy new material.

1. Exam-day checklist (non‑logistics)

Write your own short list, for example:

• 3 deep breaths before starting.
• Two‑pass timing strategy (flag and move on).
• If stuck: recall values and empiricism, then eliminate.
• Quick reset every 20 questions.

Capture this plan somewhere you will actually see it (notes app, paper). After your next Skarp diagnostic or mock, adjust the plan based on new weak spots.