SMP overview

  • 198 practice questions
  • 32 flashcards
  • 8 study guide topics
  • 38 key terms

What you'll study

  • Scrum Theory and Principles15%
  • Scrum Roles and Accountabilities15%
  • Scrum Events15%
  • Scrum Artifacts and Commitments12%
  • Coaching and Facilitation15%
  • Servant Leadership and Team Development12%
  • Product Delivery and Value Maximization8%
  • Organizational Agility and Scaling8%

The Safety Management Professional (SMP) is a professional certification offered by the Board of Certified Safety Professionals (BCSP). It is aimed at experienced safety, health and environmental practitioners who have moved, or are moving, beyond single-hazard technical work into designing, running and improving an organization's safety management system. Typical candidates already hold safety responsibilities and want an externally validated way to demonstrate competence in program-level leadership: setting policy, allocating risk-based priorities, measuring performance, and influencing managers outside the safety function. The exam samples that body of practice rather than narrow regulatory recall, so questions tend to be scenario-based and ask for the best next action rather than a definition. Preparation usually combines three things: a careful read of the current official blueprint so study time matches published domain weights; structured review of safety management system concepts, risk assessment and performance measurement; and repeated practice with applied, judgment-style questions followed by review of why each distractor fails. Candidates should confirm all administrative details - item count, time limit, passing standard, fee, retake rules and recertification cycle - directly with BCSP and the current blueprint, because those details are revised periodically and any figure circulating elsewhere may be out of date.

Common mistakes

When the stem says the Developers are stuck, unsure, or disagreeing, the candidate picks the option where the Scrum Master assigns work, sets priorities, or tells the team what to do next - effectively answering as a project manager.

Habit from traditional delivery roles and from easier exams where the Scrum Master is described as 'ensuring' things happen; the word 'ensure' gets read as 'do it myself'.

What to do instead

For any 'team is stuck' stem, eliminate every option that has the Scrum Master deciding content or assigning tasks. Keep only options where the Scrum Master teaches, coaches, facilitates, or asks a question that grows the team's ability to decide. The accountability is the Scrum Team's effectiveness, exercised through influence, not authority.

Treating the Daily Scrum as a status report to the Scrum Master - endorsing the three questions as a mandatory ritual, letting it run past 15 minutes, or having the Scrum Master run it and take notes for stakeholders.

It looks like the most familiar Scrum event and the three questions are widely quoted, so candidates answer from folklore rather than from the event's purpose.

What to do instead

Anchor every Daily Scrum option on purpose: Developers inspect progress toward the Sprint Goal and adapt the Sprint Backlog, within a 15-minute timebox, owned by the Developers. The Scrum Master teaches why it matters and ensures it happens, but does not chair or collect output from it.

Mismatching artifacts with their commitments - pairing the Sprint Backlog with the Definition of Done, the Product Backlog with the Sprint Goal, or answering that the Definition of Done is an artifact rather than a commitment.

The commitments were added later and the three pairs are structurally similar, so under time pressure candidates pattern-match on the artifact name instead of recalling the pairing.

What to do instead

Memorise the three fixed pairs and re-derive rather than recall: Product Backlog → Product Goal, Sprint Backlog → Sprint Goal, Increment → Definition of Done. If an option reorders a pair, it is wrong regardless of how sensible the sentence sounds.

Choosing options that increase control and predictability - detailed up-front design, a fixed scope commitment for the quarter, phase gates, or a consolidated status dashboard - when the stem describes uncertainty or volatility.

Risk and unpredictability feel safer when locked down, and such options read as 'responsible' and senior, which is exactly how distractors are written.

What to do instead

Test each option against empiricism: does it increase transparency and the ability to adapt, or does it freeze decisions earlier and hide information? In volatile stems the correct option usually shortens feedback loops and exposes reality sooner, even though it feels less controlled.

Using the wrong intervention level - answering 'explain the framework to them' or 'send them the Scrum Guide' when the stem needs coaching, or answering 'ask a powerful open question' when the situation needs immediate, direct action on a blocking organisational problem.

Candidates learn that coaching is the 'advanced' answer and over-apply it, or conversely default to instructing because it feels decisive and fast.

What to do instead

Match the intervention to readiness and risk: teaching when knowledge is missing, mentoring when experience is missing, coaching when the capability exists but the thinking needs unlocking, and direct action when something is actively blocking the team. Ask 'what does this person or team lack - knowledge, experience, or space to think?'

Having the Scrum Master personally remove every impediment, or escalating to management as the first move, rather than helping the team learn to remove what it can and reserving Scrum Master action for impediments outside the team's influence.

Removing blockers feels like visible, measurable service, and escalation feels like strong servant leadership, so both attract candidates over slower capability-building options.

What to do instead

Classify each impediment by who can act: if the team can remove it, coach and let them; if it is organisational, the Scrum Master owns it and works the system. Choose the option that matches the classification in the stem rather than the option that shows the most activity.

Equating value with output - selecting 'increase velocity', 'deliver more story points per Sprint', or 'keep the team fully utilised' as the goal of improvement work, and accepting utilisation-based metrics as evidence of success.

Velocity is the most visible number in Scrum reporting, so it gets treated as the scoreboard, especially in stems where stakeholders are demanding more delivery.

What to do instead

Re-anchor on outcome: value is progress toward the Product Goal and evidence that a customer or business problem moved, not throughput. When an option optimises flow of value to stakeholders it beats an option that optimises the team's output volume.

Answering a multi-team or enterprise-level stem by naming a scaling framework or adding a coordinating layer - a Scrum of Scrums, a release train, a portfolio board - before addressing the underlying Scrum and technical practice problems driving the friction.

Framework names are memorable and feel like the 'professional' answer at scale, and the stems are written to make the coordination artefact look like the missing ingredient.

What to do instead

Diagnose before prescribing: most scaling stems resolve to reducing dependencies, improving the Definition of Done and technical quality, and getting single-team Scrum genuinely working. Prefer the option that removes the cause of cross-team coupling over the option that institutionalises meetings to manage it.

Blurring single-person accountabilities into 'the team decides everything' - saying the Developers set the Sprint Goal unilaterally, that the Product Owner must accept whatever ordering the team prefers, or that the Scrum Master is accountable for the Product Backlog.

Self-management is over-generalised into a rule that nobody holds individual accountability, and the distributed language of the Scrum Guide gets flattened into 'the team owns it'.

What to do instead

Learn the accountability table precisely: one Product Owner accountable for maximising product value and for effective Product Backlog management; Developers accountable for the Sprint Backlog and the Increment; Sprint Goal is a collaborative commitment. Reject options that erase the single accountable person, and reject options that hand that person's accountability to the team.

Treating event timeboxes and the Sprint itself as flexible management levers - extending the Sprint when the work is unfinished, cancelling it because scope changed or stakeholders are unhappy, or skipping the Retrospective under delivery pressure.

In real workplaces these compromises are routine, so they feel pragmatic rather than incorrect, and the stems often supply a sympathetic reason for the exception.

What to do instead

Only the Product Owner can cancel a Sprint, and only when the Sprint Goal has become obsolete - never to protect utilisation or appease stakeholders. Timeboxes are fixed, events may be shortened but not skipped, and a Sprint that ends without a releasable Increment is a transparency signal to inspect, not a reason to extend.

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

SMP practice

