PSM I overview

  • 197 practice questions
  • 32 flashcards
  • 5 study guide topics
  • 35 key terms

What you'll study

  • Scrum Theory and Empiricism15%
  • The Scrum Team and its Accountabilities25%
  • Scrum Events25%
  • Scrum Artifacts and Commitments20%
  • Scrum Rules, Application and Organizational Context15%

The Professional Scrum Master I (PSM I) is an entry-level credential that assesses whether you understand Scrum as defined in the Scrum Guide and can apply it to real team situations. It is aimed at Scrum Masters, but product people, developers, managers and coaches often take it to establish a shared vocabulary before working in or alongside Scrum teams. The assessment is knowledge-based rather than experience-certified: it tests your grasp of Scrum theory and empiricism, the accountabilities of the Scrum Team, the events and their timeboxes, the artifacts and their commitments, and how the framework holds up against common organizational pressure to compromise it. Expect questions that reward precise reading of the Scrum Guide rather than pattern-matched buzzwords - several items hinge on distinguishing what Scrum requires from what is merely common practice. To prepare, read the current Scrum Guide closely and more than once, then work through the official and open assessments until you can explain, in your own words, why each rule exists. Wherever a candidate wants scheduling, pricing or scoring details, the certifying body publishes the current figure on its own site - always confirm there, since these logistics change.

Common mistakes

When a scenario says the team learns mid-Sprint that it cannot meet the Sprint Goal, the candidate answers 'finish the Sprint exactly as planned and review it at the Sprint Review' instead of adapting.

Prior waterfall/contract-style experience frames the Sprint as a fixed-scope commitment with a change freeze until the next formal meeting.

What to do instead

Memorise the empiricism loop: transparency surfaces the new information, the team inspects, and it adapts the Sprint Backlog immediately. The Sprint Goal is fixed for the Sprint, but scope may be renegotiated with the Product Owner as more is learned; cancelling is a last resort and only when the Sprint Goal becomes obsolete.

On questions about a surprise, a missed expectation, or a stakeholder complaint, the candidate picks 'adapt' or 'inspect' as the answer without first identifying what was not visible, e.g. answering 'the team should inspect more often' when nobody had raised the issue at all.

The three pillars are memorised as vocabulary rather than as a sequence, so any scenario containing the word 'problem' triggers the same keyword.

What to do instead

Diagnose the missing pillar first: if the relevant information never surfaced to the right people, the failure is transparency; if it surfaced and was ignored, inspection; if it was understood and nothing changed, adaptation. Most 'we didn't know until the end' scenarios are transparency failures, not inspection-frequency failures.

Answers accountability questions by assigning commitments to the wrong role, e.g. 'the Product Owner is accountable for the Sprint Goal', 'the Scrum Master owns the Product Backlog', or 'the Developers own the Product Goal'.

The three artifacts, their three commitments and their accountabilities are learned as two separate lists and get cross-wired under time pressure.

What to do instead

Memorise one chain and reconstruct the rest from it: Product Backlog -> Product Goal -> Product Owner; Sprint Backlog -> Sprint Goal -> Developers; Increment -> Definition of Done -> Developers. Say the chain out loud before answering any 'who owns X' question.

Treats the Scrum Master as a team lead, status collector or people manager, choosing answers like 'the Scrum Master assigns the work items' or 'the Scrum Master decides when the team is done'.

The job title is imported from previous organisations where 'Scrum Master' was a line-management or project-coordination role.

What to do instead

Anchor on the two services the Scrum Master actually provides (to the Scrum Team and to the organisation) and on the phrase 'true leader who serves'. The Scrum Master coaches, facilitates, teaches and removes impediments, but the answers never have the Scrum Master deciding content or assigning work.

Describes the Sprint Review as a demo or an approval gate ('the stakeholders sign off the Increment') and describes the Sprint Retrospective as something to skip when the team is busy or the Sprint went well.

Stage-gate and project-sign-off habits, plus a belief that ceremonies are optional overhead rather than required elements of the framework.

What to do instead

Learn each event as purpose first, mechanics second. Sprint Review: inspect the outcome, determine future adaptations, collaborate with stakeholders - it is a working session, not a presentation or a gate. All five events are required; the Retrospective is where inspection of the team's own process happens and is the last thing to drop, never the first.

States the Daily Scrum must use the three questions, must be held standing up, and that the Scrum Master must run it, then rules out answers where the Developers change the format or where the Scrum Master is absent.

Many teams inherited a rigid Daily Scrum script, and the exam questions using 'the team wants to change the format' look like a violation of the rules.

What to do instead

The Daily Scrum is for the Developers, is timeboxed to 15 minutes, and its structure and technique are chosen by the Developers. The three questions are one optional technique. The Scrum Master ensures the event happens and stays within the timebox, but does not have to run it and can be absent.

Answers that the Definition of Done is whatever the Scrum Team invents, and rejects answers where an organisational standard constrains the team's definition.

The phrase 'the Scrum Team creates the Definition of Done' is remembered, but the qualifier about organisational standards is not.

What to do instead

If an organisational Definition of Done exists, all teams must follow it as a minimum; a team may add stricter criteria but may not weaken it. Only when no organisational standard exists does the Scrum Team create one. Work that does not meet the Definition of Done is not an Increment and returns to the Product Backlog.

Says the team must release at the end of every Sprint, or that there is exactly one Increment per Sprint, and eliminates answers that describe several Increments being created within a single Sprint.

Release and Increment are treated as synonyms, and 'potentially releasable' is misread as 'must be released'.

What to do instead

Separate the two ideas: an Increment is created whenever a Sprint Backlog item meets the Definition of Done, so several can exist within one Sprint. Releasing is a separate business decision owned by the Product Owner and is not mandated by Scrum. An Increment is a concrete stepping stone toward the Product Goal.

Accepts extensions or early termination too freely, e.g. 'the Sprint can be extended by a few days to finish testing' or 'the Scrum Master or the stakeholders can cancel the Sprint'.

Intuition says a fixed-length Sprint should flex when work is nearly done, and cancellation sounds like a management call.

What to do instead

Two hard rules to recall verbatim: the Sprint is a fixed-length event of one month or less whose duration never changes, and only the Product Owner may cancel a Sprint. Cancellation happens only when the Sprint Goal becomes obsolete, and completed items are reviewed for release.

Assumes Scrum prescribes co-location, a particular tool or board, story points, or adoption of a named scaling framework, and picks answers that mandate those as part of 'doing Scrum correctly'.

Candidates generalise from their own organisation's implementation and from Agile-branded practices that are not part of the Scrum framework.

What to do instead

Treat Scrum as a lightweight framework that defines only the accountabilities, events, artifacts and rules - not techniques, tooling, metrics, or scaling methods. If an answer adds a mandated practice that the framework never specifies, it is almost always wrong.

Exam requirements can change. Confirm current details with the exam provider.

PSM I practice

