A lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems, using defined roles, events, and artifacts.

An ordered list of everything that is known to be needed in the product, managed by the product owner.

The single person accountable for maximizing the value of the product and managing and ordering the product backlog.

A servant-leader for the Scrum Team and organization who coaches in Scrum, removes impediments, and helps everyone understand and apply the framework.

Members of the Scrum Team committed to creating any aspect of a usable Increment each Sprint; cross-functional and self-managing.

The core iteration in Scrum, a fixed 1–4 week timebox during which a usable Increment is created.

A temporary endeavor undertaken to create a unique product, service, or result.

Scrum Fundamentals: Roles, Events, and Artifacts — CAPM Exam Mastery: Project Management, Predictive, Agile, and Business Analysis Foundations

Scrum in the CAPM Landscape

Scrum and the CAPM Exam

Scrum is central to the CAPM Agile Frameworks and Methodologies (20%) domain and connects to Fundamentals and Business Analysis because it shapes how requirements flow and value is delivered.

What Scrum Is (and Is Not)

Scrum is a lightweight framework: it defines roles, events, and artifacts, but not every practice. Teams add techniques like story points or burndown charts on top of Scrum.

Empirical Process Control

Scrum relies on transparency, inspection, and adaptation. Work and progress are visible, regularly inspected, and the team adapts quickly when they see problems or opportunities.

Key CAPM Skills Here

For CAPM, you must choose appropriate lifecycles, explain empirical control, use the product backlog, and trace how an item becomes a potentially shippable increment in a Sprint.

Scrum as an Adaptive Life Cycle

Predictive vs Adaptive

A predictive life cycle fixes scope, time, and cost early. Scrum uses an adaptive life cycle, where detailed scope is defined and approved just before each iteration (Sprint).

How Scrum Plans

Scrum plans through a dynamic product backlog, Sprint Planning, and Daily Scrums. Planning is continuous and adaptive instead of one big upfront plan.

When Scrum Fits Best

Choose Scrum when requirements are uncertain or evolving, the cost of change is acceptable, and stakeholders need frequent inspection of working product.

Exam Signal Words

On CAPM, phrases like “rapid change,” “early value,” and “learning each iteration” point toward Scrum or other adaptive approaches, not predictive.

Scrum Roles: Product Owner, Scrum Master, Developers

Three Scrum Accountabilities

Scrum has three roles: Product Owner, Scrum Master, and Developers. There is no “Scrum project manager” role defined inside the framework.

Product Owner

The Product Owner maximizes product value, manages and orders the product backlog, and decides what to build next. One person, not a committee.

Scrum Master

The Scrum Master is a servant-leader who coaches the team in Scrum, removes impediments, and helps the team and organization use Scrum effectively.

Developers

Developers are everyone who works to create the increment. They are cross-functional and self-managing, deciding how to turn backlog items into working product.

Role-Related Exam Traps

Common mistakes: treating the PO as a committee, the SM as a command-and-control PM, or Developers as only coders without shared accountability for quality.

Scrum Events Overview: The Sprint and Its Cadence

Five Scrum Events

Scrum events are: the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. The Sprint is the container for all other events.

The Sprint Timebox

A Sprint is a fixed 1–4 week timebox where the team creates a usable increment guided by a Sprint Goal. Sprints follow one another with no gaps.

Cadence and Empiricism

Timeboxed events provide a regular cadence for transparency, inspection, and adaptation. This rhythm is essential to Scrum’s empirical control.

Scope Changes in a Sprint

Scope can be clarified or adjusted during a Sprint, but changes should not put the Sprint Goal at risk. The duration of the Sprint does not change.

Scrum Artifacts and Commitments

Three Scrum Artifacts

Scrum artifacts are the Product Backlog, Sprint Backlog, and Increment. Each has a commitment: Product Goal, Sprint Goal, and Definition of Done.

Product Backlog and Product Goal

The product backlog is an ordered list of everything needed in the product, managed by the Product Owner. Its commitment is the longer-term Product Goal.

Sprint Backlog and Sprint Goal

The Sprint Backlog is the PBIs selected for the Sprint plus a delivery plan. Developers own it. Its commitment is the Sprint Goal, which gives the Sprint a clear focus.

Increment and Definition of Done

The Increment is the sum of completed PBIs that meet the Definition of Done. DoD is the shared standard for quality and completeness across all work.

DoD vs Acceptance Criteria

DoD is a global quality bar; acceptance criteria are item-specific conditions that must be met before a particular deliverable is accepted.

Walking Through a Sprint: From Backlog to Increment

Vision and Product Goal