198 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 Principles

    Which three pillars support Scrum's empirical process control?

    1. Commitment, focus, and courage.
    2. Transparency, inspection, and adaptation. Correct answer.
    3. Analysis, design, and testing.
    4. Planning, execution, and review.

    Explanation

    Empirical process control rests on making work visible, checking it regularly, and adjusting based on what is found. These three pillars underpin every Scrum event and artifact. The other listed triples are generic project phases, Scrum values, or engineering activities.

  2. Question 2Scrum Theory and Principles

    Which set lists the five Scrum values?

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

    Explanation

    Scrum defines exactly five values: commitment, focus, openness, respect, and courage. They describe how the team works together and support the empirical pillars. The other sets mix in pillars, artifacts, or values Scrum does not name.

  3. Question 3Scrum Theory and Principles

    What is a timebox in Scrum?

    1. A minimum duration an event must run to count as complete.
    2. A fixed maximum duration for an event that is never extended. Correct answer.
    3. A schedule imposed by stakeholders for delivering the product.
    4. A deadline that may be extended when the work is unfinished.

    Explanation

    Every Scrum event is timeboxed, meaning it has a maximum duration that is respected rather than stretched. A timebox caps the event, so the team must focus on what matters within that limit. It is neither a minimum duration nor a negotiable deadline.

  4. Question 4Scrum Theory and Principles

    The Sprint is best described as which of the following?

    1. A container for the other Scrum events and activities. Correct answer.
    2. A phase of testing that follows development.
    3. An optional event used only when requirements are unclear.
    4. A meeting held at the start of each month.

    Explanation

    The Sprint is the heartbeat of Scrum and acts as a container in which the other events take place. It has a fixed length of one month or less and is never optional. It is not a meeting or a testing phase.

  5. Question 5Scrum Theory and Principles

    A Scrum Team is self-managing. Which statement best describes what that means?

    1. The team operates without any contact with the wider organization.
    2. The team receives its daily task assignments from the Product Owner.
    3. The team may rewrite the Scrum framework whenever it suits them.
    4. The team decides internally who does what, when, and how. Correct answer.

    Explanation

    Self-management means the people doing the work decide internally how to divide it, sequence it, and perform it. The team still works within the organization and within Scrum's rules. Direction comes from goals, not from assigned daily tasks.

  6. Question 6Scrum Theory and Principles

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

    1. The team shares members with other teams on a rotating basis.
    2. The team has all the skills needed to create value each Sprint. Correct answer.
    3. The team reports to several functional managers at once.
    4. Every member is trained in all of the same disciplines.

    Explanation

    Cross-functional means the team collectively holds the skills required to deliver a usable Increment every Sprint, without depending on outsiders. It does not require every member to be a generalist. Reporting lines and shared members have nothing to do with the concept.

  7. Question 7Scrum Theory and Principles

    How does the Scrum Guide describe Scrum itself?

    1. A lightweight framework for complex, adaptive work. Correct answer.
    2. A stage-gate process for approving large capital projects.
    3. A complete methodology that prescribes engineering practices in detail.
    4. A certification scheme for project managers and product owners.

    Explanation

    Scrum is deliberately lightweight and defines only what is needed to implement its theory. It does not prescribe engineering practices or detailed methods. Organizations add their own practices on top of the framework.

  8. Question 8Scrum Theory and Principles

    What does an incremental approach mean in Scrum?

    1. Each Sprint reworks the entire product from scratch.
    2. The product is documented fully before development starts.
    3. Deliverables are handed over only once, at the end of the project.
    4. The product grows in additive, verified pieces. Correct answer.

    Explanation

    Increments are additive: each one builds on the previous ones and is verified so that all pieces work together. This is what allows value to be delivered before the whole product is finished. Big-bang handover and complete up-front documentation are predictive practices.

  9. Question 9Scrum Theory and Principles

    Transparency requires that aspects of the process be visible to those performing and receiving the work. What else does it require?

    1. That only managers may view the Product Backlog.
    2. That all stakeholders have access to the source code.
    3. That the team documents every conversation it holds.
    4. A common standard so that observers share the same understanding. Correct answer.

    Explanation

    Visibility alone is not transparency; everyone must interpret what they see in the same way. That requires an agreed standard, such as a shared Definition of Done. Access to code or exhaustive documentation does not create a common understanding.

  10. Question 10Scrum Theory and Principles

    How often should inspection occur in Scrum?

    1. Continuously, so that every action is reviewed by someone.
    2. At intervals set by the quality assurance department.
    3. Often enough to detect problems without disrupting the work. Correct answer.
    4. Only at the end of the project, once the Increment is complete.

    Explanation

    Inspection must be frequent enough to catch undesirable variance early, yet not so frequent that it gets in the way of the work itself. Scrum balances this through its defined events. Constant review or a single end-of-project check both break that balance.

  11. Question 11Scrum Theory and Principles

    When inspection reveals that part of the process or product is unacceptable, when should adjustment happen?

    1. As soon as possible to limit further deviation. Correct answer.
    2. At the next quarterly planning cycle.
    3. Only after a change request has been formally approved.
    4. After the release has been delivered to customers.

    Explanation

    Adaptation should occur as soon as possible so that deviation does not grow. Delaying adjustment allows more work to be built on a flawed basis. Bureaucratic approval routes are not part of Scrum's adaptive loop.

  12. Question 12Scrum Theory and Principles

    Which behaviour best reflects the Scrum value of Openness?

    1. The team shares progress and problems honestly with stakeholders. Correct answer.
    2. The team limits access to the Product Backlog to managers.
    3. The team avoids discussing disagreements in the Daily Scrum.
    4. The team waits until the Sprint Review to reveal delays.

    Explanation

    Openness means the team and its stakeholders are candid about the work and the challenges it faces. Surfacing problems early is exactly what the empirical pillars depend on. Hiding delays, avoiding disagreement, or restricting visibility all work against it.

  13. Question 13Scrum Theory and Principles

    What does the Sprint Goal provide the Scrum Team?

    1. A guarantee that all planned items will be finished.
    2. A fixed list of backlog items that may not be changed.
    3. A replacement for the Definition of Done.
    4. A shared objective that gives focus while leaving room to negotiate the work. Correct answer.

    Explanation

    The Sprint Goal is a single objective for the Sprint that creates focus and coherence. It gives the team flexibility about the exact work needed to reach it. It is not a fixed scope list, nor does it replace other artifacts.

  14. Question 14Scrum Theory and Principles

    Why does Scrum require a Definition of Done?

    1. To give a shared understanding of what it means for work to be complete. Correct answer.
    2. To allow the Product Owner to skip the Sprint Review.
    3. To standardise velocity across the organization.
    4. To replace the need for acceptance criteria in the backlog.

    Explanation

    The Definition of Done is a formal description of the quality state required for an Increment, and it creates transparency about completion. Without it, people would judge completeness differently. It does not affect velocity comparisons across teams or remove other practices.

  15. Question 15Scrum Theory and Principles

    In which situation is empirical process control clearly preferable to a predictive plan?

    1. When the team has already built the identical product before.
    2. When a regulator requires a fixed scope and fixed schedule.
    3. When the work is repetitive and the causes of variation are known.
    4. When requirements and technology change frequently and much is unknown. Correct answer.

    Explanation

    Empiricism suits work where more is unknown than known and where cause and effect only become clear in retrospect. Frequent inspection and adaptation replace up-front certainty in such conditions. Repetitive or fully understood work fits defined, predictive processes better.

  16. Question 16Scrum Theory and Principles

    Partway through a Sprint the team learns a planned feature can be built a simpler way. What does Scrum permit?

    1. Clarifying and renegotiating scope with the Product Owner. Correct answer.
    2. Escalating the decision to a change control board.
    3. Terminating the Sprint and replanning from scratch.
    4. Freezing the Sprint Backlog so the original plan is preserved.

    Explanation

    As more is learned, the scope of the Sprint may be clarified and renegotiated between the Product Owner and the developers. What must be protected is the Sprint Goal, not the original task list. Cancelling the Sprint or freezing the plan would remove the adaptability Scrum relies on.

  17. Question 17Scrum Theory and Principles

    A Scrum Master who serves the team most typically spends time on which activity?

    1. Approving the team's technical design decisions.
    2. Assigning daily tasks to each developer.
    3. Reporting the team's velocity to line managers.
    4. Causing the removal of impediments to the team's progress. Correct answer.

    Explanation

    The Scrum Master serves the team by helping remove obstacles and by coaching the team and organization toward better use of Scrum. This is a serving-leadership stance, not a command-and-control one. Assigning tasks and approving designs would undermine self-management.

  18. Question 18Scrum Theory and Principles

    Which of these is an example of waste in the Lean sense as applied to product development?

    1. Holding a fifteen-minute Daily Scrum.
    2. Refining Product Backlog items with the team.
    3. Automating a repetitive build step.
    4. Work that is started but never finished or integrated. Correct answer.

    Explanation

    Lean thinking treats partially done work that never reaches use as inventory and therefore waste. Refinement, the Daily Scrum, and automation all reduce uncertainty or effort and are not waste. Scrum's short, complete Increments exist partly to avoid this kind of build-up.

  19. Question 19Scrum Theory and Principles

    Why does Scrum limit Sprints to one month or less?

    1. To cap risk and cost exposure and enable more frequent adaptation. Correct answer.
    2. To match the organization's financial reporting cycle.
    3. So that each team can hold one Sprint Review per quarter.
    4. So that the Product Owner can reorder the backlog monthly.

    Explanation

    Short Sprints limit the risk of building the wrong thing to the cost of a single Sprint, and they create more frequent opportunities to inspect and adapt. The length comes from risk and learning, not from reporting cycles. Backlog ordering happens continuously regardless.

  20. Question 20Scrum Theory and Principles

    Which statement best distinguishes iterative from incremental development?

    1. Iterative is for software only; incremental is for hardware only.
    2. Iterative avoids feedback; incremental seeks it.
    3. Iterative refines through repeated cycles; incremental builds in pieces. Correct answer.
    4. Iterative delivers once; incremental delivers often.

    Explanation

    Iteration is about revisiting and refining the same thing across cycles, while incrementing is about adding finished pieces to what already exists. Scrum uses both together, which is why each Sprint produces a refined, additive Increment. The two are complementary rather than opposed.

  21. Question 21Scrum Theory and Principles

    A developer repeatedly talks over a junior teammate and dismisses their input as irrelevant. Which Scrum value is most directly undermined?

    1. Commitment
    2. Respect Correct answer.
    3. Focus
    4. Openness

    Explanation

    Respect means team members treat one another as capable professionals and value each other's contributions. Dismissing a colleague's input on status rather than substance attacks that foundation directly. The other values may suffer as a side effect, but respect is the value being violated.

  22. Question 22Scrum Theory and Principles

    Which statement best captures empiricism as Scrum applies it?

    1. Knowledge comes from experience, and decisions follow from what is observed. Correct answer.
    2. Experience is unreliable, so plans should be fixed early and defended.
    3. Knowledge comes from documentation, and decisions follow from contracts.
    4. Decisions should follow from detailed upfront analysis of requirements.

    Explanation

    Empiricism holds that knowledge comes from experience and that decisions should be based on observation. Scrum operationalises this through short cycles of doing, inspecting, and adapting. Up-front analysis, contractual certainty, and defended plans all belong to predictive thinking.

  23. Question 23Scrum Theory and Principles

    At the end of a Sprint, an item does not meet the Definition of Done. How should this be treated?

    1. It is not part of the Increment and returns to the Product Backlog. Correct answer.
    2. It is counted in the team's velocity but excluded from the review.
    3. It is presented at the Sprint Review as a completed Increment.
    4. The Definition of Done is relaxed so the item can be delivered.

    Explanation

    Work that does not meet the Definition of Done cannot be considered part of the Increment; it goes back to the Product Backlog for later consideration. This keeps the Increment transparent and genuinely usable. Weakening the Definition of Done to make the item fit destroys that transparency.

  24. Question 24Scrum Theory and Principles

    Which statement best describes how the three pillars relate to one another?

    1. Adaptation makes inspection possible, which in turn creates transparency.
    2. Transparency enables inspection, and inspection enables adaptation. Correct answer.
    3. Inspection works independently of transparency, but adaptation requires both.
    4. Adaptation is only needed when transparency has failed.

    Explanation

    The pillars form a sequence: work must be visible before it can be meaningfully inspected, and inspection is what provides the basis for adaptation. This is why transparency problems undermine everything downstream. Treating the pillars as independent or reversing the order breaks the logic of empiricism.

  25. Question 25Scrum Theory and Principles

    Scrum is described as intentionally incomplete. What does this imply for a Scrum Team?

    1. It must follow a prescribed set of engineering practices from the Guide.
    2. It may ignore the Scrum rules that do not suit its context.
    3. It should wait for the organization to define its processes first.
    4. It adds practices and tools as needed within Scrum's rules. Correct answer.

    Explanation

    Scrum defines only the minimum needed to implement its theory, and teams fill the rest with their own practices and tools. That freedom operates inside the framework's rules, which remain intact. The Guide does not prescribe engineering practices, and teams do not wait for permission to adapt.

  26. Question 26Scrum Theory and Principles

    Scrum rests on empirical process control, which is supported by three pillars. Which of the following is one of those pillars?

    1. Commitment
    2. Transparency Correct answer.
    3. Respect
    4. Focus

    Explanation

    The three pillars of empiricism are transparency, inspection and adaptation. Focus, respect and commitment belong to the set of five Scrum values, not to the pillars. Keeping the two lists distinct matters because the values shape behaviour while the pillars describe how knowledge is gained and used.

  27. Question 27Scrum Theory and Principles

    The Scrum value of Commitment is best described by which statement?

    1. Being personally dedicated to the team's goals Correct answer.
    2. Following the Sprint plan exactly as written
    3. Delivering every item forecast at Sprint Planning
    4. Promising stakeholders a fixed release date

    Explanation

    Commitment means the Scrum Team dedicates itself to achieving its goals and supports one another in doing so. It is a disposition toward goals and colleagues, not a guarantee about scope or dates. Forecasts and plans remain adjustable as new learning appears.

  28. Question 28Scrum Theory and Principles

    The Scrum Guide describes the Scrum Team as self-managing. What does that mean in practice?

    1. A manager assigns each team member their daily tasks
    2. The team may set aside the Definition of Done under time pressure
    3. The team decides internally who does what, when and how Correct answer.
    4. The team may change the organisation's pricing strategy on its own

    Explanation

    Self-managing means the people doing the work decide among themselves how to organise it, including task allocation and working methods. It is an internal authority over the how and who, exercised inside the boundaries of the framework. It does not remove the need to meet the Definition of Done or to respect wider organisational limits.

  29. Question 29Scrum Theory and Principles

    A team must forecast how much work it can complete in the coming Sprint. Which approach is most consistent with empiricism?

    1. Commit to finishing the whole Product Backlog in the Sprint
    2. Adopt the figure the customer finds most reassuring
    3. Base the forecast on what recent Sprints have shown to be achievable Correct answer.
    4. Accept the highest figure offered by the most senior engineer

    Explanation

    Empiricism builds decisions on observation and experience rather than on assertion or hope. Recent Sprint outcomes are the evidence the team actually has about its capacity. Forecasts derived from that evidence can be inspected and adjusted as the Sprint proceeds.

  30. Question 30Scrum Theory and Principles

    An organisation runs Sprints but also keeps a fixed twelve-month scope-and-schedule plan that no one may change during the year. Which statement best captures the problem?

    1. The fixed plan blocks the adaptation that inspection should enable, so empiricism is lost Correct answer.
    2. The only problem is that the Sprints are not timeboxed to one month or less
    3. The only problem is that the Product Owner lacks authority over the annual budget
    4. Nothing is wrong, because running Sprints already provides the inspection that Scrum requires

    Explanation

    Inspection has value only when it can lead to adjustment of product and process. A frozen annual plan keeps the ceremonies of Scrum while removing the adaptive response that makes it empirical. The framework is then used as a label on predictive management rather than as a way of working.

  31. Question 31Scrum Roles and Accountabilities

    Which three accountabilities together make up the Scrum Team?

    1. Product Owner, Scrum Master, and Developers Correct answer.
    2. Product Owner, Scrum Master, and Stakeholders
    3. Product Owner, Developers, and Business Analysts
    4. Scrum Master, Developers, and Project Manager

    Explanation

    Scrum defines a single team structure containing exactly three accountabilities: the Product Owner, the Scrum Master, and the Developers. All three together form the Scrum Team, which is self-managing and cross-functional. Roles such as project manager or business analyst are not Scrum accountabilities.

  32. Question 32Scrum Roles and Accountabilities

    Several departments want a say in what the product contains. How many Product Owners does a Scrum Team have?

    1. Exactly one Correct answer.
    2. One per contributing department
    3. One from the business side and one from technology
    4. One for each Scrum Team working on the product

    Explanation

    The Product Owner is one person, not a committee, even when many stakeholders have interests in the product. Having a single accountable person keeps the Product Backlog ordered and decisions clear. Groups wanting to influence the product must do so by persuading that one Product Owner.

  33. Question 33Scrum Roles and Accountabilities

    What is the recommended maximum size of a Scrum Team?

    1. Three to nine people
    2. Ten or fewer people Correct answer.
    3. Five to eleven people
    4. There is no guideline for team size

    Explanation

    Scrum guidance is that the Scrum Team is typically ten or fewer people, including the Product Owner and Scrum Master. Smaller teams communicate better and need less coordination. If a team grows beyond that, it is usually better to form additional Scrum Teams on the same product.

  34. Question 34Scrum Roles and Accountabilities

    Who is accountable for producing an Increment in every Sprint?

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

    Explanation

    The Developers are accountable for creating the Increment each Sprint and for meeting the Definition of Done. The Product Owner orders the work and the Scrum Master coaches, but neither builds the Increment. Creating a usable, valuable increment is squarely the Developers' accountability.

  35. Question 35Scrum Roles and Accountabilities

    Who is required to attend the Daily Scrum?

    1. The whole Scrum Team together with interested stakeholders
    2. The Developers Correct answer.
    3. The Scrum Master and Product Owner
    4. Anyone who contributes to the Sprint Backlog

    Explanation

    The Daily Scrum is an event for the Developers to inspect progress toward the Sprint Goal and adapt their plan. The Product Owner and Scrum Master may attend, but they are not required unless they are actively doing work in the Sprint Backlog. Others are generally not needed and can disrupt focus.

  36. Question 36Scrum Roles and Accountabilities

    Who has the authority to cancel a Sprint?

    1. Senior stakeholders
    2. The Scrum Team by majority vote
    3. The Scrum Master
    4. Only the Product Owner Correct answer.

    Explanation

    A Sprint can be cancelled only by the Product Owner, and only when the Sprint Goal becomes obsolete. Cancellation is rare and is driven by a change in direction or value, which is the Product Owner's accountability. The Scrum Master has no authority to cancel a Sprint.

  37. Question 37Scrum Roles and Accountabilities

    Which of these is an accountability of the Product Owner?

    1. Assigning daily tasks to the Developers
    2. Maximizing the value of the product Correct answer.
    3. Coaching the organization in Scrum adoption
    4. Deciding how the Developers will do their work

    Explanation

    The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team, primarily through effective Product Backlog management. Coaching the organization and deciding how work is performed belong elsewhere. The Product Owner focuses on what and why, not on task assignment or technical approach.

  38. Question 38Scrum Roles and Accountabilities

    Who participates in the Sprint Retrospective?

    1. Only the Developers
    2. The Scrum Team plus invited stakeholders
    3. The Scrum Master and Product Owner only
    4. The Scrum Team Correct answer.

    Explanation

    The Sprint Retrospective is an event for the Scrum Team as a whole, which includes the Product Owner, Scrum Master, and Developers. Stakeholders are not part of it, because the Retrospective is about how the team itself works. The team plans improvements to its quality and effectiveness.

  39. Question 39Scrum Roles and Accountabilities

    A Product Owner asks a senior Developer to keep the Product Backlog refined and well ordered. Who remains accountable for the Product Backlog?

    1. The Scrum Team collectively
    2. The Scrum Master
    3. The senior Developer
    4. The Product Owner Correct answer.

    Explanation

    The Product Owner may delegate work on the Product Backlog but never the accountability for it. Delegation changes who does the task, not who answers for the outcome. The Product Owner therefore remains accountable for ordering, clarity, and value.

  40. Question 40Scrum Roles and Accountabilities

    A department manager asks the Scrum Master to assign each Developer a daily task and to report individual productivity. What is the most appropriate response?

    1. Accept, because the Scrum Master leads the team
    2. Have the Developers vote on whether to accept the request
    3. Explain that the Developers self-manage their work and that the Scrum Master does not direct individuals Correct answer.
    4. Ask the Product Owner to assign the tasks instead

    Explanation

    The Scrum Master is a true leader who serves, but has no authority to direct people or assign their work. The Developers are self-managing and decide internally who does what, when, and how. The Scrum Master's response is to coach the surrounding organization toward that understanding.

  41. Question 41Scrum Roles and Accountabilities

    Halfway through a Sprint, the Developers realize their chosen technical approach will not deliver the Sprint Goal by the end of the Sprint. What should happen?

    1. The Product Owner reorders the Product Backlog to compensate
    2. The team waits for the next Sprint Planning to change the plan
    3. The Developers adjust their Sprint Backlog and continue toward the Sprint Goal Correct answer.
    4. The Scrum Master cancels the Sprint

    Explanation

    The Sprint Backlog is owned by the Developers, who adapt it as more is learned while keeping the Sprint Goal in view. Re-planning inside the Sprint is expected behaviour, not a failure. Only if the Sprint Goal itself becomes obsolete does cancellation become relevant, and only the Product Owner can cancel.

  42. Question 42Scrum Roles and Accountabilities

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

    1. The Product Owner
    2. The Developers Correct answer.
    3. The quality assurance department
    4. The Scrum Master

    Explanation

    If the organization does not already define a Definition of Done, the Developers must create one for the product. It expresses the quality standard the Increment must meet and is used to judge completeness. The Developers own it because they own the creation of the Increment.

  43. Question 43Scrum Roles and Accountabilities

    A Developer reports that the shared build server has been offline for two days. What is the Scrum Master's most appropriate action?

    1. Add it to the Product Backlog so the Product Owner can order it
    2. Help remove the impediment and escalate it where the team cannot Correct answer.
    3. Tell the Developers to keep working around it without raising it
    4. Note it for discussion at the next Sprint Retrospective

    Explanation

    Causing the removal of impediments to the team's progress is a core Scrum Master accountability. Where the team cannot resolve a blocker itself, the Scrum Master works with the wider organization to remove it. Deferring a live blocker to a later event leaves the team stuck.

  44. Question 44Scrum Roles and Accountabilities

    How is the Sprint Goal produced?

    1. The Product Owner writes it before Sprint Planning and presents it
    2. The Scrum Master derives it from the Definition of Done
    3. It is crafted collaboratively by the Scrum Team during Sprint Planning Correct answer.
    4. Stakeholders agree it during the Sprint Review

    Explanation

    The Sprint Goal is a single objective for the Sprint and is crafted during Sprint Planning by the Scrum Team as a whole. The Product Owner brings the target and value perspective, while the Developers bring feasibility. It is a collaborative commitment, not a document handed down.

  45. Question 45Scrum Roles and Accountabilities

    Which activity belongs to the Product Owner's accountability?

    1. Removing impediments reported by the Developers
    2. Engaging stakeholders to understand their needs and to communicate progress Correct answer.
    3. Deciding the technical design of backlog items
    4. Ensuring Scrum events take place on time

    Explanation

    The Product Owner represents the interests of stakeholders and is accountable for effective communication with them about the product and its progress. This keeps the Product Backlog aligned with real needs. Technical design, impediment removal, and event facilitation sit with other accountabilities.

  46. Question 46Scrum Roles and Accountabilities

    Which of these is a legitimate way the Scrum Master serves the Product Owner?

    1. Writing the acceptance criteria for every Product Backlog item
    2. Helping the Product Owner find effective Product Backlog management techniques Correct answer.
    3. Approving the Sprint Goal on behalf of the Product Owner before Sprint Planning ends
    4. Deciding which backlog items will deliver the most revenue to the organization

    Explanation

    One way the Scrum Master serves the Product Owner is helping find techniques for effective Product Goal definition and Product Backlog management. The help is coaching and facilitation, not doing the Product Owner's decisions for them. Value judgements and backlog content remain the Product Owner's accountability.

  47. Question 47Scrum Roles and Accountabilities

    In Scrum, what does it mean that the Scrum Team is cross-functional?

    1. It contains at least one member from each business department
    2. It has all the competencies needed to create value each Sprint Correct answer.
    3. Every member is able to perform every role in the team
    4. It is organized around specialist functions rather than a product

    Explanation

    Cross-functional means the team collectively holds the skills required to deliver value without depending on people outside the team. It describes the mix of competencies in the team, not the range of any individual. Individuals may still be specialists.

  48. Question 48Scrum Roles and Accountabilities

    Mid-Sprint the Developers find a Product Backlog item ambiguous and cannot continue. What does Scrum expect?

    1. The Scrum Master decides the intended meaning of the item
    2. The Developers collaborate with the Product Owner, who is accountable for the backlog content Correct answer.
    3. The item is returned to the Product Backlog and dropped from the Sprint
    4. The Developers interpret the item as written and proceed

    Explanation

    The Product Owner is accountable for the Product Backlog being transparent and understood, so clarification and collaboration between the Product Owner and Developers is expected. Direct conversation is the fastest route to shared understanding. Neither the Scrum Master nor guesswork substitutes for that dialogue.

  49. Question 49Scrum Roles and Accountabilities

    Which statement best describes the Scrum Master's relationship to the Scrum events?

    1. The Scrum Master may skip events once the team is mature
    2. The Scrum Master facilitates the events as requested or needed Correct answer.
    3. The Scrum Master leads each event and presents the results
    4. The Scrum Master decides which events the team needs each Sprint

    Explanation

    The Scrum Master facilitates Scrum events as requested or needed, keeping them within their timeboxes and purpose. Facilitation is a service to the team, not ownership of the content or outcomes. The events themselves are required by Scrum and are not optional.

  50. Question 50Scrum Roles and Accountabilities

    A Scrum Team of nine people splits into a 'requirements group' and a 'coding group' with separate meetings. Why does this conflict with Scrum?

    1. It prevents the Definition of Done from being applied
    2. It makes the team too large to hold a Daily Scrum
    3. Scrum Teams have no sub-teams or hierarchies Correct answer.
    4. It stops the Product Owner from ordering the backlog properly

    Explanation

    A Scrum Team is one unit with shared accountability and contains no sub-teams or hierarchies. Splitting into separate groups with separate meetings fragments that accountability and reintroduces handoffs. The team is meant to be self-managing as a whole.

  51. Question 51Scrum Roles and Accountabilities

    Late in a Sprint, the Product Owner wants to add a high-value, unplanned item that the Developers cannot absorb within their capacity. What is the most appropriate action?

    1. Cancel the Sprint so the new item can be planned from scratch
    2. Ask the Scrum Master to instruct the Developers to accept the item
    3. Discuss the trade-offs with the Developers, who own the Sprint Backlog Correct answer.
    4. Add the item and instruct the Developers to work extra hours to fit it in

    Explanation

    The Product Owner influences the Sprint through the ordered backlog and dialogue, but the Sprint Backlog is owned by the Developers, who decide how to respond to new information. The outcome of that conversation may be a trade-off, a deferral, or nothing at all. Unilateral imposition or unnecessary cancellation bypasses that ownership.

  52. Question 52Scrum Roles and Accountabilities

    A Scrum Team is described as self-managing. Which statement best captures this?

    1. The team chooses which members join and leave the Scrum Team
    2. The team sets its own budget and delivery deadlines with customers
    3. The team can overrule the Product Owner's ordering of the backlog
    4. The team decides internally who does what, when, and how Correct answer.

    Explanation

    Self-managing means the Scrum Team internally decides who does what, when, and how. It concerns the organisation of the team's own work, not organisational authority over membership, budgets, or backlog ordering. Backlog ordering and value decisions stay with the Product Owner.

  53. Question 53Scrum Roles and Accountabilities

    Which action is part of how the Scrum Master serves the organization?

    1. Deciding the organization's product strategy for the coming year
    2. Leading and coaching the organization in its Scrum adoption Correct answer.
    3. Approving which teams are permitted to use Scrum
    4. Assigning a Scrum Master to every department in the organization

    Explanation

    Serving the organization includes leading, training, and coaching it in Scrum adoption, planning and advising implementations, and helping people understand the empirical approach. The Scrum Master influences the wider environment rather than controlling product strategy or granting permission. Removing barriers between stakeholders and Scrum Teams also falls in this area.

  54. Question 54Scrum Roles and Accountabilities

    A Developer has an idea for a valuable new feature. What does Scrum say about how it reaches the Product Backlog?

    1. The Scrum Master decides whether the idea is worth adding to the Product Backlog
    2. Developers cannot add items; only the Product Owner may write Product Backlog items
    3. The idea must wait until the Sprint Retrospective before it can be discussed
    4. It is raised with the Product Owner, who decides on the Product Backlog Correct answer.

    Explanation

    Anyone may suggest ideas, but the Product Owner is accountable for the Product Backlog and decides whether and where an item enters it. This keeps a single ordering authority while still allowing the team's insight to reach the backlog. The Scrum Master and the Retrospective are not gates for backlog content.

  55. Question 55Scrum Roles and Accountabilities

    A Scrum Master believes one Developer is delivering far less than the others. Which action is consistent with the Scrum Master accountability?

    1. Reassign the Developer's tasks to faster team members so the Sprint Goal stays safe
    2. Ask the Product Owner to remove the Developer from the Scrum Team at the next Retrospective
    3. Coach the team and the organization, because the Scrum Master does not manage individuals Correct answer.
    4. Set individual performance targets for that Developer and review the targets at every Sprint Review

    Explanation

    The Scrum Master is a leader who serves and coaches; the accountability carries no people-management authority over individual Developers. Coaching the team and the surrounding organization is how the Scrum Master addresses effectiveness. Task assignment, targets, and removal decisions are outside that accountability.

  56. Question 56Scrum Roles and Accountabilities

    In Scrum, who is accountable for the Sprint Backlog?

    1. The whole Scrum Team, which agrees on it together during Sprint Planning.
    2. The Product Owner, who approves its contents before the Sprint begins.
    3. The Developers, who use it to manage their work toward the Sprint Goal. Correct answer.
    4. The Scrum Master, who keeps it updated and tracks the impediments listed in it.

    Explanation

    The Sprint Backlog is composed of the Sprint Goal, the selected Product Backlog items, and the plan for delivering them, and it is a plan by and for the Developers. They adapt it throughout the Sprint as they learn more. The Product Owner is accountable for the Product Backlog, and the Scrum Master is accountable for the Scrum Team's effectiveness.

  57. Question 57Scrum Roles and Accountabilities

    Which option correctly describes the composition of a Scrum Team?

    1. A Product Owner, a Scrum Master, Developers, and stakeholders.
    2. A Product Owner, a Scrum Master, Developers, and a separate test team.
    3. A Product Manager, a Scrum Master, and Developers.
    4. A Product Owner, a Scrum Master, and Developers. Correct answer.

    Explanation

    A Scrum Team is a small team made up of one Product Owner, one Scrum Master, and Developers; these are the three sets of accountabilities. There are no sub-teams or hierarchies inside it, and stakeholders sit outside the Scrum Team.

  58. Question 58Scrum Roles and Accountabilities

    A key stakeholder repeatedly brings feature requests straight to the Developers and asks them to slip the work into the current Sprint. What is the most consistent response?

    1. The Developers accept the requests and place them directly in the Sprint Backlog, which they own.
    2. The Scrum Master records the requests and prioritizes them together with the Developers for the next Sprint.
    3. The Developers funnel each request through the Scrum Master, who screens them before passing them on.
    4. The Scrum Master coaches the stakeholder to bring requests to the Product Owner, who orders the Product Backlog. Correct answer.

    Explanation

    Only the Product Owner orders the Product Backlog, so input that could change product direction belongs with that person. The Scrum Master serves the organization by teaching Scrum and helping people interact with the Scrum Team productively. The Scrum Master does not act as a filter or a substitute decision-maker.

  59. Question 59Scrum Roles and Accountabilities

    An organization runs three Scrum Teams on a single product. Which setup is consistent with Scrum?

    1. One Product Owner and one Product Backlog, with each team keeping its own Scrum Master and Developers. Correct answer.
    2. Three Product Owners, one per team, each owning that team's own Product Backlog.
    3. One Product Owner, with the three Scrum Masters setting priorities for their own teams.
    4. One Product Owner and one Scrum Master, who owns a combined Sprint Backlog for all three teams.

    Explanation

    A product has one Product Owner and one Product Backlog, and each Scrum Team has its own Scrum Master and Developers who self-manage their own Sprint Backlog. Multiple teams may work on the same product, but accountability for ordering the work stays with a single Product Owner.

  60. Question 60Scrum Roles and Accountabilities

    A Product Owner writes detailed implementation instructions for every Product Backlog item, and the Developers refuse to make any technical decision without approval. Which statement best describes this situation?

    1. The arrangement is sound, because the Product Owner remains accountable for the value that the Scrum Team delivers.
    2. The Developers are not self-managing the how of the work, and the Product Owner has moved beyond owning what and why. Correct answer.
    3. The Scrum Master should take over the technical decisions until the Developers regain their confidence.
    4. The arrangement is acceptable whenever the instructions are captured in the Sprint Backlog and the Developers agree to them.

    Explanation

    The Product Owner is accountable for product value and for the what and why of the work, while the Developers self-manage the how, including technical approach and division of work. When the Product Owner prescribes implementation and the Developers wait for approval, both accountabilities are being exercised by the wrong party. The Scrum Master's contribution is coaching the team toward self-management, not deciding the technical work.

  61. Question 61Scrum Events

    What is the timebox for the Daily Scrum?

    1. Fifteen minutes Correct answer.
    2. Thirty minutes
    3. Twenty minutes
    4. Forty-five minutes

    Explanation

    Every Scrum event is timeboxed to a maximum duration, and the Daily Scrum is capped at 15 minutes regardless of Sprint length. The short timebox keeps the event a focused inspection of progress rather than an extended status meeting.

  62. Question 62Scrum Events

    What is the maximum length of a Sprint?

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

    Explanation

    Sprints are fixed-length events of one month or less, and a new Sprint starts immediately after the previous one ends. The one-month ceiling limits risk to a horizon that is short enough to inspect and adapt reliably.

  63. Question 63Scrum Events

    What is the purpose of the Sprint Review?

    1. To identify improvements to the team's processes and tools
    2. To inspect the progress of the Daily Scrum and adjust the Sprint Backlog
    3. To decide which items will be worked on during the next Sprint
    4. To inspect the Increment and adapt the Product Backlog Correct answer.

    Explanation

    The Sprint Review inspects the outcome of the Sprint, namely the Increment, and determines future adaptations that may include adjusting the Product Backlog. Selecting items for the next Sprint belongs to Sprint Planning, and process improvement belongs to the Retrospective.

  64. Question 64Scrum Events

    What is the purpose of the Sprint Retrospective?

    1. To review the Product Backlog with stakeholders and gather feedback
    2. To confirm that the Definition of Done has been met for each item
    3. To plan ways to increase quality and effectiveness Correct answer.
    4. To plan which Product Backlog items will be delivered next

    Explanation

    The Retrospective inspects how the last Sprint went with respect to individuals, interactions, processes, tools and the Definition of Done, and it plans improvements. Its output is a plan for better effectiveness rather than a change to product scope.

  65. Question 65Scrum Events

    Which event opens a Sprint?

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

    Explanation

    Sprint Planning lays out the work of the Sprint, so it is the first event inside the Sprint container. The other events follow in the order Daily Scrum, Sprint Review and Sprint Retrospective.

  66. Question 66Scrum Events

    Who is required to participate in the Daily Scrum?

    1. The entire Scrum Team, including the Product Owner and Scrum Master
    2. The Developers and the Scrum Master
    3. The Developers Correct answer.
    4. Anyone interested in progress toward the Sprint Goal

    Explanation

    The Daily Scrum is an event for the Developers, who own the Sprint Backlog and plan the next day of work. Others may attend if they are actively working on Sprint Backlog items, but they are not required participants.

  67. Question 67Scrum Events

    Which statement best describes the Sprint?

    1. It is a meeting held at the end of each month
    2. It can be paused and restarted when requirements change
    3. It is a container for all the other Scrum events Correct answer.
    4. It becomes optional once a team reaches high maturity

    Explanation

    The Sprint is the heartbeat of Scrum and contains Sprint Planning, the Daily Scrums, the Sprint Review and the Sprint Retrospective. Because every other event happens inside a Sprint, a team cannot skip Sprints and still be practicing Scrum.

  68. Question 68Scrum Events

    During which event is the Sprint Goal created?

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

    Explanation

    The Sprint Goal is crafted during Sprint Planning, when the Scrum Team agrees the objective the Sprint will serve. The Sprint Backlog, which includes the plan for delivering that objective, is produced in the same event.

  69. Question 69Scrum Events

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

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

    Explanation

    For a one-month Sprint, Sprint Planning is timeboxed to a maximum of eight hours, and it is usually shorter when the Sprint is shorter. The timebox prevents the team from over-planning before any work has begun.

  70. Question 70Scrum Events

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

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

    Explanation

    The Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint and is usually shorter for shorter Sprints. Keeping within that limit preserves room for the Retrospective and the start of the next Sprint.

  71. Question 71Scrum Events

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

    1. Two hours
    2. One hour
    3. Half a working day
    4. Three hours Correct answer.

    Explanation

    The Sprint Retrospective is timeboxed to a maximum of three hours for a one-month Sprint, and it is usually shorter for shorter Sprints. Because the Retrospective is the final event of the Sprint, respecting the timebox keeps the cadence intact.

  72. Question 72Scrum Events

    What is the purpose of the Daily Scrum?

    1. To refine Product Backlog items for the next Sprint
    2. To inspect progress toward the Sprint Goal Correct answer.
    3. To demonstrate the completed Increment to stakeholders
    4. To report each developer's status to the Scrum Master

    Explanation

    The Daily Scrum lets the Developers inspect progress toward the Sprint Goal and adapt the Sprint Backlog, producing an actionable plan for the next day. It is a working event for the team rather than a reporting session to anyone outside it.

  73. Question 73Scrum Events

    Who is accountable for cancelling a Sprint?

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

    Explanation

    Only the Product Owner can cancel a Sprint, and this occurs when the Sprint Goal becomes obsolete. Cancellation is a deliberate decision about value, so the accountability rests with the person responsible for maximising value.

  74. Question 74Scrum Events

    Which three topics does Sprint Planning address?

    1. Who, When, and Where
    2. Why, Who, and How much
    3. What, When, and How much
    4. Why, What, and How Correct answer.

    Explanation

    Sprint Planning covers why the Sprint is valuable, what can be done during the Sprint, and how the selected work will get done. Together these produce the Sprint Goal, the selected Product Backlog items and the plan captured in the Sprint Backlog.

  75. Question 75Scrum Events

    Who attends the Sprint Review?

    1. Only the Developers and the Product Owner
    2. Anyone from the organisation, without invitation
    3. Only the Scrum Team, so that sensitive topics stay confidential
    4. The Scrum Team and invited key stakeholders Correct answer.

    Explanation

    The Sprint Review brings the Scrum Team together with the key stakeholders the Product Owner has invited so the Increment can be inspected and the future adapted. Real stakeholder participation keeps the feedback loop honest.

  76. Question 76Scrum Events

    What happens to the improvements identified in the Sprint Retrospective?

    1. They are deferred to the next Sprint Retrospective so the current Sprint is not disturbed
    2. The most impactful ones are addressed as soon as possible Correct answer.
    3. They are handed to the Scrum Master, who is accountable for implementing all of them
    4. They are documented and formally approved by the Product Owner before any action is taken

    Explanation

    The Retrospective produces a plan of concrete actions, and the most impactful improvements are addressed as soon as possible, often by adding them straight to the Sprint Backlog. Improvements that wait for approval or a later Sprint rarely change how the team works.

  77. Question 77Scrum Events

    Which statement about Scrum event timeboxes is correct?

    1. Timeboxes apply only to the Daily Scrum
    2. Timeboxes are targets that may be exceeded when the discussion is valuable to the team
    3. The Scrum Master may extend a timebox to allow consensus
    4. Each event has a maximum duration that is never exceeded Correct answer.

    Explanation

    All Scrum events are timeboxed, meaning each has a maximum duration that everyone involved respects. The timebox creates the regularity and discipline that make empirical process control practical.

  78. Question 78Scrum Events

    What happens immediately after the Sprint Retrospective ends?

    1. The Product Owner writes the Sprint Goal for the next Sprint
    2. The team takes a break until the next Sprint is scheduled
    3. The Scrum Master schedules a follow-up review with stakeholders
    4. The next Sprint begins with Sprint Planning Correct answer.

    Explanation

    There is no gap between Sprints: the next Sprint begins as soon as the current one concludes, and it opens with Sprint Planning. This continuous cadence keeps the empirical loop short and predictable.

  79. Question 79Scrum Events

    How does shortening a Sprint from one month to one week affect the Scrum event timeboxes?

    1. They are extended to compensate for the compressed schedule
    2. They are removed for any Sprint shorter than two weeks
    3. They remain unchanged, because each timebox is defined per Sprint
    4. They are usually shorter Correct answer.

    Explanation

    The stated timebox maximums apply to a one-month Sprint, and for shorter Sprints the events are usually shorter. The events keep roughly the same proportions, but their absolute durations shrink with the Sprint.

  80. Question 80Scrum Events

    Which statement about the structure of the Daily Scrum is correct?

    1. The Product Owner reviews the Sprint Backlog and assigns the day's tasks to each developer
    2. The Scrum Master facilitates the meeting and records each developer's answers for the team
    3. Any structure the Developers choose that focuses on the Sprint Goal Correct answer.
    4. Each developer answers the three standard questions in turn, in the order set by the Scrum Master

    Explanation

    The Developers may choose whatever structure and techniques they find useful, provided the Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan. The three questions are a popular technique, not a rule.

  81. Question 81Scrum Events

    Who is accountable for producing the Sprint Backlog during Sprint Planning?

    1. The Scrum Master
    2. The Scrum Team as a whole
    3. The Product Owner
    4. The Developers Correct answer.

    Explanation

    The Sprint Backlog is a plan by and for the Developers, made up of the Sprint Goal, the selected items and the plan for delivering them. The Product Owner may clarify items and the Scrum Master may coach, but the plan belongs to the Developers.

  82. Question 82Scrum Events

    A Sprint is cancelled. What happens to work that already meets the Definition of Done?

    1. It is discarded along with all other work from the Sprint
    2. It is reviewed, and potentially releasable items may be accepted Correct answer.
    3. It is automatically released to production to avoid waste
    4. It is returned to the Developers for re-estimation in the next Sprint

    Explanation

    When a Sprint is cancelled, any completed and Done Product Backlog items are reviewed, and the Product Owner typically accepts them when they are potentially releasable. Work that is not Done is re-estimated and returned to the Product Backlog.

  83. Question 83Scrum Events

    Which description best fits the Sprint Review?

    1. A working session to collaborate on what to do next Correct answer.
    2. A demonstration ceremony where only completed features are shown
    3. A status report delivered by the Product Owner to management
    4. A formal sign-off meeting where stakeholders approve the Increment

    Explanation

    The Sprint Review is a working session in which the Scrum Team and stakeholders inspect the Increment and collaborate on what to do next. The outcome is a revised Product Backlog that reflects their shared understanding.

  84. Question 84Scrum Events

    As the Developers learn more during a Sprint, what may they negotiate with the Product Owner?

    1. The Definition of Done, so that fewer items need to be completed
    2. The Daily Scrum timebox, so that longer discussions are possible
    3. The Sprint Goal, so that it reflects the new understanding
    4. The scope of the Sprint Backlog Correct answer.

    Explanation

    If the work turns out differently than expected, the Developers collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint while leaving the Sprint Goal intact. The Sprint Goal provides stability, while the detail of the plan is allowed to change.

  85. Question 85Scrum Events

    How does the Scrum Team decide how much work to take into a Sprint during Sprint Planning?

    1. The Developers forecast the work they believe they can achieve Correct answer.
    2. The stakeholders vote on how many Product Backlog items must be completed
    3. The Scrum Master sets the workload so that the team is stretched but not overloaded
    4. The Product Owner assigns a workload equal to the team's historical velocity

    Explanation

    Forecasting is done by the Developers, drawing on their capacity, past performance and the Definition of Done. The result is a forecast of what they believe is achievable rather than a guaranteed delivery commitment.

  86. Question 86Scrum Events

    How does the Scrum Master serve the Scrum Team with respect to the Scrum events?

    1. By ensuring the events take place and are kept within the timebox Correct answer.
    2. By deciding which of the events the team must hold, based on how mature the team is
    3. By taking over facilitation of an event whenever the team runs past its timebox
    4. By preparing the agendas and written minutes that each event requires

    Explanation

    One of the Scrum Master's accountabilities is to ensure that all Scrum events take place and are positive, productive, and kept within the timebox. The events themselves are fixed by Scrum and are not selected or restructured by the Scrum Master, who teaches and coaches rather than taking over.

  87. Question 87Scrum Events

    Which statement describes what the Sprint Review produces?

    1. A formally approved Increment that stakeholders must sign off before the Sprint may end
    2. A rewritten Sprint Goal that replaces the one used during the Sprint just finished
    3. A list of impediments that the Scrum Master must remove before the next event begins
    4. A revised Product Backlog showing the probable items for the next Sprint Correct answer.

    Explanation

    The Sprint Review is a working session in which the Scrum Team and stakeholders inspect the outcome of the Sprint and collaborate on what to do next. A key output is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint, along with any adjustments to the Product Goal or overall backlog.

  88. Question 88Scrum Events

    A Scrum Team spends time every week reviewing, splitting, and re-ordering Product Backlog items. Which statement about this activity is correct?

    1. It must be carried out inside the Sprint Retrospective so that the improvements found are captured
    2. It is an ongoing activity, and the Scrum Team decides how and when it is done Correct answer.
    3. It is a formal Scrum event whose duration must be limited to roughly ten percent of the Sprint
    4. It is performed by the Product Owner alone, because the Developers are not involved in refinement

    Explanation

    Refinement is an ongoing activity rather than one of the five Scrum events, and the Scrum Team decides how and when it is performed. The Product Owner may involve the Developers in refining items to keep the backlog ready for upcoming Sprint Planning.

  89. Question 89Scrum Events

    How does one Sprint relate to the next Sprint in Scrum?

    1. A new Sprint may begin only after the Increment has been released.
    2. A gap of up to one week normally separates consecutive Sprints.
    3. Sprints are separated by the Sprint Retrospective, which sits outside them.
    4. A new Sprint starts immediately after the previous Sprint concludes. Correct answer.

    Explanation

    The Sprint is the container event inside which the other Scrum events take place. Because the Sprint is a continuous cycle, the next Sprint begins as soon as the previous one ends, with no intervening gap or phase.

  90. Question 90Scrum Events

    A Scrum Team is partway through a Sprint and has already completed several Sprint Backlog items sooner than expected. Which statement best describes the Sprint Goal at this point?

    1. It is replaced by a new Sprint Goal agreed by the Developers at the Daily Scrum.
    2. It is restated at each Daily Scrum so the Product Owner can approve progress.
    3. It keeps the Developers focused while the Sprint Backlog is adjusted. Correct answer.
    4. It is closed as soon as the Product Backlog items selected for it are finished.

    Explanation

    The Sprint Goal is the single objective for the Sprint, agreed during Sprint Planning, and it stays in place for the whole Sprint. It gives the Developers a shared focus while allowing the expected work in the Sprint Backlog to be adjusted as more is learned. It is not closed early and is not re-created mid-Sprint.

  91. Question 91Scrum Artifacts and Commitments

    Which artifact has the Product Goal as its commitment?

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

    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 the Scrum Team a target.

  92. Question 92Scrum Artifacts and Commitments

    Which artifact has the Sprint Goal as its commitment?

    1. Sprint Backlog Correct answer.
    2. Product Backlog
    3. Increment
    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 single objective that gives the Sprint focus and coherence.

  93. Question 93Scrum Artifacts and Commitments

    Which artifact has the Definition of Done as its commitment?

    1. Increment Correct answer.
    2. Product Backlog
    3. Product Goal
    4. Sprint Backlog

    Explanation

    The Increment is the artifact that must meet the Definition of Done before it can be considered complete. The Definition of Done is the commitment attached to the Increment.

  94. Question 94Scrum Artifacts and Commitments

    Who is accountable for the Product Backlog?

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

    Explanation

    The Product Owner is accountable for the Product Backlog, including its ordering and transparency. The Product Owner may delegate work but remains accountable for the result.

  95. Question 95Scrum Artifacts and Commitments

    Who is accountable for the Sprint Backlog?

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

    Explanation

    The Developers are accountable for the Sprint Backlog and for managing their own work during the Sprint. They update it as more is learned and as work progresses.

  96. Question 96Scrum Artifacts and Commitments

    What is the primary purpose of Scrum artifacts?

    1. To document every decision made by the Product Owner during the Sprint for later review
    2. To provide a detailed audit trail for compliance and reporting purposes to senior management
    3. To maximize the transparency of key information so the Scrum Team and stakeholders can inspect and adapt Correct answer.
    4. To replace the need for the Sprint Review and the other Scrum events entirely

    Explanation

    Artifacts represent work or value and are designed to maximize transparency of key information. Transparency allows the Scrum Team and stakeholders to inspect the artifacts and adapt based on what they learn.

  97. Question 97Scrum Artifacts and Commitments

    What is the Definition of Done?

    1. A checklist that the Scrum Master uses to confirm that each Sprint has been completed according to plan
    2. A formal description of the state of the Increment when it meets the quality measures required for the product Correct answer.
    3. A list of acceptance criteria that the Product Owner writes for every Product Backlog item before Sprint Planning
    4. A summary of the defects found during the Sprint Review and recorded for the next Sprint Planning

    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 what it means for work to be complete.

  98. Question 98Scrum Artifacts and Commitments

    Which statement best describes the Product Backlog?

    1. A list of all work that must be completed during the current Sprint by the Developers
    2. A record of the Increments completed in previous Sprints
    3. An emergent, ordered list of what is needed to improve the product Correct answer.
    4. A fixed scope agreed with stakeholders at the start of the project

    Explanation

    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 and evolves as the product and its environment change.

  99. Question 99Scrum Artifacts and Commitments

    What is Product Backlog refinement?

    1. A formal meeting held once per Sprint to re-estimate all Product Backlog items with stakeholders present
    2. The process of removing items that are no longer prioritized from the Product Backlog by the Product Owner
    3. A review by stakeholders to approve the Product Backlog before each Sprint Planning session begins
    4. Breaking down and further defining Product Backlog items into smaller, more precise items Correct answer.

    Explanation

    Refinement is the ongoing act of breaking down and further defining Product Backlog items into smaller, more precise items. It can include adding detail, estimates, and order, and it is not a one-time event.

  100. Question 100Scrum Artifacts and Commitments

    What is the Sprint Backlog composed of?

    1. The Sprint Goal, the selected Product Backlog items, and the plan for delivering them Correct answer.
    2. The Definition of Done and the Increment produced during the Sprint, together with its quality measures
    3. Only the Product Backlog items selected for the Sprint together with their effort estimates
    4. The Product Goal and the entire Product Backlog, including all items not yet refined

    Explanation

    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 a highly visible, real-time picture of the work the Developers plan to accomplish.

  101. Question 101Scrum Artifacts and Commitments

    What is the primary purpose of the Sprint Goal?

    1. To document the acceptance criteria for every selected Product Backlog item in detail
    2. To provide a fixed scope that cannot change during the Sprint under any circumstances once agreed
    3. To describe the Sprint's single objective and allow flexibility in the work needed to achieve it Correct answer.
    4. To record the Definition of Done that applies to the Increment produced in the Sprint

    Explanation

    The Sprint Goal is the single objective for the Sprint and provides flexibility regarding the exact work needed to achieve it. It gives the Developers a shared focus while allowing scope to be clarified as more is learned.

  102. Question 102Scrum Artifacts and Commitments

    What does the Product Goal describe?

    1. The Sprint objective that the Developers commit to during Sprint Planning
    2. The acceptance criteria for the Increment produced in the current Sprint
    3. A future state of the product that serves as a target for the Scrum Team Correct answer.
    4. The list of Product Backlog items selected for the current Sprint

    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 long-term objective that helps the team decide what work is worthwhile.

  103. Question 103Scrum Artifacts and Commitments

    What is an Increment?

    1. The set of Product Backlog items selected for the Sprint
    2. A usable stepping stone that adds value toward the Product Goal Correct answer.
    3. A cumulative record of every completed item since the product began
    4. The Sprint Backlog as it stands at the end of the Sprint

    Explanation

    An Increment is a concrete stepping stone toward the Product Goal, and each Increment adds value to the product. It must be usable so that it can be inspected and, if appropriate, delivered to stakeholders.

  104. Question 104Scrum Artifacts and Commitments

    How many Increments can a Scrum Team create within a single Sprint?

    1. Only one per day, regardless of whether the Definition of Done has been met
    2. Exactly one, delivered to stakeholders at the Sprint Review at the end of the Sprint
    3. None, because Increments are created only when the product is released to end users
    4. One or more, whenever a Product Backlog item meets the Definition of Done Correct answer.

    Explanation

    A Scrum Team may create one or more Increments during a Sprint. Each Increment is created whenever a Product Backlog item meets the Definition of Done, and the sum of Increments is presented at the Sprint Review.

  105. Question 105Scrum Artifacts and Commitments

    If a Product Backlog item does not meet the Definition of Done, what happens to it?

    1. The item cannot be released to stakeholders but still counts toward achieving the Sprint Goal
    2. The item is not included in the Increment and returns to the Product Backlog for future consideration Correct answer.
    3. The item is still included in the Increment but marked as incomplete during the Sprint Review
    4. The Scrum Master must approve an exception before the item can be included in the Increment

    Explanation

    Work that does not meet the Definition of Done cannot be considered part of the Increment. It returns to the Product Backlog for future consideration rather than being presented as complete.

  106. Question 106Scrum Artifacts and Commitments

    Which statement about the Product Backlog is accurate?

    1. It must be fully detailed before the first Sprint begins
    2. It is owned and maintained by the Scrum Master
    3. It is the single source of work undertaken by the Scrum Team Correct answer.
    4. It contains only new features and excludes fixes or improvements

    Explanation

    The Product Backlog is the single source of work undertaken by the Scrum Team. It can include features, fixes, improvements, and other work needed to improve the product.

  107. Question 107Scrum Artifacts and Commitments

    During the Sprint, how is the Sprint Backlog updated?

    1. The Developers update it as more is learned, adding or removing work Correct answer.
    2. Stakeholders request changes through the Product Owner, who edits the Sprint Backlog
    3. The Scrum Master updates it daily to track progress against the Sprint Goal
    4. The Product Owner updates it at the Sprint Review based on stakeholder feedback

    Explanation

    The Developers own the Sprint Backlog and update it throughout the Sprint as more is learned. They may add, remove, or change work while keeping the Sprint Goal in focus.

  108. Question 108Scrum Artifacts and Commitments

    How is the Product Backlog ordered?

    1. By factors such as value, risk, and dependencies, with the most important items first Correct answer.
    2. Alphabetically by item name so that the Product Backlog is easy for stakeholders to search
    3. By the number of story points, with the largest items always placed first
    4. By the order in which items were first created, with the oldest items always first

    Explanation

    The Product Backlog is ordered based on factors such as value, risk, dependencies, and importance. Higher-priority items appear closer to the top so the Scrum Team knows what to work on next.

  109. Question 109Scrum Artifacts and Commitments

    Who creates the Definition of Done?

    1. The Scrum Master as a process safeguard
    2. The Product Owner alone, based on stakeholder requirements
    3. The stakeholders during the Sprint Review
    4. The Scrum Team, or the organization if it has a standard Correct answer.

    Explanation

    The Scrum Team creates its Definition of Done, unless the organization has a standard that must be followed as a minimum. If there is an organizational standard, all Scrum Teams must comply with it at minimum.

  110. Question 110Scrum Artifacts and Commitments

    When multiple Scrum Teams work on the same product, which Definition of Done applies to their combined Increment?

    1. Each team applies its own separate Definition of Done to the work it completes
    2. The strictest Definition of Done among the teams applies automatically to all work
    3. The teams share one Definition of Done and comply with it for the combined Increment Correct answer.
    4. No Definition of Done applies until all teams have integrated their work at release

    Explanation

    When multiple Scrum Teams work together on the same product, they must share the same Definition of Done and comply with it. This shared standard ensures that the combined Increment is transparent and genuinely complete.

  111. Question 111Scrum Artifacts and Commitments

    A Developer realizes mid-Sprint that a selected Product Backlog item is no longer needed to meet the Sprint Goal. What is the most appropriate action?

    1. Cancel the Sprint immediately and start a new Sprint with a revised set of Product Backlog items and a new Sprint Goal
    2. Drop the item from the Sprint Backlog and agree the change with the Product Owner while keeping the Sprint Goal Correct answer.
    3. Escalate the decision to the Scrum Master, who owns all changes to the Sprint Backlog and decides what work is removed
    4. Complete the item anyway because the Sprint Backlog scope is fixed once the Sprint begins and cannot be changed

    Explanation

    The Sprint Goal provides flexibility in the work needed to achieve it, so scope may be clarified and renegotiated with the Product Owner as more is learned. The Developers manage the Sprint Backlog and can remove work that is no longer needed while keeping the Sprint Goal intact.

  112. Question 112Scrum Artifacts and Commitments

    How does the Product Goal relate to Sprint Goals?

    1. The Product Goal is derived from each Sprint Goal during Sprint Planning and changes every Sprint
    2. The Product Goal provides direction, and each Sprint Goal contributes toward it Correct answer.
    3. They are independent of each other and must not influence each other at any point
    4. Sprint Goals replace the Product Goal once the first Sprint has started and the team has learned more

    Explanation

    The Product Goal gives the Scrum Team a long-term target, and each Sprint Goal should contribute toward reaching it. The Sprint Goal is a step that helps move the product toward the Product Goal.

  113. Question 113Scrum Artifacts and Commitments

    Which statement about the value of an Increment is true?

    1. It must be usable and provide value, and it may be delivered to stakeholders before the end of the Sprint Correct answer.
    2. It must be released to end users before it can be inspected by stakeholders at the Sprint Review
    3. It has value only when every Product Backlog item in the entire product is complete and released
    4. Its value is determined solely by the number of Product Backlog items that the Developers completed

    Explanation

    An Increment must be usable and add value, and it can be delivered to stakeholders before the end of the Sprint. Delivery does not need to wait for the Sprint Review, although the Increment is still inspected there.

  114. Question 114Scrum Artifacts and Commitments

    A Scrum Team finds that its Definition of Done does not cover a recurring defect class. What should the team do?

    1. Improve the Definition of Done to add the missing criteria and treat the work as part of the Increment Correct answer.
    2. Lower the Definition of Done so that items can be declared complete more quickly and the Sprint Goal is met
    3. Ignore the gap because the Definition of Done is fixed for the lifetime of the product and cannot change
    4. Ask the Product Owner to accept the defects as technical debt that can be handled in a later Sprint

    Explanation

    The Definition of Done can evolve as the Scrum Team learns and as quality expectations improve. If a defect class is not covered, the team should strengthen the Definition of Done and treat the resulting work as part of the Increment rather than hiding the gap.

  115. Question 115Coaching and Facilitation

    In a coaching relationship, what is the primary source of the agenda and solutions?

    1. The coachee's own goals and insights Correct answer.
    2. The organization's published competency model
    3. The coach's subject-matter expertise
    4. The line manager's performance targets

    Explanation

    Coaching is primarily non-directive: the coach helps the coachee generate awareness, goals, and solutions. The coachee owns the agenda rather than the coach, manager, or organization.

  116. Question 116Coaching and Facilitation

    Which coaching behavior best demonstrates active listening during a conversation?

    1. Preparing the next question while the coachee is speaking
    2. Completing the coachee's sentences to save time
    3. Sharing a similar personal story to build rapport
    4. Summarizing the coachee's main points Correct answer.

    Explanation

    Active listening involves fully attending to the speaker and reflecting back content or feeling to confirm understanding. Summarizing shows that the coach has heard and processed the coachee's message.

  117. Question 117Coaching and Facilitation

    Which question is most characteristic of a powerful coaching question?

    1. Why did you make that mistake again?
    2. What would success look like? Correct answer.
    3. Don't you think you should escalate this?
    4. Have you tried using the standard template?

    Explanation

    Powerful questions are open-ended and invite the coachee to explore, discover, and take ownership. They avoid embedding the coach's preferred answer or a judgment.

  118. Question 118Coaching and Facilitation

    In the GROW coaching model, which step follows Goal and Reality?

    1. Review
    2. Options Correct answer.
    3. Reflection
    4. Wrap-up

    Explanation

    GROW stands for Goal, Reality, Options, and Will. After clarifying the goal and current reality, the coach explores possible options before agreeing on action.

  119. Question 119Coaching and Facilitation

    A coach wants to give feedback using the Situation-Behavior-Impact model. Which sequence should the coach follow?

    1. Self-assessment, impact, goal setting
    2. Behavior, advice, summary of situation
    3. Situation, behavior, impact Correct answer.
    4. Impact, situation, request for change

    Explanation

    The SBI model separates observable facts from interpretation by first naming the situation, then the specific behavior, and then its impact. This helps the receiver hear feedback without feeling personally judged.

  120. Question 120Coaching and Facilitation

    A newly formed team begins disagreeing about roles and challenging the facilitator's authority. Which stage of Tuckman's model is this?

    1. Norming
    2. Forming
    3. Storming Correct answer.
    4. Performing

    Explanation

    Storming is the stage in which conflict, role ambiguity, and challenges to authority often surface. Facilitators help the team surface and work through these tensions rather than suppress them.

  121. Question 121Coaching and Facilitation

    What is the main purpose of dot voting in a facilitated workshop?

    1. To prioritize options quickly and democratically Correct answer.
    2. To assign individual accountability for each action
    3. To record every idea in full detail for the minutes
    4. To replace consensus with a single expert decision

    Explanation

    Dot voting lets participants distribute a limited number of votes across many options to reveal group priorities. It is a fast, participatory way to narrow choices, not a substitute for detailed documentation or accountability planning.

  122. Question 122Coaching and Facilitation

    Psychological safety in a team is best described as which of the following?

    1. A guarantee that every idea will be adopted
    2. A formal process for reporting policy violations
    3. A climate where team members avoid disagreement
    4. A shared belief that speaking up is safe Correct answer.

    Explanation

    Psychological safety is a shared belief that interpersonal risk-taking, such as asking questions or admitting mistakes, will not be punished or humiliated. It is not the same as conflict avoidance or guaranteed acceptance of every idea.

  123. Question 123Coaching and Facilitation

    What does the retrospective Prime Directive ask participants to assume?

    1. The process is more important than the people involved
    2. Every problem must have a named owner before the meeting ends
    3. Everyone did the best they could with what they knew Correct answer.
    4. The facilitator will decide which improvements to implement

    Explanation

    The Prime Directive asks participants to assume that everyone did the best job they could, given their situation and knowledge at the time. This reduces blame and supports honest reflection.

  124. Question 124Coaching and Facilitation

    In a facilitated decision, what does holding up five fingers in a fist-of-five vote typically signal?

    1. Strong objection that blocks the decision
    2. A request for more discussion before voting
    3. Full support and willingness to help Correct answer.
    4. Abstention because the voter lacks information

    Explanation

    In fist of five, five fingers usually mean full support and willingness to help implement the decision. Lower fingers indicate varying degrees of concern, with one finger typically signaling a block.

  125. Question 125Coaching and Facilitation

    Why does a coach establish a clear coaching agreement at the start of an engagement?

    1. To guarantee the coachee will achieve every goal
    2. To ensure the coach can direct the coachee's decisions
    3. To define roles, boundaries, and expected outcomes Correct answer.
    4. To replace the need for confidentiality in sessions

    Explanation

    A coaching agreement clarifies roles, logistics, confidentiality, boundaries, and expected outcomes. It creates a safe, explicit container for the work rather than guaranteeing results or giving the coach decision authority.

  126. Question 126Coaching and Facilitation

    A coachee says, 'I can never lead a meeting because I am not a natural presenter.' What is the coach's most appropriate move?

    1. Explore evidence for and against the belief Correct answer.
    2. Explain why the belief is factually incorrect
    3. Agree and recommend avoiding presentation roles
    4. Provide a list of presentation techniques to study

    Explanation

    The statement reflects a limiting belief that can be examined through inquiry. The coach helps the coachee test the evidence and consider alternative perspectives rather than arguing or giving advice.

  127. Question 127Coaching and Facilitation

    Which sequence correctly represents the ORID focused conversation method?

    1. Objective, Reflective, Interpretive, Decisional Correct answer.
    2. Observation, Reaction, Insight, Direction-setting
    3. Open, Reframe, Imagine, Do
    4. Outcome, Review, Ideation, Decision-making

    Explanation

    ORID stands for Objective, Reflective, Interpretive, and Decisional. The method moves a group from facts and observations through feelings and meaning to decisions and action.

  128. Question 128Coaching and Facilitation

    Why might a facilitator use silent brainstorming before group discussion?

    1. To let the loudest participants set the direction
    2. To evaluate which ideas are cheapest to implement
    3. To reduce anchoring and groupthink Correct answer.
    4. To shorten the session by removing discussion entirely

    Explanation

    Silent brainstorming lets participants generate ideas independently before hearing others, which reduces anchoring on early speakers and limits groupthink. Discussion then builds on a broader set of inputs.

  129. Question 129Coaching and Facilitation

    Two team members disagree about a technical approach. The facilitator wants a win-win outcome that addresses both concerns. Which conflict mode is being used?

    1. Avoiding
    2. Accommodating
    3. Competing
    4. Collaborating Correct answer.

    Explanation

    Collaborating seeks a solution that fully addresses the concerns of both parties. In the Thomas-Kilmann model, it is high on both assertiveness and cooperativeness.

  130. Question 130Coaching and Facilitation

    What does coaching presence primarily involve?

    1. Sharing the coach's own experiences frequently
    2. Keeping the coachee focused on the coach's agenda
    3. Maintaining a calm, curious, and fully attentive state Correct answer.
    4. Having a detailed script of questions prepared in advance

    Explanation

    Coaching presence is the ability to be fully conscious and present with the coachee, using curiosity, calm, and attentiveness. It is not about following a rigid script or directing the coachee toward the coach's agenda.

  131. Question 131Coaching and Facilitation

    A coach asks, 'You do want to finish this project on time, don't you?' What is the main problem with this question?

    1. It is leading and limits the coachee's thinking Correct answer.
    2. It is too open-ended to generate useful information
    3. It requires the coach to give advice afterward
    4. It focuses on the coachee's strengths rather than weaknesses

    Explanation

    The question embeds the coach's preferred answer and pressures the coachee to agree. A powerful question would be more open, such as asking what finishing on time would require.

  132. Question 132Coaching and Facilitation

    What is the purpose of a 'parking lot' during a facilitated meeting?

    1. To record decisions that have already been approved
    2. To hold off-topic items for later Correct answer.
    3. To list participants who arrive late to the meeting
    4. To capture action items assigned to absent members

    Explanation

    A parking lot captures issues that are relevant but off-topic or better handled later. This allows the group to maintain focus without losing valuable points.

  133. Question 133Coaching and Facilitation

    In Tuckman's model, which stage is characterized by agreement on roles and shared working norms?

    1. Forming
    2. Norming Correct answer.
    3. Storming
    4. Performing

    Explanation

    Norming is the stage when the team begins to settle, agree on roles, and establish shared norms. Trust and cohesion typically increase as working agreements take hold.

  134. Question 134Coaching and Facilitation

    In coaching, a 'saboteur' or 'gremlin' most often refers to which of the following?

    1. A facilitator who blocks consensus to test the team
    2. A meeting role responsible for timekeeping
    3. An internal voice that creates self-doubt and limiting behavior Correct answer.
    4. A colleague who deliberately undermines the coachee's projects

    Explanation

    In coaching language, a saboteur or gremlin is an internal critic that generates self-doubt and limiting behavior. The coach helps the coachee notice and work with this inner voice.

  135. Question 135Coaching and Facilitation

    A coachee describes a conflict with a peer. Which coach response best keeps the conversation in a coaching stance?

    1. When I had a similar conflict, I handled it by escalating
    2. What outcome do you want, and what options exist? Correct answer.
    3. Your peer is clearly the one who needs to change
    4. You should document the conflict and send it to HR

    Explanation

    A coaching stance uses open questions to help the coachee clarify desired outcomes and generate options. This keeps ownership with the coachee instead of giving advice or judging the peer.

  136. Question 136Coaching and Facilitation

    How does the Liberating Structure '1-2-4-All' progress?

    1. Individuals reflect, pairs discuss, groups of four refine, everyone shares Correct answer.
    2. One facilitator presents, two people debate, four people vote, all decide
    3. One question is asked, two answers are chosen, four options are tested, all agree
    4. One team plans, two teams review, four teams implement, all report

    Explanation

    1-2-4-All moves from individual reflection to pair discussion, then groups of four, and finally whole-group sharing. The structure ensures broad participation before collective synthesis.

  137. Question 137Coaching and Facilitation

    In consent-based decision making, a decision is accepted when which condition is met?

    1. The most senior person agrees with the decision
    2. A simple majority of participants votes in favor
    3. Every participant personally prefers the decision
    4. No participant has a reasoned, paramount objection Correct answer.

    Explanation

    Consent means no one has a reasoned, paramount objection that the decision would harm the group's ability to fulfill its purpose. It is different from consensus, which seeks everyone's agreement or preference.

  138. Question 138Coaching and Facilitation

    A coach asks, 'On a scale of 1 to 10, how confident are you about this plan?' What is the main purpose of this scaling question?

    1. To make progress and next steps concrete and discussable Correct answer.
    2. To compare the coachee with other team members
    3. To calculate the statistically valid probability of success
    4. To end the session with a measurable metric

    Explanation

    Scaling questions help make an abstract feeling or level of confidence more concrete so the coachee can discuss what would move the number higher. They are not statistical measurements or comparisons with others.

  139. Question 139Coaching and Facilitation

    Which facilitator action is most likely to increase engagement in a long workshop?

    1. Allowing only the most senior participants to speak
    2. Extending the lecture segment to cover all remaining content
    3. Varying formats between reflection and small-group work Correct answer.
    4. Removing breaks to finish faster

    Explanation

    Varying formats gives participants different ways to process and contribute, which sustains attention and participation. Long lecture blocks, restricted voice, and removed breaks tend to reduce engagement.

  140. Question 140Coaching and Facilitation

    In the GROW coaching model, what does the 'O' stand for?

    1. Obstacles
    2. Objectives
    3. Options Correct answer.
    4. Outcomes

    Explanation

    GROW stands for Goal, Reality, Options, and Will. After clarifying the goal and current reality, the coach helps the coachee generate possible options before agreeing on action. Objectives and outcomes relate more to goal setting, while obstacles are usually explored as part of reality.

  141. Question 141Coaching and Facilitation

    Which coach behavior best demonstrates active listening?

    1. Paraphrasing the coachee's key points back to them Correct answer.
    2. Waiting silently while planning the next powerful question
    3. Changing the subject when the coachee becomes emotional
    4. Sharing a similar personal story to build rapport

    Explanation

    Active listening is shown by reflecting the coachee's content and feeling so they feel understood and can hear their own thinking. Planning the next question, self-disclosing, or avoiding emotion shifts the focus away from the coachee.

  142. Question 142Coaching and Facilitation

    A team member arrives late to several meetings. Which feedback statement follows the SBI (Situation-Behavior-Impact) model?

    1. At yesterday's stand-up, your 15-minute delay made the team pause and repeat context. Correct answer.
    2. You are unreliable and need to improve your attitude.
    3. Everyone on the team has noticed that you do not care about their time or the project.
    4. I feel you are not committed; please reflect on your behavior.

    Explanation

    SBI feedback names a specific situation, describes observable behavior, and states the impact. This keeps the feedback concrete and less defensive than global judgments or speaking for others.

  143. Question 143Coaching and Facilitation

    During a workshop, one senior participant repeatedly interrupts others. What is the facilitator's most appropriate first intervention?

    1. Ignore the behavior so the session does not become sidetracked by conflict.
    2. Publicly confront the participant in front of the group to set an example.
    3. Ask the participant to leave the session until they can behave appropriately.
    4. Use round-robin turn-taking and restate the ground rules. Correct answer.

    Explanation

    A facilitator's first move should be a process intervention that protects psychological safety and balances airtime. Structured turn-taking and restating agreed ground rules address the behavior without escalating defensiveness.

  144. Question 144Coaching and Facilitation

    A coachee commits to an action but repeatedly does not follow through. Which coaching response best reflects the coaching stance?

    1. Take over the task to ensure it gets done.
    2. Set a firmer deadline and remind them of the consequences of missing it.
    3. Conclude that the coachee is not yet ready to benefit from coaching.
    4. Explore what got in the way and ask for a new commitment. Correct answer.

    Explanation

    In coaching, non-completion is treated as useful information rather than failure. The coach explores barriers and supports the coachee's own choice and accountability for the next commitment.

  145. Question 145Servant Leadership and Team Development

    Which author is credited with originating the concept of servant leadership?

    1. Daniel Goleman
    2. Robert K. Greenleaf Correct answer.
    3. John Kotter
    4. Peter Senge

    Explanation

    Servant leadership as a named concept was introduced by Robert K. Greenleaf in his 1970 essay 'The Servant as Leader'. He argued that the leader is first a servant, and that leadership emerges from the desire to serve others.

  146. Question 146Servant Leadership and Team Development

    A servant leader's primary motivation is best described as:

    1. Achieving personal recognition within the organization
    2. Maximizing short-term returns for stakeholders
    3. Ensuring that the needs of others are served first Correct answer.
    4. Maintaining strict control over team decisions

    Explanation

    Servant leadership inverts the usual order by placing service to others ahead of the leader's own ambitions. The leader's success is measured through the growth and well-being of the people served.

  147. Question 147Servant Leadership and Team Development

    According to Tuckman's model, in which order do teams typically pass through the stages of development?

    1. Storming, forming, norming, performing
    2. Forming, norming, storming, performing
    3. Norming, forming, performing, storming
    4. Forming, storming, norming, performing Correct answer.

    Explanation

    Tuckman described a sequence in which teams first orient themselves, then experience conflict, then establish norms, and finally perform. A later addition placed adjourning after the performing stage.

  148. Question 148Servant Leadership and Team Development

    A self-organizing team is one that:

    1. Decides among its members how to accomplish its work Correct answer.
    2. Relies on the manager to assign every task individually
    3. Has no defined roles or accountability at all
    4. Follows a fixed plan that cannot be changed mid-iteration

    Explanation

    Self-organization means the team holds the authority to determine how it does its work within agreed boundaries. It does not mean an absence of structure, accountability, or shared goals.

  149. Question 149Servant Leadership and Team Development

    Which behavior best demonstrates active listening?

    1. Nodding frequently without asking any questions
    2. Changing the subject to keep the conversation moving
    3. Summarizing the speaker's message to confirm understanding Correct answer.
    4. Planning your reply while the other person is still speaking

    Explanation

    Active listening is visible in behaviors such as paraphrasing, summarizing, and asking clarifying questions to verify meaning. The listener's attention is fully on understanding the speaker before responding.

  150. Question 150Servant Leadership and Team Development

    Which servant-leader characteristic involves anticipating what may happen in the future based on past experience and present signals?

    1. Stewardship
    2. Foresight Correct answer.
    3. Persuasion
    4. Empathy

    Explanation

    Foresight is the ability to look ahead and anticipate consequences, drawing on lessons from the past and cues in the present. Greenleaf treated it as a distinguishing mark of the servant leader.

  151. Question 151Servant Leadership and Team Development

    Stewardship, as a servant-leader characteristic, refers to:

    1. Holding resources in trust for the good of others Correct answer.
    2. Maximizing the leader's personal influence
    3. Delegating all decisions to senior management
    4. Protecting the team from any external feedback

    Explanation

    Stewardship frames the leader as a trustee who cares for people, resources, and the institution on behalf of others. The emphasis is on responsibility to the wider community rather than on ownership or personal gain.

  152. Question 152Servant Leadership and Team Development

    A newly formed team begins arguing over roles and disagreeing about how to approach the work. As a servant leader, the most appropriate response is to:

    1. Wait for the team to resolve the conflict without any involvement
    2. Facilitate discussion of working agreements and concerns Correct answer.
    3. Reassign the work so conflict is avoided entirely
    4. Postpone the work until the team agrees on every detail

    Explanation

    Conflict over roles and approach is a normal feature of the storming stage and is best worked through rather than suppressed. The servant leader helps the team surface concerns and establish shared working agreements while keeping the work moving.

  153. Question 153Servant Leadership and Team Development

    Which statement best distinguishes coaching from mentoring?

    1. Coaching is a one-off event, while mentoring is a permanent assignment
    2. Coaching focuses only on technical skills, while mentoring covers only career goals
    3. Coaching draws out the learner's own answers, whereas mentoring shares experience Correct answer.
    4. Coaching is always delivered by a line manager, while mentoring is delivered by peers

    Explanation

    Coaching is typically non-directive: the coach asks questions that help the learner find their own solutions. Mentoring is more often directive, with the mentor offering experience, advice, and networks.

  154. Question 154Servant Leadership and Team Development

    A team repeatedly loses time because a shared test environment is unavailable. The servant leader's first action should be to:

    1. Ask the team to work around the problem without escalating
    2. Reduce the team's commitment for the next few sprints
    3. Work to have the environment issue resolved and remove the obstacle Correct answer.
    4. Add the problem to the team's definition of done

    Explanation

    Removing impediments is a core servant-leadership responsibility, especially when the obstacle lies outside the team's control. The leader uses their organizational access to get the environment fixed rather than shifting the burden back to the team.

  155. Question 155Servant Leadership and Team Development

    Psychological safety in a team is best described as:

    1. A shared belief that it is safe to speak up and take interpersonal risks Correct answer.
    2. A climate in which conflict is avoided to keep everyone comfortable
    3. A policy that all team decisions must be unanimous
    4. A guarantee that no one will be held accountable for mistakes

    Explanation

    Psychological safety is a shared team belief that voicing questions, concerns, or mistakes will not lead to humiliation or punishment. It supports learning and candor while remaining compatible with accountability and productive disagreement.

  156. Question 156Servant Leadership and Team Development

    Which action is an example of genuine delegation rather than abdication?

    1. Handing over a task with no context and no follow-up
    2. Assigning work but retaining every decision for yourself
    3. Giving a task to whoever is least busy at the moment
    4. Transferring a task together with authority and support Correct answer.

    Explanation

    Effective delegation transfers the task, the authority to act, and access to the support or resources needed. Abdication drops the task on someone without authority, context, or follow-up.

  157. Question 157Servant Leadership and Team Development

    Greenleaf argued that a servant leader influences teams primarily through:

    1. Persuasion rather than positional coercion Correct answer.
    2. Formal authority and compliance rules
    3. Financial incentives and bonuses
    4. Escalation to senior leadership

    Explanation

    Greenleaf held that influence rooted in persuasion respects the other person's freedom to choose. Coercion through position may produce compliance but not genuine commitment.

  158. Question 158Servant Leadership and Team Development

    Which action best reflects a commitment to the growth of people?

    1. Keeping development conversations out of the workplace
    2. Assigning each person the same tasks they have already mastered
    3. Setting aside time to help a team member develop a skill they want to build Correct answer.
    4. Protecting team members from stretch assignments they might fail

    Explanation

    Commitment to growth means treating each person as a whole individual with aspirations and investing time in their development. It requires intentional support, not merely keeping people within their comfort zone.

  159. Question 159Servant Leadership and Team Development

    A team member is new to a task and lacks the skill but shows high enthusiasm. Which leadership style fits best?

    1. Observing, because the person should figure it out alone
    2. Delegating, because enthusiasm is all that is needed
    3. Directing, because the person needs clear guidance on what and how Correct answer.
    4. Coaching, because the person needs only occasional support

    Explanation

    Situational leadership matches style to the person's competence and commitment for the specific task. Low competence combined with high willingness calls for clear direction on what to do and how to do it.

  160. Question 160Servant Leadership and Team Development

    When a servant leader facilitates a team meeting, the leader should:

    1. Remain neutral and help the group reach its own decisions Correct answer.
    2. Steer the group away from disagreement
    3. Make the final decision for the team to save time
    4. Advocate for their preferred solution during the discussion

    Explanation

    Facilitation is about managing the process so the group can do its best thinking, which requires neutrality on the content. If the leader also holds a decision-making role, that role should be made explicit and separated from facilitation.

  161. Question 161Servant Leadership and Team Development

    The 'Prime Directive' used in retrospectives asks participants to:

    1. Identify which individual caused the most defects
    2. Agree to keep the discussion free of any data
    3. Assume everyone did the best job possible given what they knew Correct answer.
    4. Record only the successes and skip problem areas

    Explanation

    The Prime Directive sets a blame-free frame by assuming good intent and good faith effort from everyone involved. This makes it safer to examine problems candidly and focus on improvement rather than fault.

  162. Question 162Servant Leadership and Team Development

    Which practice most directly builds a sense of community within a team?

    1. Limiting social contact so work time stays protected
    2. Rotating members between teams every few days
    3. Creating regular opportunities for members to learn about each other Correct answer.
    4. Publishing a ranking of individual velocity results

    Explanation

    Building community depends on knowing one another as people and developing genuine relationships over time. Structured, recurring opportunities for personal connection nurture trust and belonging.

  163. Question 163Servant Leadership and Team Development

    A leader notices they are becoming defensive during a tense exchange. The best demonstration of self-regulation is to:

    1. Agree with everything to end the discussion quickly
    2. Raise their voice so the team understands the seriousness
    3. Pause, take a breath, and respond deliberately Correct answer.
    4. Leave the room and never revisit the topic

    Explanation

    Self-regulation is the capacity to notice an emotional reaction and choose a response rather than act on impulse. A deliberate pause creates space to respond constructively and keeps the conversation productive.

  164. Question 164Servant Leadership and Team Development

    Greenleaf's 'best test' of servant leadership asks whether those served:

    1. Become healthier, wiser, freer, and more autonomous Correct answer.
    2. Deliver the highest possible output in the shortest time
    3. Remain dependent on the leader for guidance
    4. Comply fully with the leader's instructions

    Explanation

    Greenleaf's best test asks whether those served grow as persons and become healthier, wiser, freer, more autonomous, and more likely to serve others. Output and compliance are not the measure he proposed.

  165. Question 165Servant Leadership and Team Development

    A leader resolves every problem for the team and is praised for fast answers. Which analysis best reflects a servant-leadership perspective?

    1. The behavior is ideal because the leader removes all obstacles
    2. The behavior is ideal because teams should never handle problems
    3. The behavior is neutral because servant leadership says nothing about problem ownership
    4. Short-term speed is gained at the cost of the team's capability to solve problems itself Correct answer.

    Explanation

    Servant leadership measures success by the growth and autonomy of the people served, so solving every problem for the team trades long-term capability for short-term speed. Removing impediments beyond the team's reach is appropriate; taking over problems the team could own is not.

  166. Question 166Servant Leadership and Team Development

    A performing team loses two experienced members and a new member joins. Which outcome is most consistent with Tuckman's model?

    1. The team may return to forming or storming as roles and relationships are renegotiated Correct answer.
    2. The team stays in performing because the stage depends on the group's duration
    3. The team's stage is unaffected because stages apply only to individuals
    4. The team moves directly to adjourning because membership changed

    Explanation

    Tuckman's stages describe the state of the group's relationships, not a calendar milestone, so a significant change in membership can send the team back to earlier stages. Roles, trust, and norms typically need to be renegotiated with new members.

  167. Question 167Servant Leadership and Team Development

    Which pair best distinguishes conceptualization from foresight?

    1. Conceptualization concerns the leader's feelings, while foresight concerns budgets
    2. Conceptualization concerns delegation, while foresight concerns controlling others
    3. Conceptualization concerns past events, while foresight concerns formal authority
    4. Conceptualization is envisioning possibilities, while foresight is anticipating outcomes Correct answer.

    Explanation

    Conceptualization is the ability to think beyond day-to-day operations and imagine a larger vision or set of possibilities. Foresight is forward-looking judgment about what is likely to happen and what it implies.

  168. Question 168Servant Leadership and Team Development

    A team keeps escalating every small decision to its Scrum Master, who answers promptly each time. What is the most likely effect over time?

    1. The team's decision-making capability grows because they see good examples
    2. The team's morale improves because the leader is responsive
    3. The team's throughput improves because waiting is eliminated
    4. The team becomes dependent and stops developing its own judgment Correct answer.

    Explanation

    Repeatedly answering questions the team could decide itself reinforces escalation and prevents the team from building decision-making capability. A servant leader instead helps the team establish its own decision boundaries and supports it in using them.

  169. Question 169Product Delivery and Value Maximization

    In Scrum, who is accountable for maximizing the value of the product resulting from the work of the Scrum Team?

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

    Explanation

    Scrum assigns product value maximization to a single accountable role so that trade-offs have one clear owner. That role is the Product Owner, who orders the backlog and decides what is worth building. The Scrum Master and Developers contribute, but they are not accountable for value.

  170. Question 170Product Delivery and Value Maximization

    What is the primary purpose of the Definition of Done?

    1. To list every task the Developers must complete in a Sprint
    2. To give a shared standard for when work is complete Correct answer.
    3. To describe the team's engineering tools and coding standards
    4. To record the acceptance tests the Product Owner wrote

    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, explicit understanding of what completion means, which makes status reporting transparent. Task lists and tooling choices may exist, but they are not what the Definition of Done is for.

  171. Question 171Product Delivery and Value Maximization

    What does incremental delivery primarily enable?

    1. Detailed long-term plans fixed at project start
    2. Early feedback and earlier realization of value Correct answer.
    3. Individual performance measurement across teams
    4. Larger releases with fewer integration points

    Explanation

    Delivering in small increments puts usable functionality in front of users sooner, so the team learns early and value is realized before the whole scope is finished. It also reduces the risk carried in unfinished work. Larger releases and fixed upfront plans work against these benefits.

  172. Question 172Product Delivery and Value Maximization

    Mid-Sprint the Developers discover a simpler way to reach the Sprint Goal that changes some of the planned work. What is the most appropriate response?

    1. Ask the stakeholders to vote on which approach the team should take
    2. Finish the original plan and defer the simpler approach to the next Sprint
    3. Cancel the Sprint and re-plan the whole Sprint Backlog from scratch
    4. Adjust the work with the Product Owner while keeping the Sprint Goal Correct answer.

    Explanation

    The Sprint Goal is the fixed commitment for the Sprint, while the Sprint Backlog may change as more is learned. The Developers and Product Owner negotiate the scope as details emerge, provided the Sprint Goal remains achievable. Cancelling the Sprint is reserved for a Sprint Goal becoming obsolete.

  173. Question 173Product Delivery and Value Maximization

    Several stakeholders each insist their item must be done first. On what basis should the Product Owner order the Product Backlog?

    1. The size of each item, smallest items first
    2. The order in which the requests were received
    3. The seniority of the stakeholder making the request
    4. The estimated value and its timeliness relative to cost Correct answer.

    Explanation

    The Product Owner orders the backlog to maximize value, weighing the value an item delivers, when that value can be realized, and the effort required. Request recency or the requester's rank are not value signals. Size alone is a cost proxy and says nothing about benefit.

  174. Question 174Product Delivery and Value Maximization

    A team wants to learn quickly whether customers will pay for a new capability. What best describes a minimum viable product?

    1. The first release that includes every planned feature
    2. A prototype built only for internal demonstration to executives
    3. The smallest set of features that covers the whole vision
    4. The least effort that yields validated learning about value Correct answer.

    Explanation

    A minimum viable product is scoped to produce the maximum validated learning for the least effort, so the team can test demand before investing further. Its purpose is learning about value, not completeness of the vision or internal show-and-tell.

  175. Question 175Product Delivery and Value Maximization

    A team reports 40% more story points delivered this quarter, yet customer adoption is flat. What does this most likely indicate?

    1. Story points are a reliable measure of customer value
    2. The Product Backlog was ordered incorrectly by the Product Owner
    3. The team needs to increase velocity further to see adoption
    4. Output increased without a corresponding increase in value Correct answer.

    Explanation

    Story points measure the size of work completed, not the value realized from it, so a rise in points with flat adoption signals output growth without outcome improvement. Teams should then examine outcome measures such as adoption, retention or revenue. Points should never be treated as a value metric.

  176. Question 176Product Delivery and Value Maximization

    What is the main purpose of Product Backlog refinement?

    1. To estimate the exact number of hours each item will take
    2. To obtain formal stakeholder sign-off on each backlog item
    3. To clarify and split items until they are ready to start Correct answer.
    4. To convert the Product Backlog into a fixed Sprint contract

    Explanation

    Refinement is the ongoing activity of breaking down and clarifying backlog items so they are small enough and well enough understood to be brought into a Sprint. It is a continuous conversation, not an approval gate or a commitment device. Exact hour-level estimates are neither required nor reliable.

  177. Question 177Product Delivery and Value Maximization

    A team that introduces a strict work-in-progress limit finds that items finish sooner, even though nobody works harder. Why does this happen?

    1. Because less multitasking and rework shortens lead time Correct answer.
    2. Because the limit increases the amount of work in progress
    3. Because velocity is then measured much more accurately
    4. Because the team is able to skip the testing steps

    Explanation

    A WIP limit forces the team to finish work before starting more, which reduces context switching, queue growth and rework. The result is a shorter lead time at the same effort. The limit restricts work in progress rather than increasing it.

  178. Question 178Product Delivery and Value Maximization

    A team builds a feature exactly to specification, but users find it confusing to use. Which change to how the team works addresses this most directly?

    1. Add more detail to the specification documents
    2. Add a final acceptance phase before each release
    3. Show a usable increment to users early and adapt Correct answer.
    4. Increase the number of features delivered per Sprint

    Explanation

    Confusion that survives a correct implementation points to a gap between assumptions and real user behaviour. Putting a usable increment in front of real users early creates the feedback needed to correct course. More documentation or more scope does not close that gap.

  179. Question 179Product Delivery and Value Maximization

    Over the last six Sprints a team delivered an average of 30 points per Sprint on comparable scope, and the remaining backlog is estimated at 150 points of similar size. What is the most reasonable forecast?

    1. It cannot be forecast until every item is fully detailed
    2. Exactly five Sprints, because velocity is a fixed capacity
    3. About three Sprints, to allow for improved efficiency
    4. About five Sprints, refined as more is learned Correct answer.

    Explanation

    Dividing remaining size by recent average throughput gives a reasonable starting forecast of about five Sprints. Because the backlog and the team's context will change, the forecast is refined each Sprint rather than treated as fixed. It is not a reason to avoid forecasting altogether.

  180. Question 180Product Delivery and Value Maximization

    Two features compete for the same team. Feature A has higher total value and can ship at any point this year. Feature B has lower total value, but its value drops sharply after a regulatory deadline in six weeks. Which should be prioritized?

    1. Both together, to balance value and risk
    2. Neither, until the full annual roadmap is approved
    3. Feature B, because its value is more time-sensitive Correct answer.
    4. Feature A, because its total value is higher

    Explanation

    Prioritization should weigh value against the cost of delaying it, not total value alone. Feature B carries a steep cost of delay because its value decays after a fixed date, whereas Feature A loses little by waiting. Sequencing the time-sensitive item first protects the larger combined value.

  181. Question 181Product Delivery and Value Maximization

    A value stream map shows that work waits about twelve days for review and is actively worked on for about three days. What does this most strongly suggest?

    1. The team should shorten the review checklist and criteria
    2. Delay dominates lead time, so the review queue is the bottleneck Correct answer.
    3. The team should work faster during the three active days
    4. Lead time is already efficient since active work is short

    Explanation

    When wait time greatly exceeds touch time, most of the lead time is queueing rather than working, so improvement effort belongs at the queue. Increasing the capacity or reducing the batch size at the review step shortens the delay. Speeding up the active work addresses only a small share of the total.

  182. Question 182Product Delivery and Value Maximization

    A team's Definition of Done omits testing, so untested work is reported as complete and stakeholders plan releases on that basis. Which pillar of empiricism is most directly compromised?

    1. Transparency, because reported status misstates reality Correct answer.
    2. Self-management, because the team sets its own standards
    3. Adaptation, because the team cannot change its plan
    4. Inspection, because reviews happen too infrequently

    Explanation

    Empiricism requires that the artifacts reflect reality so that inspection of them is meaningful. Reporting untested work as done makes the Increment's status opaque, which then corrupts inspection and any adaptation built on it. The first failing is transparency.

  183. Question 183Organizational Agility and Scaling

    Organizational agility is best described as which of the following?

    1. The ability to sense change and continuously reallocate people, money, and priorities toward new value Correct answer.
    2. The share of the workforce that holds an agile certification and has completed the organization's agile training curriculum
    3. The speed at which a single team can complete a fixed scope of requirements that were agreed at the start of the year
    4. The degree to which every team follows the same prescribed set of ceremonies, roles, and tools without exception

    Explanation

    Agility at the organizational level is about responsiveness: sensing change early and being able to move resources and investment toward what matters now. It depends on decision rights, funding models, and structure, not on ceremony conformance or fixed scope delivery. Certification counts and uniform process adoption are proxies for activity, not evidence of adaptability.

  184. Question 184Organizational Agility and Scaling

    In an agile organization, what is a value stream?

    1. The ordered list of backlog items that a product owner ranks by expected business value before each sprint
    2. The sequence of activities an organization uses to deliver value to a customer, from demand to outcome Correct answer.
    3. The organization chart that shows reporting lines, job titles, and headcount for each department
    4. The financial ledger that records how much each project has spent against its approved annual budget

    Explanation

    A value stream is the end-to-end flow of work that converts a customer need into a delivered outcome, crossing whatever teams and systems are involved. Organizing and funding around value streams is what allows an enterprise to optimize flow rather than local departmental efficiency. Backlogs, budgets, and org charts are artifacts that support or obstruct that flow but are not the flow itself.

  185. Question 185Organizational Agility and Scaling

    What is an Agile Release Train?

    1. A long-lived team of teams, usually 50 to 125 people, that plans and integrates work together Correct answer.
    2. A single cross-functional team of five to nine people that owns one product increment from start to finish
    3. A temporary program team that is assembled for one release and disbanded once that release ships to production
    4. An executive steering committee that approves quarterly budgets and resolves escalated portfolio risks

    Explanation

    An Agile Release Train is a long-lived structure of agile teams aligned to a value stream, large enough to deliver end-to-end increments but small enough to coordinate. Its persistence is the point: stable teams build trust, reduce handoffs, and accumulate knowledge across increments. Temporary program teams and steering committees lack the continuous delivery capability the train is meant to provide.

  186. Question 186Organizational Agility and Scaling

    In Lean Portfolio Management, what is the purpose of participatory budgeting?

    1. Approve individual features one at a time through a central intake committee that meets on a monthly cadence
    2. Allocate capacity across value streams collaboratively and on a rolling basis Correct answer.
    3. Replace strategic portfolio reviews with team retrospectives so that spending decisions emerge from the bottom up
    4. Allow every team to set its own headcount and spending without any portfolio-level review or trade-off discussion

    Explanation

    Participatory budgeting replaces annual, project-by-project funding with a collaborative, rolling allocation of capacity to value streams. It keeps investment aligned to strategy while allowing the portfolio to shift money as evidence changes. It is neither unlimited local autonomy nor feature-by-feature central approval.

  187. Question 187Organizational Agility and Scaling

    What distinguishes a platform team in modern organizational design?

    1. It offers internal services that reduce cognitive load for stream-aligned teams Correct answer.
    2. It manages budgets, headcount, and performance ratings for the whole engineering organization
    3. It owns all architecture decisions and must approve every change that delivery teams propose before release
    4. It is a temporary group formed to deliver one large release and then return members to their home teams

    Explanation

    A platform team exists to make the work of stream-aligned teams easier by providing self-service capabilities that lower cognitive load and remove repeated effort. It succeeds when stream-aligned teams are treated as customers who can adopt its services voluntarily. Approval-gate architecture boards and centralized line management are different, largely incompatible, structures.

  188. Question 188Organizational Agility and Scaling

    What is the primary purpose of a community of practice?

    1. To assign specialists to project teams according to their current utilization rate and skills inventory
    2. To develop and spread craft knowledge among practitioners who share a discipline across teams Correct answer.
    3. To report delivery metrics and trend reports upward to portfolio leadership on a fixed monthly schedule
    4. To approve cross-team dependencies and confirm that each dependency has an owner before the release

    Explanation

    A community of practice is a voluntary, cross-team network of people who share a discipline and want to improve how it is practiced. It spreads standards, patterns, and tacit knowledge faster than formal channels and strengthens craft without adding reporting lines. Governance of dependencies and resource allocation are separate mechanisms.

  189. Question 189Organizational Agility and Scaling

    Two organizations adopt the same scaling framework; one becomes faster while the other becomes slower and more bureaucratic. What is the most likely explanation?

    1. The faster organization skipped the recommended ceremonies and therefore removed unnecessary overhead
    2. Frameworks provide starting conditions, so results depend on each organization's constraints and change approach Correct answer.
    3. Scaling outcomes are essentially random and cannot be usefully analyzed or compared across organizations
    4. The slower organization must have selected the wrong framework, since framework choice is the main determinant of speed

    Explanation

    A framework supplies roles, cadences, and artifacts, but it does not supply the diagnosis of what is limiting flow in a particular enterprise. Organizations that import practices without adapting them to their own constraints often add coordination overhead rather than removing it. The same framework can therefore help or hinder depending on context and on how the change is led.

  190. Question 190Organizational Agility and Scaling

    When leaders begin an agile transformation in a large enterprise, what should they do first?

    1. Mandate a single tooling standard for all teams before any training or engagement begins
    2. Create urgency by making the cost of the status quo visible and widely understood Correct answer.
    3. Publish a complete five-year transformation roadmap before speaking with teams or middle managers
    4. Roll out new role titles and reporting lines in the first month so the structure is in place early

    Explanation

    Large-scale change stalls when the organization sees no compelling reason to move, so the first task is establishing shared urgency around the cost of current ways of working. Structural and tooling changes made before that sense of purpose tend to produce compliance without commitment. A long, fixed roadmap published up front also undercuts the adaptive, learning-based nature of transformation.

  191. Question 191Organizational Agility and Scaling

    A large organization wants faster local decisions while keeping strategic alignment. Which enabler is most effective?

    1. Requiring every decision to be escalated to a portfolio board for approval before action
    2. Clear guardrails that define boundaries within which teams decide locally Correct answer.
    3. Granting teams unlimited autonomy with no shared objectives, constraints, or alignment mechanisms
    4. Standardizing every team's process to one template so that decisions become predictable

    Explanation

    Decentralized decision-making works when strategy is expressed as boundaries - objectives, constraints, non-negotiables - that let people act without asking permission each time. This keeps alignment while reducing latency. Escalation and blanket standardization both restore alignment by removing local judgment, which increases delay.

  192. Question 192Organizational Agility and Scaling

    Which measure best indicates that organizational agility has improved?

    1. Count of agile ceremonies held each quarter, tracked per team and reported to leadership
    2. Time from a validated customer need to a measurable customer outcome Correct answer.
    3. Percentage of teams that have adopted the organization's standard backlog management tool
    4. Number of story points the teams complete per sprint, summed across the program

    Explanation

    Agility is about shortening the delay between a real need and a real outcome, so flow from validated need to measurable result is the most direct indicator. Output volume and activity counts can rise while lead time and responsiveness stagnate. Tool adoption is an input measure that says nothing about the speed of value delivery.

  193. Question 193Organizational Agility and Scaling

    An organization wants a product-oriented architecture but keeps its existing component-silo teams intact. What is the most likely architectural result?

    1. The silo structure will be reproduced in the architecture, because designs mirror communication paths Correct answer.
    2. There will be little effect, because architecture is determined solely by architects and technology choices
    3. A modular, product-oriented architecture will emerge automatically once the roadmap states that goal
    4. Integration speed will improve, because specialization increases the volume of work each team can finish

    Explanation

    System designs tend to copy the communication structures of the organization that builds them, so unchanged silos will keep producing interfaces that reflect departmental boundaries. Changing architecture therefore usually requires changing team boundaries and ownership alongside the technical design. Declaring an architectural goal without changing the organization leaves the forces in place that produced the current design.

  194. Question 194Organizational Agility and Scaling

    A portfolio is moving from project funding to product funding. What should the basis of approval become?

    1. Fixed-cost business cases that are re-approved at every stage gate before the team may continue
    2. Persistent, outcome-based funding of long-lived value streams with periodic reviews Correct answer.
    3. Annual line-item budgets for each team's tools, training, and headcount, set by finance centrally
    4. Funding each feature request separately through a central intake committee that ranks incoming ideas

    Explanation

    Product funding gives long-lived teams and value streams stable capacity and holds them accountable to outcomes reviewed periodically. This removes the stop-start dynamic of project approval while preserving portfolio-level oversight of value. Stage gates, line-item budgets, and feature-level funding all reinstate project thinking under a new label.

  195. Question 195Organizational Agility and Scaling

    What is the primary responsibility of a Release Train Engineer?

    1. Owning the product vision and prioritizing the portfolio backlog on behalf of executive stakeholders
    2. Managing the careers, performance ratings, and compensation decisions for all engineers on the train
    3. Serving as chief scrum master for the train, facilitating its events and helping remove impediments Correct answer.
    4. Chairing the architecture review board and approving technical designs before each program increment

    Explanation

    The Release Train Engineer is a servant leader and facilitator for the train, running its planning and synchronization events and helping resolve impediments that span teams. The role focuses on flow and process health rather than product content or technical approval. Line management of engineers sits elsewhere in the organization.

  196. Question 196Organizational Agility and Scaling

    What is the main purpose of a recurring cross-team planning event in a scaled organization?

    1. Replacing team-level planning entirely so that teams can adapt daily without shared commitments
    2. Surfacing and committing to cross-team dependencies while aligning on a shared near-term objective Correct answer.
    3. Producing a detailed twelve-month delivery plan with task-level assignments for every engineer
    4. Approving the annual budget for each participating team and confirming headcount for the coming year

    Explanation

    Cross-team planning exists to make dependencies visible and to align many teams on one near-term objective they can commit to together. It complements, rather than replaces, team-level planning and adaptation during the increment. Detailed long-range task assignment and budget approval are outside its scope.

  197. Question 197Organizational Agility and Scaling

    In a squad-and-tribe operating model, what is the role of a chapter?

    1. Managing hiring, compensation, and facilities for the entire engineering organization
    2. Owning end-to-end delivery of a customer-facing product with all the skills needed to ship it
    3. Coordinating dependencies between tribes and sequencing work at the portfolio level
    4. Keeping craft standards and competency aligned for specialists who share a discipline within a tribe Correct answer.

    Explanation

    A chapter groups people with the same craft within a tribe, typically with a line-management relationship, so that professional standards and skill growth stay coherent while individuals work in squads. Delivery accountability stays with the squad. Cross-tribe coordination and enterprise administration are separate roles.

  198. Question 198Organizational Agility and Scaling

    A program's largest delays come from waiting for a central architecture review board. Applying theory of constraints, what is the best first action?

    1. Measure and equalize utilization across all teams so that no group appears to be the bottleneck
    2. Optimize the downstream delivery teams first, because they are where value is actually produced
    3. Increase work in progress so that teams stay busy while they wait for review decisions
    4. Relieve the constraint by adding capacity to, and loosening the criteria for, the review board Correct answer.

    Explanation

    Throughput of a system is limited by its constraint, so improvement effort belongs at the bottleneck; work done elsewhere only builds queues in front of it. Adding review capacity and reducing the number of changes that genuinely require review raises flow at the constraint. Raising work in progress or chasing utilization elsewhere makes the queue longer.