197 questions. Each one lists the choices, the correct answer, and an explanation. With JavaScript, this list opens one question at a time. The checker at the top of this page saves progress in this browser when it is available.

  1. Question 1Scrum Theory and Empiricism

    What does empiricism mean in the context of Scrum?

    1. Knowledge comes from following a defined process that eliminates all variation
    2. Knowledge comes from senior management forecasts and market analysis
    3. Knowledge comes from detailed up-front documentation agreed by the stakeholders
    4. Knowledge comes from experience, and decisions are based on what is observed Correct answer.

    Explanation

    Empiricism holds that knowledge comes from experience and that decisions should be based on observation. Scrum applies this by working in small increments, so that what is actually observed informs the next decision.

  2. Question 2Scrum Theory and Empiricism

    Which three pillars underpin every implementation of Scrum?

    1. Commitment, focus and respect
    2. Planning, executing and controlling
    3. Transparency, inspection and adaptation Correct answer.
    4. Analysis, design and delivery

    Explanation

    The Scrum Guide names transparency, inspection and adaptation as the three pillars of empirical process control. All three must be present for Scrum to work as intended.

  3. Question 3Scrum Theory and Empiricism

    Which set lists the five Scrum values?

    1. Commitment, focus, openness, respect and courage Correct answer.
    2. Planning, courage, respect, focus and quality
    3. Openness, respect, quality, commitment and delivery
    4. Courage, transparency, commitment, focus and trust

    Explanation

    The five Scrum values are commitment, focus, openness, respect and courage. Teams that live these values build the trust needed for the pillars of empiricism to function.

  4. Question 4Scrum Theory and Empiricism

    Scrum is founded on which approach to controlling work?

    1. Stage-gate control based on formal sign-off at each phase
    2. Statistical process control based on eliminating all variation
    3. Empirical process control based on observation and adaptation Correct answer.
    4. Predictive process control based on detailed up-front planning

    Explanation

    Scrum is founded on empirical process control, in which decisions are made on what is observed rather than on a detailed prediction. Predictive and stage-gate approaches assume the future can be planned accurately in advance.

  5. Question 5Scrum Theory and Empiricism

    How does the Scrum Guide describe Scrum?

    1. A detailed methodology that prescribes every activity the team performs
    2. A lightweight framework for adaptive solutions to complex problems Correct answer.
    3. A software development lifecycle model with defined phases
    4. A project management method focused on fixed scope and deadlines

    Explanation

    The Scrum Guide defines Scrum as a lightweight framework that helps people, teams and organisations generate value through adaptive solutions for complex problems. It deliberately leaves the choice of techniques to the people using it.

  6. Question 6Scrum Theory and Empiricism

    What does transparency mean in Scrum?

    1. The process and the work are visible to those doing and receiving it Correct answer.
    2. All stakeholders can access the source code and the documentation at any time
    3. Every meeting is recorded and published to the whole organisation
    4. The Product Owner reports progress to senior management every week

    Explanation

    Transparency means the emergent process and the work are visible to those performing it and those receiving it. It requires a shared standard so that everyone interprets what they see in the same way.

  7. Question 7Scrum Theory and Empiricism

    Which statement best describes inspection as a Scrum pillar?

    1. It removes the need for adaptation once the Increment is accepted
    2. It should happen only once, at the end of the project
    3. It is carried out exclusively by people outside the Scrum Team
    4. It should be frequent enough to detect variance promptly Correct answer.

    Explanation

    Inspection is the regular examination of artefacts and of progress toward agreed goals. The Scrum Guide advises that it be frequent enough to detect undesirable variances, but not so frequent that it interferes with the work.

  8. Question 8Scrum Theory and Empiricism

    Which statement best describes adaptation in Scrum?

    1. It happens when a deviation puts the result outside acceptable limits Correct answer.
    2. It is performed by the PMO after each release goes live
    3. It is unnecessary when the plan was approved by the stakeholders
    4. It is permitted only at the start of a new fiscal year

    Explanation

    Adaptation is the adjustment of the process or of the produced work when inspection reveals that one or more aspects deviate outside acceptable limits. Adjustments should be made as soon as possible to limit further deviation.

  9. Question 9Scrum Theory and Empiricism

    At a Sprint Review, users say a new feature solves the wrong problem, and the team revises the Product Backlog in response. Which pillar does this response most directly represent?

    1. Self-management, because the team chose the change itself
    2. Inspection, because the feature was demonstrated at the event
    3. Adaptation, because the team adjusts based on what it learned Correct answer.
    4. Transparency, because the feature was shown to the users

    Explanation

    The demonstration is inspection, and acting on the feedback by changing course is adaptation. Scrum keeps these close together so that adjustments happen while they are still inexpensive.

  10. Question 10Scrum Theory and Empiricism

    Why must transparency in Scrum rest on a common standard?

    1. So that the Definition of Done never has to change
    2. So that managers can compare different teams using identical productivity metrics
    3. So that the team does not need to document its work at all
    4. So that people inspecting the work reach the same understanding of it Correct answer.

    Explanation

    Transparency is only useful when everyone shares the same standard for what they are seeing; otherwise observers draw different conclusions from the same facts. Scrum uses the artefacts and the Definition of Done to provide that shared standard.

  11. Question 11Scrum Theory and Empiricism

    The Scrum Guide describes Scrum as intentionally incomplete. What does that mean in practice?

    1. Teams must add missing roles before they can begin using Scrum
    2. Teams fill the gaps with practices that suit their context Correct answer.
    3. Teams must obtain approval before changing any part of the framework
    4. Teams must apply every prescribed practice exactly as written

    Explanation

    The Scrum Guide defines only the parts of Scrum needed to implement its theory, leaving the rest open. Teams are expected to fill the gaps with practices, techniques and tools that fit their context.

  12. Question 12Scrum Theory and Empiricism

    Which activity most directly demonstrates the inspection pillar?

    1. The Developers updating the Sprint Backlog during the day
    2. The Scrum Team examining the Increment at the Sprint Review Correct answer.
    3. The Scrum Master coaching the team on the Scrum values
    4. The Product Owner ordering the Product Backlog by value

    Explanation

    The Sprint Review is the formal event in which the Scrum Team and stakeholders inspect the Increment and progress toward the Product Goal. That inspection then informs adaptation of the Product Backlog.

  13. Question 13Scrum Theory and Empiricism

    What does it mean that the Scrum Team is cross-functional?

    1. Members rotate into the Product Owner role on a regular schedule
    2. The team includes at least one member from every department in the organisation
    3. Members together hold the skills needed to create value each Sprint Correct answer.
    4. Each member is trained to perform every team role equally well

    Explanation

    Cross-functional means the team as a whole has all the competencies needed to create value in every Sprint. It does not require every individual to be able to perform every job.

  14. Question 14Scrum Theory and Empiricism

    Which statement describes a self-managing Scrum Team?

    1. A team that is accountable to no one outside the team
    2. A team whose line manager assigns tasks and reviews every decision
    3. A team that sets its own budget without reference to the organisation
    4. A team that decides internally who does what, when and how Correct answer.

    Explanation

    A self-managing team has the authority to decide internally how to do its work: who does what, when and how. It remains accountable to the organisation and to the Product Owner for the value it creates.

  15. Question 15Scrum Theory and Empiricism

    Why does Scrum timebox its events?

    1. To let managers compare the velocity of different teams across the organisation
    2. To create regularity and limit the cost of inspection and adaptation Correct answer.
    3. To guarantee that no work carries over between Sprints
    4. To remove the need to estimate items in the Product Backlog

    Explanation

    Timeboxes impose a regular rhythm, so the team inspects and adapts on a predictable cadence. They also cap the effort spent on any single event so that inspection and adaptation do not consume the work itself.

  16. Question 16Scrum Theory and Empiricism

    Stakeholders cannot tell whether the Increment is finished or not. Which pillar is most weakened?

    1. Transparency, because the work's state is not understood Correct answer.
    2. Focus, because the team is distracted by feedback
    3. Adaptation, because the team cannot change its plan
    4. Inspection, because reviews are scheduled too often

    Explanation

    Transparency requires that the state of the work be visible and understood by those receiving it. When completeness is unclear, any inspection is unreliable and adaptation rests on a false picture.

  17. Question 17Scrum Theory and Empiricism

    How do the three pillars of Scrum relate to one another?

    1. Adaptation enables inspection, and inspection enables control
    2. Transparency enables inspection, and inspection enables adaptation Correct answer.
    3. Transparency enables adaptation, and adaptation enables inspection
    4. Inspection enables transparency, and transparency enables planning

    Explanation

    Transparency makes the work visible, which allows meaningful inspection; inspection then reveals what must change, enabling adaptation. Weakening any one pillar undermines the other two.

  18. Question 18Scrum Theory and Empiricism

    A Scrum Team changes direction every few days but rarely examines the Increment. How should this be described in empiricist terms?

    1. Appropriate self-management, because the team chooses its own direction
    2. Inspection without transparency, because the Increment stays hidden
    3. Healthy adaptation, because responding to change is the goal of Scrum
    4. Adaptation without inspection, so changes lack an observed basis Correct answer.

    Explanation

    Empiricism links the pillars in order: observation informs inspection, and inspection informs adaptation. Changing course without inspecting actual results produces guesses rather than evidence-based decisions.

  19. Question 19Scrum Theory and Empiricism

    For which type of work is Scrum designed?

    1. Complex problems where needs and technology keep changing Correct answer.
    2. Regulated work where the process must never vary between runs
    3. Simple problems where every step can be predicted in advance
    4. Routine production where variation must be eliminated entirely

    Explanation

    Scrum was designed for complex work, where more is unknown than known at the outset and requirements emerge over time. For such work, empirical control is more effective than trying to predict everything in advance.

  20. Question 20Scrum Theory and Empiricism

    Transparency requires a shared standard for judging the work. Which element provides that standard for the Increment?

    1. The Definition of Done used by the Scrum Team Correct answer.
    2. The Product Goal recorded at the top of the Product Backlog
    3. The Sprint Goal agreed during Sprint Planning
    4. The Sprint Backlog owned by the Developers

    Explanation

    The Definition of Done is the Scrum Team's shared agreement of what it means for the Increment to be complete. Because everyone applies the same definition, observers of the work reach a common understanding.

  21. Question 21Scrum Theory and Empiricism

    A Scrum Team writes a detailed two-year plan and refuses to change it regardless of what it learns. Which empiricist principle is most directly violated?

    1. Inspecting the Increment at least once in every Sprint
    2. Using a shared standard agreed by everyone to judge completeness
    3. Keeping the work visible to the people who receive it
    4. Adapting to what is observed rather than to a fixed plan Correct answer.

    Explanation

    Empiricism bases decisions on observation, so a plan must change when what is observed contradicts it. Refusing to adapt turns the plan into a prediction that ignores the evidence.

  22. Question 22Scrum Theory and Empiricism

    A team holds a lively Sprint Retrospective every Sprint but never changes anything afterwards. Which pillar is missing?

    1. Adaptation, because no adjustments were made Correct answer.
    2. Authority, because the team met without its stakeholders
    3. Inspection, because no one reviewed the process
    4. Transparency, because the Retrospective was not documented

    Explanation

    The Retrospective is the event for inspecting how the last Sprint went; the value comes from the adaptations that follow. Without any adjustment, the inspection produces no change in how the team works.

  23. Question 23Scrum Theory and Empiricism

    Which statement about the Scrum values is accurate?

    1. They are enforced through a formal certification process
    2. They are optional guidelines that teams may adopt once they mature
    3. They replace transparency, inspection and adaptation
    4. They guide behaviour and build the trust the pillars depend on Correct answer.

    Explanation

    The five Scrum values shape how team members behave toward each other and toward the work. Living them builds the trust that allows transparency, inspection and adaptation to function.

  24. Question 24Scrum Theory and Empiricism

    Which practice best reflects the lean thinking that underpins Scrum?

    1. Adding detailed documentation for every design decision
    2. Maximising the number of features released in each Sprint
    3. Approving work through several management layers
    4. Doing only what is essential and removing waste Correct answer.

    Explanation

    Scrum draws on lean thinking, which focuses on reducing waste and keeping attention on what is essential. This shows up in short Sprints, a single ordered backlog and the deliberate exclusion of non-essential work.

  25. Question 25Scrum Theory and Empiricism

    Why does Scrum favour an iterative, incremental approach?

    1. It lets teams skip the Retrospective when time is short
    2. It removes the need for stakeholder involvement during the work
    3. It offers frequent chances to inspect and adapt real results Correct answer.
    4. It guarantees a predictable final delivery date for stakeholders

    Explanation

    Working in iterations produces usable Increments, which give the team and its stakeholders real results to inspect. Increments also limit risk, because each small addition can be adjusted before more is built on it.

  26. Question 26Scrum Theory and Empiricism

    Scrum is founded on empirical process control. Which statement best describes empiricism?

    1. Knowledge comes from experience, and decisions are based on what is observed. Correct answer.
    2. Knowledge comes from documentation, and decisions are traced back to signed requirements.
    3. Knowledge comes from thorough upfront analysis, and decisions follow the approved plan.
    4. Knowledge comes from seniority, and decisions are validated by the highest-ranking person.

    Explanation

    Empiricism holds that knowledge comes from experience and that decisions should be made on what is actually observed rather than on forecasts or assumptions. Scrum applies this by making work transparent, inspecting it frequently and adapting as findings emerge.

  27. Question 27Scrum Theory and Empiricism

    Which option correctly lists the five Scrum Values?

    1. Courage, respect, commitment, trust and openness
    2. Commitment, courage, focus, openness and respect Correct answer.
    3. Focus, openness, courage, respect and transparency
    4. Respect, focus, commitment, inspection and courage

    Explanation

    The five Scrum Values are commitment, courage, focus, openness and respect. Together they guide how the Scrum Team behaves and make the pillars of empiricism possible in practice.

  28. Question 28Scrum Theory and Empiricism

    A Scrum Team shortens its Sprint from four weeks to one week. What is the main empiricist benefit of this change?

    1. Undesirable variances are detected and corrected sooner. Correct answer.
    2. The Product Owner no longer needs to attend the Sprint Review.
    3. Less documentation is needed to satisfy the Definition of Done.
    4. The team completes more Product Backlog items each month.

    Explanation

    Empirical process control depends on inspecting often enough to catch problems early, and shorter Sprints put the team in front of the Increment more often. Deviations therefore surface while they are still cheap to correct.

  29. Question 29Scrum Theory and Empiricism

    Scrum asks for frequent inspection, yet warns against inspecting so often that it gets in the way of the work. Which statement best explains this guidance?

    1. Inspection is most effective as a single event that takes place once the product is finished and released.
    2. Inspection must be frequent enough to catch problems early, without disrupting the work itself. Correct answer.
    3. Inspection should be postponed until the end of the Sprint so that it never distracts the Developers from their work.
    4. Inspection delivers value only when the entire organization participates in every inspection session.

    Explanation

    Inspection exists to detect undesirable variances while they can still be corrected, so it has to happen often. The limit is practical: inspection that consumes more than it reveals slows the work it is meant to serve.

  30. Question 30Scrum Theory and Empiricism

    Scrum relies on empirical process control because of the nature of product development work. Which condition best explains that reliance?

    1. Progress is measured most accurately by comparing effort spent with the original plan.
    2. Requirements can be fully specified in advance if the analysis phase is thorough enough.
    3. What works is often only clear after the team tries something and observes the result. Correct answer.
    4. The same inputs reliably produce the same outputs, so variation can be controlled.

    Explanation

    In complex work the relationship between cause and effect is visible only in hindsight, so predictions are unreliable and must be replaced by observation of real results. Scrum builds short cycles so that each observation can inform the next decision.

  31. Question 31The Scrum Team and its Accountabilities

    According to Scrum, which set of accountabilities makes up a Scrum Team?

    1. One Scrum Master, one Product Owner, and a separate development team
    2. A Product Owner, a project manager, and Developers
    3. A Scrum Master, stakeholders, and Developers
    4. One Scrum Master, one Product Owner, and Developers Correct answer.

    Explanation

    A Scrum Team is a small team consisting of one Scrum Master, one Product Owner, and Developers. The Developers are the people in the team who create the Increment; there is no separate development team. These accountabilities together form one Scrum Team.

  32. Question 32The Scrum Team and its Accountabilities

    Which Scrum Team member is accountable for maximizing the value of the product resulting from the work of the Scrum Team?

    1. The Developers
    2. The stakeholders
    3. The Product Owner Correct answer.
    4. The Scrum Master

    Explanation

    The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. This is a single accountability, not one shared by a committee. The Product Owner achieves this through effective Product Backlog management.

  33. Question 33The Scrum Team and its Accountabilities

    What are Developers accountable for creating during each Sprint?

    1. The Scrum Master's coaching plan
    2. A stakeholder approval document
    3. The Product Goal
    4. A usable Increment that meets the Definition of Done Correct answer.

    Explanation

    Developers are accountable for creating any aspect of a usable Increment that meets the Definition of Done each Sprint. The Increment is the concrete result of their work. The Product Goal and coaching plan are not the Increment.

  34. Question 34The Scrum Team and its Accountabilities

    What is the Scrum Master accountable for?

    1. Creating the Increment
    2. Maximizing product value
    3. Ordering the Product Backlog
    4. The Scrum Team's effectiveness Correct answer.

    Explanation

    The Scrum Master is accountable for establishing Scrum and for the Scrum Team's effectiveness. This is done by enabling the team to improve its practices and by serving the team, Product Owner, and organization. The Scrum Master does not own product value, backlog ordering, or Increment creation.

  35. Question 35The Scrum Team and its Accountabilities

    What is the recommended maximum size of a Scrum Team?

    1. Ten or fewer people Correct answer.
    2. Twenty or fewer people
    3. Three people
    4. Five people

    Explanation

    Scrum recommends a Scrum Team of ten or fewer people. This size supports communication and self-management. If the team becomes too large, it should consider reorganizing into multiple cohesive Scrum Teams.

  36. Question 36The Scrum Team and its Accountabilities

    A self-managing Scrum Team means the team is responsible for...

    1. Avoiding all direction from outside the team
    2. Having no defined accountabilities
    3. Reporting to a project manager for daily decisions
    4. Deciding who does what, when, and how Correct answer.

    Explanation

    Self-management means the Scrum Team internally decides who does what, when, and how. This does not remove accountabilities or prevent interaction with the organization. It describes how the team organizes its own work.

  37. Question 37The Scrum Team and its Accountabilities

    Which statement describes a cross-functional Scrum Team?

    1. Working across departments without a Product Owner
    2. Sharing members with other teams to cover missing skills
    3. Including only people with a single specialty
    4. Having all skills needed to create value each Sprint Correct answer.

    Explanation

    A cross-functional Scrum Team has all the skills necessary to create value each Sprint. The team does not depend on people outside the team for essential skills. Cross-functionality supports the team's ability to deliver a usable Increment.

  38. Question 38The Scrum Team and its Accountabilities

    Which statement about the structure of a Scrum Team is correct?

    1. It is one team with no sub-teams or hierarchies Correct answer.
    2. It is led by a delivery manager above the Scrum Master
    3. It may have a separate testing team outside the Scrum Team
    4. It contains sub-teams for analysis, design, and testing

    Explanation

    A Scrum Team is one team with no sub-teams or hierarchies. The Scrum Master, Product Owner, and Developers are accountabilities within that single team. Creating internal sub-teams or outside reporting layers conflicts with Scrum's structure.

  39. Question 39The Scrum Team and its Accountabilities

    Who is required to participate in the Daily Scrum?

    1. Anyone interested in the team's progress
    2. Only the Scrum Master and Product Owner
    3. All stakeholders
    4. The Developers Correct answer.

    Explanation

    The Daily Scrum is an event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. Others may attend if useful, but they are not required participants. The event exists to support the Developers' daily planning.

  40. Question 40The Scrum Team and its Accountabilities

    Who is accountable for ordering the Product Backlog to maximize value?

    1. The Developers
    2. The stakeholders
    3. The Scrum Master
    4. The Product Owner Correct answer.

    Explanation

    The Product Owner is accountable for effective Product Backlog management, including ordering Product Backlog items. Ordering is done to maximize value and may involve input from others. The accountability remains with the Product Owner.

  41. Question 41The Scrum Team and its Accountabilities

    How does the Scrum Master serve the Product Owner?

    1. By approving the Product Owner's decisions with stakeholders
    2. By ordering the Product Backlog for the Product Owner
    3. By helping the Product Owner find techniques for effective Product Goal definition and Product Backlog management Correct answer.
    4. By taking over stakeholder communication when the Product Owner is busy

    Explanation

    The Scrum Master serves the Product Owner by helping with techniques for effective Product Goal definition and Product Backlog management. This includes helping establish emergent product planning and facilitating stakeholder collaboration. The Scrum Master supports the Product Owner without taking over the accountability.

  42. Question 42The Scrum Team and its Accountabilities

    During a Sprint, Developers report a repeated technical blocker. What is the Scrum Master's most appropriate action?

    1. Add the blocker to the Product Backlog and wait for prioritization
    2. Instruct the Developers to work around the blocker
    3. Ask the Product Owner to reassign the affected work
    4. Cause the impediment to be removed Correct answer.

    Explanation

    The Scrum Master serves the Scrum Team by causing impediments to be removed. A repeated technical blocker is an impediment to progress. The Scrum Master should help resolve it rather than simply recording it or reassigning the work.

  43. Question 43The Scrum Team and its Accountabilities

    Who is accountable for creating the Sprint Backlog?

    1. The stakeholders
    2. The Product Owner
    3. The Scrum Master
    4. The Developers Correct answer.

    Explanation

    The Developers are accountable for creating the Sprint Backlog. It is their plan for the Sprint and is updated as they learn more. The Product Owner and Scrum Master may collaborate, but they do not own the Sprint Backlog.

  44. Question 44The Scrum Team and its Accountabilities

    Which accountability belongs to Developers during the Sprint?

    1. Adapting their plan each day toward the Sprint Goal Correct answer.
    2. Approving the Product Goal with stakeholders
    3. Ordering the Product Backlog
    4. Facilitating the Sprint Retrospective

    Explanation

    Developers adapt their plan each day toward the Sprint Goal. They inspect progress and update the Sprint Backlog as needed. This daily adaptation is part of their accountability for delivering a usable Increment.

  45. Question 45The Scrum Team and its Accountabilities

    Who is accountable for creating a valuable, useful Increment every Sprint?

    1. The Scrum Master and Product Owner
    2. Only the Product Owner
    3. The whole Scrum Team Correct answer.
    4. Only the Developers

    Explanation

    The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint. Developers do the work of creating the Increment, while the Product Owner and Scrum Master contribute to the team's ability to deliver value. The accountability belongs to the whole Scrum Team.

  46. Question 46The Scrum Team and its Accountabilities

    Which statement about the Product Owner accountability is correct?

    1. It rotates among Developers each Sprint
    2. It may be shared by a committee of stakeholders
    3. It is held by one person, not a committee Correct answer.
    4. It is optional for small teams

    Explanation

    The Product Owner accountability is held by one person, not a committee. That person may represent the needs of many stakeholders but remains accountable for Product Backlog management. The role does not rotate by default or disappear for small teams.

  47. Question 47The Scrum Team and its Accountabilities

    Which action best reflects the Scrum Master serving the Scrum Team?

    1. Assigning daily tasks to the Developers
    2. Coaching the team in self-management and cross-functionality Correct answer.
    3. Approving which Product Backlog items are valuable
    4. Deciding the Sprint Goal for the team

    Explanation

    The Scrum Master serves the Scrum Team by coaching it in self-management and cross-functionality. This helps the team take ownership of its work and improve its effectiveness. The Scrum Master does not assign daily tasks, set the Sprint Goal alone, or approve backlog value.

  48. Question 48The Scrum Team and its Accountabilities

    What are Developers accountable for instilling in the product?

    1. Speed by shortening the Sprint timebox
    2. Profitability by selecting high-value items
    3. Quality by adhering to the Definition of Done Correct answer.
    4. Compliance by obtaining stakeholder sign-off

    Explanation

    Developers are accountable for instilling quality by adhering to the Definition of Done. The Definition of Done creates a shared understanding of what it means for work to be complete. Quality is built into the Increment rather than added through external sign-off.

  49. Question 49The Scrum Team and its Accountabilities

    A Scrum Team has grown to 15 people and coordination is difficult. What does Scrum suggest?

    1. Split into multiple cohesive Scrum Teams sharing the same Product Goal, Product Backlog, and Product Owner Correct answer.
    2. Keep one team but create internal sub-teams
    3. Reduce the Sprint length to one week to improve coordination
    4. Add a project manager to coordinate the work

    Explanation

    When a Scrum Team becomes too large, Scrum suggests reorganizing into multiple cohesive Scrum Teams. These teams should share the same Product Goal, Product Backlog, and Product Owner. Adding managers or internal sub-teams does not follow Scrum's team structure.

  50. Question 50The Scrum Team and its Accountabilities

    How does the Scrum Master serve the larger organization?

    1. By acting as the final decision-maker for product scope
    2. By removing barriers between stakeholders and Scrum Teams Correct answer.
    3. By assigning employees to Scrum Teams
    4. By managing budgets for all Scrum Teams

    Explanation

    The Scrum Master serves the organization by helping remove barriers between stakeholders and Scrum Teams. This is part of leading, training, and coaching the organization in its Scrum adoption. Budgets, product scope decisions, and staffing assignments are not Scrum Master accountabilities.

  51. Question 51The Scrum Team and its Accountabilities

    A Product Owner is frequently unavailable, and Developers begin making product decisions independently. Who remains accountable for maximizing product value?

    1. The Developers, because they are self-managing
    2. The Product Owner, because accountability cannot be delegated away Correct answer.
    3. The Scrum Master, because they coach the team
    4. The stakeholders, because they own the product

    Explanation

    The Product Owner remains accountable for maximizing product value even when unavailable or when work is delegated. Accountability for the Product Backlog cannot be transferred away. Developers may be self-managing in their work, but that does not make them accountable for product value.

  52. Question 52The Scrum Team and its Accountabilities

    Developers disagree about how to complete a Sprint Backlog item. Who decides how the work is done?

    1. The Developers decide as a self-managing team Correct answer.
    2. The Product Owner decides based on value
    3. The stakeholders decide through a vote
    4. The Scrum Master decides and assigns tasks

    Explanation

    Developers are self-managing and decide how to turn Product Backlog items into a usable Increment. Technical decisions about completing Sprint Backlog work belong to the Developers. The Product Owner decides value and ordering, while the Scrum Master coaches and serves.

  53. Question 53The Scrum Team and its Accountabilities

    A new Scrum Master wants to assign each Developer a daily task to ensure progress. What does Scrum say?

    1. This is required when the team is new to Scrum
    2. This is appropriate because the Scrum Master owns team effectiveness
    3. This undermines self-management; Developers decide who does what, when, and how Correct answer.
    4. This is appropriate if the Product Owner agrees

    Explanation

    Assigning daily tasks undermines the Developers' self-management. The Scrum Team internally decides who does what, when, and how. The Scrum Master supports the team's effectiveness through coaching and serving, not by acting as a task assigner.

  54. Question 54The Scrum Team and its Accountabilities

    Developers notice a teammate is not following the Definition of Done. According to Scrum, who is accountable for holding each other accountable?

    1. The Developers, as a self-managing team Correct answer.
    2. The Product Owner, by rejecting the Increment
    3. The Scrum Master, through performance reviews
    4. The stakeholders, through acceptance testing

    Explanation

    Developers are accountable for holding each other accountable as professionals. They are self-managing and jointly responsible for quality and adherence to the Definition of Done. The Scrum Master can coach the team, but does not enforce compliance through performance reviews.

  55. Question 55The Scrum Team and its Accountabilities

    A stakeholder asks the Scrum Master to add a high-priority item to the Product Backlog. What is the most appropriate response?

    1. Add it directly because the Scrum Master serves the organization
    2. Direct the stakeholder to the Product Owner, who is accountable for Product Backlog management Correct answer.
    3. Ask the Developers to add it during the Daily Scrum
    4. Reject it because stakeholders cannot influence the Product Backlog

    Explanation

    The Product Owner is accountable for effective Product Backlog management, including ordering and clarity. The Scrum Master should direct the stakeholder to the Product Owner rather than changing the Product Backlog directly. Stakeholders can and should provide input through the Product Owner.

  56. Question 56The Scrum Team and its Accountabilities

    Which statement about the size of a Scrum Team is accurate?

    1. It is set by the Scrum Master based on the size of the Product Backlog.
    2. It is typically ten or fewer people. Correct answer.
    3. It must contain between three and nine Developers, excluding the Scrum Master and Product Owner.
    4. It grows until every specialty in the organization is represented.

    Explanation

    Scrum Teams are typically ten or fewer people, counting everyone in the team. A team that is small enough stays nimble, while a larger one needs too much coordination to complete significant work each Sprint.

  57. Question 57The Scrum Team and its Accountabilities

    Who is accountable for the Scrum Team's effectiveness?

    1. The stakeholders who fund the product
    2. The Scrum Master Correct answer.
    3. The Product Owner
    4. The Developers

    Explanation

    The Scrum Master is accountable for the Scrum Team's effectiveness, working with both the team and the organization to improve how Scrum is applied. The Product Owner and Developers hold different accountabilities, such as value maximization and creating the Increment.

  58. Question 58The Scrum Team and its Accountabilities

    Who participates in the Sprint Retrospective?

    1. The Product Owner and invited stakeholders
    2. The Scrum Team Correct answer.
    3. The Scrum Master and the Developers only
    4. Anyone who attended the Sprint Review

    Explanation

    The Sprint Retrospective is an event for the whole Scrum Team, which includes the Scrum Master, the Product Owner, and the Developers. It is used to inspect how the last Sprint went and to plan improvements.

  59. Question 59The Scrum Team and its Accountabilities

    An organization has no standard Definition of Done. Who creates the Definition of Done for the product?

    1. The Scrum Team Correct answer.
    2. The quality assurance specialists on the Scrum Team
    3. The Scrum Master, to ensure consistency
    4. The Product Owner, with approval from stakeholders

    Explanation

    When the organization does not already provide a Definition of Done, the Scrum Team creates one so that everyone shares the same meaning of 'done'. It makes the state of the Increment transparent.

  60. Question 60The Scrum Team and its Accountabilities

    How many Product Owners does a Scrum Team have?

    1. One per product area covered by the team
    2. As many as the Scrum Team agrees on
    3. One person Correct answer.
    4. One for each major stakeholder group

    Explanation

    The Product Owner is one person, not a committee, even though that person may represent the needs of many stakeholders. A single accountable person keeps product decisions clear.

  61. Question 61The Scrum Team and its Accountabilities

    Who is accountable for ensuring that Scrum events take place, are productive, and stay within their timeboxes?

    1. The Product Owner
    2. The Developers
    3. Whoever facilitates each event
    4. The Scrum Master Correct answer.

    Explanation

    Part of the Scrum Master's accountability is establishing Scrum as defined in the Scrum Guide, which includes ensuring the events happen and are kept productive and timeboxed. Facilitation may be shared, but the accountability is not.

  62. Question 62The Scrum Team and its Accountabilities

    Who is accountable for developing and explicitly communicating the Product Goal?

    1. The stakeholders at the Sprint Review
    2. The Product Owner Correct answer.
    3. The Developers during Sprint Planning
    4. The Scrum Master as part of coaching

    Explanation

    The Product Owner is accountable for developing and explicitly communicating the Product Goal, which describes a future state of the product. It is recorded in the Product Backlog as a commitment the team plans toward.

  63. Question 63The Scrum Team and its Accountabilities

    Which statement about who counts as a Developer is correct?

    1. Anyone creating the Increment is a Developer. Correct answer.
    2. Developers are the people the Scrum Master assigns to the Sprint.
    3. Only people with the job title 'Developer' are Developers.
    4. Testers and analysts are separate from the Developers.

    Explanation

    Developers are the members of the Scrum Team committed to creating any aspect of a usable Increment each Sprint, whatever their job title. Testers, designers, and analysts working on the Increment all fall under that accountability.

  64. Question 64The Scrum Team and its Accountabilities

    Who can cancel a Sprint?

    1. The Developers
    2. The Product Owner Correct answer.
    3. The Scrum Master
    4. The Scrum Team by unanimous agreement

    Explanation

    Only the Product Owner has the authority to cancel a Sprint, and it is done only when the Sprint Goal becomes obsolete. Cancellation is rare because it consumes resources and disrupts the team.

  65. Question 65The Scrum Team and its Accountabilities

    A Product Owner asks a business analyst to draft Product Backlog items. Who remains accountable for those items?

    1. The Scrum Master, because they facilitate collaboration
    2. The Product Owner Correct answer.
    3. The Developers, because they will build the items
    4. The business analyst, because they produced the items

    Explanation

    A Product Owner may delegate work such as drafting or refining Product Backlog items, but the accountability for the Product Backlog stays with the Product Owner. Delegation moves the task, not the accountability.

  66. Question 66The Scrum Team and its Accountabilities

    How does Scrum regard sub-teams such as a separate testing group inside the Scrum Team?

    1. The Scrum Team is one team with no sub-teams. Correct answer.
    2. They are acceptable when the Scrum Team has more than ten people.
    3. They help the Scrum Master coordinate large Scrum Teams.
    4. They are allowed if each sub-team reports to the Product Owner.

    Explanation

    The Scrum Team is one cohesive unit of professionals focused on one objective at a time, with no sub-teams or hierarchies. Different skills exist inside the team but do not create separate structures.

  67. Question 67The Scrum Team and its Accountabilities

    Who participates in the Sprint Review?

    1. The Developers and the Product Owner, without other stakeholders
    2. Only the Scrum Master and the Developers
    3. Only the Product Owner and the stakeholders
    4. The Scrum Team and key stakeholders Correct answer.

    Explanation

    The Sprint Review brings the Scrum Team together with key stakeholders to inspect the Increment and adapt the Product Backlog. It is a working session with the people who care about the product, not a status report.

  68. Question 68The Scrum Team and its Accountabilities

    Who creates the Sprint Goal?

    1. The Scrum Team, collaboratively during Sprint Planning Correct answer.
    2. The Scrum Master, based on the previous Sprint's Retrospective
    3. The Product Owner, before Sprint Planning begins
    4. The Developers alone, after the Sprint has started

    Explanation

    The Sprint Goal is crafted by the whole Scrum Team during Sprint Planning and gives the Sprint a single objective. The Product Owner brings value-focused proposals, but the goal is shaped together.

  69. Question 69The Scrum Team and its Accountabilities

    An organization already has a standard Definition of Done. What must a Scrum Team do?

    1. Ask the Scrum Master to approve any deviation from it.
    2. Ignore it, because each Scrum Team owns its own definition.
    3. Replace it with its own definition if the team prefers different criteria.
    4. Adopt it as a minimum and may add stricter criteria. Correct answer.

    Explanation

    If the organization defines a Definition of Done, every Scrum Team must follow it as a minimum and may apply stricter criteria. Where no organizational standard exists, each Scrum Team creates its own.

  70. Question 70The Scrum Team and its Accountabilities

    Can people who are not members of the Scrum Team attend Sprint Planning?

    1. Yes, if the Scrum Team invites them to provide advice. Correct answer.
    2. Yes, but only stakeholders with decision-making authority.
    3. No; Sprint Planning is closed to protect the team's focus.
    4. Yes, but only the Scrum Master's manager.

    Explanation

    Sprint Planning is the Scrum Team's event, but the team may invite other people to attend to provide advice. Attendance by outsiders is the team's choice and carries no decision rights.

  71. Question 71The Scrum Team and its Accountabilities

    Who is accountable for ensuring the Developers understand the Product Backlog items well enough to select them?

    1. The Product Owner Correct answer.
    2. The stakeholders who requested the items
    3. The Developers alone
    4. The Scrum Master

    Explanation

    Effective Product Backlog management includes making items clear and understood, and that accountability belongs to the Product Owner. Developers need that clarity to forecast what they can deliver.

  72. Question 72The Scrum Team and its Accountabilities

    Who is accountable for keeping the Sprint Backlog up to date as the Sprint progresses?

    1. The Developers Correct answer.
    2. The Product Owner
    3. The Scrum Master
    4. The person who created each Sprint Backlog item

    Explanation

    The Sprint Backlog is owned by the Developers, who update it throughout the Sprint as more is learned. Neither the Scrum Master nor the Product Owner manages its day-to-day contents.

  73. Question 73The Scrum Team and its Accountabilities

    Which statement about the Scrum Master's authority is correct?

    1. The Scrum Master directs the Developers' daily work.
    2. The Scrum Master approves each Increment before it is released.
    3. The Scrum Master decides the order of the Product Backlog.
    4. The Scrum Master leads through coaching and influence. Correct answer.

    Explanation

    The Scrum Master is a true leader who serves the Scrum Team and the organization, leading through coaching, teaching, and facilitation. The accountability carries no command authority over the Developers or over product decisions.

  74. Question 74The Scrum Team and its Accountabilities

    Which of the following is an accountability of the Scrum Master?

    1. Deciding how the Developers will do their work
    2. Establishing Scrum as defined in the Scrum Guide Correct answer.
    3. Maximizing the value delivered by the Scrum Team
    4. Selecting the Product Backlog items for each Sprint

    Explanation

    Establishing Scrum as defined in the Scrum Guide is part of the Scrum Master's accountability, along with coaching the team and organization. Ordering the backlog belongs to the Product Owner, and deciding how to do the work belongs to the Developers.

  75. Question 75The Scrum Team and its Accountabilities

    A new Product Owner asks the Scrum Master to approve the ordering of the Product Backlog before each Sprint. What is the most appropriate response?

    1. Escalate the ordering request to the stakeholders.
    2. Ask the Developers to vote on the ordering instead.
    3. Approve the ordering so that each Sprint can begin on time.
    4. Explain that ordering is the Product Owner's call. Correct answer.

    Explanation

    Ordering the Product Backlog is the Product Owner's accountability, and the Scrum Master does not approve it. The Scrum Master can instead help the Product Owner with techniques for effective backlog management.

  76. Question 76The Scrum Team and its Accountabilities

    Midway through a Sprint, the Product Owner learns a competitor has released a major feature and wants to change the Sprint Goal. What does Scrum say?

    1. The Developers must immediately replan to deliver the new feature within the Sprint.
    2. The Scrum Master must call a new Sprint Planning and restart the Sprint.
    3. The Product Owner may cancel the Sprint if its Sprint Goal is obsolete. Correct answer.
    4. The Product Owner may change the Sprint Goal at any time during the Sprint.

    Explanation

    The Sprint Goal is fixed for the Sprint; if it becomes obsolete the Product Owner may cancel the Sprint. Within a Sprint, scope may be renegotiated between the Product Owner and the Developers, but the Sprint Goal is not simply swapped.

  77. Question 77The Scrum Team and its Accountabilities

    Two Scrum Teams work together on the same product and have different Definitions of Done. What does Scrum require?

    1. The Product Owner writes a single Definition of Done for both teams.
    2. Each team keeps its own Definition of Done to preserve self-management.
    3. The Scrum Master of each team negotiates a compromise with the other.
    4. They mutually define and comply with the same Definition of Done. Correct answer.

    Explanation

    When multiple Scrum Teams work together on one product, they mutually define and comply with the same Definition of Done. This ensures their combined work produces a transparent, integrated Increment.

  78. Question 78The Scrum Team and its Accountabilities

    A functional manager asks the Scrum Master to provide individual performance ratings for each Developer. What is the most appropriate response?

    1. Decline, and coach the manager on assessing team effectiveness. Correct answer.
    2. Provide only the ratings of Developers who are performing poorly.
    3. Provide the ratings, because the manager is accountable for performance.
    4. Ask the Developers to rate one another and forward the results.

    Explanation

    Scrum assesses effectiveness at the level of the Scrum Team, and the Scrum Master coaches the organization on that view. Producing individual ratings undermines self-management and the trust the team depends on.

  79. Question 79The Scrum Team and its Accountabilities

    An engineering director begins writing Sprint Backlog items and assigning them to Developers. Which accountability is being undermined?

    1. The stakeholders' accountability for attending the Sprint Review
    2. The Product Owner's accountability for ordering the Product Backlog
    3. The Developers' accountability for the Sprint Backlog Correct answer.
    4. The Scrum Master's accountability for removing impediments

    Explanation

    The Sprint Backlog belongs to the Developers, who create it and adapt it throughout the Sprint to meet the Sprint Goal. When an outsider assigns items, the Developers lose the self-management that Scrum relies on.

  80. Question 80The Scrum Team and its Accountabilities

    A Product Owner frequently tells the Developers which design and testing approach to use. What is the Scrum Master's most appropriate action?

    1. Coach the Product Owner on the boundary between the accountabilities. Correct answer.
    2. Ask the organization to appoint a separate technical lead.
    3. Instruct the Developers to follow the Product Owner's technical direction.
    4. Raise the issue at the next Sprint Review with stakeholders.

    Explanation

    Deciding how to build the product - design, technique, and testing approach - belongs to the Developers, while the Product Owner focuses on what is most valuable. The Scrum Master coaches the Product Owner on this boundary so self-management is preserved.

  81. Question 81Scrum Events

    What is the timebox for the Daily Scrum?

    1. One hour
    2. As long as the Developers agree it needs
    3. Fifteen minutes Correct answer.
    4. Half an hour

    Explanation

    The Daily Scrum is timeboxed to fifteen minutes and this holds for every Sprint length. The Developers use that window to inspect progress toward the Sprint Goal and adapt their plan for the next day. Anything that needs more time is handled after the event.

  82. Question 82Scrum Events

    What is the maximum duration of the Sprint Retrospective in a one-month Sprint?

    1. One hour
    2. Three hours Correct answer.
    3. Eight hours
    4. Four hours

    Explanation

    The Sprint Retrospective is timeboxed to a maximum of three hours when the Sprint lasts one month. For shorter Sprints the event is usually shorter. The timebox sets an upper limit, not a target.

  83. Question 83Scrum Events

    What is the longest a Sprint is allowed to last?

    1. Two months
    2. One month Correct answer.
    3. Three weeks
    4. Two weeks

    Explanation

    Sprints are fixed-length events of one month or less. Keeping the Sprint within one month bounds the risk and keeps inspection and adaptation frequent. The Scrum Team may choose shorter Sprints, but not longer ones.

  84. Question 84Scrum Events

    Who is required to take part in the Daily Scrum?

    1. The Scrum Master and the Developers only
    2. The Developers only Correct answer.
    3. The Product Owner, the Scrum Master and the Developers
    4. The whole Scrum Team together with invited stakeholders

    Explanation

    The Daily Scrum is an event for the Developers, who own the Sprint Backlog and the plan for the day. The Scrum Master and Product Owner may attend but are not required, and stakeholders are not part of the event. Its purpose is the Developers' own inspection and adaptation.

  85. Question 85Scrum Events

    What is the maximum timebox for Sprint Planning in a one-month Sprint?

    1. One working day
    2. Three hours
    3. Four hours
    4. Eight hours Correct answer.

    Explanation

    Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. Shorter Sprints usually need proportionally less time. The timebox caps the event; the team does not have to use all of it.

  86. Question 86Scrum Events

    What is the maximum timebox for the Sprint Review in a one-month Sprint?

    1. Two hours
    2. Four hours Correct answer.
    3. Six hours
    4. Eight hours

    Explanation

    The Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint. Shorter Sprints generally need a shorter Review. Within that box the Scrum Team and stakeholders inspect the outcome and adapt the Product Backlog.

  87. Question 87Scrum Events

    Why does the Scrum Team hold a Sprint Retrospective?

    1. To reorder the Product Backlog by business value
    2. To show the Increment to stakeholders and collect their feedback
    3. To agree the Sprint Goal for the upcoming Sprint
    4. To plan ways to increase quality and effectiveness Correct answer.

    Explanation

    The Sprint Retrospective is the event in which the Scrum Team inspects how the last Sprint went and plans improvements to quality and effectiveness. It closes the Sprint and feeds concrete improvements into the next one. It is not a demonstration or a backlog-ordering session.

  88. Question 88Scrum Events

    What is the main purpose of the Sprint Review?

    1. To inspect the Sprint outcome and adapt the Product Backlog Correct answer.
    2. To inspect and improve the team's way of working
    3. To decide whether the Sprint should be cancelled before it ends
    4. To estimate the effort needed for upcoming items

    Explanation

    The Sprint Review is a working session in which the Scrum Team and key stakeholders inspect the outcome of the Sprint and adapt the Product Backlog. It looks outward at the product and what to do next. Process improvement belongs to the Retrospective.

  89. Question 89Scrum Events

    Which question does the Sprint Goal primarily answer during Sprint Planning?

    1. Why is this Sprint valuable? Correct answer.
    2. When will each item be finished?
    3. Who will carry out each task?
    4. How will the Developers do the work?

    Explanation

    Sprint Planning covers why the Sprint is valuable, what can be done in it, and how the chosen work will get done. The Sprint Goal expresses the why: the single objective the Sprint serves. The how is captured in the plan held in the Sprint Backlog.

  90. Question 90Scrum Events

    What is the main purpose of the Daily Scrum?

    1. To inspect progress toward the Sprint Goal Correct answer.
    2. To confirm that every Developer has enough work for the day
    3. To report individual task status to the Scrum Master
    4. To update the Product Backlog with newly discovered items

    Explanation

    The Daily Scrum exists so the Developers can inspect progress toward the Sprint Goal and adapt the Sprint Backlog accordingly. It produces an actionable plan for the next day of work. It is not a status report to anyone outside the Developers.

  91. Question 91Scrum Events

    Who is allowed to cancel a Sprint?

    1. The Product Owner, when the Sprint Goal becomes obsolete Correct answer.
    2. The stakeholders, when market conditions change
    3. The Developers, when they cannot finish the work
    4. The Scrum Master, when Scrum is not being followed

    Explanation

    Only the Product Owner has the authority to cancel a Sprint, and the trigger is the Sprint Goal becoming obsolete. Because the Sprint Goal is the Product Owner's commitment, nobody else can discard it. Cancellation is rare and happens only when the objective no longer makes sense.

  92. Question 92Scrum Events

    When is the Sprint Retrospective held?

    1. Whenever the Scrum Team feels the need during the Sprint
    2. At the start of the Sprint, before Sprint Planning
    3. After the Sprint Review, before the next Sprint Planning Correct answer.
    4. Halfway through the Sprint, after the Daily Scrum

    Explanation

    The Retrospective is the last event of the Sprint and takes place after the Sprint Review. It concludes the Sprint and produces improvements that flow into the next Sprint Planning. It is a scheduled event, not an on-demand meeting.

  93. Question 93Scrum Events

    A Scrum Team runs two-week Sprints. How should its Sprint Planning timebox be set?

    1. It must be exactly four hours for any two-week Sprint
    2. It stays at eight hours because the maximum never changes
    3. It is usually shorter than for a one-month Sprint Correct answer.
    4. It is replaced by daily planning sessions in short Sprints

    Explanation

    Scrum sets one maximum per event for a one-month Sprint and states that shorter Sprints generally need shorter events. A two-week Sprint therefore usually plans in less than eight hours. The exact figure is for the Scrum Team to decide within the timebox.

  94. Question 94Scrum Events

    Who takes part in the Sprint Review?

    1. The Scrum Team together with key stakeholders Correct answer.
    2. Only the Scrum Master and invited managers
    3. Only the Developers and the Product Owner
    4. The Developers and the Quality Assurance group

    Explanation

    The Sprint Review brings the Scrum Team together with key stakeholders to inspect the outcome of the Sprint and adapt the Product Backlog. Stakeholder collaboration is what makes the event useful. It is a working session rather than an internal team meeting.

  95. Question 95Scrum Events

    The Developers want to change the way they run the Daily Scrum. What does Scrum permit?

    1. They may use any structure that keeps focus on the Sprint Goal Correct answer.
    2. They may replace the event with written status updates
    3. Nothing may change; the three standard questions must always be asked
    4. Only the Scrum Master may change the format of the event

    Explanation

    Scrum leaves the format of the Daily Scrum to the Developers. They may use any structure or technique provided the focus stays on progress toward the Sprint Goal and an actionable plan for the next day emerges. The event itself cannot be dropped or replaced.

  96. Question 96Scrum Events

    What does the Sprint Retrospective produce?

    1. A set of actionable improvements to increase quality Correct answer.
    2. A signed-off Definition of Done for the next Sprint
    3. The Product Backlog items selected for the Sprint
    4. A revised Product Backlog for the upcoming Sprint Review

    Explanation

    The Retrospective yields concrete, actionable improvements the team intends to make, often addressing the Definition of Done, processes or interactions. The most impactful ones may be added to the Sprint Backlog for the next Sprint. It does not produce Product Backlog decisions.

  97. Question 97Scrum Events

    What is a typical result of the Sprint Review?

    1. A new Sprint Goal for the current Sprint
    2. A prioritized list of improvements owned by the Scrum Master
    3. A finalized budget for the next quarter
    4. A revised Product Backlog that defines what to do next Correct answer.

    Explanation

    The Sprint Review adapts the Product Backlog so that it reflects what the Scrum Team and stakeholders now understand to be most valuable. Items may be added, removed or reordered as a result of the discussion. This input feeds directly into the next Sprint Planning.

  98. Question 98Scrum Events

    Who is responsible for the Sprint Backlog?

    1. The whole Scrum Team, acting by consensus
    2. The Developers, who plan and manage their own work Correct answer.
    3. The Scrum Master, who removes impediments
    4. The Product Owner, who owns the ordering of all backlog items

    Explanation

    The Sprint Backlog is a plan by and for the Developers, who create and update it as they learn more during the Sprint. They are the only ones who change it. The Product Owner owns the Product Backlog, not the Sprint Backlog.

  99. Question 99Scrum Events

    A Sprint has just ended. What happens next?

    1. The team takes a short break before planning resumes
    2. The next Sprint starts immediately Correct answer.
    3. A new Sprint Planning session is scheduled for the following week
    4. The Scrum Master decides when the next Sprint begins

    Explanation

    A new Sprint begins as soon as the previous one ends, with no gap between them. The Retrospective closes the old Sprint and Sprint Planning opens the new one. Continuity keeps the cadence and the feedback loop intact.

  100. Question 100Scrum Events

    Stakeholders want more time at the Sprint Review than its timebox allows. What is the correct response?

    1. Cancel the next Daily Scrum to make up the lost time
    2. Keep the timebox and continue the discussions afterwards Correct answer.
    3. Extend the Sprint Review until all questions are answered
    4. Let the Product Owner decide the length of each Sprint Review

    Explanation

    Every Scrum event is timeboxed to a maximum, and the Review is no exception. Valuable conversations that need longer continue outside the event rather than stretching it. This protects the cadence and keeps the event focused.

  101. Question 101Scrum Events

    How does the Sprint relate to the other four Scrum events?

    1. The Sprint is the sum of the other four events' timeboxes
    2. The Sprint runs in parallel with all of the other events
    3. The Sprint is a container event that holds the other four Correct answer.
    4. The Sprint is optional when the other events are performed

    Explanation

    Scrum defines five events: the Sprint plus Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective. The Sprint is the container in which the other four take place. Nothing in Scrum happens outside a Sprint.

  102. Question 102Scrum Events

    Under what condition is cancelling a Sprint most appropriate?

    1. The Sprint Goal has become obsolete Correct answer.
    2. The Developers have fallen behind their forecast
    3. A key stakeholder withdraws from the Sprint Review
    4. The Scrum Master identifies a process violation

    Explanation

    A Sprint may be cancelled only when its Sprint Goal becomes obsolete, for example because the market or the business direction changed. Falling behind is handled by negotiating scope with the Product Owner. When a Sprint is cancelled, completed and Done items are reviewed and incomplete ones return to the Product Backlog.

  103. Question 103Scrum Events

    A Scrum Team under delivery pressure proposes to skip its Sprint Retrospective. What is the most appropriate response?

    1. It must still be held, although it can be kept within its timebox Correct answer.
    2. It may be skipped once per quarter with stakeholder approval
    3. It can be replaced by a written survey completed asynchronously
    4. The Scrum Master may cancel it if the Sprint Review ran long

    Explanation

    The Retrospective is a required Scrum event and cannot be dropped, because it is the team's only formal opportunity to inspect and improve how it works. A team can shorten the event and stay inside its timebox, but not remove it. Sacrificing improvement is exactly the wrong move under pressure.

  104. Question 104Scrum Events

    Near the end of a Sprint the Developers ask to extend it by one week to finish the Increment. What does Scrum say?

    1. The Sprint duration is fixed and cannot be extended Correct answer.
    2. The Scrum Team may vote to extend the Sprint by a fixed period
    3. Extensions are allowed as long as the total stays under two months
    4. The Product Owner may approve an extension of up to one week

    Explanation

    A Sprint has a fixed duration chosen by the Scrum Team, and that duration is not stretched once the Sprint is under way. If the Sprint Goal becomes obsolete the Product Owner may cancel the Sprint instead. Unfinished work simply returns to the Product Backlog for the next Sprint.

  105. Question 105Scrum Events

    Midway through a Sprint the Developers realize there is more work than expected. Which statement best describes what Scrum permits?

    1. The Sprint Backlog must not change once the Sprint has started
    2. The Sprint Goal must be abandoned and a new Sprint started
    3. The Developers must work overtime to deliver all selected items
    4. Scope may be renegotiated with the Product Owner as more is learned Correct answer.

    Explanation

    As the Developers learn more during the Sprint, the scope of the Sprint Backlog may be clarified and renegotiated with the Product Owner. The Sprint Goal itself stays in place and is not to be discarded. The Sprint Backlog therefore emerges and changes throughout the Sprint.

  106. Question 106Scrum Events

    What is the maximum length of a Sprint?

    1. Two weeks
    2. Six weeks
    3. Three months
    4. One month Correct answer.

    Explanation

    Sprints are fixed-length events of one month or less, which keeps risk and complexity bounded. Shorter Sprints are common, but a Sprint may never exceed one month. The length is agreed once and held constant while the Sprint is underway.

  107. Question 107Scrum Events

    In Scrum, what does a timebox represent for an event?

    1. A minimum duration the event should always reach
    2. The exact duration the event is expected to run
    3. A maximum duration that the event must not exceed Correct answer.
    4. The duration reserved for the event in the team calendar

    Explanation

    Every Scrum event is timeboxed, which means it has a maximum duration that is never exceeded. An event may well finish earlier when its purpose has been served. The timebox is a ceiling, not a target to be filled.

  108. Question 108Scrum Events

    What is the timebox for the Sprint Retrospective in a one-month Sprint?

    1. Three hours Correct answer.
    2. Two hours
    3. One hour
    4. Ninety minutes

    Explanation

    For a one-month Sprint the Retrospective is timeboxed to a maximum of three hours. The event closes the Sprint by planning ways to increase quality and effectiveness. Shorter Sprints typically use a proportionally shorter timebox.

  109. Question 109Scrum Events

    What is the timebox for Sprint Planning in a one-month Sprint?

    1. Three hours
    2. Eight hours Correct answer.
    3. Two hours
    4. Four hours

    Explanation

    Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. Shorter Sprints scale the timebox down accordingly. The event ends early whenever the Scrum Team has laid out the work of the Sprint.

  110. Question 110Scrum Events

    Which three topics does Sprint Planning address?

    1. What customers have asked for, what competitors are building, and how the product will be priced
    2. Which risks the product carries, who owns each risk, and how those risks will be reported to stakeholders
    3. Who will carry out each task, when each task will finish, and what the work will cost the organization
    4. Why the Sprint is valuable, what can be done, and how the chosen work will be done Correct answer.

    Explanation

    Sprint Planning establishes why the Sprint is valuable, what can be done in the Sprint, and how the chosen work will get done. These three questions are answered collaboratively by the Scrum Team. The answers produce the Sprint Goal and the Sprint Backlog.

  111. Question 111Scrum Events

    How is the Sprint Goal created?

    1. Stakeholders agree on it during the Sprint Review for the following Sprint
    2. The Product Owner writes it alone before Sprint Planning and presents it to the Developers
    3. The Scrum Team collaborates on it during Sprint Planning Correct answer.
    4. The Scrum Master drafts it from the previous Sprint's Retrospective outcomes

    Explanation

    The Sprint Goal is crafted collaboratively by the whole Scrum Team during Sprint Planning. It gives the Sprint a single objective that the Developers commit to. Ownership by the entire team is what makes the goal something the team can rally behind.

  112. Question 112Scrum Events

    Who participates in Sprint Planning?

    1. The Developers and the key stakeholders
    2. The entire Scrum Team Correct answer.
    3. The Scrum Master and the stakeholders
    4. The Product Owner and the Scrum Master only

    Explanation

    Sprint Planning is an event for the Scrum Team, meaning the Developers, the Product Owner and the Scrum Master. The Developers do the work of selecting and planning, while the Product Owner brings the business context. Stakeholders are not required participants in this event.

  113. Question 113Scrum Events

    What does Sprint Planning produce?

    1. A Sprint Goal and a Sprint Backlog Correct answer.
    2. A Product Goal and a release plan
    3. A Retrospective plan and an improvement backlog
    4. A Definition of Done and a risk register

    Explanation

    Sprint Planning results in a Sprint Goal, which explains why the Sprint is valuable, and a Sprint Backlog, which is the set of items selected plus the plan for delivering them. These two artifacts guide the Developers throughout the Sprint. Neither is a document produced by other events.

  114. Question 114Scrum Events

    What do the Developers leave the Daily Scrum with?

    1. An updated Definition of Done
    2. A list of impediments for the Scrum Master to resolve
    3. A signed status report for the Product Owner
    4. A plan of action for the next day of the Sprint Correct answer.

    Explanation

    The Daily Scrum exists so the Developers can inspect progress toward the Sprint Goal and adapt the Sprint Backlog, producing an actionable plan for the next day. It is a planning event, not a reporting event. Any item needing deeper discussion is taken offline afterwards.

  115. Question 115Scrum Events

    How should the Daily Scrum be scheduled to reduce complexity?

    1. Only on days when the Developers have something to report
    2. At the same time and place every working day of the Sprint Correct answer.
    3. At a different time each day so that it stays fresh
    4. Whenever the Developers finish their current task

    Explanation

    Scrum recommends holding the Daily Scrum at the same time and place every working day of the Sprint. This regularity reduces complexity and removes the need to negotiate a slot each day. The Developers own the event and can vary the technique, but a stable cadence is the norm.

  116. Question 116Scrum Events

    The Product Owner has been actively working on several Sprint Backlog items this Sprint. How should this affect the Daily Scrum?

    1. The Product Owner must stay away from the Daily Scrum regardless of the work being done
    2. The Product Owner should send written updates that the Scrum Master reads out
    3. The Product Owner joins as a Developer while working on those items Correct answer.
    4. The Product Owner should attend as a guest and listen without contributing

    Explanation

    The Daily Scrum is for the Developers, and anyone who is actively working on items in the Sprint Backlog participates as a Developer. A Product Owner doing that work therefore takes part fully. Attendance is driven by the work, not by the job title.

  117. Question 117Scrum Events

    A Sprint has just finished. When does the next Sprint begin?

    1. Immediately after the current Sprint concludes Correct answer.
    2. After the Product Owner approves the Increment
    3. After stakeholders have reviewed the Retrospective notes
    4. At the start of the next calendar month

    Explanation

    Sprints follow one another without a gap, so the next Sprint begins as soon as the previous one concludes. This continuous cadence keeps the product moving and preserves a steady rhythm of inspection and adaptation. No approval gate sits between Sprints.

  118. Question 118Scrum Events

    How does the Sprint relate to the other Scrum events?

    1. It replaces them when the team is under pressure
    2. It follows them and summarizes their outcomes
    3. It runs in parallel with them and sets their budgets
    4. It is a container for all the other events Correct answer.

    Explanation

    The Sprint is the container event inside which Sprint Planning, the Daily Scrums, the Sprint Review and the Sprint Retrospective take place. All the work needed to meet the Sprint Goal happens within it. The other events are fixed points inside that container.

  119. Question 119Scrum Events

    Which statement best describes how a Sprint Review should be run?

    1. As a formal presentation of completed features to executives
    2. As a working session in which attendees collaborate Correct answer.
    3. As a status meeting led by the Scrum Master
    4. As a question-and-answer session with the Product Owner

    Explanation

    The Sprint Review is a working session, and the Scrum Team should avoid limiting it to a presentation. Attendees collaborate on what was done and what to do next, adapting the Product Backlog as needed. Discussion of the Increment and its implications is the heart of the event.

  120. Question 120Scrum Events

    Why are the Scrum events timeboxed?

    1. To create regularity and keep inspection and adaptation focused Correct answer.
    2. To ensure that a written record is produced for each event
    3. To allow the Product Owner to control the team's calendar
    4. To make sure that every event always fills its full allotted duration

    Explanation

    Timeboxing gives the Scrum Team a regular rhythm and keeps each period of inspection and adaptation sharply focused. It also reduces the need for meetings that Scrum does not define. Events are allowed to end early once their purpose is achieved.

  121. Question 121Scrum Events

    Which areas does the Sprint Retrospective inspect?

    1. Only the velocity and the number of defects found in the Increment
    2. Individuals, interactions, processes, tools, and the Definition of Done Correct answer.
    3. The team's adherence to the original project schedule and budget
    4. The Product Backlog order and the pricing of upcoming features

    Explanation

    The Retrospective examines how the last Sprint went with respect to individuals, interactions, processes, tools and the Definition of Done. It looks at the way the team works, not just at output metrics. The aim is to identify the most helpful changes to increase quality and effectiveness.

  122. Question 122Scrum Events

    What must be true of the Increment produced by each Sprint?

    1. It must be deployed to production before the Sprint ends
    2. It must include every item that was in the Sprint Backlog
    3. It must be approved by the stakeholders at the Sprint Review
    4. It must meet the Definition of Done and be usable Correct answer.

    Explanation

    Every Sprint must produce an Increment that is usable and meets the Definition of Done, even if the Sprint Goal is not fully achieved. The Increment is inspected at the Sprint Review. Deployment to production is a business decision, not a Scrum requirement.

  123. Question 123Scrum Events

    Which of the following is one of the five Scrum events?

    1. Sprint Retrospective Correct answer.
    2. Stakeholder steering committee
    3. Release planning meeting
    4. Backlog refinement workshop

    Explanation

    The five Scrum events are the Sprint, Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective. Backlog refinement and release planning are useful activities but are not Scrum events. They can be done as needed within the Sprint.

  124. Question 124Scrum Events

    Which event opens a Sprint?

    1. Sprint Planning Correct answer.
    2. Sprint Review
    3. The Daily Scrum
    4. Sprint Retrospective

    Explanation

    Sprint Planning initiates the Sprint by laying out the work to be performed. The Sprint Goal and Sprint Backlog are established there, and the Developers then carry the work forward through the Daily Scrums. The Review and Retrospective come at the end of the Sprint.

  125. Question 125Scrum Events

    A manager asks the Scrum Team to add a weekly progress meeting for senior leadership. Which response is most consistent with Scrum?

    1. The new meeting can replace the Daily Scrum as long as it covers the same information
    2. The new meeting should be added to the Sprint and timeboxed to fifteen minutes
    3. Additional meetings are allowed, but they are not Scrum events and add little value Correct answer.
    4. The request must be rejected, because Scrum permits no meetings other than the five defined events

    Explanation

    Scrum does not prohibit other meetings; it simply does not define them as events. The five events are designed to reduce the need for extra meetings, so adding one should be weighed against that. Transparency to leadership is better served by attending the Sprint Review.

  126. Question 126Scrum Events

    On day eight of a ten-day Sprint, the Developers have completed every item in the Sprint Backlog. What is the most appropriate action?

    1. Stop working until the Sprint Review, because the Sprint Backlog is complete
    2. Extend the Sprint by two days so that more work can be completed
    3. Pull more Product Backlog items in collaboration with the Product Owner Correct answer.
    4. Start the next Sprint early so that the team keeps its rhythm

    Explanation

    Sprint Backlog scope may be clarified and renegotiated with the Product Owner as more is learned during the Sprint. Selecting further valuable items keeps the team productive toward the Sprint Goal. The Sprint itself is never extended or started early.

  127. Question 127Scrum Events

    The Developers use the Daily Scrum to report progress one by one to the Scrum Master. What is the Scrum Master's best course of action?

    1. Take detailed notes and redistribute them to stakeholders after the event
    2. Cancel the event until the team is ready to self-manage
    3. Coach the Developers to keep the event focused and within the timebox Correct answer.
    4. Assign each Developer a speaking slot so the event stays orderly

    Explanation

    The Scrum Master ensures the Scrum events take place and are kept positive, productive and within the timebox. Coaching the Developers toward self-management serves that duty. Taking over the event or cancelling it would undermine the Developers' ownership.

  128. Question 128Scrum Events

    Halfway through a one-month Sprint the Developers say the Sprint Review is unnecessary because the Increment is incomplete. What is the most appropriate response?

    1. Postpone the Sprint Review until the Increment has been completed in a later Sprint
    2. Hold it anyway; the review inspects the Increment and adapts the Product Backlog Correct answer.
    3. Cancel the Sprint Review and extend the Sprint by one week
    4. Replace the Sprint Review with a written status report to stakeholders

    Explanation

    The Sprint Review is held at the end of every Sprint, regardless of how complete the work is. It is where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog. An incomplete Increment is itself valuable information for that adaptation.

  129. Question 129Scrum Events

    Partway through a Sprint, a sudden market shift makes the Sprint Goal obsolete overnight. What does Scrum prescribe in this situation?

    1. The Developers cancel the Sprint once they confirm the Sprint Goal can no longer be met.
    2. The Scrum Team continues the work and decides at the Sprint Review whether the Sprint should be cancelled.
    3. The Product Owner cancels the Sprint; completed Done items are reviewed and potentially released. Correct answer.
    4. The Scrum Master cancels the Sprint and directs the Developers to begin the next Sprint immediately.

    Explanation

    Only the Product Owner has the authority to cancel a Sprint, and a Sprint is cancelled when the Sprint Goal becomes obsolete. On cancellation, any completed items that are Done are reviewed and, if potentially releasable, may be accepted; unfinished items go back to the Product Backlog for future consideration.

  130. Question 130Scrum Artifacts and Commitments

    Which commitment is associated with the Product Backlog?

    1. Definition of Ready
    2. Definition of Done
    3. Product Goal Correct answer.
    4. Sprint Goal

    Explanation

    Each Scrum artifact contains a commitment that reinforces transparency and focus. The Product Backlog carries the Product Goal, which describes a future state of the product and gives direction to the ordering of the backlog.

  131. Question 131Scrum Artifacts and Commitments

    Which commitment is paired with the Sprint Backlog?

    1. Sprint Goal Correct answer.
    2. Release Goal
    3. Product Goal
    4. Definition of Done

    Explanation

    The Sprint Backlog is composed of the Sprint Goal, the selected Product Backlog items and the plan for delivering them. The Sprint Goal is the commitment that explains why the Sprint is valuable.

  132. Question 132Scrum Artifacts and Commitments

    Which commitment is paired with the Increment?

    1. Sprint Goal
    2. Definition of Done Correct answer.
    3. Acceptance criteria
    4. Product Goal

    Explanation

    The Definition of Done is the commitment that makes the state of the Increment transparent. Work that does not meet the Definition of Done cannot be considered part of the Increment.

  133. Question 133Scrum Artifacts and Commitments

    Which statement best describes the Product Backlog?

    1. A schedule of releases agreed with stakeholders for the coming year.
    2. A document listing the acceptance criteria agreed for each user story.
    3. A record of every task the Developers plan to finish during the current Sprint.
    4. An emergent, ordered list of what is needed to improve the product. Correct answer.

    Explanation

    The Product Backlog is the single source of work undertaken by the Scrum Team. It is emergent, meaning it changes as more is learned, and it is ordered so that the most valuable items come first.

  134. Question 134Scrum Artifacts and Commitments

    Which statement describes a well-managed Product Backlog?

    1. It is ordered, with items nearer the top being clearer and more detailed. Correct answer.
    2. It is grouped by team so that each team has its own separate list of items.
    3. It contains only the items that the Product Owner has personally authored and estimated.
    4. It is locked in place once the first release plan has been agreed with stakeholders.

    Explanation

    Product Backlog refinement breaks items into smaller, more precise pieces, and the items that are higher in the order are typically better understood and more detailed. The backlog remains emergent rather than fixed.

  135. Question 135Scrum Artifacts and Commitments

    What does the Definition of Done primarily provide?

    1. A shared understanding of what it means for work to be complete. Correct answer.
    2. The forecast of how many items the Developers will finish this Sprint.
    3. The acceptance criteria that each Product Backlog item must satisfy before review.
    4. The release schedule agreed with stakeholders for delivering the Increment.

    Explanation

    The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It creates a shared understanding of completeness and therefore transparency.

  136. Question 136Scrum Artifacts and Commitments

    Which statement best describes the Sprint Goal?

    1. A long-term target that describes a future state of the overall product offering.
    2. A forecast of the number of Product Backlog items the Developers will finish.
    3. A list of every task needed to complete the selected Product Backlog items.
    4. A single objective for the Sprint that provides focus and flexibility. Correct answer.

    Explanation

    The Sprint Goal is the single objective for the Sprint and is created during Sprint Planning. It gives the Developers a shared focus while leaving room to negotiate the exact work as more is learned.

  137. Question 137Scrum Artifacts and Commitments

    Which statement describes the Increment?

    1. The collection of all Product Backlog items that have not yet been started by the team.
    2. The documentation package that is handed over to the operations team after each release.
    3. The Sprint Backlog exactly as it stands at the very end of the Sprint, including all its tasks.
    4. A concrete, usable step toward the Product Goal that meets the Definition of Done. Correct answer.

    Explanation

    An Increment is the sum of the completed Product Backlog items produced during a Sprint. It must be usable and meet the Definition of Done so that it delivers value toward the Product Goal.

  138. Question 138Scrum Artifacts and Commitments

    A Scrum Team works within an organizational standard Definition of Done but wants stricter criteria for its product. What is appropriate?

    1. They may replace the organizational standard entirely if the Product Owner agrees.
    2. They may add stricter criteria as long as the organizational minimum is met. Correct answer.
    3. They may not modify or extend the Definition of Done in any way once it has been agreed.
    4. They may define a separate Definition of Done for each Product Backlog item.

    Explanation

    When an organizational standard exists, all Scrum Teams must follow it as a minimum. Teams may apply stricter criteria, but they cannot fall below the organizational standard.

  139. Question 139Scrum Artifacts and Commitments

    Two Scrum Teams work together on the same product. What does Scrum require regarding their Definition of Done?

    1. Only the Scrum Master defines the Definition of Done that both teams will use.
    2. They must mutually define and comply with the same Definition of Done. Correct answer.
    3. The Definition of Done applies only to the team that performs the final integration.
    4. Each team must have its own Definition of Done, since each team owns its Increment.

    Explanation

    When multiple Scrum Teams work on the same product, their combined work must produce a single releasable Increment. This requires a shared, mutually defined Definition of Done that all teams comply with.

  140. Question 140Scrum Artifacts and Commitments

    What makes up the Sprint Backlog?

    1. The selected Product Backlog items and the acceptance criteria for each item.
    2. The Sprint Goal, the selected items, and the plan for delivering them. Correct answer.
    3. The Sprint Goal and the Definition of Done agreed for the product.
    4. The Product Goal and the Product Backlog items selected for the Sprint.

    Explanation

    The Sprint Backlog is composed of the Sprint Goal (why), the Product Backlog items selected for the Sprint (what), and the plan for delivering them (how). It is a plan by and for the Developers.

  141. Question 141Scrum Artifacts and Commitments

    Stakeholders disagree about the priority of two Product Backlog items. How is this resolved in Scrum?

    1. The Scrum Master makes the decision so that the team can keep moving forward.
    2. Both items are pulled into the next Sprint so that no stakeholder loses out.
    3. The Developers hold a vote to decide which of the two items should come first.
    4. The Product Owner decides the order after hearing the stakeholders. Correct answer.

    Explanation

    The Product Owner is accountable for the Product Backlog and for effective Product Backlog management, which includes ordering the items. Stakeholders may provide input, but the ordering decision belongs to the Product Owner.

  142. Question 142Scrum Artifacts and Commitments

    The Developers finish a Product Backlog item, but it does not meet the Definition of Done. How should this be handled?

    1. It is not part of the Increment and returns to the Product Backlog. Correct answer.
    2. It is part of the Increment but is flagged as incomplete for stakeholders.
    3. It is included in the Increment if the Product Owner decides to accept it.
    4. It is moved to a separate list of undone work maintained by the Scrum Master.

    Explanation

    The Definition of Done is the standard that determines whether work is complete enough to be part of the Increment. Work that does not meet it is not presented as part of the Increment and goes back to the Product Backlog for future consideration.

  143. Question 143Scrum Artifacts and Commitments

    What is the relationship between the Definition of Done and the Increment?

    1. It determines when work on the Increment is complete. Correct answer.
    2. The Increment determines when the Definition of Done may be revised.
    3. Both are optional and are agreed with stakeholders at the Sprint Review.
    4. The Increment is created first and the Definition of Done is written at the Retrospective.

    Explanation

    The Definition of Done is the commitment attached to the Increment and is the quality standard used to judge completeness. An Increment only exists to the extent that its items meet that standard.

  144. Question 144Scrum Artifacts and Commitments

    Which statement best describes the Product Goal?

    1. A detailed list of the features scheduled for the next three Sprints.
    2. The release plan for the product, owned and maintained by the stakeholders.
    3. A future state of the product that the Scrum Team plans against. Correct answer.
    4. The same as the Sprint Goal, but covering a much longer period of time.

    Explanation

    The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. It is the commitment of the Product Backlog and gives long-term direction to the team's work.

  145. Question 145Scrum Artifacts and Commitments

    A Scrum Team's organization has no standard Definition of Done. What should happen?

    1. The Scrum Team must create a Definition of Done for the product. Correct answer.
    2. The Product Owner writes the Definition of Done alone and shares it later.
    3. Quality is checked only at the Sprint Review, so no definition is needed.
    4. The Definition of Done can be left undefined for the first few Sprints.

    Explanation

    If the organization's Definition of Done is not a standard, the Scrum Team must create one appropriate for the product. It is created by the whole Scrum Team and evolves as the team matures.

  146. Question 146Scrum Artifacts and Commitments

    A product has one Product Goal. How should the Scrum Team use it?

    1. Each team member should set a personal Product Goal aligned to their own specialty.
    2. The Product Goal is fixed for the lifetime of the product and never changes.
    3. A new Product Goal should be set at the start of every Sprint to keep work fresh.
    4. It guides ordering and refinement; only one is pursued at a time. Correct answer.

    Explanation

    The Scrum Team focuses on one objective at a time, and the Product Goal is that longer-term objective for the product. It informs the ordering of the Product Backlog and the shaping of each Sprint Goal.

  147. Question 147Scrum Artifacts and Commitments

    What is the purpose of Product Backlog refinement?

    1. To allow stakeholders to approve every item before the next Sprint Review.
    2. To record the acceptance criteria for each item in the current Increment.
    3. To convert the Product Backlog into the Sprint Backlog for the current Sprint.
    4. To keep the Product Backlog emergent and ready for the next Sprint Planning. Correct answer.

    Explanation

    Refinement is the ongoing act of breaking down and further defining Product Backlog items into smaller, more precise items. It keeps the backlog transparent and gives the Scrum Team enough understanding to plan the next Sprint.

  148. Question 148Scrum Artifacts and Commitments

    Which set correctly matches each artifact with its commitment?

    1. Product Backlog to Definition of Done; Sprint Backlog to Sprint Goal; Increment to Product Goal.
    2. Product Backlog to Sprint Goal; Sprint Backlog to Product Goal; Increment to Definition of Done.
    3. Product Backlog to Product Goal; Sprint Backlog to Definition of Done; Increment to Sprint Goal.
    4. Product Backlog to Product Goal; Sprint Backlog to Sprint Goal; Increment to Definition of Done. Correct answer.

    Explanation

    Each of the three artifacts contains a commitment: the Product Backlog contains the Product Goal, the Sprint Backlog contains the Sprint Goal, and the Increment contains the Definition of Done. These commitments reinforce transparency and focus.

  149. Question 149Scrum Artifacts and Commitments

    Which statement about the Increment is accurate?

    1. Only one Increment can be produced per Sprint, delivered at the Sprint Review.
    2. An Increment exists only once the Product Owner approves it at the Sprint Review.
    3. Several Increments may be created in one Sprint and delivered before it ends. Correct answer.
    4. The Increment is simply another name for the product that has been released.

    Explanation

    Work is released in increments and more than one Increment can be created within a single Sprint. Increments may be delivered to stakeholders before the Sprint concludes, which enables earlier feedback.

  150. Question 150Scrum Artifacts and Commitments

    Why must an Increment be usable?

    1. Because the Definition of Done requires all Increments to be sold to customers.
    2. Because the Scrum Master verifies usability at the end of the Sprint Retrospective.
    3. Because every Increment must be deployed to production before the Sprint Review.
    4. Value is delivered only when the Increment is usable, enabling early feedback. Correct answer.

    Explanation

    Scrum works by delivering valuable, useful increments of work frequently. Value can only be realized, and empirically inspected, when the Increment is in a usable state.

  151. Question 151Scrum Artifacts and Commitments

    The Sprint Backlog is described as a highly visible, real-time picture of the work. What follows from this?

    1. It is jointly owned by the Product Owner and stakeholders, who approve changes.
    2. It emerges during the Sprint and belongs solely to the Developers. Correct answer.
    3. It is maintained by the Scrum Master so the team follows the agreed process.
    4. It is frozen at the end of Sprint Planning so progress can be measured against it.

    Explanation

    The Sprint Backlog is a plan by and for the Developers that emerges during the Sprint as more is learned. It is updated throughout the Sprint so it reflects the real, current picture of the work.

  152. Question 152Scrum Artifacts and Commitments

    Which statement about the state of the Product Backlog is accurate?

    1. It is never complete; it evolves as the product and its environment change. Correct answer.
    2. It is updated only by stakeholders during the Sprint Review, once per Sprint.
    3. It is frozen at the first Sprint Planning in order to protect the Sprint Goal.
    4. It is complete once all the items planned for the upcoming release have been defined.

    Explanation

    The Product Backlog is a living artifact that is never complete; as the product and its environment change, so does the backlog. It is updated continuously by the Scrum Team as part of backlog management and refinement.

  153. Question 153Scrum Artifacts and Commitments

    At the Sprint Review the Scrum Team presents the results of its work. Which artifact is being presented for inspection?

    1. The Sprint Backlog, frozen at the start of the Sprint Review.
    2. The Sprint Goal, which is replaced at the end of the Sprint Review.
    3. The Increment produced during the Sprint. Correct answer.
    4. The Definition of Done, which is renegotiated at each Sprint Review.

    Explanation

    The Sprint Review is a working session where the Scrum Team and stakeholders inspect the outcome of the Sprint. The Increment is the artifact that shows what was actually accomplished and that enables inspection of progress toward the Product Goal.

  154. Question 154Scrum Artifacts and Commitments

    Scrum describes Increments as additive. What does that mean?

    1. Only the final Increment of a release counts as valuable work.
    2. Increments are added together only at the end of the release.
    3. Each Increment builds on earlier ones and stays usable. Correct answer.
    4. Each new Increment replaces the previous one entirely.

    Explanation

    Because each Increment is cumulative, it must build on and remain consistent with the earlier Increments. New work adds to what already exists so the product stays in a usable state after every Sprint.

  155. Question 155Scrum Artifacts and Commitments

    Which artifact is the single source of work undertaken by the Scrum Team?

    1. The Sprint Backlog
    2. The Increment
    3. The Product Backlog Correct answer.
    4. The Definition of Done

    Explanation

    The Product Backlog is an emergent, ordered list of what is needed to improve the product and is the single source of work undertaken by the Scrum Team. The Sprint Backlog is a plan derived from it for the current Sprint, while the Increment is the output and the Definition of Done is a commitment.

  156. Question 156Scrum Artifacts and Commitments

    Who is accountable for the Product Backlog, including its content, availability, and ordering?

    1. The Developers
    2. The Scrum Master
    3. Product Owner Correct answer.
    4. External stakeholders

    Explanation

    The Product Owner is accountable for effective Product Backlog management, which includes content, availability, and ordering. The Developers, Scrum Master, and stakeholders may contribute information, but accountability rests with the Product Owner.

  157. Question 157Scrum Artifacts and Commitments

    Which artifact is updated throughout the Sprint as the Developers learn more?

    1. The Product Goal
    2. The Sprint Backlog Correct answer.
    3. The Increment
    4. The Definition of Done

    Explanation

    The Sprint Backlog is a living plan that is updated throughout the Sprint as more is learned. The Product Goal is a longer-term objective, the Definition of Done is a quality standard, and the Increment is the completed output.

  158. Question 158Scrum Artifacts and Commitments

    Who is accountable for creating the Definition of Done?

    1. The Scrum Team Correct answer.
    2. The Scrum Master
    3. The stakeholders
    4. The Product Owner alone

    Explanation

    The Scrum Team creates the Definition of Done; if an organizational standard exists, it is used as a minimum. The Product Owner, Scrum Master, and stakeholders do not create it unilaterally.

  159. Question 159Scrum Artifacts and Commitments

    Midway through a Sprint, the Developers find that a selected Product Backlog item is larger than expected. What may they negotiate with the Product Owner without changing the Sprint Goal?

    1. A lower Definition of Done for the current Increment
    2. An extension of the Sprint by a few days
    3. The scope of the Sprint Backlog Correct answer.
    4. A replacement Sprint Goal for the remainder of the Sprint

    Explanation

    When work turns out to be different than expected, the Developers collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint without affecting the Sprint Goal. The Sprint Goal, the Definition of Done, and the Sprint length are not adjusted to fit the new information.

  160. Question 160Scrum Artifacts and Commitments

    Why is the Product Backlog described as emergent?

    1. Because it is updated continuously as understanding of the product grows Correct answer.
    2. Because it is written only by external stakeholders and reviewed once
    3. Because it is finalized before the first Sprint begins and then held stable
    4. Because it is reviewed only at the Sprint Review and never between events

    Explanation

    The Product Backlog is emergent because it is continuously updated as the product, its users, and the environment are better understood. It is not frozen at the start, and it is not limited to stakeholder authorship or Sprint Review updates.

  161. Question 161Scrum Artifacts and Commitments

    At the Sprint Review, a stakeholder requests a change that would affect the product but not the current Sprint Goal. What is the most appropriate response?

    1. Ask the Scrum Master to decide whether the request is accepted
    2. Add the request directly to the current Sprint Backlog so the Developers can start on it immediately
    3. Capture the request in the Product Backlog and let the Product Owner consider its ordering Correct answer.
    4. Reject the request because the Sprint is already underway and its scope is fixed

    Explanation

    The Sprint Review is an opportunity to inspect the outcome and adapt the Product Backlog. New requests are captured in the Product Backlog, where the Product Owner can order them against other work; they are not inserted directly into the current Sprint Backlog.

  162. Question 162Scrum Artifacts and Commitments

    When more than one Increment is produced within a single Sprint, what must be true of each Increment?

    1. It must be tied to a separate Sprint Goal
    2. It must be released to production immediately
    3. It must be usable and meet the Definition of Done Correct answer.
    4. It must be reviewed in its own separate Sprint Review

    Explanation

    Multiple Increments may be produced in a Sprint, but each must be usable and meet the Definition of Done. Release is a separate business decision, there is only one Sprint Review per Sprint, and there is only one Sprint Goal.

  163. Question 163Scrum Artifacts and Commitments

    What is the primary reason the Product Owner orders the Product Backlog?

    1. To satisfy the Scrum Master's reporting requirements
    2. To ensure every Product Backlog item has an equal chance of being selected in a Sprint
    3. To lock the scope of the next release
    4. To focus the Scrum Team on the items that will deliver the most value Correct answer.

    Explanation

    Ordering the Product Backlog helps the Scrum Team focus on the most valuable work first. It is not about equal selection chances, reporting to the Scrum Master, or freezing release scope.

  164. Question 164Scrum Artifacts and Commitments

    A Scrum Team is still pursuing its Product Goal when the Product Owner proposes a second, unrelated long-term objective. What does Scrum require?

    1. The second objective is added to the Sprint Backlog instead of the Product Backlog
    2. The team must fulfill or abandon the current Product Goal before taking on another Correct answer.
    3. Both objectives may be pursued in parallel as two separate Product Goals for the product
    4. The Scrum Master decides which objective takes priority

    Explanation

    A product has one Product Goal at a time, and the Scrum Team must fulfill or abandon it before taking on the next objective. Multiple long-term product goals are not pursued in parallel, and Sprint Backlog or Scrum Master authority does not resolve the conflict.

  165. Question 165Scrum Artifacts and Commitments

    Which statement about the ordering of the Product Backlog is accurate?

    1. Items must be ordered strictly by estimated effort, smallest first
    2. The Product Owner orders items by value, risk, dependencies, and size Correct answer.
    3. The Developers order the backlog because they estimate the work
    4. Ordering is fixed at project start and changes only through formal change requests

    Explanation

    The Product Owner orders the Product Backlog, considering value, risk, dependencies, and size as appropriate. Ordering is neither a fixed baseline nor a Developers' decision, and it is not dictated solely by effort.

  166. Question 166Scrum Artifacts and Commitments

    Which approach best reflects Scrum's guidance on Product Backlog refinement?

    1. Items are refined continuously, with near-term items more detailed Correct answer.
    2. Refinement is performed solely by the Product Owner between Sprints
    3. Every item is decomposed to the same level of detail before the first Sprint
    4. Only items selected for the current Sprint are refined by the Developers

    Explanation

    Refinement is an ongoing activity, and items likely to be worked on sooner are broken down more finely than distant items. It is not a one-time decomposition, it is not limited to the current Sprint, and it is not performed solely by the Product Owner.

  167. Question 167Scrum Artifacts and Commitments

    A Product Backlog contains abbreviations that only the Product Owner understands, so other Scrum Team members cannot assess the items. Why is this a problem in Scrum?

    1. It automatically invalidates the Sprint Goal
    2. It reduces transparency, limiting inspection and adaptation Correct answer.
    3. It makes the Increment impossible to release to production users
    4. It prevents the Daily Scrum from starting on time

    Explanation

    Scrum relies on transparent artifacts so that inspection can lead to adaptation. If the Product Backlog cannot be understood by the Scrum Team, its ordering and content cannot be effectively inspected, even though it does not directly invalidate the Sprint Goal or block release.

  168. Question 168Scrum Artifacts and Commitments

    An Increment meets the Definition of Done, but the Product Owner decides not to release it. Which statement is correct?

    1. The Sprint must be cancelled because no value was delivered
    2. The Increment is not truly done until it is released to users
    3. The Definition of Done must be revised to require release
    4. It remains a valid Increment and may be released later Correct answer.

    Explanation

    The Definition of Done determines whether work is complete, while release is a separate business decision. An Increment can meet the Definition of Done without being released immediately, and the Sprint is not cancelled merely because release is deferred.

  169. Question 169Scrum Artifacts and Commitments

    The Scrum Master wants to reorder the Sprint Backlog to help the Developers finish faster. What is the appropriate Scrum response?

    1. The Scrum Master should reorder it because they facilitate the team
    2. The stakeholders should vote on the new order at the Daily Scrum
    3. The Product Owner should reorder it because they own value delivery
    4. The Developers own it and decide how to order the work Correct answer.

    Explanation

    The Sprint Backlog is owned by the Developers, who decide how to plan and order the work within the Sprint. The Scrum Master facilitates, the Product Owner focuses on the Product Backlog, and stakeholders do not vote on the Sprint Backlog order.

  170. Question 170Scrum Rules, Application and Organizational Context

    What is the maximum length of a Sprint in Scrum?

    1. Two weeks
    2. Two months
    3. Six weeks
    4. One month Correct answer.

    Explanation

    A Sprint is a fixed-length event of one month or less that keeps consistency and limits risk to the cost of a single Sprint. Shorter Sprints are common, but the maximum allowed is one month.

  171. Question 171Scrum Rules, Application and Organizational Context

    What is the purpose of the Daily Scrum?

    1. To inspect progress toward the Sprint Goal and adapt the plan Correct answer.
    2. To demonstrate the Increment to stakeholders
    3. To report individual progress to the Scrum Master and Product Owner
    4. To update the Product Backlog with new items

    Explanation

    The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as needed. It is a planning and inspection event for the team, not a status meeting for others.

  172. Question 172Scrum Rules, Application and Organizational Context

    What is the purpose of the Sprint Retrospective?

    1. To refine Product Backlog items for the next Sprint
    2. To review the Increment with stakeholders
    3. To plan ways to increase quality and effectiveness Correct answer.
    4. To draft the Sprint Goal for the next Sprint

    Explanation

    The Sprint Retrospective concludes the Sprint and is the opportunity for the Scrum Team to inspect how the last Sprint went and identify the most helpful changes to improve. The most impactful improvements may be addressed as soon as possible, even added to the Sprint Backlog.

  173. Question 173Scrum Rules, Application and Organizational Context

    Which three pillars uphold empirical process control in Scrum?

    1. Courage, focus, and openness
    2. Vision, value, and validation
    3. Planning, executing, and reviewing
    4. Transparency, inspection, and adaptation Correct answer.

    Explanation

    Scrum is founded on empiricism, which asserts that knowledge comes from experience and decisions are based on what is observed. The three pillars that uphold empirical process control are transparency, inspection, and adaptation.

  174. Question 174Scrum Rules, Application and Organizational Context

    Who is accountable for ordering the Product Backlog?

    1. The key stakeholders
    2. The Scrum Master
    3. The Product Owner Correct answer.
    4. The Developers

    Explanation

    The Product Owner is accountable for effective Product Backlog management, which includes developing and explicitly communicating the Product Goal and ordering Product Backlog items. Others may influence the ordering, but the accountability rests with the Product Owner.

  175. Question 175Scrum Rules, Application and Organizational Context

    What is an Increment?

    1. A concrete step toward the Product Goal Correct answer.
    2. The set of Product Backlog items selected for a Sprint
    3. The list of tasks completed during the Sprint
    4. A document describing the Sprint Goal

    Explanation

    An Increment is a concrete stepping stone toward the Product Goal and is the sum of the useful work completed during a Sprint. Each Increment adds to previous Increments and must meet the Definition of Done to be considered part of it.

  176. Question 176Scrum Rules, Application and Organizational Context

    What is the purpose of the Sprint Review?

    1. To estimate the effort needed for the next Sprint
    2. To inspect the Sprint outcome and adapt future plans Correct answer.
    3. To approve the work completed by the Developers
    4. To identify process improvements for the team

    Explanation

    The Sprint Review is held at the end of the Sprint to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team and stakeholders collaborate on what was accomplished and what to do next.

  177. Question 177Scrum Rules, Application and Organizational Context

    Which statement best describes the Scrum Master's accountability?

    1. Maximizing the value of the product
    2. Owning and ordering the Sprint Backlog
    3. Assigning daily tasks to the Developers and tracking them
    4. Establishing Scrum as described in the Scrum Guide Correct answer.

    Explanation

    The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, which includes coaching the Scrum Team and helping the wider organization understand and adopt Scrum effectively.

  178. Question 178Scrum Rules, Application and Organizational Context

    At the end of a Sprint, a Product Backlog item is functionally complete but does not meet the team's Definition of Done. What should happen?

    1. The Definition of Done is adjusted so the work qualifies
    2. It is presented at the Sprint Review as done
    3. It is excluded from the Increment and returned to the Product Backlog Correct answer.
    4. The Sprint is extended until the work meets the Definition of Done

    Explanation

    Work cannot be considered part of an Increment unless it meets the Definition of Done. Incomplete work is therefore not presented as done and returns to the Product Backlog for future consideration.

  179. Question 179Scrum Rules, Application and Organizational Context

    What is the Sprint Goal?

    1. A forecast of how many items the team will finish
    2. A commitment from the Product Owner to the stakeholders
    3. The Product Backlog items selected for the Sprint
    4. A single objective for the Sprint that provides focus Correct answer.

    Explanation

    The Sprint Goal is a single objective for the Sprint created during Sprint Planning, and it provides guidance on why the Sprint is valuable. It is a commitment of the Sprint Backlog and gives the Developers flexibility on the exact work needed.

  180. Question 180Scrum Rules, Application and Organizational Context

    Which statement about the timebox for Sprint Planning is correct?

    1. Sprint Planning is always timeboxed to four hours no matter the Sprint length
    2. Sprint Planning is timeboxed to two hours for a one-month Sprint in all cases
    3. Sprint Planning has no fixed timebox and can run as long as the team finds useful
    4. Sprint Planning is capped at eight hours for a one-month Sprint Correct answer.

    Explanation

    Sprint Planning initiates the Sprint by laying out the work to be performed, and it is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints the event is usually shorter.

  181. Question 181Scrum Rules, Application and Organizational Context

    Which of the following is the Product Owner accountable for?

    1. Coaching the organization in Scrum adoption
    2. Maximizing the value of the product Correct answer.
    3. Removing impediments that block the Developers
    4. Creating and maintaining the Definition of Done

    Explanation

    The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.

  182. Question 182Scrum Rules, Application and Organizational Context

    Which of the following is the Developers accountable for?

    1. Creating the Sprint Backlog and delivering an Increment Correct answer.
    2. Deciding which stakeholders attend the Sprint Review
    3. Ordering the Product Backlog to maximize product value
    4. Facilitating the Scrum events and coaching the team on Scrum

    Explanation

    The Developers are accountable for creating a plan for the Sprint (the Sprint Backlog), instilling quality by adhering to the Definition of Done, and adapting their plan daily toward the Sprint Goal, delivering a usable Increment each Sprint.

  183. Question 183Scrum Rules, Application and Organizational Context

    What is the Sprint Backlog composed of?

    1. A list of tasks assigned to Developers by the Product Owner
    2. Only the Product Backlog items selected for the Sprint
    3. The Definition of Done and the Product Goal
    4. The Sprint Goal, selected items, and a delivery plan Correct answer.

    Explanation

    The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), and an actionable plan for delivering the Increment (how). It is a plan by and for the Developers.

  184. Question 184Scrum Rules, Application and Organizational Context

    An organization has no standard Definition of Done and the Scrum Team has never created one. What should the Scrum Team do?

    1. Use the acceptance criteria of each Product Backlog item instead
    2. Ask the Scrum Master to write one on the team's behalf
    3. Rely on the Sprint Review to confirm quality
    4. Create a Definition of Done appropriate for the product Correct answer.

    Explanation

    If a Definition of Done is not an organizational standard, the Scrum Team must create one appropriate for the product. The Definition of Done creates transparency by providing everyone with a shared understanding of what it means for work to be complete.

  185. Question 185Scrum Rules, Application and Organizational Context

    What is Product Backlog refinement?

    1. Breaking down and clarifying Product Backlog items Correct answer.
    2. A task performed by the Product Owner alone before Sprint Planning
    3. A meeting held only in the week before a release
    4. A formal Scrum event with a fixed timebox set by the Scrum Master

    Explanation

    Refinement is the ongoing act of breaking down and further defining Product Backlog items into smaller, more precise items. It is not a formal Scrum event and may take as much time as the Scrum Team decides is appropriate.

  186. Question 186Scrum Rules, Application and Organizational Context

    Which topics does Sprint Planning address?

    1. Which stakeholders will attend the Sprint Review
    2. How many defects were resolved in the previous Sprint
    3. The why, the what, and the how of the Sprint Correct answer.
    4. Who will do each task and when progress will be reported to the Product Owner

    Explanation

    Sprint Planning addresses why the Sprint is valuable (the Sprint Goal), what can be done this Sprint (items selected from the Product Backlog), and how the chosen work will get done (the plan). The Sprint Goal is crafted during this event.

  187. Question 187Scrum Rules, Application and Organizational Context

    What does it mean that the Scrum Team is self-managing?

    1. They set their own Sprint length without any constraints
    2. They choose which stakeholders receive progress updates
    3. They may disregard the Scrum Master's coaching
    4. They internally decide who does what, when, and how Correct answer.

    Explanation

    Self-managing Scrum Teams internally decide who does what, when, and how to accomplish their work. This autonomy is bounded by Scrum rules and the accountability of the roles within the team.

  188. Question 188Scrum Rules, Application and Organizational Context

    Two Scrum Teams are working together on the same product. What does Scrum require regarding their Definitions of Done?

    1. The Definition of Done applies only at the final product release
    2. Each team defines and uses its own separate Definition of Done
    3. The teams share one mutually defined Definition of Done Correct answer.
    4. The Product Owner writes a separate Definition of Done for each team

    Explanation

    When multiple Scrum Teams work together on the same product, they must mutually define and comply with the same Definition of Done. A shared standard makes the combined work transparent and allows one integrated Increment.

  189. Question 189Scrum Rules, Application and Organizational Context

    A Sprint is cancelled before its end. What happens to the Product Backlog items that were already completed during that Sprint?

    1. They are carried into the next Sprint without review
    2. Any potentially releasable ones are reviewed and accepted by the Product Owner Correct answer.
    3. They are all discarded and must be re-estimated before reuse
    4. They are automatically released to production

    Explanation

    When a Sprint is cancelled, any completed Product Backlog items are reviewed and, if potentially releasable, accepted by the Product Owner. All incomplete items are returned to the Product Backlog for re-planning.

  190. Question 190Scrum Rules, Application and Organizational Context

    Who is required to attend the Daily Scrum?

    1. All Scrum Team members and any interested stakeholder
    2. The Scrum Master and the Product Owner
    3. Anyone who contributes work to the Sprint
    4. The Developers Correct answer.

    Explanation

    The Daily Scrum is an event for the Developers, who inspect progress toward the Sprint Goal and adapt the Sprint Backlog. If the Product Owner or Scrum Master is actively working on Sprint Backlog items, they participate as Developers.

  191. Question 191Scrum Rules, Application and Organizational Context

    What is the Product Goal?

    1. A metric used to measure team velocity
    2. A commitment the Developers make for each Sprint
    3. A target future state of the product Correct answer.
    4. A list of features planned for the next release

    Explanation

    The Product Goal describes a future state of the product that can serve as a target for the Scrum Team to plan against. It is a commitment of the Product Backlog and lives there as the long-term objective of the team.

  192. Question 192Scrum Rules, Application and Organizational Context

    An organization is adopting Scrum across several departments. Which activity falls within the Scrum Master's accountability to the organization?

    1. Selecting the Product Owner for each Scrum Team
    2. Leading, training, and coaching the organization in its Scrum adoption Correct answer.
    3. Approving the Definition of Done used by all teams
    4. Assigning Developers to teams based on individual skill

    Explanation

    The Scrum Master serves the organization by leading, training, and coaching it in its Scrum adoption, and by helping people understand and enact an empirical approach to complex work. This includes removing barriers between stakeholders and Scrum Teams.

  193. Question 193Scrum Rules, Application and Organizational Context

    Scrum is founded on empiricism. Which three pillars underpin the empirical approach that Scrum applies?

    1. Transparency, documentation, and forecasting
    2. Adaptation, estimation, and collaboration
    3. Planning, inspection, and control
    4. Transparency, inspection, and adaptation Correct answer.

    Explanation

    Scrum is based on empiricism, which asserts that knowledge comes from experience and decisions are made on what is observed. The three pillars that support this process control approach are transparency, inspection, and adaptation, and each Scrum event exists to enable them.

  194. Question 194Scrum Rules, Application and Organizational Context

    Which list contains exactly the five Scrum values?

    1. Focus, respect, transparency, commitment, and inspection
    2. Commitment, discipline, openness, quality, and courage
    3. Courage, openness, accountability, focus, and trust
    4. Commitment, focus, openness, respect, and courage Correct answer.

    Explanation

    The Scrum Guide names five values: commitment, focus, openness, respect, and courage. Successful use of Scrum depends on the team and the people around it living these values, which give direction to the empirical pillars.

  195. Question 195Scrum Rules, Application and Organizational Context

    A Scrum Team's Sprint Retrospective has turned into a status meeting in which each member reports what they did during the Sprint. What should the event focus on instead?

    1. Preparing the Increment for demonstration at the Sprint Review and confirming release dates
    2. Assigning action items to individual members so they can be tracked in the next Daily Scrum
    3. Inspecting how the last Sprint went and identifying the most useful improvements Correct answer.
    4. Reviewing the Sprint Backlog item by item to confirm that every task was finished as planned

    Explanation

    The Sprint Retrospective exists to inspect how the last Sprint went with regard to individuals, interactions, processes, tools, and the Definition of Done, and to identify and address the most impactful improvements. Reporting individual activity describes output rather than inspecting how the team works.

  196. Question 196Scrum Rules, Application and Organizational Context

    A newly formed Scrum Team proposes a Sprint length of five weeks so that it has enough time to complete a whole feature. What does Scrum require?

    1. Five weeks is acceptable if the Product Owner and the Developers agree and record it in the Definition of Done
    2. Five weeks is acceptable for the first few Sprints only, after which the length must be reduced to two weeks
    3. Sprints may be of any length provided every other event stays within its own timebox
    4. Sprints are of fixed length and limited to one month at most, so a shorter length must be chosen Correct answer.

    Explanation

    Sprints are fixed-length events of one month or less, and a new Sprint starts immediately after the previous one ends. Shorter Sprints generally generate more learning and limit risk to the cost of a Sprint, so the team must pick a length within that limit.

  197. Question 197Scrum Rules, Application and Organizational Context

    The Scrum Guide describes Scrum as purposefully incomplete. Which statement best describes what this means in practice?

    1. The Scrum Master must add a delivery process before the first Sprint begins
    2. The framework defines the rules and the team adds the practices it needs Correct answer.
    3. Organizations may replace Scrum with an equivalent method once they mature
    4. The Scrum Team may drop any event it considers unnecessary for its product

    Explanation

    Scrum defines only the parts required to implement its theory and leaves the rest to the people involved, who build in the practices, techniques, and tools that fit their context. The rules themselves are mandatory; incompleteness means the framework expects the team to fill in the tactics, not to omit elements.

