SkarpChapter 11 of 20
Scrum Essentials: Roles, Events, and Artifacts
Walk through a Scrum sprint from planning to review and retrospective, meeting the roles, events, and artifacts along the way. This module turns Scrum from a buzzword into a concrete framework you can easily recognize and reason about on the exam.
From Agile Mindset to Scrum: Where This Fits
Scrum in Your Study Path
You know predictive vs. adaptive and the agile mindset. Scrum is one of the most common adaptive life cycle frameworks and shows up heavily in CAPM agile questions.
Key Definition
An adaptive life cycle is: "A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration." Scrum is one such life cycle.
What You Will Do
You will walk through a Sprint, meet Scrum roles, events, and artifacts, and see how they enable transparency, inspection, and adaptation in practice.
Exam Alignment
We follow the current Scrum Guide (latest major update in 2020, still current in 2026) and PMI wording where the exam expects it, highlighting common traps along the way.
Scrum in One Picture: Empiricism, Sprints, and Flow of Value
Empiricism in Scrum
Scrum uses empiricism: decisions are based on what is observed. It rests on three pillars: transparency, inspection, and adaptation.
Sprints as Mini-Projects
Work happens in Sprints, usually 1–4 weeks. Each Sprint has a goal, plan, daily coordination, a review of results, and a retrospective to improve.
Flow of Value
1) Product Backlog holds ideas. 2) Sprint Planning selects items and sets a Sprint Goal. 3) Daily Scrums inspect/adapt. 4) Sprint Review shows an Increment. 5) Retrospective improves the process.
Roles and Exam Focus
Product Owner, Scrum Master, and Developers collaborate through all events. CAPM questions often ask which role or event best supports transparency, inspection, or adaptation.
Scrum Roles: Product Owner, Scrum Master, Developers
Three Scrum Roles
Scrum has three roles: Product Owner, Scrum Master, and Developers. There is no separate project manager role inside Scrum teams.
Product Owner
The Product Owner is accountable for maximizing product value and managing the product backlog: vision, priorities, and what gets built next.
Developers
Developers are everyone who builds the Increment: programmers, testers, designers, etc. They own the Sprint Backlog and decide how to do the work.
Scrum Master
The Scrum Master is a servant-leader and coach, accountable for the Scrum Team’s effectiveness, ensuring Scrum is understood and practiced well.
Exam Clues
Prioritizing backlog? Think Product Owner. Coaching and removing impediments? Scrum Master. Estimating and implementing work? Developers.
Scrum Artifacts: Product Backlog, Sprint Backlog, Increment
Three Scrum Artifacts
Scrum artifacts are Product Backlog, Sprint Backlog, and Increment. They make work visible and support transparency, inspection, and adaptation.
Product Backlog Definition
Memorize: "An ordered list of everything that is known to be needed in the product, managed by the product owner." This is central for the CAPM.
Sprint Backlog
The Sprint Backlog is the selected Product Backlog items for the Sprint plus a plan to deliver them and meet the Sprint Goal, owned by the Developers.
Increment
The Increment is the working product resulting from the Sprint, integrated with prior work and meeting the Definition of Done, so it is potentially releasable.
Artifact Commitments
Each artifact has a commitment: Product Backlog → Product Goal, Sprint Backlog → Sprint Goal, Increment → Definition of Done.
Walking a Sprint Step-by-Step: Planning to Increment
Scenario Setup
A Scrum Team builds a mobile banking feature: instant bill payments. Product Goal: quick, secure bill pay. Product Backlog holds ordered user stories.
Before the Sprint
The Product Owner refines backlog items with the team, adding acceptance criteria and estimates so high-priority items are ready for selection.
Sprint Planning
The team sets a Sprint Goal: "Customers can add billers and make one-time payments." Developers select and task-out items, forming the Sprint Backlog.
During the Sprint
Developers use the Daily Scrum to inspect progress and adapt. They may adjust scope with the PO to still meet the Sprint Goal if capacity is tight.
End of Sprint: Increment
A working Increment lets users add billers and make one-time payments, meeting acceptance criteria and Definition of Done, and is potentially releasable.
Scrum Events: Sprint and Sprint Planning in Detail
Five Scrum Events
Scrum events: the Sprint (container) plus Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
The Sprint
A fixed-length iteration (1–4 weeks). No changes that endanger the Sprint Goal; scope can be clarified and negotiated as learning occurs.
Purpose of Sprint Planning
Sprint Planning sets direction: define the Sprint Goal, decide what can be done, and outline how to do it.
Three Planning Questions
1) Why is this Sprint valuable? 2) What can be done? 3) How will the work get done? All three must be addressed.
Exam Traps
Sprint Planning is not just task lists. Developers, not managers, decide how much work to take and how to organize it.
Daily Scrum, Sprint Review, and Retrospective
Daily Scrum
A 15-minute daily event for Developers to inspect progress toward the Sprint Goal and adapt their plan for the next 24 hours.
Who Attends Daily Scrum
Daily Scrum is for Developers. PO and Scrum Master may attend, but Developers run it and focus on progress and impediments.
Sprint Review
At Sprint end, Scrum Team and stakeholders inspect the Increment and discuss the Product Backlog and context. It is a working session, not just a demo.
Stakeholder Definition
A stakeholder is: "An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio."
Sprint Retrospective
After the Review, the Scrum Team inspects how they worked and plans concrete improvements to process, tools, and collaboration for the next Sprint.
Exam Hint
Need to improve the product or backlog? Think Sprint Review. Need to improve teamwork or process? Think Sprint Retrospective.
Thought Exercise: Mapping Events to Empiricism
Use this exercise to link each Scrum event to the empiricism pillars: transparency, inspection, and adaptation.
For each prompt, pause and answer mentally or jot down a few words before revealing the guidance.
- Which event creates transparency about the product’s current state and future direction for stakeholders?
- Think: Which meeting includes stakeholders and looks at the Increment and Product Backlog?
- Guidance: That is the Sprint Review. It makes the Increment and roadmap transparent.
- Which event is primarily focused on frequent inspection and short-term adaptation of the plan?
- Think: Which event happens every day with a 15-minute timebox?
- Guidance: The Daily Scrum. Developers inspect progress and adapt their plan for the next 24 hours.
- Which event is focused on inspecting and adapting the team’s way of working, not the product itself?
- Think: Which event is Scrum Team only and happens at the end of the Sprint?
- Guidance: The Sprint Retrospective. It inspects processes, tools, and collaboration.
- Which artifact gives ongoing transparency into all known work for the product?
- Think: Which artifact is ordered and managed by the Product Owner?
- Guidance: The product backlog: "An ordered list of everything that is known to be needed in the product, managed by the product owner."
As you review, ask yourself for each event and artifact: What is made transparent? What is inspected? What can be adapted? This is exactly how exam questions are framed.
Quiz 1: Roles and Artifacts
Check your understanding of Scrum roles and artifacts.
A Scrum Team is unsure which items to work on next. Who is primarily responsible for ordering the work, and which artifact do they use to do this?
- Scrum Master using the Sprint Backlog
- Product Owner using the product backlog
- Developers using the Increment
- Stakeholders using the requirements traceability matrix
Show Answer
Answer: B) Product Owner using the product backlog
The Product Owner is accountable for maximizing value and manages the ordering of work using the **product backlog**, defined as "An ordered list of everything that is known to be needed in the product, managed by the product owner." The Scrum Master coaches on process, Developers deliver the Increment, and stakeholders do not manage Scrum artifacts. A requirements traceability matrix is a different artifact used mainly in predictive contexts.
Quiz 2: Events and Empiricism
Apply what you know about Scrum events and empiricism.
After several Sprints, a Scrum Team notices recurring communication problems and handoff delays. Which Scrum event is the BEST place to identify root causes and agree on process improvements?
- Sprint Planning
- Daily Scrum
- Sprint Review
- Sprint Retrospective
Show Answer
Answer: D) Sprint Retrospective
The **Sprint Retrospective** is dedicated to inspecting how the last Sprint went regarding people, relationships, processes, and tools, and then adapting by creating improvement actions. Sprint Planning focuses on the upcoming Sprint’s work, the Daily Scrum on short-term coordination, and the Sprint Review on inspecting the product and backlog with stakeholders.
Key Scrum Terms: Flashcards
Use these flashcards to reinforce essential Scrum concepts and exam-ready definitions.
- Product backlog (PMI definition)
- An ordered list of everything that is known to be needed in the product, managed by the product owner.
- Increment
- The sum of all completed Product Backlog items during a Sprint, integrated with previous work, that meets the Definition of Done and is potentially releasable.
- Sprint Backlog
- The set of Product Backlog items selected for the Sprint, plus a plan for delivering them and achieving the Sprint Goal, owned and updated by the Developers.
- Sprint Goal
- A single objective for the Sprint that provides focus and guidance to the Scrum Team about why the Increment is being built.
- Scrum Master
- The servant-leader and coach accountable for the Scrum Team’s effectiveness and for ensuring Scrum is understood and enacted properly.
- Product Owner
- The role accountable for maximizing the value of the product and managing the product backlog, including ordering items and clarifying the product vision.
- Developers (in Scrum)
- The people in the Scrum Team committed to creating any aspect of a usable Increment each Sprint, including coding, testing, design, and other work.
- Daily Scrum
- A 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the plan for the next 24 hours.
- Sprint Review
- An event at the end of the Sprint where the Scrum Team and stakeholders inspect the Increment and discuss the Product Backlog and environment to adapt future work.
- Sprint Retrospective
- An event for the Scrum Team to inspect how the last Sprint went in terms of people, process, and tools, and to plan improvements for the next Sprint.
Mini Scenario Drill: What Should Happen Next?
Practice CAPM-style thinking: choose the next best Scrum action.
Scenario 1
Halfway through a 2-week Sprint, the team discovers that an external API is slower than expected. They may not finish all selected items, but the main user flow can still work with some adjustments.
Pause and decide: What should the Scrum Team do next?
Suggested answer: The Developers and Product Owner should collaborate to adapt the Sprint Backlog while preserving the Sprint Goal. They might drop or split lower-priority items and adjust scope. They do not cancel the Sprint or ask management to extend it.
Scenario 2
Stakeholders are surprised at Sprint Review that a feature behaves differently from what they expected. This has happened in the last three Sprints.
What is the best action to reduce this mismatch?
Suggested answer: Improve ongoing collaboration and transparency during the Sprint. For example, the Product Owner can invite key stakeholders to backlog refinement and clarify acceptance criteria. The team might also enhance Sprint Reviews to encourage more discussion, not just a demo. The fix is not to skip Sprints or lengthen them, but to strengthen feedback loops.
Scenario 3
The Scrum Master notices that Daily Scrums have turned into long status reports to them personally.
What should the Scrum Master do?
Suggested answer: Coach the Developers that the Daily Scrum is for them, to inspect progress toward the Sprint Goal and adapt their plan, not to report to the Scrum Master. Help them experiment with formats that keep it within 15 minutes and focused on collaboration and impediments.
Key Terms
- Sprint
- A fixed-length, timeboxed iteration in Scrum, usually 1–4 weeks, during which a usable Increment is created.
- project
- A temporary endeavor undertaken to create a unique product, service, or result.
- Increment
- The sum of all completed Product Backlog items during a Sprint, integrated with previous work, that meets the Definition of Done and is potentially releasable.
- Daily Scrum
- A 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the plan for the next 24 hours.
- Sprint Goal
- A single objective for the Sprint that provides focus and guidance to the Scrum Team about why the Increment is being built.
- stakeholder
- An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
- Sprint Review
- An event at the end of the Sprint where the Scrum Team and stakeholders inspect the Increment and discuss the Product Backlog and environment to adapt future work.
- Sprint Backlog
- The set of Product Backlog items selected for the Sprint, plus a plan for delivering them and achieving the Sprint Goal, owned and updated by the Developers.
- product backlog
- An ordered list of everything that is known to be needed in the product, managed by the product owner.
- Definition of Done
- A shared understanding of what it means for work to be complete, ensuring the Increment is potentially releasable.
- acceptance criteria
- A set of conditions that is required to be met before deliverables are accepted.
- adaptive life cycle
- A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
- Sprint Retrospective
- An event for the Scrum Team to inspect how the last Sprint went in terms of people, process, and tools, and to plan improvements for the next Sprint.