SMP flashcards

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

Empiricism
Knowledge comes from experience and decisions are based on what is observed. Scrum is founded on it to handle complex work where prediction is unreliable.
Three pillars of Scrum
Transparency, inspection and adaptation. They enable empirical process control and require a shared standard so artifacts are interpreted the same way.
Scrum values
Commitment, focus, openness, respect and courage. They guide behavior and build the trust the Scrum Team needs to inspect and adapt honestly.
Self-managing team
A team that internally decides who does what, when and how. It holds real authority over its own work process instead of receiving task assignments.
Product Owner accountability
Accountable for maximizing product value and for effective Product Backlog management, including ordering items and communicating the Product Goal.
Scrum Master accountability
Accountable for the Scrum Team's effectiveness. Coaches the team and organization, facilitates events and removes impediments to applying Scrum.
Developers accountability
Accountable for creating a usable Increment each Sprint and for deciding how the work is done. They are self-managing within the team.
Product Owner as one person
The Product Owner is a single individual, never a committee. Work may be delegated, but accountability for the Product Backlog remains.
Sprint
The container event of one month or less in which all other events occur. A new Sprint starts immediately after the previous one ends.
Daily Scrum
A 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog for the next day of work.
Sprint Review
An event to inspect the Increment and adapt the Product Backlog. Timeboxed to four hours for a one-month Sprint.
Sprint Retrospective
An event to inspect how the last Sprint went and plan improvements in quality and effectiveness. Three hours maximum for one-month Sprints.
Product Goal
The commitment for the Product Backlog. A long-term target the Scrum Team plans against, with only one active at a time.
Sprint Goal
The commitment for the Sprint Backlog. A single objective that gives the Sprint focus and guides the Developers' daily work.
Definition of Done
The commitment for the Increment. A formal description of quality the Increment must meet before it counts as complete.
Increment
A concrete, usable stepping stone toward the Product Goal. It must meet the Definition of Done to be considered releasable.
Coaching versus mentoring
Coaching uses questions to raise self-awareness and ownership. Mentoring transfers experience and advice from a more experienced person.
Facilitation
Designing and guiding group processes so the group reaches a defined outcome, while remaining neutral about the content of the discussion.
Powerful question
An open, concise question that invites reflection and new thinking, rather than a yes/no or leading question.
Psychological safety
A shared belief that speaking up and admitting mistakes is safe. It enables honest inspection in events such as the Retrospective.
Servant leadership
A leadership stance that prioritizes the growth, needs and effectiveness of others, removing impediments rather than directing work.
Tuckman stages
Forming, storming, norming and performing. Teams move through these stages as relationships, roles and ways of working mature.
Situational leadership
Matching direction and support to a person's competence and commitment for a specific task. Autonomy grows as capability grows.
Delegation decision rule
Delegate when competence and commitment are high for the task. Provide more direction or support when either of them is low.
Little's Law
Average cycle time equals work in progress divided by throughput. Reducing WIP shortens cycle time when throughput stays constant.
Cost of delay
The economic impact of not delivering a feature on time. It helps the Product Owner order backlog items by value.
Outcome versus output
Output counts delivered features. Outcome measures the change in behavior or results that actually creates value for users.
Undone work as debt
Work that does not meet the Definition of Done is undone work. It accumulates as debt and reduces the transparency of the Increment.
Nexus
A scaling approach for three to nine Scrum Teams on one product, with a Nexus Integration Team addressing cross-team integration and dependencies.
Scaling decision rule
Scale only when one team cannot deliver the product. Additional teams add coordination cost and dependencies that must be actively managed.
Shared Product Backlog
When multiple teams build one product they use one Product Backlog, one Product Owner and one Product Goal.
Dependency management
Dependencies across teams are the main scaling challenge. Make them visible during refinement and plan integration work explicitly.