PSM I flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Three pillars of empiricism
Transparency, inspection, and adaptation support Scrum's empirical process control; if any pillar is weakened, the decisions made and the artifacts they rely on become unreliable.
Empiricism
Knowledge comes from experience and decisions are based on what is observed; Scrum applies this through short cycles of inspection and adaptation instead of up-front prediction.
Transparency
The emergent process and the work must be visible to those performing it and those receiving it; without visibility, inspection produces misleading conclusions about progress and value.
Scrum value: commitment
The Scrum Team commits to achieving its goals and to supporting each other; the commitment attaches to the team's goals, not to a fixed, unchangeable scope of work.
Scrum value: courage
Team members do the right thing and tackle tough problems; courage supports transparency because people are willing to surface bad news and difficult impediments.
Scrum Team size
Ten or fewer people: one Scrum Master, one Product Owner, and Developers. Smaller teams communicate better; larger groups should split into multiple cohesive Scrum Teams on the same product.
Self-managing Scrum Team
The team internally decides who does what, when, and how. Self-management means no external manager directs the team's day-to-day technical work.
Product Owner accountability
Accountable for maximizing product value and for effective Product Backlog management. The Product Owner is always one person, never a committee, and may delegate work while staying accountable.
Scrum Master accountability
Accountable for establishing Scrum as defined in the Scrum Guide and for the Scrum Team's effectiveness, serving the Scrum Team, the Product Owner, and the wider organization.
Developers' accountabilities
Developers build the Sprint Backlog, instill quality by following the Definition of Done, adapt their plan each day, and hold each other accountable as professionals.
Cross-functional Scrum Team
The team holds all skills needed to create value in every Sprint, which removes hand-offs and dependencies on people outside the team.
Sprint timebox
A Sprint is fixed at one month or less; a new Sprint begins immediately after the previous one ends, and the Sprint contains all other Scrum events.
Sprint Planning timebox
A maximum of eight hours for a one-month Sprint, shorter for shorter Sprints. Planning covers why the Sprint is valuable, what can be done, and how.
Daily Scrum
A fifteen-minute event for Developers on every working day, at the same time and place, to inspect progress toward the Sprint Goal and adapt the Sprint Backlog.
Sprint Review
A maximum four-hour event for a one-month Sprint where the Scrum Team presents the Increment's outcome, stakeholders give feedback, and the Product Backlog is updated.
Sprint Retrospective
The Scrum Team inspects how the last Sprint went regarding individuals, interactions, processes, tools, and the Definition of Done, then plans the most helpful improvements.
Sprint cancellation
Only the Product Owner can cancel a Sprint, and only when the Sprint Goal becomes obsolete. Completed, Done items are reviewed and potentially released.
Product Goal
A long-term target for the Scrum Team described in the Product Backlog; it is the commitment against which the Product Backlog is measured.
Sprint Goal
The single objective for the Sprint, part of the Sprint Backlog; it provides focus and coherence while allowing flexibility about the exact work performed.
Definition of Done
A formal description of the quality measures required for an Increment; when it is an organizational standard, every Scrum Team must meet it as a minimum.
Increment
A concrete, usable stepping stone toward the Product Goal. Work cannot be counted as part of an Increment unless it satisfies the Definition of Done.
Product Backlog
An emergent, ordered list of what is needed to improve the product; it is the single source of the work the Scrum Team undertakes.
Sprint Backlog
Composed of the Sprint Goal, the Product Backlog items selected for the Sprint, and the plan for delivering them; it is updated throughout the Sprint.
Timebox rule
Every Scrum event is a maximum duration. An event may finish early but never runs long, and the Scrum Master keeps each event within its timebox.
Sprint scope renegotiation
As more is learned, scope may be clarified and renegotiated with the Product Owner, provided the Sprint Goal is not endangered and quality does not decrease.
Sprint Goal stability
The Sprint Goal is fixed for the duration of the Sprint; only the scope of the Sprint Backlog around it can be renegotiated with the Product Owner.
Multiple teams, one product
When several Scrum Teams work on the same product, they share one Product Owner, one Product Backlog, one Product Goal, and a common Definition of Done.
Daily Scrum attendance
The Daily Scrum is an internal meeting for Developers; a Product Owner or Scrum Master participates as a Developer only when actively working on Sprint Backlog items.
Scrum is intentionally incomplete
The framework defines only what is required to implement Scrum theory, leaving specific techniques, processes, and tools to the people using it.
Scrum applicability
Scrum can be used to develop products, services, and other complex work; it is not restricted to software development or to information technology.
Adopting Scrum
Implementing Scrum requires changes to organizational structure, processes, and practices; there is no single prescribed path or fixed rollout sequence.
Engineering practices not prescribed
The Scrum Guide does not mandate engineering practices, tools, or techniques; teams choose practices that fit their context and satisfy their Definition of Done.