Example: a Scrum Team builds a campus events app. Product Goal: “Students can easily discover, bookmark, and get reminders for campus events from their phones.”

Building the Product Backlog

The Product Owner lists and orders user stories like “view upcoming events by date” and “search events by keyword,” sorted by value and risk.

Sprint Planning and Sprint Goal

For a 2-week Sprint, the team sets a Sprint Goal: “Students can browse upcoming events.” They select top PBIs and break them into tasks in the Sprint Backlog.

Working Through the Sprint

At each Daily Scrum, Developers inspect progress and adapt their plan. When they hit API issues, they negotiate with the PO to drop a lower-priority PBI but still meet the Sprint Goal.

Review and Retrospective

In the Sprint Review, they demo the increment and capture feedback as new PBIs. In the Retrospective, they improve their process by enhancing the Definition of Done.

Deep Dive: Product Backlog Management and Prioritization

Product Backlog Definition

The product backlog is an ordered list of everything known to be needed in the product, managed by the Product Owner. It is the single source of work for the Scrum Team.

PO’s Accountability

The Product Owner keeps the backlog transparent and orders it to maximize value, making final decisions on what comes first after consulting stakeholders.

Value vs Technical Convenience

Scrum prefers prioritizing by business value and risk reduction, not by what is easiest technically or keeps every specialist maximally utilized.

Backlog Refinement

Backlog refinement clarifies and splits items, especially high-priority ones, so they are ready for upcoming Sprints. Requirements detail grows iteratively over time.

Daily Scrum, Definition of Done, and Quality in Scrum

Daily Scrum Purpose

The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt their plan. It is not a status meeting for managers.

Daily Scrum Anti-Pattern

If the Daily Scrum is described as reporting to the Scrum Master or a manager, that conflicts with Scrum. Developers talk to each other to plan the next 24 hours.

Definition of Done Basics

The Definition of Done is the commitment for the Increment. It is the shared standard for when work is complete, including quality and integration checks.

DoD and Quality

A clear DoD prevents partially done work from being labeled “done” and reduces late integration problems. Teams can strengthen the DoD as they improve.

Thought Exercise: Choosing Scrum vs Predictive

Apply your understanding of when Scrum (adaptive) is appropriate.

Scenario A

A government agency is building a compliance reporting system. Regulations are fixed and detailed. The contract requires a fully specified scope, and changes will be expensive to negotiate.

Scenario B

A startup is creating a new AI-based study assistant app. The founders have a vision but are unsure which features students will actually use. They want to release early and learn from real usage.

Scenario C

A construction project is building a campus library. Structural design and safety codes are strict. Some interior design elements (like study room features) can evolve.

Your task

For each scenario, decide:

Primarily predictive, Scrum/adaptive, or hybrid?

Explain your reasoning in 1–2 sentences each.

Sample reasoning guide (do this in your own words):

Look at requirement stability: Are they well-known and unlikely to change?
Consider uncertainty and innovation: Is experimentation encouraged or required?
Assess cost of change: Is it cheap to pivot (software features) or very expensive (physical structures)?

After you answer, compare mentally to this reference thinking:

Scenario A leans predictive due to fixed regulations and costly changes.
Scenario B strongly favors Scrum/adaptive due to high uncertainty and need for early feedback.
Scenario C may be hybrid: predictive for structural work, adaptive for evolving interior features.

Use this pattern-recognition skill during CAPM questions that ask you to select the appropriate life cycle.

Quiz 1: Scrum Roles and Events

Test your understanding of Scrum accountabilities and events.

In a Scrum Team, who is primarily accountable for ordering the product backlog to maximize value, and what is the primary purpose of the Daily Scrum?

The Scrum Master; to collect status updates for management
The Product Owner; to let Developers inspect progress toward the Sprint Goal and adapt their plan
The most senior stakeholder; to approve scope changes during the Sprint
The Developers; to re-estimate all Product Backlog Items every day

Show Answer

Answer: B) The Product Owner; to let Developers inspect progress toward the Sprint Goal and adapt their plan

The Product Owner manages and orders the product backlog to maximize value. The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt their plan, not a status meeting for management or a daily re-estimation session.

Quiz 2: Artifacts, Commitments, and Quality

Check your grasp of Scrum artifacts and quality controls.

A Scrum Team frequently discovers that items marked as 'done' require significant rework after Sprint Review. Which Scrum concept should they strengthen first to address this problem?

The Product Goal, so long-term vision is clearer
The Definition of Done, so everyone shares a clear standard of completeness
The Sprint Goal, so the team has a single objective each Sprint
The acceptance criteria, so the Product Owner can change scope mid-Sprint