SMP study guide

Scrum Theory and Principles

The foundation: empiricism

Scrum is a lightweight framework built on empiricism - knowledge comes from experience and decisions are made on what is observed. Three pillars support it: transparency (the process and the work are visible to those accountable for the outcome), inspection (artifacts and progress are examined frequently enough to detect problems), and adaptation (the process or the work is adjusted as soon as deviation crosses acceptable limits). The pillars form a chain: inspection without transparency produces false signals, and inspection without adaptation is pure waste.

The five values

Commitment, Focus, Openness, Respect and Courage are not decoration - they are the behavioural preconditions that make the pillars function. Openness enables transparency; courage enables adaptation. Expect questions that treat the values as soft extras, or that ask which value a specific behaviour violates.

Lean and iterative-incremental thinking

Scrum inherits from Lean: eliminate waste, focus on essentials, respect people, deliver as fast as possible, and build quality in. It is iterative (refine through repeated cycles) and incremental (build up a usable whole). Iteration without increment is churn; increment without iteration loses the feedback loop.

Traps

  • Treating Scrum as a methodology or a prescriptive process - it defines what is required, not how.
  • Assuming the Sprint is the only moment for inspection; the Daily Scrum, review and refinement all inspect.
  • Assuming adaptation happens automatically once a problem becomes visible.