PSM I study guide

Scrum Theory and Empiricism

Why Scrum works the way it does

Scrum is founded on empiricism - knowledge comes from experience and decisions are made on what is observed - and on lean thinking, which removes what does not add value and keeps focus on the essentials. Work proceeds in iterations and increments so the product is inspected and adapted frequently.

The three pillars

Transparency means the process and the work are visible to those performing and receiving it, using a shared Definition of Done as the standard. Inspection must be frequent enough to detect undesirable variance but not so frequent that it gets in the way of the work. Adaptation follows: if any aspect deviates outside acceptable limits, or the resulting product is unacceptable, adjust as soon as possible - which requires empowered, self-managing people.

The pillars form a chain. Without transparency, inspection is misleading; without inspection, adaptation is guesswork; without adaptation, inspection is theatre. When a question describes something going wrong, trace the failure back to the earliest broken link.

Values

The five Scrum Values - commitment, focus, openness, respect and courage - give direction to behaviour and build the trust empiricism needs. Note that in current Scrum, commitment means dedication to the team's goals (the Sprint Goal, the Product Goal), not a promise to deliver a fixed scope.

Traps

  • Treating empiricism as "no planning" - Scrum plans, but plans are revised as evidence arrives.
  • Confusing transparency with status reporting to management; more reports do not equal more transparency.
  • Assuming inspection must be frequent documentation reviews rather than empirical checkpoints.
  • Believing the values are optional sentiment rather than the behavioural basis of trust.

