AgilePM Foundation · Domain 2 of 10

AgilePM Foundation Domain 2: Scrum overview

AgilePM v3 uses Scrum as its product delivery engine, so you need the Scrum values, accountabilities, events, artefacts and commitments exactly, plus the empirical theory that makes iterative, incremental delivery work.

Exam weight estimate
Not published
Official syllabus topics
3
Estimated questions estimate
~5
Suggested study time estimate
3–4 hrs

About 14 min read Reviewed October 2026

Overview

Scrum overview reflects a new emphasis in AgilePM v3, which adopted Scrum as the engine that builds the product inside an AgilePM project. The area covers the five Scrum values (commitment, focus, openness, respect and courage), the three accountabilities (Product Owner, Scrum Master and Developers), and the five events: the Sprint itself, Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective.

It then covers the three artefacts and the commitment attached to each: the Product Backlog with the Product Goal, the Sprint Backlog with the Sprint Goal, and the Increment with the Definition of Done. Finally it explains why this works: Scrum rests on empiricism (transparency, inspection and adaptation) and lean thinking, so each short Sprint produces a usable Increment that is inspected and used to adapt the next step. Later areas connect these pieces to AgilePM planning, roles and governance.

How it's tested

Questions are short recall and understanding items built on Scrum Guide terms: which accountability does what, the purpose or timebox of an event, which commitment belongs to which artefact, and which empirical pillar a practice supports. Distractors borrow real Scrum words and attach them to the wrong thing, so precise pairing is the skill.

  • Match the pairing

    You pair an artefact with its commitment, an event with its purpose, or a responsibility with the accountability that owns it.

  • Purpose of an event

    A short situation in a Sprint is described and you identify which event addresses it, such as inspecting the Increment with stakeholders at the Sprint Review.

  • Empirical pillar

    A practice is described and you name the pillar it serves: transparency, inspection or adaptation.

Reasoning it through

A question asks which event exists to inspect how the last Sprint went for individuals, interactions, processes, tools and the Definition of Done. The Sprint Review is tempting because it also inspects, but it inspects the outcome and the product with stakeholders. Improving the way the team works is the Sprint Retrospective's purpose, so that is the answer. Separate product inspection from process inspection.

Syllabus topics 3

Official syllabus topics from the APMG International outline, in outline order.