Rule of thumb

Check transparency before you inspect. If the backlog, the Definition of Done or the reported status is not honest and visible, any decision you make from inspection will be wrong.

Scrum Roles and Accountabilities

Three accountabilities, five events, three artifacts

Scrum defines exactly three accountabilities inside one Scrum Team: Product Owner, Scrum Master and Developers.

Product Owner - accountable for maximizing the value of the product. A single person, not a committee; the PO may delegate work but never accountability. The PO develops and communicates the Product Goal, orders the Product Backlog, and ensures it is transparent, visible and understood.

Scrum Master - accountable for the Scrum Team's effectiveness. A true leader who serves: coaching self-management and cross-functionality, causing impediments to be removed, ensuring the events are positive, productive and within timebox, and helping the wider organization understand Scrum. The SM has no authority to make product decisions and is not a people manager.

Developers - the people committed to creating any aspect of a usable Increment each Sprint. They are self-managing (deciding who does what, when and how) and cross-functional, own the Definition of Done, estimate, and hold each other accountable.

Traps

  • Casting the Scrum Master as team lead, project manager or administrator - the SM has accountability for effectiveness, not for delivery.
  • Making the PO a committee, or a proxy who cannot actually order the backlog.
  • Reading "Developers" as "programmers only" - testers, designers and analysts are Developers too.
  • Assuming the SM owns product value or the team's results.