Rule of thumb

When something feels wrong, ask: what is not visible, what inspection is missing, and who can adapt? Fix transparency first.

The Scrum Team and its Accountabilities

One team, three accountabilities

The Scrum Team is a single small team of 10 or fewer people, cross-functional (it collectively has the skills to create value every Sprint) and self-managing (it decides internally who does what, when and how). There are no sub-teams and no hierarchies within it. The three accountabilities - Product Owner, Scrum Master, Developers - are not three separate teams.

Product Owner is accountable for maximizing product value and for effective Product Backlog management: ordering, clarity and transparency. The Product Owner is one person, never a committee, and may delegate work while remaining accountable. The Product Owner does not dictate the how.

Scrum Master is accountable for the Scrum Team's effectiveness: establishing Scrum as defined in the Scrum Guide, coaching the team and the wider organization, facilitating events where useful, removing impediments and causing change. The Scrum Master is not a project manager, team lead, or scrum police.

Developers are accountable for creating a usable Increment each Sprint, for the Sprint Backlog, and for quality through the Definition of Done.

Traps

  • "Cross-functional" means the team has the skills collectively - not that every person can do every job.
  • "Self-managing" covers how the team organises its own work; it does not remove organizational constraints or accountability for the Increment.
  • The Product Owner is not required at the Daily Scrum; if working on Sprint Backlog items, they participate as Developers.
  • A Scrum Master who assigns tasks has slipped into a management role the framework does not define.
  • "The team decided" is not an answer when the question asks who is accountable.

