Home / agile-scrum / Scrum Master Professional Certificate (SMPC) / Cheat Sheet
Scrum Master Professional Certificate (SMPC)

SMPC Cheat Sheet

SMPC Tests 2020 Scrum Guide Precision — Not Agile Folklore or 2017 Vocabulary

SMPC is CertiProf's entry-level Scrum Master credential. Answers come straight from the 2020 Scrum Guide and Agile Manifesto, so swap habits like the Development Team and three Daily Scrum questions for current wording.

Check Your Readiness →
Among the harder certs
Avg: Not published by CertiProf
Pass: 750 / 1000
Most candidates understand Scrum Master Professional Certificate (SMPC) concepts — and still fail. This exam tests how you apply knowledge under pressure.

SMPC Learning Objective Map

CertiProf lists nine learning-objective headings but no weights. The 40 questions mix straight Guide recall (timeboxes, commitments, who cancels a Sprint) with short scenarios asking for the Scrum Master's best first move. Scaling frameworks such as SAFe and LeSS sit outside this syllabus.

  1. 01
    Agile Introduction (weight not published) — Manifesto values, twelve principles, Cynefin domains, predictive vs. agile fit
  2. 02
    What is Scrum? (weight not published) — lightweight framework, immutable core, 2020 changes such as the Product Goal
  3. 03
    Scrum Theory (weight not published) — empiricism plus lean thinking; transparency enables inspection, inspection enables adaptation
  4. 04
    Scrum Values (weight not published) — commitment, focus, openness, respect, courage identified from behaviour
  5. 05
    Scrum Team (weight not published) — one team, 10 or fewer, three accountabilities, no sub-teams
  6. 06
    Scrum Events (weight not published) — Sprint, Planning, Daily Scrum, Review, Retrospective and their timeboxes
  7. 07
    Scrum Artifacts (weight not published) — each artifact paired with its commitment; undone work rules
  8. 08
    Advanced Scrum Concepts (weight not published) — INVEST, Planning Poker, velocity, Kanban, MVP, Scrum of Scrums
  9. 09
    Act as Scrum Master (weight not published) — teach, coach, facilitate; cause impediments to be removed

Wrong instinct vs correct approach

A functional manager attends every Daily Scrum, Developers report status to him, and the event runs 30 minutes
✕ Wrong instinct

The Scrum Master chairs it and keeps the manager's questions short

✓ Correct approach

The Daily Scrum belongs to the Developers and inspects progress toward the Sprint Goal. The Scrum Master teaches them to keep it within 15 minutes and coaches the manager on why it is not a reporting meeting.

Sprint ends with two items untested; the team wants three extra days to finish them
✕ Wrong instinct

Extend the Sprint so the committed items can be completed

✓ Correct approach

Sprint length is fixed and the next Sprint starts immediately. Work failing the Definition of Done cannot be presented at the Review or released; it returns to the Product Backlog for the Product Owner to reorder.

Every Retrospective records the same slow code-review problem, yet nothing changes for months
✕ Wrong instinct

Blame inspection and add more frequent status checks

✓ Correct approach

The issue is visible and inspected, so the failing pillar is adaptation. The team should commit to at least one improvement, possibly adding it to the next Sprint Backlog, and act on it as soon as possible.

A senior Developer always reveals her Planning Poker card first and juniors copy her number
✕ Wrong instinct

Let the most experienced Developer set estimates to save time

✓ Correct approach

Early reveal causes anchoring, which Planning Poker exists to prevent. The Scrum Master suggests simultaneous reveals, discussion of the outliers and a re-vote, so sizing reflects every Developer's view.

Know these cold

  • ▸ Only the Product Owner can cancel a Sprint, usually when the Sprint Goal becomes obsolete
  • ▸ Scrum Team — ne Product Owner, one Scrum Master, Developers; typically 10 or fewer people
  • ▸ Scrum rests on two foundations in 2020 — mpiricism and lean thinking
  • ▸ Sprint Planning answers why, what and how; the Sprint Goal comes from why
  • ▸ Refinement is an ongoing activity, not a sixth event; Developers who do the work size items
  • ▸ Increments may be released mid-Sprint; the Sprint Review is a working session, not a gate
  • ▸ Teams on one product share one Product Backlog, one Product Owner and one Definition of Done
  • ▸ INVEST — ndependent, Negotiable, Valuable, Estimable, Small, Testable; velocity is never compared between teams
  • ▸ Cynefin complex domain means probe, sense, respond, which is why empiricism fits product work
  • ▸ Scrum Master serves as a true leader — oaches self-management, never assigns tasks or orders the backlog

Can you answer these without checking your notes?

In this scenario: "A functional manager attends every Daily Scrum, Developers report status to him, and the event runs 30 minutes" — what should you do first?
The Daily Scrum belongs to the Developers and inspects progress toward the Sprint Goal. The Scrum Master teaches them to keep it within 15 minutes and coaches the manager on why it is not a reporting meeting.
In this scenario: "Sprint ends with two items untested; the team wants three extra days to finish them" — what should you do first?
Sprint length is fixed and the next Sprint starts immediately. Work failing the Definition of Done cannot be presented at the Review or released; it returns to the Product Backlog for the Product Owner to reorder.
In this scenario: "Every Retrospective records the same slow code-review problem, yet nothing changes for months" — what should you do first?
The issue is visible and inspected, so the failing pillar is adaptation. The team should commit to at least one improvement, possibly adding it to the next Sprint Backlog, and act on it as soon as possible.

Common Exam Mistakes — What candidates get wrong

Answering with 2017 Scrum Guide terms the 2020 Guide removed

The 2020 Guide has one Scrum Team with Developers as an accountability, says self-managing rather than self-organizing, and drops the three Daily Scrum questions. Options built on the Development Team or mandatory yesterday/today/blockers are distractors.

Pairing the Definition of Done with the Sprint Backlog

Each artifact has exactly one commitment: Product Backlog to Product Goal, Sprint Backlog to Sprint Goal, Increment to Definition of Done. Matching items rotate these on purpose, and the Product Goal is the one older material omits.

Swapping the Sprint Review and Retrospective timeboxes

For a one-month Sprint: Planning up to 8 hours, Review up to 4, Retrospective up to 3, Daily Scrum 15 minutes at any Sprint length. The Retrospective concludes the Sprint, so it comes after the Review, never before.

Listing transparency or trust among the five Scrum values

The values are commitment, focus, openness, respect and courage. Transparency, inspection and adaptation are the empirical pillars. A Product Owner refusing an executive's low-value mid-Sprint request shows courage, not openness, even though she explains her reasons.

Treating story points, burndowns or user stories as required Scrum

Scrum is purposefully incomplete: stories, points, Planning Poker, burndown charts and Kanban boards are optional practices layered on top. Removing an event, accountability or artifact, however, means the result is no longer Scrum.

Resources to help you pass Scrum Master Professional Certificate on your first attempt

SMPC leaves room for only eight misses. Check whether your 2020 Scrum Guide recall holds up.