Rule of thumb

PO owns what and why; Developers own how and how much; SM owns how well the team works together. If a scenario asks "who is accountable?", map it to these three verbs.

Scrum Events

The Sprint as a container

All other events happen inside the Sprint, which is fixed at one month or less and of consistent length. A Sprint may only be cancelled by the Product Owner, and only when the Sprint Goal becomes obsolete - it is a rare, expensive act, not a routine management response to scope change.

The four inside events

  • Sprint Planning addresses three topics: why (Sprint Goal), what (items selected), how (the plan).
  • Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is not a status report upward.
  • Sprint Review inspects the outcome with stakeholders and adapts the Product Backlog. It is a working session, not a gate, sign-off or pure demo.
  • Sprint Retrospective inspects how the last Sprint went regarding individuals, interactions, processes, tools and the Definition of Done, and identifies the most helpful changes.

Timeboxes

For a one-month Sprint: Planning ≤ 8 hours, Review ≤ 4 hours, Retrospective ≤ 3 hours. Shorten proportionally for shorter Sprints.

Traps

  • Inventing "backlog refinement" as a fifth formal event - it is an ongoing activity, typically up to 10% of capacity.
  • Treating the Daily Scrum as a report to the Scrum Master.
  • Retrospectives that produce actions with no owner and no follow-through.
  • Confusing the Sprint Review's purpose (inspect outcome, adapt backlog) with stakeholder approval.