Rule of thumb

Ask who is the single accountable person? - one person maximizes value, one accountable for effectiveness, and the Developers as a group accountable for the Increment.

Scrum Events

The Sprint as container

Every other event happens inside the Sprint, which is fixed in length at one month or less. Within a Sprint: no changes that endanger the Sprint Goal, quality does not decrease, and scope may be clarified and renegotiated with the Product Owner as more is learned. Only the Product Owner can cancel a Sprint, and only when the Sprint Goal becomes obsolete.

The four events

Sprint Planning (maximum 8 hours for a one-month Sprint) answers why (Sprint Goal), what (items selected) and how (the plan). The output is the Sprint Backlog.

Daily Scrum is a 15-minute event for the Developers, held every working day at the same time and place. Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. The structure is chosen by the Developers. It is not a status meeting, and it is not the only time Developers may adjust their plan.

Sprint Review (maximum 4 hours) is a working session with stakeholders to inspect the Increment and adapt the Product Backlog. It is not a sign-off gate, a demo ritual, or an approval stage.

Sprint Retrospective (maximum 3 hours) concludes the Sprint. The team inspects individuals, interactions, processes, tools and the Definition of Done, and identifies improvements. A new Sprint starts immediately afterwards.

Traps

  • Only Sprint Planning shortens for shorter Sprints (2 hours for a one-week Sprint); the other timeboxes are fixed maximums.
  • The Review and Retrospective happen inside the Sprint, not after it.
  • "Sprint 0", "hardening Sprints" and "release Sprints" are not Scrum events.
  • The Daily Scrum is not where the Product Owner assigns work or collects status.