2.1 Scrum values, roles and eventsFive values, three accountabilities and five events, with their purposes.
What it means
The values are commitment, focus, openness, respect and courage. The Scrum Guide calls the roles accountabilities: the Product Owner maximises product value and manages the Product Backlog, the Scrum Master establishes Scrum and the team's effectiveness, and the Developers create a usable Increment each Sprint. The events are the Sprint, Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective.
What to understand
The Sprint is a fixed-length container of one month or less that holds the other four events. The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal, not a report to a manager. The Product Owner is one person, not a committee.
How it shows up
A situation is described and you choose who is accountable, which event fits, or which value is being shown or ignored.
Common confusion
Treating the Scrum Master as the team's manager or the person who assigns tasks; the Scrum Master is a servant leader accountable for Scrum's effectiveness.
2.2 Scrum artefacts and commitmentsProduct Backlog, Sprint Backlog and Increment, each with its commitment.
What it means
The Product Backlog is the ordered list of what is needed to improve the product, and its commitment is the Product Goal. The Sprint Backlog is the Sprint Goal plus the selected items and the plan to deliver them. The Increment is a usable step toward the Product Goal, and its commitment is the Definition of Done.
What to understand
Each commitment gives its artefact a focus to measure progress against. Work that does not meet the Definition of Done is not part of the Increment and cannot be presented at the Sprint Review as done.
How it shows up
You pair an artefact with its commitment, or decide whether partly finished work counts as part of the Increment.
Common confusion
Attaching the Sprint Goal to the Product Backlog, or naming a 'Definition of Ready' as an official Scrum commitment.
2.3 How Scrum theory underpins iterative, incremental deliveryEmpiricism and lean thinking as the basis for short feedback cycles.
What it means
Scrum is founded on empiricism, which says knowledge comes from experience and decisions are made on what is observed, and on lean thinking, which reduces waste and focuses on essentials. Its three pillars are transparency, inspection and adaptation.
What to understand
Iterative means revisiting and refining the solution through repeated cycles; incremental means delivering it in usable pieces. Each Sprint does both: it builds an Increment and uses inspection of that Increment to adapt the plan and the product.
How it shows up
A practice such as a visible board or a review with stakeholders is described and you identify the pillar or the iterative and incremental benefit it supports.
Common confusion
Using iterative and incremental as synonyms; one is about refining through repetition and the other about delivering in pieces.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Five Scrum values

    Commitment, focus, openness, respect and courage guide how the Scrum Team behaves and make the empirical pillars work in practice.

    Remember
    Exactly five values; distractors add words such as 'transparency', which is a pillar, not a value.
    Tested as
    Recall items and behaviour-matching items ask which value is shown.
    Trap
    Confusing the values with the three pillars of empiricism.

  • Three accountabilities

    The Scrum Team is one Product Owner, one Scrum Master and Developers, with no sub-teams or hierarchies inside it.

    Remember
    The Product Owner is one person, accountable for the Product Backlog even if others help maintain it.
    Tested as
    Who-does-what questions and questions linking Scrum roles to AgilePM roles.
    Trap
    Choosing a committee or the Scrum Master as owner of backlog ordering.

  • The Sprint

    The Sprint is a fixed-length event of one month or less that contains all the other events and produces at least one usable Increment.

    Remember
    A new Sprint starts immediately after the previous one ends; the Sprint Goal is not changed in ways that endanger it.
    Tested as
    Basis for timebox and planning questions in later areas.
    Trap
    Thinking the Sprint can be extended to finish work; its length is fixed.

  • Daily Scrum

    A 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog for the next day.

    Remember
    It belongs to the Developers and is about the Sprint Goal, not a status meeting for managers.
    Tested as
    Event-purpose questions.
    Trap
    Describing it as a report to the Scrum Master or project manager.

  • Sprint Review vs. Retrospective

    The Review inspects the outcome and the Increment with stakeholders and discusses what to do next; the Retrospective plans ways to improve quality and effectiveness of how the team works.

    Remember
    Review is about the product, Retrospective is about the process and the team.
    Tested as
    A frequent pairing question.
    Trap
    Picking the Review for a process-improvement scenario.

  • Product Goal

    The Product Goal is the commitment for the Product Backlog: the long-term objective the Scrum Team is working toward.

    Remember
    Product Backlog pairs with the Product Goal.
    Tested as
    Artefact-commitment pairing.
    Trap
    Pairing the Product Backlog with the Sprint Goal.

  • Sprint Goal

    The Sprint Goal is the commitment for the Sprint Backlog: the single objective for the Sprint, created in Sprint Planning.

    Remember
    It gives the Developers flexibility over the exact work while keeping a fixed objective.
    Tested as
    Artefact-commitment and Sprint Planning questions.
    Trap
    Treating the Sprint Goal as a list of every selected item.

  • Definition of Done

    The Definition of Done is the commitment for the Increment: a formal description of the quality state an item must reach to be part of it.

    Remember
    Work not meeting it is not part of the Increment and returns to the Product Backlog for future consideration.
    Tested as
    Quality and transparency questions.
    Trap
    Presenting 'nearly done' work at the Sprint Review as complete.

  • Empiricism: transparency, inspection, adaptation

    Scrum's three pillars: make work and progress visible, inspect artefacts and progress frequently, and adapt as soon as a deviation is found.

    Remember
    Inspection without transparency is misleading, and inspection without adaptation is pointless.
    Tested as
    Pillar-matching questions.
    Trap
    Listing 'collaboration' or 'commitment' as a pillar.

  • Iterative vs. incremental

    Iterative development refines the solution through repeated cycles and feedback; incremental delivery releases it in usable pieces that add value.

    Remember
    Scrum and AgilePM do both at once.
    Tested as
    Theory questions and lifecycle questions in other areas.
    Trap
    Treating them as the same word.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Artefacts and their commitments