Worked example

A two-week Sprint halves the one-month timeboxes: Planning up to 4 hours, Review up to 2 hours, Retrospective up to 1.5 hours. Scale proportionally; never scale upward.

Scrum Artifacts and Commitments

Three artifacts, each with a commitment

Each artifact carries a commitment that reinforces transparency and focus.

Product Backlog → Product Goal. The backlog is an emergent, ordered list of what is needed to improve the product. The Product Goal is the long-term objective the team plans against; there is one at a time, and it lives in the backlog.

Sprint Backlog → Sprint Goal. The Sprint Backlog is composed of the Sprint Goal (why), the selected items (what) and the plan for delivering them (how). The Sprint Goal is a single objective - a coherent purpose, not a list of tickets - and it gives the team flexibility on how while holding the why fixed.

Increment → Definition of Done. An Increment is a concrete stepping stone toward the Product Goal, additive to previous increments. Multiple increments may be created within one Sprint. The Definition of Done is the formal description of the quality state required; the moment an item meets it, an Increment is born.

Traps

  • Confusing the Definition of Done with acceptance criteria: acceptance criteria are per-item and product-specific; the DoD is the team-wide (or organizational) quality bar.
  • Writing the Sprint Goal as a list of backlog items - it must be one objective.
  • Assuming only one Increment per Sprint, or that unfinished work counts toward it.
  • Treating the Product Goal as a per-Sprint target; it spans many Sprints.

Rule of thumb

If it does not meet the Definition of Done, it is not part of the Increment - it returns to the Product Backlog and is reconsidered. Never report partially done work as delivered.

Coaching and Facilitation

Coaching stance

The Scrum Master coaches the team, the Product Owner and the organization. Coaching means asking rather than telling: listening fully, asking open questions, and holding back your own answer so the group builds capability. Useful questions: What have you tried? What did you expect? What would good look like? What is one thing you could change next Sprint? The goal is durable capability, not compliance with your preferred solution.

Facilitation

Facilitation is designing and guiding the process so the group owns the content. Strong facilitation has a clear purpose, a visible agenda, and techniques that prevent the loudest voice from dominating: silent writing before discussion, round-robins, dot voting or fist-of-five for consent, a parking lot for out-of-scope items, and timeboxed turns. Retrospective formats are tools, not rituals - Start/Stop/Continue, the 4Ls and the sailboat each surface different data. Rotate deliberately.

Traps

  • Equating facilitation with deciding: a neutral facilitator does not push content, but is firm about process.
  • Jumping in with a solution when the team stalls - that trains the team to stall.
  • Running the same retrospective format every time and wondering why the data is flat.
  • Confusing coaching with mentoring or advice-giving, or using coaching questions as a technique to steer someone to a predetermined answer.
  • Ignoring the silent participant; psychological safety is a facilitation responsibility.

Worked example

A team says, "our Sprint Reviews are useless." Do not redesign the review for them. Ask what they hoped to get from it, what actually happens, who attends, and what one change they could test for two Sprints - then support the experiment.

Servant Leadership and Team Development

Serving first

Servant leadership inverts the traditional hierarchy of attention: the Scrum Master's job is to remove impediments, build capability, protect focus and create psychological safety so the team can self-manage. Crucially, servant leadership is not passivity. You still hold the boundary of Scrum, give direct feedback when behaviour undermines the team, and let the team experience the consequences of its choices.

Stages of team development

Tuckman's model is a practical map: forming (polite, dependent, needs direction), storming (conflict over roles and ways of working - normal, not a failure), norming (agreements solidify), performing (self-managing, high trust), and adjourning. Situational leadership complements it: directing, coaching, supporting, delegating as capability rises. Motivation theory (autonomy, mastery, purpose) explains why removing control often increases output.

Traps

  • Treating storming as a defect to be suppressed; unaddressed conflict resurfaces later as disengagement.
  • Shielding the team from all organizational friction - teams need to learn to negotiate with their environment.
  • Using "servant leadership" to avoid hard conversations; that is abdication.
  • Assuming a quiet team is a high-performing team.
  • Applying the same leadership stance regardless of the team's stage.

Rule of thumb

Match your stance to the stage: be more directive while forming and storming, more coaching and delegating once norming and performing. If a team cannot describe its own working agreements, it is not yet performing.

Product Delivery and Value Maximization

Value is an outcome, not an output

Value is realized when a customer or stakeholder outcome changes - not when a feature ships. The Product Owner orders the backlog to maximize value, but ordering is a hypothesis that must be tested. Slice work small so feedback arrives early and cheaply. A Minimum Viable Product is the smallest thing that tests a hypothesis about value, not a small first release of the full feature set.

Flow and delivery metrics

Lead time (request to delivery), cycle time (start to finish), throughput and WIP are the practical levers. Little's Law tells you that reducing work in progress reduces cycle time - often faster than adding capacity. Velocity is a planning aid for a single team; it is not a productivity measure and must never be compared across teams. Story points are relative estimates, not units of value.

Evidence-Based Management

EBM guides decisions with four Key Value Areas: current value, time to market, ability to innovate, and unrealized value. Measure outcomes, not activity. Technical debt is a delivery risk that compounds; paying it down early is value maximization, not overhead.

Traps

  • Equating more story points or more features with more value.
  • Comparing velocity between teams or treating it as a performance target.
  • Defining the MVP as "phase one" of a planned build-out.
  • Postponing technical debt until it becomes a delivery wall.

Rule of thumb

When delivery feels slow, cut WIP and slice smaller before adding people. More capacity on a congested system mostly increases queue length.

Organizational Agility and Scaling

Change the system, not the people

Most impediments a team faces live outside the team: funding and budgeting models, policy, procurement, architecture, dependencies, HR rules, reporting demands. The Scrum Master works at the organizational boundary - making these visible, teaching the cost they impose, and influencing their removal. If the system rewards utilization and output, no amount of team-level coaching will produce agility.

Scaling

Scrum is deliberately designed for one team. Scaling frameworks (Nexus, LeSS, SAFe, Scrum@Scale) are pattern libraries, not requirements, and none of them substitutes for solving the underlying problem: cross-team dependency. The primary scaling moves are aligning many teams on one Product Goal, keeping one Product Backlog per product where possible, and re-architecting the work so teams can deliver independently. Coordination roles and ceremony layers often hide dependencies rather than remove them.

Traps

  • Treating an agile transformation as a rollout plan with a fixed end date and a communications calendar.
  • Copying another organization's framework wholesale without diagnosing your own constraints.
  • Assuming adopting a scaling framework makes an organization agile.
  • Confining the Scrum Master to team level and ignoring organizational impediments.
  • Accepting PMO reporting requirements as immutable rather than negotiating their purpose.

Rule of thumb

De-scale before you scale. Map the dependencies between teams; every dependency you eliminate is worth more than any coordination meeting you add. Start by asking what the dependency costs and who could own the decision locally.

SMP cheat sheet

Quick reference

Scrum Theory and Principles

  • Scrum is founded on empiricism: knowledge comes from experience and decisions are based on observation of the actual work.

  • Three empirical pillars: transparency, inspection and adaptation; all three must be present for empirical process control to work.

  • Transparency requires a shared standard so that inspectors and stakeholders interpret artifacts the same way.

  • Inspection must be frequent enough to detect deviation but not so frequent that it interferes with the work itself.

  • Adaptation should happen as soon as possible; if any aspect of the process or artifacts falls outside acceptable limits, adjust it.

  • Five Scrum values: commitment, focus, openness, respect and courage; they guide behavior and build trust.

  • Lean thinking in Scrum: eliminate waste, focus on essentials, respect people and deliver value continuously.

  • Iterative and incremental delivery maximizes feedback opportunities and reduces risk before large investments are made.

  • Decision rule: when a deviation is found during inspection, adapt the process or artifact rather than accepting the deviation.

Quick reference

Scrum Roles and Accountabilities

  • Scrum defines three accountabilities: Product Owner, Scrum Master and Developers; there are no sub-teams or hierarchies.

  • Product Owner is accountable for maximizing product value and for effective Product Backlog management, including ordering.

  • Scrum Master is accountable for the Scrum Team's effectiveness, coaching the team and organization and removing impediments.

  • Developers are accountable for creating a usable Increment each Sprint and decide internally who does what, when and how.

  • The Product Owner is one person, never a committee; work may be delegated but accountability remains with the Product Owner.

  • Scrum Master is a true leader who serves the Scrum Team and the wider organization rather than a project manager or task assigner.

  • Decision rule: the Product Owner orders the Product Backlog; the Developers determine how much work enters the Sprint Backlog.

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

Quick reference

Scrum Events

  • Five events: Sprint (the container), Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective.

  • A Sprint is fixed length, one month or less, and a new Sprint starts immediately after the previous Sprint ends.

  • Sprint Planning addresses three topics: why the Sprint is valuable (Sprint Goal), what can be done, and how the work will be done.

  • Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog.

  • Sprint Review inspects the outcome of the Sprint and determines future adaptations; timebox up to four hours for a one-month Sprint.

  • Sprint Retrospective plans ways to increase quality and effectiveness; timebox up to three hours for a one-month Sprint.

  • Sprint Planning timebox is up to eight hours for a one-month Sprint; shorter Sprints reduce the timeboxes proportionally.

  • Events create regularity and minimize the need for meetings not defined in Scrum.

  • Decision rule: if the Sprint Goal becomes obsolete, the Product Owner may cancel the Sprint; otherwise the Sprint runs to its timebox.

Quick reference

Scrum Artifacts and Commitments

  • Three artifacts: Product Backlog, Sprint Backlog and Increment; each artifact has one commitment attached to it.

  • Product Backlog commitment is the Product Goal: a long-term target for the Scrum Team, with only one active at a time.

  • Sprint Backlog commitment is the Sprint Goal: a single objective that provides focus and guides the Developers' work.

  • Increment commitment is the Definition of Done: a formal description of quality the Increment must meet.

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

  • Sprint Backlog is composed of the Sprint Goal, selected Product Backlog items and a plan for delivering the Increment.

  • An Increment is a concrete, usable stepping stone toward the Product Goal; it must be usable to provide value.

  • Decision rule: if an item does not meet the Definition of Done, it is not part of the Increment and cannot be released.

  • If the organizational Definition of Done is a minimum standard, teams may add stricter criteria but may not relax it.

Quick reference

Coaching and Facilitation

  • Coaching stance: ask before telling; questions raise self-awareness and ownership more reliably than instructions.

  • Facilitation means designing and guiding group processes to reach a defined outcome while staying neutral on content.

  • Decision rule: facilitate when the group can solve the problem; teach or mentor when a skill gap exists; coach for personal growth.

  • Powerful questions are open, concise and invite reflection; leading or yes/no questions reduce ownership.

  • Psychological safety is a precondition for honest inspection; facilitation should protect equal voice and dissent.

  • Retrospective facilitation typically moves through data gathering, insight generation and decision on actions.

  • Conflict handling: address behavior and interests rather than personalities, using structured formats to depersonalize.

  • Distinguish impediments the team can remove itself from those needing organizational action and escalation.

Quick reference

Servant Leadership and Team Development

  • Servant leadership prioritizes the growth, needs and effectiveness of others; the leader removes impediments rather than directing work.

  • Tuckman stages: forming, storming, norming, performing, with adjourning when a team disbands.

  • Situational leadership: match direction and support to the person's competence and commitment for the specific task.

  • Psychological safety, the shared belief that speaking up is safe, predicts learning behavior and team performance.

  • Self-managing teams require clear goals, explicit boundaries and real decision authority to function.

  • Decision rule: give more structure and direction to new teams and more autonomy as capability and trust grow.

  • Delegation rule: delegate when competence and commitment are high; increase direction or support when either is low.

  • Protect the team from interruptions while ensuring it still receives direct stakeholder feedback.

Quick reference

Product Delivery and Value Maximization

  • Value is realized when Increments are released and used; delivered value is an outcome, not a count of completed items.

  • Little's Law: average cycle time equals work in progress divided by throughput; limiting WIP shortens cycle time if throughput holds.

  • Flow metrics to monitor: cycle time, throughput and work in progress; rising WIP predicts longer delivery times.

  • Cost of delay expresses the economic impact of late delivery and supports ordering the Product Backlog by value.

  • The Sprint Goal should express a single valuable outcome rather than a list of separate tasks.

  • Work that does not meet the Definition of Done is undone work and accumulates as debt, reducing transparency.

  • Decision rule: an Increment may be released only when it meets the Definition of Done; release frequency is a business decision.

  • The Product Owner orders the Product Backlog using value, risk, dependencies and cost of delay as criteria.

Quick reference

Organizational Agility and Scaling

  • Scrum is a framework for a single Scrum Team; scaling frameworks add coordination practices but are not Scrum itself.

  • Nexus applies to three to nine Scrum Teams working on one product, with a Nexus Integration Team addressing cross-team integration.

  • Dependencies between teams are the primary scaling constraint; they must be made visible and minimized.

  • Decision rule: scale only when a single team cannot deliver the product; extra teams add coordination cost and dependencies.

  • When several teams build one product, they share one Product Backlog, one Product Owner and one Product Goal.

  • Structure the organization around products and value streams rather than functional handoffs to reduce coordination overhead.

  • Empirical process control at scale requires integration, a shared Definition of Done and a single integrated Increment.

  • Agile transformation is a change in operating model and leadership behavior, not a process rollout or tool installation.