Rule of thumb

For any event, name what is inspected and what is adapted. If you cannot name both, the event is being run as a ritual.

Scrum Artifacts and Commitments

Three artifacts, three commitments

Each artifact carries a commitment that makes it inspectable: the Product Backlog → Product Goal, the Sprint Backlog → Sprint Goal, and the Increment → Definition of Done.

Product Backlog is an emergent, ordered list of what is needed to improve the product; it is the single source of work. The Product Owner is accountable for its ordering and transparency. Refinement - decomposing and clarifying items - is an ongoing activity, not a formal event.

Product Goal describes a future state of the product and is the long-term objective the team plans against. It is not the Sprint Goal.

Sprint Backlog is composed of the Sprint Goal (why), the selected items (what) and the plan for delivering them (how). It belongs to the Developers and is updated throughout the Sprint as more is learned. It is not a fixed contract with a fixed scope.

Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to previous ones and must be usable. Several Increments may be created within a single Sprint. The Definition of Done is the formal description of the quality state required; the whole Scrum Team creates it, and if multiple teams work on one product they must share and mutually define it. Work that does not meet the Definition of Done is not part of the Increment and returns to the Product Backlog.

Traps

  • Confusing the Product Goal (long-term, product-wide) with the Sprint Goal (one Sprint).
  • Treating the Sprint Backlog as a promise of fixed scope rather than an emerging plan.
  • Assuming "usable Increment" means it must be released every Sprint.
  • Believing the Product Owner alone sets the Definition of Done.
  • Thinking artifacts must be specific documents or tools.

Rule of thumb

Artifact = information you inspect; commitment = the target that makes inspection meaningful.

Scrum Rules, Application and Organizational Context

Scrum Rules

The non-negotiables

Scrum's rules are few, but they are what make it Scrum. If you remove them, you are doing something else - possibly useful, but not the framework being tested.

Team rules: one Scrum Team, 10 or fewer, with no sub-teams or hierarchies; exactly one Product Owner; three accountabilities, not three teams.

Sprint rules: length is one month or less and consistent; no changes that endanger the Sprint Goal; quality does not decrease; scope may be clarified and renegotiated with the Product Owner; only the Product Owner may cancel, and only when the Sprint Goal becomes obsolete.

Event rules: all five events happen; timeboxes are maximums (Planning 8 hours, Daily 15 minutes, Review 4 hours, Retrospective 3 hours for a one-month Sprint); the Daily Scrum is held every working day; the Retrospective ends the Sprint.

Artifact rules: the Product Backlog is ordered and transparent; the Sprint Backlog is updated as more is learned; the Definition of Done is used whenever work is judged complete.

Accountability rules: the Product Owner maximizes value; the Scrum Master ensures the team's effectiveness and that events take place within their timeboxes; the Developers create the Increment; the Scrum Team is accountable for all product-related activities.

Traps

  • "We skipped the Retrospective because we were busy" - the event is mandatory and its loss is a loss of adaptation.
  • "We added a hardening Sprint" - not a Scrum construct.
  • Treating refinement as a formal, timeboxed event in the framework.
  • Believing the Daily Scrum may run long if the discussion is valuable.
  • Believing a Sprint can be extended to finish work.

Rule of thumb

If a proposed practice needs a new role, event or artifact, it is a complement to Scrum - permitted, but never confused with the framework itself.

Application and Organizational Context

Deliberately incomplete

Scrum is intentionally incomplete: it defines only what is required to implement empiricism, and the organization supplies the rest. It is designed for complex work where requirements and approach emerge, and it says nothing about funding models, HR policy, architecture or tooling - those must be shaped to support it, not the reverse.

Serving beyond the team

The Scrum Master serves the organization: leading and coaching Scrum adoption, planning and advising implementations, helping stakeholders and employees understand empiricism, and removing barriers between stakeholders and the Scrum Team. The Product Owner serves the stakeholders by managing the Product Backlog and its transparency; the Developers serve each other.

Environment is the constraint

Organizations adopting Scrum usually must change funding cycles, performance measurement, governance and reporting that assume predictive planning. Common anti-patterns: a proxy Product Owner relaying decisions, a PMO approving Increments, component teams creating hand-offs, scaling by adding process instead of removing dependencies, and "transformation" programmes that leave incentives untouched.

Traps

  • "Escalate to the PMO and follow the stage gates" - first ask whether the gate is an impediment the Scrum Master should help remove.
  • "The team should produce a weekly percent-complete report" - the Sprint Review and the Increment are the transparency mechanisms; extra reporting is not transparency.
  • "The Daily Scrum should be open so managers can get status" - the Daily Scrum serves the Developers; other channels can carry information outward.
  • Treating Scrum as a complete methodology, or as a fix for problems caused by unclear goals or poor engineering.

Worked example

A team is required to report percent-complete against a fixed annual plan. The Scrum Master coaches the stakeholders on why an emerging Product Backlog cannot be forecast that way, and offers the Sprint Review plus the Product Goal as the honest substitute. The framework is not bent to fit the plan; the plan is changed to fit empiricism.

Rule of thumb

When the organization and Scrum conflict, the Scrum Master's job is to change the organization - not to bend the framework.

PSM I cheat sheet

Quick reference

Scrum Theory and Empiricism

  • Scrum is founded on empiricism and lean thinking; empiricism asserts that knowledge comes from experience and that decisions are made on observation.

  • The three empirical pillars are transparency, inspection, and adaptation; weakening any one of them undermines the other two.

  • Transparency requires that the emergent process and the work be visible to those performing it and those receiving it; low transparency produces decisions that reduce value and increase risk.

  • Inspection must be frequent enough to detect unwanted variance but not so frequent that it interferes with the work being inspected.

  • Adaptation follows inspection: the process, or the products being produced, is adjusted when results fall outside acceptable limits.

  • The four formal inspect-and-adapt events are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective; the Sprint is the container event for all of them.

  • The five Scrum values are commitment, focus, openness, respect, and courage; they shape behavior and build the trust on which empiricism depends.

  • Lean thinking in Scrum means reducing waste and focusing on the essentials; the Product Backlog is pruned of work that does not add value.

Quick reference

The Scrum Team and its Accountabilities

  • The Scrum Team consists of one Scrum Master, one Product Owner, and Developers; it has 10 or fewer people and no sub-teams or hierarchies.

  • The Scrum Team is cross-functional (it has all skills needed to create value each Sprint) and self-managing (it decides who does what, when, and how).

  • The Product Owner is accountable for maximizing the value of the product and for effective Product Backlog management; the role is held by one person, not a committee.

  • The Scrum Master is accountable for the Scrum Team's effectiveness, coaching self-management and helping the team improve its practices.

  • The Scrum Master serves the Product Owner by helping find techniques for defining the Product Goal and managing the Product Backlog, and by facilitating stakeholder collaboration.

  • The Scrum Master serves the organization by leading Scrum adoption, advising on implementation, and removing barriers between stakeholders and Scrum Teams.

  • Developers create the Sprint Backlog, instill quality by adhering to the Definition of Done, adapt their plan daily, and hold each other accountable.

  • The whole Scrum Team is accountable for creating a valuable, useful Increment every Sprint; individual accountabilities exist, but the result is shared.

Quick reference

Scrum Events

  • The Sprint is a fixed-length event of one month or less; a new Sprint starts immediately after the conclusion of the previous one, with no gap between them.

  • Sprint Planning has a maximum of 8 hours for a one-month Sprint and addresses why the Sprint is valuable (Sprint Goal), what can be done, and how the work will be done.

  • The Daily Scrum is a 15-minute event for Developers, held every working day at the same time and place, to inspect progress toward the Sprint Goal and adapt the Sprint Backlog.

  • The Sprint Review has a maximum of 4 hours for a one-month Sprint; the Scrum Team presents results to key stakeholders and the Product Backlog is updated.

  • The Sprint Retrospective has a maximum of 3 hours for a one-month Sprint and closes the Sprint by identifying the most helpful improvements.

  • Shorter Sprints generate more learning cycles and limit risk; event timeboxes scale down proportionally for shorter Sprints.

  • Only the Product Owner can cancel a Sprint, and only when the Sprint Goal becomes obsolete.

  • The Daily Scrum is not the only time Developers may adapt their plan; they can meet as often as needed throughout the day.

Quick reference

Scrum Artifacts and Commitments

  • There are three artifacts: Product Backlog, Sprint Backlog, and Increment; each carries a commitment, namely the Product Goal, the Sprint Goal, and the Definition of Done respectively.

  • The Product Backlog is an emergent, ordered list of what is needed to improve the product; it is the single source of work undertaken by the Scrum Team.

  • The Product Goal describes a future state of the product and serves as a long-term target; it must be fulfilled or abandoned before the next Product Goal is taken on.

  • The Sprint Backlog is composed of the Sprint Goal, the Product Backlog items selected for the Sprint, and the plan for delivering them; it is updated throughout the Sprint.

  • An Increment is a concrete stepping stone toward the Product Goal; work cannot be considered part of an Increment unless it meets the Definition of Done.

  • The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.

  • If the Definition of Done is an organizational standard, all Scrum Teams must follow it as a minimum; if not, the Scrum Team creates its own.

  • Multiple Scrum Teams working on the same product share the same Product Owner, Product Backlog, Product Goal, and Definition of Done.

Quick reference

