Overview
Understanding and Applying the Scrum Framework is the heart of the PSM I assessment, covering Scrum exactly as defined in the Scrum Guide. It spans empiricism, the three pillars of transparency, inspection and adaptation, and the five Scrum Values. It covers the Scrum Team: Developers, the Product Owner and the Scrum Master, and their accountabilities. It covers the five events: the Sprint, Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective. It covers the three artifacts, the Product Backlog, the Sprint Backlog and the Increment, each with its commitment, the Product Goal, the Sprint Goal and the definition of Done.
The PSM I tests precise knowledge of the Scrum Guide, not general agile practice or how teams often deviate. Most questions come from this area, and they reward understanding what Scrum actually prescribes, the accountabilities, the timeboxes, the purpose of each event and artifact, and the empirical foundation that makes Scrum work.
How it's tested
PSM I questions test the Scrum Guide precisely, often as scenarios asking what Scrum prescribes or what a Scrum Master should do. Answer from the Guide, not from how teams commonly behave: when an option reflects a common deviation (a status-meeting Daily Scrum, a Scrum Master assigning work), it is usually wrong. Read for what Scrum actually defines.
-
What Scrum prescribes
A situation is described, and you choose the answer consistent with the Scrum Guide, not common practice.
-
Accountability or event purpose
A responsibility or event is described, and you identify the correct accountability, timebox or purpose.
-
Empiricism in action
A transparency, inspection or adaptation need is described, and you apply the empirical pillars and values.
A stakeholder asks the Scrum Master to assign tasks to Developers and report who is behind. In Scrum, the Developers are a self-managing team that decides how to turn Product Backlog items into an Increment, and the Scrum Master serves the team rather than directing it. So the correct response is not to assign tasks but to help the organization understand self-management, which is what the Scrum Guide prescribes rather than the command-and-control habit the question tempts you toward.
Focus areas 6
Official focus areas from the Scrum.org outline, in outline order.
1.1 EmpiricismTransparency, inspection and adaptation, and empirical process control.
- What it means
- This covers empiricism, the foundation of Scrum: making decisions based on what is observed, through the three pillars of transparency (the work and process are visible), inspection (frequently checking progress and artifacts) and adaptation (adjusting based on inspection), supported by lean thinking.
- What to understand
- Scrum is built on empirical process control for complex work where more is unknown than known. Transparency enables meaningful inspection, and inspection enables adaptation; all three are needed. The Scrum events are the formal opportunities for inspection and adaptation. Understanding empiricism explains why Scrum works and underlies most of the framework.
- How it shows up
- A decision-making or visibility situation is described, and you must apply the empirical pillars.
- Common confusion
- Treating the pillars as optional or separable; transparency enables inspection, which enables adaptation, and all three are required.
1.2 Scrum ValuesCommitment, focus, openness, respect and courage.
- What it means
- This covers the five Scrum Values, commitment, focus, openness, respect and courage, that guide the Scrum Team's work, behavior and decisions, and build trust and effective use of the framework.
- What to understand
- The values are not decoration: they make the empirical pillars work in practice. The team commits to goals, focuses on the Sprint's work, is open about work and challenges, respects one another, and has the courage to do the right thing and tackle hard problems. Living the values builds the trust that transparency requires. The exam expects you to recognize the values in behavior.
- How it shows up
- A behavior or decision is described, and you must identify the Scrum Value it reflects or lacks.
- Common confusion
- Confusing the five values or treating them as abstract rather than practical guides to behavior.
1.3 The Scrum Team and accountabilitiesDevelopers, Product Owner, Scrum Master and their accountabilities.
- What it means
- This covers the Scrum Team: one cohesive unit of professionals with no sub-teams or hierarchies, typically ten or fewer people, comprising the Developers, one Product Owner and one Scrum Master, and the distinct accountabilities of each.
- What to understand
- The whole Scrum Team is accountable for creating a valuable, useful Increment each Sprint. The Developers create the Increment, the Product Owner is accountable for maximizing product value and manages the Product Backlog, and the Scrum Master is accountable for the team's effectiveness and for establishing Scrum. The Scrum Master is a true leader who serves, not a project manager who directs.
- How it shows up
- A responsibility is described, and you must assign it to the correct accountability.
- Common confusion
- Treating the Scrum Master as a project manager, or confusing the Product Owner's and Developers' accountabilities.
1.4 Scrum EventsThe Sprint, Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective.
- What it means
- This covers the five Scrum events: the Sprint as the container for all others (one month or less), Sprint Planning (starting the Sprint by planning the work), the Daily Scrum (the Developers' 15-minute daily inspection and adaptation), the Sprint Review (inspecting the Increment and adapting the Product Backlog with stakeholders) and the Sprint Retrospective (inspecting and improving how the team works).
- What to understand
- Each event is a formal opportunity for inspection and adaptation, is timeboxed, and has a specific purpose. The Sprint contains all the work and other events. The Daily Scrum is for the Developers to plan their day toward the Sprint Goal, not a status report to the Scrum Master. Knowing each event's purpose, timebox and participants precisely is essential.
- How it shows up
- An event situation is described, and you must identify the correct event, its purpose, timebox or participants.
- Common confusion
- Treating the Daily Scrum as a status meeting for the Scrum Master, or misremembering event timeboxes and purposes.
1.5 Scrum Artifacts and commitmentsProduct Backlog, Sprint Backlog, Increment and their commitments.
- What it means
- This covers the three artifacts and their commitments: the Product Backlog with its commitment the Product Goal, the Sprint Backlog with its commitment the Sprint Goal, and the Increment with its commitment the definition of Done, each designed to maximize transparency.
- What to understand
- Each artifact has a commitment that gives it focus and measures progress: the Product Goal is the long-term objective, the Sprint Goal is the single objective for the Sprint, and the definition of Done is the quality standard for the Increment. The commitments reinforce transparency and empiricism. Pairing each artifact with its commitment correctly is a frequent exam point.
- How it shows up
- An artifact or commitment is described, and you must identify it or pair the artifact with its commitment.
- Common confusion
- Confusing the artifacts with their commitments, such as pairing the Sprint Backlog with the wrong commitment.
1.6 Done and incrementsThe definition of Done and valuable, usable increments.
- What it means
- This covers the definition of Done, the shared, formal description of the state an Increment must meet to be considered complete and releasable, and the Increment as a concrete, usable step toward the Product Goal, with multiple Increments possible within a Sprint.
- What to understand
- The definition of Done creates transparency about what complete means and ensures quality. Work does not count toward the Sprint and is not part of the Increment unless it meets the definition of Done. An Increment is usable and adds to prior Increments, and it is not released only at the Sprint Review, it can be delivered whenever it is Done. Understanding Done and increments is central to Scrum's value delivery.
- How it shows up
- A completeness or quality situation is described, and you must apply the definition of Done or the increment concept.
- Common confusion
- Treating work that does not meet the definition of Done as part of the Increment, or thinking an Increment can only be released at the Sprint Review.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Empiricism
Decisions based on observation.
- Remember
- Transparency, inspection, adaptation.
- Tested as
- Foundational questions.
- Trap
- Treating a pillar as optional.
-
Three pillars
Transparency, inspection, adaptation.
- Remember
- Transparency enables inspection, which enables adaptation.
- Tested as
- Empiricism questions.
- Trap
- Separating them.
-
Scrum Values
Commitment, focus, openness, respect, courage.
- Remember
- They make empiricism work.
- Tested as
- Behavior questions.
- Trap
- Confusing the five values.
-
Scrum Team
One team of 10 or fewer, no sub-teams.
- Remember
- Developers, Product Owner, Scrum Master.
- Tested as
- Accountability questions.
- Trap
- Adding hierarchies or sub-teams.
-
Scrum Master accountability
Team effectiveness and establishing Scrum.
- Remember
- A leader who serves, not a project manager.
- Tested as
- Accountability questions.
- Trap
- Treating them as a project manager.
-
Product Owner accountability
Maximizing product value, managing the backlog.
- Remember
- One person, decisions respected.
- Tested as
- Accountability questions.
- Trap
- Splitting the role among many.
-
The Sprint
The container event, one month or less.
- Remember
- Holds all work and other events.
- Tested as
- Event questions.
- Trap
- Extending or shortening mid-Sprint improperly.
-
Daily Scrum
The Developers' 15-minute daily plan.
- Remember
- For the Developers, not a status report.
- Tested as
- Event questions.
- Trap
- Treating it as a status meeting.
-
Artifacts and commitments
Product Backlog/Product Goal, Sprint Backlog/Sprint Goal, Increment/Done.
- Remember
- Each artifact has one commitment.
- Tested as
- Artifact questions.
- Trap
- Mispairing them.
-
Definition of Done
The quality standard for the Increment.
- Remember
- Not Done means not part of the Increment.
- Tested as
- Done questions.
- Trap
- Counting undone work.
-
Increment
A usable step toward the Product Goal.
- Remember
- Can be released any time it is Done.
- Tested as
- Increment questions.
- Trap
- Thinking it ships only at the Review.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
The three accountabilities
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Developers | Create the Increment | Decide how to do the work | Having the Scrum Master assign their work |
| Product Owner | Maximizes product value | Owns the Product Backlog | Splitting across many people |
| Scrum Master | Team effectiveness, establishes Scrum | Leader who serves | Acting as project manager |
Artifacts and their commitments
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Product Backlog | What may be done on the product | Commitment: Product Goal | Pairing with the wrong commitment |
| Sprint Backlog | The plan for the Sprint | Commitment: Sprint Goal | Pairing with the wrong commitment |
| Increment | A usable step toward the goal | Commitment: definition of Done | Counting undone work |
Daily Scrum: Scrum vs. common deviation
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Scrum | Developers plan the day toward the Sprint Goal | By and for the Developers | Confusing with the deviation |
| Common deviation | Status report to the Scrum Master or manager | Not what Scrum prescribes | Choosing it as correct |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Scrum Master assigns work
- What candidates pick
- Have the Scrum Master assign tasks to Developers.
- Why it looks right
- It resembles project management.
- Why it's wrong
- The Developers are self-managing and decide how to do the work; the Scrum Master serves the team rather than directing it.
Clue to watch for The option has the Scrum Master directing the Developers' work.
-
Daily Scrum is a status meeting
- What candidates pick
- Describe the Daily Scrum as a status update for the Scrum Master or manager.
- Why it looks right
- Many teams run it that way.
- Why it's wrong
- The Daily Scrum is by and for the Developers to plan their day toward the Sprint Goal, not a status report.
Clue to watch for The event is framed as reporting to someone outside the Developers.
-
Undone work counts
- What candidates pick
- Include work that does not meet the definition of Done in the Increment.
- Why it looks right
- The work seems nearly finished.
- Why it's wrong
- Work that does not meet the definition of Done is not part of the Increment and does not count as complete.
Clue to watch for Work is almost done but does not meet the definition of Done.
-
Multiple Product Owners
- What candidates pick
- Split the Product Owner accountability across several people.
- Why it looks right
- The backlog is large.
- Why it's wrong
- The Product Owner is one person whose decisions must be respected; the role is not split into a committee.
Clue to watch for The scenario suggests sharing the Product Owner role.
-
Mispair artifact and commitment
- What candidates pick
- Pair the Sprint Backlog with the Product Goal or the Increment with the Sprint Goal.
- Why it looks right
- The terms are similar.
- Why it's wrong
- Each artifact has one commitment: Product Backlog with the Product Goal, Sprint Backlog with the Sprint Goal, and Increment with the definition of Done.
Clue to watch for The question links an artifact to a commitment.
-
Increment ships only at the Review
- What candidates pick
- Assume an Increment can only be released at the Sprint Review.
- Why it looks right
- The Review showcases the Increment.
- Why it's wrong
- An Increment can be delivered to stakeholders whenever it is Done; the Review is not a release gate.
Clue to watch for The scenario ties releasing to the Sprint Review.
Answer framework
For any Focus Area 1 scenario, use these steps to find the answer the PSM I expects.
- Answer from the Scrum Guide, not from how teams commonly behave; reject options that reflect common deviations.
- Apply empiricism: ensure transparency so inspection and adaptation can happen, and use the events as the inspection points.
- Assign responsibilities to the correct accountability, remembering the Developers self-manage and the Scrum Master serves rather than directs.
- Match each event to its purpose, timebox and participants, and the Daily Scrum to the Developers planning their day.
- Pair each artifact with its commitment, and treat only work meeting the definition of Done as part of the Increment. Where two options seem to fit, choose the one that reflects what the Scrum Guide prescribes rather than a common deviation.
Practice question
Want more like this? The PSM I practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Study this focus area straight from the Scrum Guide, reading it several times until the framework is exact in your mind, because the PSM I tests the Guide precisely and the pass mark is a demanding 85%. The single most important habit is to answer from what Scrum defines, not from how teams commonly work, since many wrong options are realistic workplace deviations.
Master the accountabilities, keeping the Scrum Master as a servant leader distinct from a project manager, and the Product Owner and Developers distinct. Learn each event's purpose, timebox and participants, especially that the Daily Scrum is by and for the Developers. Drill the artifacts and their commitments as fixed pairs, and understand empiricism and the values as the reason the framework works.
Because accuracy matters, use quality practice assessments such as the open ones from Scrum.org and aim consistently above 85%. Afterwards, move to Focus Area 2, Developing People and Teams.
FAQ
What does Focus Area 1 cover on the PSM I?
Understanding and Applying the Scrum Framework, the core and largest focus area: empiricism and the Scrum Values, the Scrum Team and accountabilities, the five events, the three artifacts and their commitments, and the definition of Done, all as defined in the Scrum Guide.
Should I answer PSM I questions from the Scrum Guide or from experience?
From the Scrum Guide. The PSM I tests Scrum as defined, and many incorrect options reflect common workplace deviations. When an answer describes what teams often do rather than what Scrum prescribes, it is usually wrong.
What are the three pillars of empiricism?
Transparency, inspection and adaptation. Transparency makes the work and process visible, which enables meaningful inspection, which enables adaptation. All three are required, and the Scrum events are the formal inspection and adaptation points.
Is the Scrum Master a project manager?
No. The Scrum Master is a true leader who serves the Scrum Team and organization, accountable for the team's effectiveness and for establishing Scrum. They do not assign tasks or direct the Developers, who self-manage.
What is the commitment for each artifact?
The Product Backlog's commitment is the Product Goal, the Sprint Backlog's commitment is the Sprint Goal, and the Increment's commitment is the definition of Done. Each commitment adds focus and transparency.
When can an Increment be released?
Whenever it meets the definition of Done. An Increment does not have to wait for the Sprint Review, which is an inspection and adaptation event, not a release gate; multiple Increments may be created and delivered within a Sprint.
How does Focus Area 1 connect to the rest of the exam?
The framework here is the foundation; developing people and teams and managing products with agility both build on a precise understanding of the accountabilities, events, artifacts and empiricism established in this area.
Other Agile & Scrum certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 1 knowledge
You have covered empiricism, the values, the Scrum Team, events, artifacts and Done. Test whether you can answer from the Scrum Guide, not common practice, under exam conditions.