SMP key terms

Empiricism

The belief that knowledge comes from experience and from decisions based on what is observed. Scrum relies on short cycles of doing and checking so teams learn and adjust instead of predicting everything up front.

Related: Transparency, Inspection, Adaptation
Transparency

A state in which the process, its work, and the results are visible to the people who manage and inspect them. It requires an honest shared view of reality and a common understanding of what done means.

Related: Inspection, Empiricism
Inspection

The frequent, careful examination of Scrum artifacts and progress toward agreed goals. It is done by skilled people against a clear standard so problems and deviations are detected early enough to be useful.

Related: Adaptation, Transparency
Adaptation

Adjusting the process, product, or plan based on what inspection reveals. Without adaptation inspection has no value, so Scrum builds opportunities to correct course into every event.

Related: Inspection, Empiricism
Lean thinking

A way of working that maximizes customer value while minimizing waste. It favors small batches, flow, continuous improvement, and respect for people, and underpins Scrum's emphasis on removing unnecessary work.

Related: Empiricism, Scrum Values
Scrum Values

Five qualities, namely commitment, focus, openness, respect, and courage, that guide behavior in Scrum. When lived consistently they build the trust that transparency and self-management depend on.

Related: Transparency, Self-management
Self-management

The Scrum Team's authority to decide internally how to do its work and who does what. Rather than a manager assigning tasks, the team organizes itself around the goal within agreed boundaries.

Related: Scrum Values, Developers
Scrum Master

An accountability for establishing Scrum as described in the Scrum Guide and for the team's effectiveness. The Scrum Master serves the team, the Product Owner, and the organization through coaching, teaching, and removing impediments.

Related: Servant leadership, Impediment, Coaching
Product Owner

An accountability for maximizing product value by managing the Product Backlog. The Product Owner clarifies items, orders them, and keeps the team's work aligned with the Product Goal and stakeholder needs.

Related: Product Goal, Product Backlog
Developers

The people in the Scrum Team accountable for creating any aspect of a usable Increment each Sprint. They self-manage, own the Sprint Backlog, and hold the technical and quality standards of the work.

Related: Self-management, Sprint Backlog
Product Backlog

An emergent, ordered list of what is needed to improve the product and the single source of work for the Scrum Team. It is never complete, and its ordering reflects value, risk, and dependency.

Related: Product Goal, Backlog refinement
Sprint Backlog

The set of Product Backlog items selected for a Sprint together with the plan for delivering them. It is a living, team-owned view of the work that is updated as the team learns.

Related: Sprint Goal, Sprint Planning
Increment

A concrete, usable step toward the Product Goal produced during a Sprint. Each Increment adds to all previous ones, is verified against the Definition of Done, and must be usable even before the Sprint ends.

Related: Definition of Done, Sprint
Product Goal

A long-term, measurable objective describing the future state of the product that the Scrum Team is working toward. It gives the Product Backlog its direction and is the commitment attached to that artifact.

Related: Product Backlog, Increment
Sprint Goal

A single coherent objective for the Sprint that gives the team both focus and flexibility. It is agreed during Sprint Planning and is the commitment attached to the Sprint Backlog.

Related: Sprint Backlog, Sprint Planning
Definition of Done

A shared, explicit checklist of quality standards that an Increment must meet to be considered complete. It creates transparency, prevents partial work from being called done, and is the commitment for the Increment.

Related: Increment, Transparency
Sprint

A fixed-length period of one month or less in which the Scrum Team turns backlog items into a usable Increment. Every other Scrum event happens inside it, and a new Sprint starts immediately after.

Related: Sprint Planning, Timebox
Sprint Planning

The event that opens a Sprint, where the team agrees why the Sprint is valuable, what can be done, and how. It produces the Sprint Goal and Sprint Backlog and is timeboxed to eight hours or less.

Related: Sprint Goal, Sprint Backlog
Daily Scrum

A fifteen-minute event each working day where the Developers inspect progress toward the Sprint Goal and adapt their plan. It improves communication and removes the need for other status meetings.

Related: Sprint Goal, Self-management
Sprint Review

The second-to-last event of a Sprint, where the team and stakeholders inspect the Increment and adapt the Product Backlog. It is a working session rather than a formal presentation and is timeboxed to four hours.

Related: Increment, Sprint Retrospective
Sprint Retrospective

The closing event of a Sprint, where the team inspects how it worked together and identifies the most useful improvements. Chosen actions may be added to the next Sprint Backlog, and the timebox is three hours.

Related: Psychological safety, Impediment
Timebox

A maximum amount of time allotted to a Scrum event or activity. Rather than stretching the event to fit the work, the team adjusts the scope of its discussion so the event stays focused.

Related: Sprint Planning, Daily Scrum
Sprint cancellation

Ending a Sprint before its timebox expires because the Sprint Goal has become obsolete. Only the Product Owner can cancel, and the team then reviews and adapts whatever work was completed.

Related: Sprint Goal, Product Owner
Backlog refinement

The ongoing activity of breaking down and clarifying Product Backlog items so they are small and understood well enough for a future Sprint. It is a continuous conversation rather than a formal event.

Related: Product Backlog, Product Owner
Coaching

Partnering with people so they find their own answers, build capability, and reach goals they define themselves. A coach asks more than tells, holds the client's agenda, and supports lasting behavior change.

Related: Powerful questions, Active listening
Powerful questions

Open, short questions that invite reflection and new thinking rather than justify an existing position. They are a core coaching and facilitation tool for raising awareness and prompting the speaker's own insight.

Related: Coaching, Active listening
Active listening

Fully attending to a speaker in order to understand both content and feeling, then confirming that understanding through paraphrasing and open questions. It builds trust and surfaces information a distracted listener would miss.

Related: Coaching, Psychological safety
Facilitation

Designing and guiding a group process so participants can reach their own outcomes efficiently. The facilitator manages the how, such as agenda, format, and participation, while leaving content and decisions to the group.

Related: Powerful questions, Psychological safety
Psychological safety

A shared belief that people can speak up, admit mistakes, ask questions, and disagree without punishment. It is a precondition for transparency, learning, and the honest retrospectives Scrum depends on.

Related: Sprint Retrospective, Conflict navigation
Servant leadership

Leading by focusing on the needs and growth of others rather than on status or control. The leader removes obstacles, shares power, and creates conditions in which the team can succeed on its own.

Related: Scrum Master, Impediment
Impediment

A blocker or obstacle outside the team's ability to resolve that slows progress toward its goals. The Scrum Master helps the team identify, escalate, and eliminate such impediments.

Related: Scrum Master, Servant leadership
Team development stages

The forming, storming, norming, and performing sequence first described by Tuckman. Knowing these stages helps a Scrum Master choose the right support, from direction early on to coaching and delegation later.

Related: Coaching, Psychological safety
Conflict navigation

Helping people address disagreement directly and constructively instead of avoiding or escalating it. The aim is a workable decision and a preserved working relationship, not a winner and a loser.

Related: Psychological safety, Facilitation
Value

The worth a product delivers to customers and to the organization, judged by outcomes rather than by output. Scrum orders work by value and inspects it so the most valuable things are done first.

Related: Evidence-Based Management, Product Goal
Evidence-Based Management

An approach to steering toward goals using four key value areas: current value, unrealized value, time to market, and ability to innovate. It keeps decisions grounded in evidence rather than opinion.

Related: Value, Product Goal
Technical debt

The future cost of shortcuts taken in design or code that make later change harder. Making it visible helps the team and Product Owner trade short-term speed against long-term value delivery.

Related: Definition of Done, Increment
Organizational agility

An organization's capacity to sense change and respond by adjusting strategy, structure, and work. Scrum teams contribute by delivering value iteratively and by surfacing system-level impediments for leadership to remove.

Related: Scaling, Impediment
Scaling

Applying Scrum across several teams working on one product, adding coordination while keeping each team's Scrum intact. Frameworks such as Nexus or LeSS differ mainly in how much extra coordinating structure they introduce.

Related: Organizational agility, Product Goal

SMP study plan

8 weeks · About 8 hours per week

Week 1

Scrum Theory and Principles

  • Explain empiricism and the three pillars (transparency, inspection, adaptation) aloud from memory without notes

  • State each of the five Scrum values and give one observable behavior that demonstrates it in a team

  • Distinguish what Scrum prescribes as rules versus what it leaves open as choices, using the purpose of Scrum as the justification

  • Rewrite five common misconceptions about Scrum into accurate statements and explain why each original claim is wrong

Your checkpoint

A one-page empiricism and values reference sheet covering all five misconceptions, plus a score of at least 8/10 on a self-written 10-question Domain 1 quiz.

Week 2

Scrum Roles and Accountabilities

  • Map each of the three accountabilities to its distinct responsibilities, decision rights, and the artifact commitment it serves

  • Contrast the three Scrum accountabilities with traditional manager, analyst, and team-lead roles on authority and accountability

  • Justify from Scrum theory why no accountability may be merged or delegated away

  • Identify five role-confusion anti-patterns and prescribe a concrete corrective action for each

Your checkpoint

A role matrix (3 accountabilities x responsibilities x decision rights x owned commitment) plus 15 self-authored flashcards scored at 80% or better on two consecutive passes.

Week 3

Scrum Events

  • Reconstruct all five events from memory, stating purpose, timebox, participants, inputs, and outputs for each

  • Explain how each event creates an opportunity for inspection and adaptation rather than serving as a status meeting

  • Compare Sprint Review and Sprint Retrospective on purpose, participants, and outcome produced

  • Defend the Daily Scrum's structure and explain why it serves the Developers rather than managers

  • Diagnose three event anti-patterns (for example a cancelled retrospective or a review with no stakeholder feedback) and propose a fix for each

Your checkpoint

An events reference table filled in from memory first, then corrected, that is 100% accurate on all five timeboxes, plus 10 practice questions answered at 80% or above.

Week 4

Coaching and Facilitation

  • Select the appropriate stance (teaching, coaching, mentoring, facilitating, or advising) for eight given team situations and justify each choice

  • Design a 45-minute retrospective with a stated purpose, sequenced activities, and explicit timeboxes

  • Convert ten closed or leading questions into neutral open questions that invite the team's own answer

  • Distinguish facilitation from training and from consulting when a team is stuck

  • Write and rehearse an intervention plan for a participant who repeatedly dominates a team session

Your checkpoint

One facilitated session (live or recorded role-play) plus a written self-assessment against a six-point facilitation checklist, with at least one concrete improvement identified.

Week 5

Scrum Artifacts and Commitments

  • Pair each of the three artifacts with its commitment and explain what transparency each commitment creates

  • Apply a Definition of Done to four increment scenarios and judge whether the increment is releasable

  • Explain the purpose of Product Backlog refinement and how it fits within the Sprint rather than replacing an event

  • Diagnose three artifact anti-patterns (vague Definition of Done, Sprint Backlog used as an assignment list, Product Backlog treated as a wish list) and give a remedy for each

  • Explain how an unclear commitment degrades inspection and adaptation downstream

Your checkpoint

A one-page artifact-to-commitment map plus a rewritten Definition of Done for a sample product, scored against five transparency quality criteria.

Week 6

Servant Leadership and Team Development

  • Contrast servant-leadership behaviors with command-and-control behaviors across six concrete team scenarios

  • Apply a team-development stage model to a described team and select an intervention appropriate to its current stage

  • Design one team-development activity aimed specifically at building psychological safety

  • Explain how a Scrum Master removes impediments without taking ownership away from the team

  • Coach a struggling Developer through a self-management conversation in a role-play, keeping the solution with the team

Your checkpoint

A written three-sprint team-development plan with one targeted intervention per stage and a reflection on the coaching role-play noting where you slipped into directing.

Week 7

Product Delivery and Value Maximization & Organizational Agility and Scaling

  • Trace value from Product Goal to Sprint Goal to Increment, naming which events create the feedback that keeps the path valid

  • Order a ten-item backlog by value, risk, and effort, and defend the ordering in writing

  • Compare output measures with outcome measures and propose three outcome metrics for a sample product

  • Identify four organizational impediments to agility and write a removal strategy and stakeholder for each

  • Evaluate when a scaling approach reduces dependency waste and when it adds coordination overhead instead

Your checkpoint

A one-page value-delivery case write-up containing a justified backlog ordering, three outcome metrics with baselines, and a scaling recommendation with rationale.

Week 8

Scrum Theory and Principles & Scrum Roles and Accountabilities & Scrum Events & Scrum Artifacts and Commitments & Coaching and Facilitation & Servant Leadership and Team Development & Product Delivery and Value Maximization & Organizational Agility and Scaling

  • Complete a full-length timed practice exam and score 85% or higher

  • Re-teach your three weakest domains in a short recorded explainer each, without notes

  • Reconstruct the timeboxes, commitments, and accountabilities on a single recall sheet from memory

  • Revisit every question missed in weeks 1 through 7, confirm the root cause, and verify it no longer recurs

Your checkpoint

A full-length practice exam scored at 85% or above plus a completed error log with zero unresolved root causes.

Milestones

Week 2: Recite the three pillars, five values, and three accountabilities with their decision rights from memory in under five minutes with no factual errors.

Week 4: Score 80% or higher on a 30-question cumulative check covering domains 1, 2, 3, and 5, and log a root cause for every miss.

Week 6: Score 80% or higher on a 25-question check covering domains 4 and 6, and correctly pair all three artifacts with their commitments without notes.

Week 8: Score 85% or higher on a full-length timed practice exam and demonstrate that no error from weeks 1 through 7 repeats.

SMP exam day

Your checklist

Government-issued photo ID

Bring the original physical ID (not a photocopy or a photo on your phone). The name must match your registration exactly. Confirm the accepted ID forms and any secondary-ID requirement with the exam provider before test day.

Appointment confirmation / authorization to test

Have your confirmation number, candidate ID, and the appointment time available. Confirm with the provider whether a printed copy is required or a digital copy on your phone is acceptable.

Login credentials for the test platform

If you are testing online with remote proctoring, verify your username and password work at least 48 hours ahead, and keep them somewhere you can reach without unlocking a phone during check-in.

Completed system and equipment check

For remote delivery, run the provider's compatibility test on the same computer, webcam, microphone, and network you will use on test day. Confirm minimum bandwidth and browser requirements with the provider.

Quiet, private, well-lit room (remote delivery)

Use a closed room with a door, a clear desk, and no other people. Position the camera so the proctor can see your face, hands, desk surface, and the door. Confirm the provider's room and 360-degree scan requirements.

Clear desk and cleared surroundings

Remove notes, books, sticky notes, second screens, phones, smart watches, and any paper you were not explicitly authorized to have. Stow personal items where the provider requires.

Approved aids confirmed in advance

Find out ahead of time whether a calculator, scratch paper, pen, or formula sheet is permitted, and whether the platform supplies an on-screen version. Do not assume any of these are allowed.

Testing center logistics settled

If testing in person, confirm the address, entrance, parking or transit plan, and the check-in window. Do a route check the day before so arrival timing is not guesswork.

Arrival time confirmed

Ask the provider how early you must arrive or check in, and what happens if you are late. Late-arrival and forfeiture policies vary, so confirm rather than guess.

Break provisions planned

Confirm whether breaks are scheduled or on request, whether the clock keeps running, and what you may access during a break. Plan hydration and a snack around those rules.

Candidate handbook or exam policy read

Read the provider's current handbook section on conduct, ID, breaks, technical issues, and scoring so nothing on test day is a surprise.

Backup plan for disruptions

Have a phone number for the testing center or provider support, a backup internet option if testing remotely, and a backup route if traveling to a site.

Plan the day

72 hours before

Reconfirm your appointment date, time, delivery method, and location. Re-run the system test if testing remotely. Read the provider's exam-day policy page once, carefully, and note anything you need to ask about.

72 hours before

Switch from learning new material to consolidation: review your own summary notes, error log, and the two or three topics you most often get wrong. Stop adding new resources.

48 hours before

Do one timed practice set under realistic conditions, then review only what you got wrong. Do not chase a score target; use it to tune pacing.

24 hours before

Lay out your ID, confirmation, and any approved items. Confirm travel time or workspace setup. Check the provider's site for any last-minute changes. Stop studying by early evening.

24 hours before

Protect sleep. Avoid a late-night review session; a rested recall beats an extra hour of cramming.

Morning of

Eat a normal meal, hydrate, and dress in layers. Leave buffer time so a delay does not become a crisis. Skip last-minute cramming of new topics; if you review anything, skim your own one-page summary.

At check-in

Arrive or log in at the time the provider specifies. Have your ID ready, follow the proctor's instructions exactly, and ask before doing anything you are unsure about.

During the test

Read the instructions and note the number of questions and the time limit before starting. Write down your time checkpoints so you know your pace.

During the test

Answer in passes: do the straightforward items first, flag anything long or uncertain, and return to flagged items with the time remaining. Never leave a question blank if the format has no penalty for guessing; confirm the scoring rule first.

During the test

Use scheduled breaks if offered, but check whether the clock runs during them. Stand, stretch, and reset attention.

Final minutes

Reserve the last few minutes to confirm every flagged item has an answer and that you have not accidentally skipped a section. Submit deliberately.

After the test

Note what you would do differently while it is fresh. If your result is not immediate, confirm with the provider how and when it will be reported.

Rules to check

  • Bring valid government-issued photo ID with a name matching your registration exactly. Confirm the accepted ID forms and any name-discrepancy procedure with the provider before test day.

  • Do not bring unauthorized materials into the testing area. Phones, smart watches, notes, and second screens are normally prohibited; confirm where to store personal items.

  • Follow all proctor instructions. During a remotely proctored exam, stay in camera view, do not talk to others, and do not leave the room without permission. Confirm the provider's specific rules.

  • Break policy, including whether the timer pauses, varies by provider and delivery method. Ask in advance rather than assuming.

  • If equipment fails or the session drops, stop and contact the proctor or provider support immediately. Do not attempt to restart or troubleshoot the exam on your own; confirm the provider's technical-issue and incident-reporting procedure.

  • Scoring, pass standards, and score reporting timelines are set by the provider. Do not rely on secondhand claims about a pass mark or question count; confirm current details from official material.

  • Exam content is confidential. Do not copy, record, or discuss specific questions after the exam; doing so can invalidate your result.

  • Misconduct, prohibited items, or ID problems can result in removal or score cancellation. If anything is unclear at check-in, ask the proctor before you begin.

SMP FAQ

How many SMP practice questions are available?

The practice set has 198 SMP questions. Each one includes the choices, the correct answer, and an explanation, and the set is free to read with no signup.

How many SMP flashcards are available?

The flashcard set has 32 SMP cards. Each card shows the term and its definition.

Which topics does the SMP study material cover?

The SMP study material has 8 sections, including Scrum Theory and Principles, Scrum Roles and Accountabilities, and Scrum Events.

What format facts does the catalog list for the SMP exam?

The catalog lists these item types: multiple choice for the SMP exam.