ConceptMeaningKey differenceCommon trap
Product Backlog Ordered list of what is needed to improve the product Commitment is the Product Goal (long-term objective) Pairing it with the Sprint Goal
Sprint Backlog Sprint Goal, selected items and the plan for the Sprint Commitment is the Sprint Goal (this Sprint's objective) Thinking it is fixed once Sprint Planning ends
Increment Usable step toward the Product Goal Commitment is the Definition of Done (quality standard) Counting work that does not meet the Definition of Done

Sprint Review vs. Sprint Retrospective vs. Daily Scrum

ConceptMeaningKey differenceCommon trap
Sprint Review Inspect the Increment and outcome with stakeholders Product focus; adapts the Product Backlog Treating it as a sign-off gate only
Sprint Retrospective Plan improvements to how the team works Process and team focus; held after the Review Using it to re-demonstrate the product
Daily Scrum Developers inspect progress toward the Sprint Goal 15 minutes, daily, owned by the Developers Running it as a status report to a manager

Product Owner vs. Scrum Master

ConceptMeaningKey differenceCommon trap
Product Owner Maximises the value of the product Accountable for the Product Backlog and its ordering Thinking a committee can share the accountability
Scrum Master Establishes Scrum and the team's effectiveness Coaches and removes impediments; does not assign work Treating the role as the team's manager

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Scrum Master as manager

    What candidates pick
    The Scrum Master assigns tasks to Developers to meet the Sprint Goal.
    Why it looks right
    Many organisations use the title for a coordinator or team lead.
    Why it's wrong
    Developers plan and self-manage the Sprint Backlog; the Scrum Master coaches, facilitates and removes impediments.

    Clue to watch for Any option where the Scrum Master directs or allocates work.

  2. Extending the Sprint

    What candidates pick
    Lengthen the Sprint by a few days so the planned work can be finished.
    Why it looks right
    It seems to protect the Sprint Goal.
    Why it's wrong
    Sprints are fixed length; unfinished work returns to the Product Backlog and the next Sprint begins on schedule.

    Clue to watch for A scenario where work is late near the end of the Sprint.

  3. Definition of Ready as a commitment

    What candidates pick
    The Definition of Ready as the commitment for the Product Backlog.
    Why it looks right
    Many teams use one, and it sounds official next to the Definition of Done.
    Why it's wrong
    The Scrum Guide's three commitments are the Product Goal, the Sprint Goal and the Definition of Done.

    Clue to watch for A question asking for the official commitment of an artefact.

  4. Review for process problems

    What candidates pick
    Raise a team communication problem at the Sprint Review.
    Why it looks right
    The Review is an inspection event and stakeholders are present.
    Why it's wrong
    Improving how the team works is the purpose of the Sprint Retrospective; the Review inspects the product outcome.

    Clue to watch for The issue concerns how the team works, not what it built.

  5. Transparency as a value

    What candidates pick
    Transparency listed among the five Scrum values.
    Why it looks right
    Transparency is central to Scrum and sounds like a value.
    Why it's wrong
    Transparency is one of the three empirical pillars; the values are commitment, focus, openness, respect and courage.

    Clue to watch for A list question mixing values and pillars.

  6. Product Owner by committee

    What candidates pick
    A steering group acting jointly as Product Owner.
    Why it looks right
    Projects often have many senior stakeholders.
    Why it's wrong
    The Product Owner is one person; others can influence the backlog through that person.

    Clue to watch for Several people described as jointly owning backlog decisions.

Answer framework

Use these steps when a question uses Scrum terms inside an AgilePM context.

  1. Translate the question into Scrum Guide vocabulary and decide whether it is about a value, an accountability, an event, an artefact or a pillar.
  2. For artefacts, recall the fixed pairings: Product Backlog with Product Goal, Sprint Backlog with Sprint Goal, Increment with Definition of Done.
  3. For events, separate product inspection (Sprint Review) from process improvement (Retrospective) and daily progress toward the Sprint Goal (Daily Scrum).
  4. For accountabilities, reject any option where the Scrum Master manages or assigns work or where the Product Owner is a committee.
  5. Check the option against empiricism: the correct answer keeps work transparent, inspects it frequently and adapts quickly, without extending fixed timeboxes.

Practice question

Near the end of a Sprint, Developers have coded a feature but have not completed the testing their team agreed every item must pass. Which Scrum commitment decides whether the feature can be presented as part of the Increment at the Sprint Review?

Want more like this? The AgilePM Foundation practice test has questions for every domain.

Checklist

0 of 11

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Learn this area as a set of fixed pairings. Make a single table with four columns (values, accountabilities, events, artefacts with commitments) and test yourself until you can fill it from memory. Most marks come from pairing the right term with the right purpose, so recall precision matters more than depth.

Prioritise the artefact-commitment pairs and the purpose of each event, especially the difference between the Sprint Review and the Retrospective, because these produce the most plausible distractors. Then learn the theory in one sentence each: empiricism, the three pillars, lean thinking, and iterative versus incremental.

If you already use Scrum at work, the underestimated risk is your own habits. Check every assumption against the Scrum Guide's wording: Daily Scrums are for the Developers, Sprints are not extended, and there is no official Definition of Ready.

Afterwards, study individuals and interactions to see how the Product Owner and Scrum Master relate to AgilePM's project roles, then planning and control to see how Sprints fit into AgilePM's planning levels. Finish with a timed set of short Scrum questions.

FAQ

Why is Scrum in the AgilePM syllabus?

AgilePM v3 adopted Scrum as its product delivery engine, so the project framework now assumes delivery teams work in Sprints with Scrum accountabilities, events and artefacts.

Do I need to know the Scrum Guide in detail?

You need the core terms precisely: values, accountabilities, events, artefacts, commitments and the empirical pillars. Detailed Scrum Master stances or scaling patterns are beyond what this area lists.

Are Scrum roles and AgilePM roles the same?

No. Scrum's accountabilities work at the team level, while AgilePM adds project-level roles for governance and business direction. The individuals and interactions area covers how they relate.

How long is a Sprint?

One month or less, and fixed for each Sprint. Shorter Sprints give more frequent feedback and reduce risk.

What is the difference between the Sprint Goal and the Product Goal?

The Product Goal is the long-term objective and the commitment for the Product Backlog. The Sprint Goal is the single objective for one Sprint and the commitment for the Sprint Backlog.

Is a Definition of Ready part of Scrum?

Not in the Scrum Guide. Teams may use one, but the official commitments are the Product Goal, the Sprint Goal and the Definition of Done.

How many questions does Scrum overview carry?

APMG publishes no per-area counts. An even split of 50 questions over ten areas suggests about five, as a planning estimate only.

Other Project Management certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 2 knowledge

You have covered Scrum's values, accountabilities, events, artefacts and commitments and the empirical theory behind them. Check that you can pair each one correctly under time pressure.

Take the AgilePM Foundation practice test Check your AgilePM Foundation readiness

Keep going