Scrum Rules

  • Timeboxes are maximum durations; an event may end early but must never exceed its allotted timebox.

  • A Sprint may not exceed one month; shorter Sprints reduce risk, but no Sprint may run longer than the maximum.

  • During a Sprint, no change is permitted that would endanger the Sprint Goal, and quality goals do not decrease.

  • Sprint scope may be clarified and renegotiated with the Product Owner as more is learned, without altering the Sprint Goal.

  • The Scrum Master ensures that all Scrum events take place and are positive, productive, and kept within the timebox.

  • If the Sprint Goal becomes obsolete, the Product Owner may cancel the Sprint; completed and Done items are reviewed and potentially released.

  • There is exactly one Product Owner per product; the Product Owner may delegate work but remains accountable for the outcome.

Quick reference

Application and Organizational Context

  • Scrum is a lightweight framework that is intentionally incomplete; it defines only what is required to implement Scrum theory, leaving techniques to the people using it.

  • Scrum can be used to develop products, services, and other complex work; it is not limited to software.

  • Scrum employs an iterative, incremental approach to optimize predictability and to control risk.

  • Adopting Scrum requires changes to organizational structure, processes, and practices; there is no single prescribed path or rollout sequence.

  • Implementations typically start with a small, willing team and expand iteratively, learning from each cycle of inspection and adaptation.

  • The Scrum Guide does not prescribe engineering practices, tools, or techniques; teams select practices that fit their context and satisfy the Definition of Done.

  • Because self-management shifts authority, organizations commonly need leadership support and adjustments to budgeting, governance, and people practices.

PSM I key terms

Empiricism

The belief that knowledge comes from experience and from decisions based on what is actually observed, rather than on theory or prediction alone. Scrum applies it through transparency, inspection, and adaptation.

Related: Transparency, Inspection, Adaptation
Transparency

A state in which the process, its work, and its results are visible to the people who need to see them, so that inspection reveals real problems instead of hidden ones.

Related: Inspection, Adaptation
Inspection

The frequent, careful examination of Scrum artifacts and progress toward goals, carried out by skilled people using agreed standards, so that problems are detected early.

Related: Transparency, Adaptation
Adaptation

Adjusting the process or the product as soon as an inspection shows that something is off-track or is producing an unacceptable result.

Related: Inspection, Sprint Retrospective
Complexity

A condition with many interacting parts and unpredictable outcomes, where cause and effect are clear only in hindsight; Scrum is built for this kind of work.

Related: Empiricism, Iterative and Incremental Development
Scrum Values

Commitment, focus, openness, respect, and courage: five behavioral expectations that guide how Scrum Team members work together and treat each other and their stakeholders.

Related: Transparency, Self-Managing Team
Iterative and Incremental Development

Building a product through repeated short cycles while adding usable pieces of functionality each cycle, so that learning and value arrive early and often.

Related: Sprint, Increment
Lean Thinking

A way of working that aims to reduce waste, limit work in progress, and keep attention on what delivers value, shaping Scrum's short cycles and focus on essentials.

Related: Scrum Values, Complexity
Scrum Team

A small, cohesive group of ten or fewer people made up of one Product Owner, one Scrum Master, and Developers, collectively responsible for delivering a valuable, usable Increment each Sprint.

Related: Product Owner, Developers, Scrum Master
Product Owner

The single accountable person for maximizing product value, who develops and communicates the Product Goal, orders the Product Backlog, and decides which work is worth doing.

Related: Product Goal, Product Backlog
Developers

The Scrum Team members who create the usable Increment each Sprint, self-manage their daily work, and hold all the skills needed to turn backlog items into Done work.

Related: Sprint Backlog, Definition of Done
Scrum Master

The accountable person for establishing Scrum as defined in the Scrum Guide and for helping the team and organization improve their use of it through teaching, coaching, and removing impediments.

Related: Scrum Team, Impediment
Self-Managing Team

A team that decides internally who does what, when, and how, rather than being directed by a manager or by the Scrum Master.

Related: Developers, Scrum Team
Cross-Functional Team

A team holding all the skills necessary to create value independently, so it does not depend on people outside the team to finish an Increment.

Related: Developers, Increment
Impediment

A blocker or obstacle that slows or stops the team's progress and that the Scrum Master helps to remove. It may sit inside the team or in the wider organization.

Related: Scrum Master, Daily Scrum
Product Goal

A long-term target describing a future state of the product that gives the Product Backlog direction; it is the commitment attached to the Product Backlog.

Related: Product Backlog, Artifact Commitment
Product Backlog

An emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team and it is never complete.

Related: Product Owner, Product Backlog Refinement, Product Goal
Product Backlog Refinement

The ongoing activity of breaking down and clarifying Product Backlog items so they are small and understood well enough to be selected in Sprint Planning; the team decides how much time to spend.

Related: Product Backlog, Product Backlog Item
Product Backlog Item

A single entry in the Product Backlog, such as a feature, fix, or improvement. Items carry a description, an order, and often an estimate, and become Sprint work when selected.

Related: Product Backlog, Sprint Backlog
Sprint Goal

A single objective for the Sprint that gives the team a shared focus and flexibility; it is the commitment attached to the Sprint Backlog and is met through the items selected.

Related: Sprint Backlog, Sprint, Artifact Commitment
Sprint Backlog

The set of Product Backlog items selected for the Sprint plus the plan for delivering them. It is created in Sprint Planning and updated by the Developers as they learn.

Related: Sprint Goal, Developers, Sprint Planning
Increment

The concrete, usable step toward the Product Goal produced during a Sprint. Each Increment adds to earlier ones and must meet the Definition of Done to count as complete.

Related: Definition of Done, Sprint
Definition of Done

A shared, explicit checklist of the quality standards work must meet before it counts as complete; it is the commitment attached to the Increment.

Related: Increment, Artifact Commitment
Artifact Commitment

The value or standard attached to each Scrum artifact, namely the Product Goal, Sprint Goal, and Definition of Done, used to check progress and keep work focused.

Related: Product Goal, Sprint Goal, Definition of Done
Sprint

A fixed-length cycle of one month or less in which the Scrum Team turns selected work into a usable Increment; every other Scrum event happens inside it.

Related: Sprint Planning, Increment, Timebox
Sprint Planning

The event that starts the Sprint, where the team agrees why the Sprint is valuable, what can be done in it, and how the chosen work will be carried out.

Related: Sprint Goal, Sprint Backlog, Forecast
Daily Scrum

A 15-minute event for the Developers, held every working day, to inspect progress toward the Sprint Goal and adjust the Sprint Backlog plan for the next day.

Related: Developers, Sprint Backlog, Impediment
Sprint Review

The second-to-last event of the Sprint, where the team and stakeholders inspect the Increment and the Product Backlog together and adapt what happens next.

Related: Increment, Stakeholder Collaboration, Sprint Retrospective
Sprint Retrospective

The final event of the Sprint, where the team inspects how it worked and identifies the most useful improvements to apply in the next Sprint.

Related: Adaptation, Sprint Review
Timebox

A maximum duration set for a Scrum event so it stays focused; if the event's purpose is achieved earlier, it can end sooner.

Related: Sprint, Daily Scrum
Forecast

The team's realistic expectation, formed during Sprint Planning, about what it can deliver in the Sprint based on its capacity and on what it has learned so far.

Related: Sprint Planning, Sprint Backlog
Sprint Cancellation

Ending a Sprint before its timebox expires. Only the Product Owner may do this, and only when the Sprint Goal becomes obsolete; finished work is reviewed and the rest returns to the backlog.

Related: Sprint, Sprint Goal, Product Owner
Scrum Framework

The lightweight structure of accountabilities, events, artifacts, and rules described in the Scrum Guide; it is deliberately incomplete, leaving specific practices to the team.

Related: Timebox, Empiricism, Scrum Team
Stakeholder Collaboration

Working closely with customers, users, and others affected by the product so their needs inform the Product Backlog and are examined at each Sprint Review.

Related: Sprint Review, Product Owner
Organizational Adoption of Scrum

Changing structures, policies, and habits across an organization so Scrum Teams can genuinely self-manage and deliver value, often guided by the Scrum Master.

Related: Scrum Master, Definition of Done, Self-Managing Team

PSM I study plan

8 weeks · About 7 hours per week

Week 1

The Scrum Team and its Accountabilities

  • Define each Scrum Team accountability (Product Owner, Scrum Master, Developers) in your own words and list two behaviors that do and do not belong to each

  • Map the three accountabilities onto a single product scenario and write out who decides what for five sample decisions

  • Explain why the Scrum Team is one self-managing unit with no sub-teams or hierarchies, citing at least three consequences for how work is assigned

  • Distinguish the Product Owner's authority over Product Backlog ordering from the Developers' authority over how to do the work

Your checkpoint

A one-page accountability matrix (3 roles x decisions/behaviors) with zero role overlap and a 10-question self-quiz scored at 8/10 or better

Week 2

The Scrum Team and its Accountabilities & Scrum Theory and Empiricism

  • Describe the ideal size and composition of a Scrum Team and justify the trade-offs of being too small or too large

  • Connect each of the three empirical pillars (transparency, inspection, adaptation) to a concrete Scrum Team behavior that supports or undermines it

  • Explain the five Scrum values and give one observable team behavior that demonstrates each

  • Identify three anti-patterns where a role is diluted or outsourced (e.g., proxy Product Owner, part-time Scrum Master) and state the empirical cost of each

Your checkpoint

A written scenario analysis of a 12-person team with a proxy Product Owner, naming every violation and the corrective action, reviewed against your own notes for accuracy

Week 3

Scrum Events

  • Sequence the five Scrum events and state for each its purpose, timebox, participants, and the artifact or commitment it serves

  • Compute correct timeboxes for a one-month Sprint and for a shortened two-week Sprint

  • Explain the Sprint as a container for the other four events and list what may and may not change during a Sprint

  • Describe how Sprint Planning produces a Sprint Goal and how Daily Scrum serves the Developers' plan for the next 24 hours

  • Distinguish Sprint Review (product inspection, stakeholder collaboration) from Sprint Retrospective (process and people improvement) with two concrete agenda items each

Your checkpoint

A single reference table of all five events (purpose, who attends, timebox for 1-month and 2-week Sprints, output) plus a timed 25-question practice set scored at 80% or above

Week 4

Scrum Events & Scrum Theory and Empiricism

  • Explain how each event creates inspect-and-adapt opportunities and what breaks empirically when an event is skipped or merged

  • Justify the Daily Scrum as a Developers' event, not a status report to the Scrum Master or Product Owner

  • Describe how the Sprint Retrospective leads to at least one concrete improvement acted on in the next Sprint

  • Correct five common event anti-patterns (e.g., cancelling the Retrospective, using the Review as a demo-only session) and state the replacement behavior

Your checkpoint

A 30-minute mock exam covering Domains 2 and 3 only, scored at 85% or above, with every missed question rewritten as a corrected statement

Week 5

Scrum Artifacts and Commitments

  • State the purpose of each artifact (Product Backlog, Sprint Backlog, Increment) and the single commitment attached to each

  • Explain why the Product Goal, Sprint Goal, and Definition of Done are commitments rather than optional add-ons

  • Describe the Definition of Done as a commitment to quality and explain what happens to an Increment that does not meet it

  • Explain why the Product Backlog is emergent and how refinement keeps it ready without turning it into a fixed contract

  • Identify which artifact or commitment a given scenario violates and name the repair

Your checkpoint

A three-artifact / three-commitment poster plus 15 scenario cards (violation + repair) that you can answer correctly without notes

Week 6

Scrum Artifacts and Commitments & Scrum Rules, Application and Organizational Context

  • Trace how information flows between artifacts and events across one full Sprint, from Product Goal to Increment

  • Explain the Increment as a stepping stone toward the Product Goal and why multiple Increments may exist within one Sprint

  • Describe what it means for Scrum to be lightweight, simple to understand, and difficult to master, using two examples of each

  • Explain why Scrum is intentionally incomplete and how the organization's context shapes its application without changing the rules

  • Identify organizational impediments (e.g., mandated processes conflicting with Scrum) and describe the Scrum Master's role in removing them

Your checkpoint

A one-page Sprint flow diagram linking every artifact, commitment, and event, with a written explanation of two organizational impediments and the Scrum Master's response

Week 7

Scrum Rules, Application and Organizational Context & Scrum Theory and Empiricism

  • Apply the Scrum rules to five ambiguous situations (mid-Sprint scope change, Sprint cancellation, unfinished work, a team member added mid-Sprint) and state the rule-based answer

  • Explain why Sprint cancellation is rare and who alone holds that authority, and what happens to completed work when a Sprint is cancelled

  • Distinguish empiricism from waterfall and gate-based planning using a single product example carried through both

  • Identify at least three ways organizations misuse Scrum while keeping the ceremony names, and name the empirical consequence of each

  • Explain how the Scrum Master serves the Scrum Team, the Product Owner, and the organization differently

Your checkpoint

A written response to five rule-application scenarios, each citing the relevant Scrum principle, checked against your event and artifact tables for consistency

Week 8

Scrum Theory and Empiricism & The Scrum Team and its Accountabilities & Scrum Events & Scrum Artifacts and Commitments & Scrum Rules, Application and Organizational Context

  • Recite from memory the purpose, timebox, participants, artifacts, and commitments for all five events and three artifacts

  • Complete two full-length timed practice exams and log every miss by domain

  • Re-study only the two weakest domains identified by the practice-exam log

  • Explain every wrong answer in your own words without referring to the original question wording

  • Simulate exam conditions once end to end within the time limit

Your checkpoint

A scored practice-exam log showing 85% or above on the final attempt with all domains at 80% or above, plus a one-page personal weak-spot summary

Milestones

Week 2: Can name all three accountabilities, the three empirical pillars, and the five Scrum values from memory and explain how they connect

Week 4: Scores 85% or above on a 30-question mock limited to Domains 2 and 3, the two heaviest domains

Week 6: Can draw the full artifact/commitment/event map from memory in under five minutes and explain each link aloud

Week 8: Scores 85% or above on a full-length timed mock with no domain below 80%, and has a written weak-spot summary

PSM I exam day

Your checklist

Government-issued photo ID

Bring/confirm acceptable ID. Whether ID is checked depends on delivery format; confirm exact requirements with Scrum.org before exam day. needs_review

Scrum.org account credentials

Know your username and password and be able to log in before your test window. Do not rely on a password reset during the exam.

Assessment access link or confirmation email

Locate the assessment link/instructions in your Scrum.org account or email before you start. Confirm with the provider how access is delivered. needs_review

Reliable internet connection with a backup

Use a stable connection and have a phone hotspot or alternate network available in case your primary connection fails.

Suitable computer and browser

Use a supported browser on a reliable computer. Confirm with the provider whether a webcam, microphone, or specific browser is required for your delivery format. needs_review

Power cable or fully charged device

Prevent mid-exam shutdowns by keeping the device plugged in or fully charged.

Quiet, private, distraction-free space

Arrange a room where you will not be interrupted. Tell household members or colleagues not to disturb you.

Current Scrum Guide

Have the current Scrum Guide available only if the provider permits reference materials during the assessment. Confirm the open-book/closed-book policy with Scrum.org. needs_review

Clock or timer

Keep track of elapsed time. Confirm the exact time limit and question count with the provider before exam day. needs_review

Provider support contact information

Save the support/contact details so you can report technical problems immediately if they occur.

Water and a light snack for before/after

Stay hydrated and eat beforehand; keep snacks for after the exam so they do not distract you during the timed session.

Plan the day

Final 72 hours

Re-read the current Scrum Guide and focus on areas you miss on practice assessments. Take a timed practice assessment if available and review every missed question.

Final 72 hours

Confirm your assessment access, login, price/retake terms, time limit, question count, passing score, and any ID or proctoring requirements directly with Scrum.org.

Final 72 hours

Protect sleep. Avoid cramming new material late at night; consolidate rather than memorize.

Final 24 hours

Do a light review only: Scrum accountabilities, events, artifacts, commitments, and the purpose of each. Stop studying early enough to sleep well.

Final 24 hours

Test your computer, browser, internet, and login. Find your access link and support contact details.

Morning of

Eat normally, hydrate, and avoid scheduling the exam immediately after a stressful event. Set up your quiet space and close unnecessary applications.

Morning of

Log in early enough to resolve technical issues. Keep your ID, login details, and support contact within reach.

During the test

Read each question fully and watch for multiple-select items. Select the required number of answers and do not leave blanks unless the format penalizes guessing; confirm the scoring rules with the provider.

During the test

Pace yourself. Use a simple time checkpoints plan, flag uncertain items if the platform allows it, and reserve time to review flagged questions.

During the test

If a technical problem occurs, contact provider support immediately and note the time and issue. Do not wait until the end of the exam.

Rules to check

  • Use only your own Scrum.org account and take the assessment yourself. Do not share questions, answers, or screenshots with others.

  • Follow the provider's rules on reference materials. Do not assume the assessment is open book or closed book; confirm the policy with Scrum.org before starting.

  • Keep your ID and account details available. Confirm with the provider whether ID verification or proctoring applies to your delivery format.

  • Breaks are generally not built into a timed assessment. If you leave the screen, the timer may continue; confirm break rules with the provider before exam day.

  • Confirm the current question count, time limit, and passing score with Scrum.org. Do not rely on remembered numbers from older materials.

  • If you fail, confirm retake pricing and eligibility directly with the provider rather than assuming a free or discounted retake.

  • Report technical issues to provider support immediately and follow their instructions; do not attempt unauthorized workarounds.

  • Do not use unauthorized assistance, second devices, or communication tools during the assessment. If you are unsure whether something is allowed, ask the provider before exam day.

PSM I FAQ

How many Professional Scrum Master I (PSM I) practice questions are available?

The practice set has 197 Professional Scrum Master I (PSM I) questions. Each one includes the choices, the correct answer, and an explanation, and the set is free to read with no signup.

How many Professional Scrum Master I (PSM I) flashcards are available?

The flashcard set has 32 Professional Scrum Master I (PSM I) cards. Each card shows the term and its definition.

Which topics does the Professional Scrum Master I (PSM I) study material cover?

The Professional Scrum Master I (PSM I) study material has 5 sections, including Scrum Theory and Empiricism, The Scrum Team and its Accountabilities, and Scrum Events.

What format facts does the catalog list for the Professional Scrum Master I (PSM I) exam?

The catalog lists these item types: multiple choice, multiple answer, and true/false for the Professional Scrum Master I (PSM I) exam.