PSM I overview

  • 196 practice questions
  • 32 flashcards
  • 4 study guide topics
  • 37 key terms

What you'll study

  • Scrum Framework and Theory25%
  • Scrum Roles and Accountabilities25%
  • Scrum Events and Artifacts25%
  • Scrum Master Accountabilities and Professional Scrum25%

The Professional Scrum Master (PSM) credential is part of the Professional Scrum Master assessment family offered by Scrum.org, described on its site as covering "Fundamental, advanced & distinguished levels of Scrum Master knowledge in levels I, II & III." The PSM I entry point is aimed at anyone accountable for, or working alongside, a Scrum Master: practising Scrum Masters, team members, Product Owners, managers and coaches who want to demonstrate that they understand Scrum as written in the Scrum Guide rather than as adapted folklore. Expect questions that test the framework's theory and the reasoning behind it - empiricism, the Scrum Values, the accountabilities within the Scrum Team, the events and their purposes, the artifacts and their commitments, and how a Scrum Master serves the team and the wider organisation. Because Scrum.org presents its certifications as tests that "do not require renewal," preparation is best treated as a one-off investment in understanding rather than exam technique. Study order that works: read the Scrum Guide end to end twice, then work the free Scrum Open practice assessment until you can explain every wrong answer, then re-read the Guide with your notes. The assessment is multiple choice. Scrum.org publishes its own course and resource pages; this page is independent study material and is not affiliated with or endorsed by Scrum.org.

Common mistakes

Treating the Scrum Master as the person who assigns tasks, runs standups as a status meeting, or owns the Sprint Backlog and tells the Developers what to do.

Candidates carry over command-and-control habits from traditional project management and map 'Scrum Master' onto 'team lead' or 'project manager' from their own workplace experience.

What to do instead

Memorise the Scrum Master's accountabilities verbatim from the Scrum Guide: coaching the team in self-management and cross-functionality, removing impediments, causing the removal of barriers between stakeholders and the team, and ensuring Scrum events are positive, productive, and timeboxed. The Developers own the Sprint Backlog; the Product Owner owns the Product Backlog. Practise classifying each activity as 'Scrum Master does' vs 'Scrum Master causes to happen'.

Assigning the Product Owner sole authority to estimate, or conversely giving the Developers authority to change the Product Backlog order, and mixing up who owns which artifact.

The three artifacts and their owners are superficially similar and candidates conflate 'managing the work' with 'owning the artifact'.

What to do instead

Lock in the ownership table: Product Goal and Product Backlog order belong to the Product Owner; Sprint Goal, Sprint Backlog and estimates belong to the Developers; the Definition of Done is created by the organisation or, if none exists, by the Developers. Drill by writing each artifact and its single accountable owner until recall is automatic.

Describing the Sprint Review as a sign-off, gate, or demo to management, and describing the Sprint Retrospective as a general team meeting where work items are planned.

Candidates map Scrum events onto familiar phase-gate reviews and status meetings rather than reading the stated purpose of each event.

What to do instead

Learn each event's purpose sentence by sentence: the Review inspects the outcome of the Sprint and determines future adaptations, and is a working session with stakeholders, not a gate; the Retrospective plans ways to increase quality and effectiveness. For each event, be able to state its purpose, its timebox, who attends, and its inputs and outputs.

Treating the Daily Scrum as a report to the Scrum Master or Product Owner with the three classic questions, and treating it as mandatory for the whole team to answer to someone.

The three-question format is widely circulated in secondary material and predates the current Scrum Guide, so candidates default to it.

What to do instead

State that the Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog, that it is owned and run by the Developers, and that its structure and technique are up to them. If the Product Owner or Scrum Master attends, they do so as Developers if they are working on Sprint Backlog items, otherwise they participate only if needed.

Describing the Sprint as cancellable by the Scrum Master or the Developers, or describing cancellation as producing a 'failed Sprint' with partial credit.

Candidates reason from general management intuition about stopping work rather than from the single stated authority in the framework.

What to do instead

Memorise that only the Product Owner can cancel a Sprint, and only when the Sprint Goal becomes obsolete. On cancellation, completed and 'Done' Product Backlog items are reviewed, and anything not Done returns to the Product Backlog for reordering. Rehearse the exact conditions and consequences.

Choosing 'the Scrum Master should tell the Developers to split the work' or 'escalate to the manager' when a question describes a self-management problem, instead of choosing the answer where the team solves it themselves.

Candidates optimise for 'resolving the situation' rather than for 'upholding the framework', and the most decisive-sounding option looks most attractive.

What to do instead

Adopt a decision rule for scenario questions: prefer the answer that keeps accountability with the correct role and lets the team self-manage; reject answers where the Scrum Master or Product Owner makes a decision that belongs to the Developers. When two options both seem reasonable, prefer the one that teaches, coaches, or facilitates over the one that directs.

Reading the Definition of Done as a team-optional checklist that can be relaxed under time pressure, or confusing it with acceptance criteria.

The two concepts are often presented together in study material, and 'Done' feels like a quality nicety rather than a commitment.

What to do instead

Learn that the Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product, that it is a commitment for the Increment, and that if it is not met the work cannot be released and does not count toward the Increment. Distinguish it from acceptance criteria, which are item-specific and belong to the Product Backlog item.

Assuming the Product Owner must attend every event and must be present to answer questions, or that the Scrum Team consists of the Developers plus the Scrum Master only.

Candidates absorb organisational habits where the Product Owner is external or part-time, and never internalise the Scrum Team definition.

What to do instead

Memorise that the Scrum Team is one team of ten or fewer people consisting of one Scrum Master, one Product Owner, and Developers, with no sub-teams or hierarchies, and that the whole team is accountable for creating a valuable Increment each Sprint. Learn event attendance precisely: the Sprint Planning, Daily Scrum, Review, and Retrospective are all Scrum Team events, with the Review and Planning also involving stakeholders as needed.

Answering questions about empiricism by quoting 'transparency, inspection, adaptation' without being able to say what each pillar requires in practice, or naming the wrong artifact for a commitment.

The three pillars and three commitments are memorised as lists without being linked to the artifacts, so they collapse under scenario wording.

What to do instead

Build the paired structure explicitly: Product Backlog carries the Product Goal, Sprint Backlog carries the Sprint Goal, Increment carries the Definition of Done. Then practise explaining, for each pillar, one concrete way Scrum enables it: transparency through the artifacts and Definition of Done, inspection through the five events, adaptation through the Sprint and the events' outputs.

Treating Professional Scrum as a set of soft skills and picking 'do whatever the customer asks' or 'follow the process exactly' when a question probes the balance between empiricism and following prescribed events.

Candidates split 'framework compliance' from 'professional judgement' and assume one must win, so they choose an extreme option.

What to do instead

Frame Professional Scrum as applying the framework faithfully and then using empiricism and self-management within it: the events and accountabilities are non-negotiable, but the techniques, formats, and tools are for the team to choose. In scenario questions, prefer the option that preserves the framework while adapting the practice, and reject options that abandon an event or accountability to please a stakeholder.

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

PSM I practice

196 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 Framework and Theory

    In the Scrum framework, what is the primary purpose of the Daily Scrum?

    1. To refine the Product Backlog for the next Sprint
    2. To inspect progress toward the Sprint Goal and adapt the Sprint Backlog as needed Correct answer.
    3. To demonstrate the completed Increment to stakeholders
    4. To report status to the Product Owner and stakeholders

    Explanation

    The 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 meeting for stakeholders or a backlog refinement session.

  2. Question 2Scrum Framework and Theory

    Who is responsible for maximizing the value of the product resulting from the work of the Scrum Team?

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

    Explanation

    The Product Owner is accountable for maximizing the value of the product and for managing the Product Backlog effectively. The Scrum Master facilitates Scrum, and the Developers create the Increment.

  3. Question 3Scrum Framework and Theory

    What is the recommended timebox for a Sprint Review when the Sprint length is one month?

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

    Explanation

    The Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.

  4. Question 4Scrum Framework and Theory

    Which Scrum artifact is defined as a list of features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future Sprints?

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

    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.

  5. Question 5Scrum Framework and Theory

    What is the maximum duration of a Sprint in Scrum?

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

    Explanation

    Sprints are fixed length and are limited to one month or less to maintain predictability. If a Sprint's horizon is too long, complexity may rise and risk may increase.

  6. Question 6Scrum Framework and Theory

    Which of the following best describes the Scrum Master's role in relation to the Product Owner?

    1. To prioritize the Product Backlog items according to stakeholder demands
    2. To help the Product Owner define and communicate product goals and manage the Product Backlog effectively Correct answer.
    3. To approve the Definition of Done before each Sprint
    4. To manage the Product Backlog on the Product Owner's behalf

    Explanation

    The Scrum Master serves the Product Owner by helping to find techniques for effective Product Goal definition and Product Backlog management. The Scrum Master does not take over the Product Owner's accountabilities.

  7. Question 7Scrum Framework and Theory

    During a Sprint, the Developers realize they have completed all Sprint Backlog items but have not met the Sprint Goal. What should they do?

    1. Continue working on additional Product Backlog items without adjusting the Sprint Goal
    2. End the Sprint early and start a new one
    3. Ask the Product Owner to change the Sprint Goal
    4. Collaborate with the Product Owner to negotiate the scope of the Sprint Backlog Correct answer.

    Explanation

    The Sprint Backlog is emergent and can be adjusted during the Sprint. The Developers and Product Owner may negotiate scope as more is learned, while the Sprint Goal remains fixed unless it becomes obsolete.

  8. Question 8Scrum Framework and Theory

    What is the primary purpose of the Sprint Retrospective?

    1. To update the Definition of Done
    2. To demonstrate the Increment to stakeholders
    3. To review the Product Backlog and plan the next Sprint
    4. To inspect how the last Sprint went and identify improvements Correct answer.

    Explanation

    The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. It focuses on individuals, interactions, processes, tools, and the Definition of Done.

  9. Question 9Scrum Framework and Theory

    Which statement about the Definition of Done is correct?

    1. It is optional and only used if the team decides to adopt it
    2. It is created by the Scrum Master and enforced by the Product Owner
    3. It is a checklist that must be identical for all Scrum Teams in an organization
    4. It is a formal description of the state of the Increment when it meets the quality measures required for the product Correct answer.

    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 is created by the Scrum Team and is used to assess when work is complete.

  10. Question 10Scrum Framework and Theory

    Who is allowed to attend the Daily Scrum?

    1. The Developers and the Scrum Master
    2. Only the Developers Correct answer.
    3. The entire Scrum Team and stakeholders
    4. Anyone who wants to observe

    Explanation

    The Daily Scrum is an internal event for the Developers. If others are present, the Scrum Master ensures that they do not disrupt the meeting.

  11. Question 11Scrum Framework and Theory

    What is the role of the Product Owner in the Sprint Review?

    1. To decide which stakeholders may speak
    2. To explain what Product Backlog items have been Done and what has not Correct answer.
    3. To demonstrate the technical details of the Increment
    4. To facilitate the event and keep time

    Explanation

    The Product Owner discusses the Product Backlog as it stands and explains which items have been Done and which have not. The Scrum Team presents the results of their work.

  12. Question 12Scrum Framework and Theory

    Which of the following is a characteristic of the Sprint Backlog?

    1. It is a forecast by the Developers of the work needed to achieve the Sprint Goal Correct answer.
    2. It contains all Product Backlog items for the entire product
    3. It is a fixed list that cannot be changed during the Sprint
    4. It is owned exclusively by the Product Owner

    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 forecast by the Developers and is updated as more is learned.

  13. Question 13Scrum Framework and Theory

    What does the term 'empiricism' mean in the context of Scrum?

    1. Working in short cycles to deliver value frequently
    2. Following a detailed plan created at the start of the project
    3. Making decisions based on what is known, observed, and demonstrated Correct answer.
    4. Making decisions based on intuition and experience

    Explanation

    Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Scrum employs an iterative, incremental approach to optimize predictability and control risk.

  14. Question 14Scrum Framework and Theory

    A Scrum Team is working on a product with high uncertainty. How should they use the Sprint to manage risk?

    1. Deliver a potentially releasable Increment each Sprint to gather feedback Correct answer.
    2. Create a detailed risk register and review it at every Daily Scrum
    3. Extend the Sprint length to allow more time for analysis
    4. Postpone all releases until the product is fully complete

    Explanation

    Scrum uses short Sprints and frequent delivery of Increments to reduce risk and enable fast feedback. This allows the team to inspect and adapt based on real outcomes.

  15. Question 15Scrum Framework and Theory

    What are the three pillars of empiricism in Scrum?

    1. Inspection, adaptation, and prediction
    2. Collaboration, communication, and commitment
    3. Planning, execution, and review
    4. Transparency, inspection, and adaptation Correct answer.

    Explanation

    Scrum is founded on empiricism, which relies on transparency, inspection, and adaptation. These pillars support the ability to detect and respond to change.

  16. Question 16Scrum Framework and Theory

    Which Scrum event is described as a formal opportunity to inspect and adapt the product?

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

    Explanation

    The Sprint Review is a formal opportunity to inspect the Increment and adapt the Product Backlog. The Retrospective inspects the team's process, not the product.

  17. Question 17Scrum Framework and Theory

    What is the primary responsibility of the Developers during Sprint Planning?

    1. To update the Definition of Done
    2. To create the Product Backlog
    3. To estimate the effort for each Product Backlog item
    4. To decide the Sprint Goal and select Product Backlog items Correct answer.

    Explanation

    During Sprint Planning, the Scrum Team collaborates to define the Sprint Goal and the Developers select the Product Backlog items they can complete. The Product Owner ensures the Product Backlog is ready.

  18. Question 18Scrum Framework and Theory

    Which statement best describes the relationship between the Product Backlog and the Sprint Backlog?

    1. The Sprint Backlog is a subset of the Product Backlog selected for a Sprint Correct answer.
    2. The Product Backlog is a subset of the Sprint Backlog
    3. The Product Backlog and Sprint Backlog are independent and unrelated
    4. The Sprint Backlog contains all items from the Product Backlog

    Explanation

    The Sprint Backlog is composed of the Sprint Goal, the selected Product Backlog items for the Sprint, and the plan for delivering them. It is a subset of the Product Backlog.

  19. Question 19Scrum Framework and Theory

    A Scrum Team has a Product Owner who is also the Scrum Master. What does the Scrum Guide say about this?

    1. It is allowed if the organization approves
    2. It is allowed if the team is small
    3. It is allowed only for a temporary period
    4. It is not allowed because the roles have conflicting accountabilities Correct answer.

    Explanation

    The Scrum Guide states that the Scrum Master and Product Owner are distinct roles, and combining them can create conflicts of interest. The Product Owner focuses on value, while the Scrum Master focuses on process and facilitation.

  20. Question 20Scrum Framework and Theory

    What is the purpose of the Sprint Goal?

    1. To list all the tasks needed to complete the Increment
    2. To provide a single objective for the Sprint that guides the Developers Correct answer.
    3. To provide a fixed scope for the Sprint
    4. To describe the overall product vision

    Explanation

    The Sprint Goal is a single objective for the Sprint that provides focus and flexibility. It is created during Sprint Planning and helps the Developers understand why they are building the Increment.

  21. Question 21Scrum Framework and Theory

    Which of the following is an example of a Scrum artifact?

    1. The Daily Scrum
    2. The Sprint Retrospective
    3. The Increment Correct answer.
    4. The Definition of Done

    Explanation

    The three Scrum artifacts are the Product Backlog, the Sprint Backlog, and the Increment. The Definition of Done is a commitment associated with the Increment, but the Increment itself is the artifact.

  22. Question 22Scrum Framework and Theory

    During a Sprint, a new urgent requirement is discovered. What is the most appropriate action?

    1. Ignore it until the next Sprint
    2. Discuss it with the Product Owner to decide whether to include it in the current Sprint Correct answer.
    3. Add it to the current Sprint Backlog without discussion
    4. Ask the Scrum Master to prioritize it

    Explanation

    The Product Owner is responsible for managing the Product Backlog and maximizing value. The Developers and Product Owner collaborate to decide if the new requirement should be added to the current Sprint, considering the Sprint Goal.

  23. Question 23Scrum Framework and Theory

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

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

    Explanation

    Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.

  24. Question 24Scrum Framework and Theory

    Which statement about the Increment is correct?

    1. It is optional and only required for complex products
    2. It is created only at the end of the project
    3. It is the sum of all completed Product Backlog items and must be in a usable condition Correct answer.
    4. It must be released to production at the end of every Sprint

    Explanation

    An Increment is the sum of all completed Product Backlog items during a Sprint and the value of the increments of all previous Sprints. It must be in a usable condition to provide value, regardless of whether it is released.

  25. Question 25Scrum Framework and Theory

    What is the primary purpose of the Scrum Master serving the organization?

    1. To hire new Scrum Team members
    2. To approve all Product Backlog items
    3. To lead and coach the organization in its Scrum adoption Correct answer.
    4. To manage the organization's budget for Scrum projects

    Explanation

    The Scrum Master serves the organization by leading, training, and coaching it in its Scrum adoption, and by helping employees and stakeholders understand and enact Scrum.

  26. Question 26Scrum Framework and Theory

    What is the timebox for the Daily Scrum?

    1. 60 minutes
    2. 15 minutes Correct answer.
    3. 10 minutes
    4. 30 minutes

    Explanation

    The Daily Scrum is timeboxed to 15 minutes for every Sprint length, so the Developers can inspect progress toward the Sprint Goal and adapt the Sprint Backlog.

  27. Question 27Scrum Framework and Theory

    What is the maximum timebox for the Sprint Review when the Sprint is one month long?

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

    Explanation

    The Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint, and it is shortened for shorter Sprints.

  28. Question 28Scrum Framework and Theory

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

    1. 90 minutes
    2. Four hours
    3. 45 minutes
    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 shortened for shorter Sprints.

  29. Question 29Scrum Framework and Theory

    Which three artifacts does Scrum define?

    1. Product Vision, Product Backlog, and Release Plan
    2. Sprint Backlog, Burndown Chart, and Increment
    3. Product Backlog, Sprint Backlog, and Increment Correct answer.
    4. Product Backlog, Sprint Goal, and Definition of Done

    Explanation

    Scrum defines exactly three artifacts: the Product Backlog, the Sprint Backlog, and the Increment. Each artifact contains a commitment: the Product Goal, the Sprint Goal, and the Definition of Done respectively.

  30. Question 30Scrum Framework and Theory

    Which commitment is associated with the Product Backlog?

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

    Explanation

    Each artifact has a commitment: the Product Goal is the commitment for the Product Backlog, describing a future state of the product.

  31. Question 31Scrum Framework and Theory

    What is the timebox for the Sprint itself?

    1. Two weeks or less
    2. One month or less Correct answer.
    3. Six weeks or less
    4. As long as the team decides

    Explanation

    Sprints are fixed-length events of one month or less that maintain consistency. A new Sprint starts immediately after the conclusion of the previous Sprint.

  32. Question 32Scrum Framework and Theory

    Which statement best describes who is accountable for the Scrum Team's effectiveness?

    1. The Product Owner
    2. The stakeholders
    3. The Scrum Master Correct answer.
    4. The most senior Developer

    Explanation

    The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide and for the Scrum Team's effectiveness, by enabling the team to improve its practices.

  33. Question 33Scrum Framework and Theory

    What is the recommended maximum size of the Scrum Team?

    1. Five people
    2. Twelve people
    3. Ten or fewer people Correct answer.
    4. Eight people

    Explanation

    The Scrum Guide recommends a Scrum Team of ten or fewer people. Smaller teams communicate better and are more productive, while larger teams require more coordination.

  34. Question 34Scrum Framework and Theory

    A Developer notices that a Sprint Backlog item no longer makes sense given new learning. What does Scrum permit?

    1. The item may be removed only by the Product Owner
    2. The Scrum Master must approve any change
    3. The item must remain until the Sprint Review
    4. The Developers may adjust the Sprint Backlog as more is learned Correct answer.

    Explanation

    The Sprint Backlog is a plan by and for the Developers and is updated throughout the Sprint as more is learned. Scope may be clarified and renegotiated with the Product Owner as more is learned.

  35. Question 35Scrum Framework and Theory

    A team finishes its Daily Scrum in 20 minutes with eight Developers participating. What is the most accurate assessment?

    1. This is acceptable because larger teams need more time
    2. The Scrum Master should cancel the event
    3. The event should be extended to 30 minutes for eight people
    4. The event exceeded its timebox and should be kept to 15 minutes Correct answer.

    Explanation

    The Daily Scrum is timeboxed to 15 minutes regardless of team size. The Developers should structure the conversation so it fits within the timebox.

  36. Question 36Scrum Framework and Theory

    Who creates the Definition of Done when the organization has no existing standard?

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

    Explanation

    If the Definition of Done is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product. All work must meet it for the Increment to be considered complete.

  37. Question 37Scrum Framework and Theory

    What happens to unfinished Sprint Backlog items when a Sprint ends?

    1. They are discarded permanently
    2. They become part of the Increment
    3. They return to the Product Backlog for reordering and prioritization Correct answer.
    4. They are automatically carried into the next Sprint unchanged

    Explanation

    Work that is not finished by the end of the Sprint returns to the Product Backlog, where the Product Owner can reassess and reprioritize it. Only work meeting the Definition of Done counts toward the Increment.

  38. Question 38Scrum Framework and Theory

    A stakeholder asks to add a new feature mid-Sprint that would jeopardize the Sprint Goal. What should happen?

    1. The team waits until the next Sprint Review to discuss it
    2. The Developers add the feature and extend the Sprint by a week
    3. The Product Owner and Developers discuss it, and the Product Owner may choose to cancel the Sprint if the Sprint Goal becomes obsolete Correct answer.
    4. The Scrum Master decides whether the feature is added

    Explanation

    Scope may be clarified and renegotiated with the Product Owner as more is learned, but a Sprint can be cancelled only by the Product Owner, and only if the Sprint Goal becomes obsolete.

  39. Question 39Scrum Framework and Theory

    Which of the following best describes the Sprint Review's focus?

    1. Confirming that the Definition of Done was followed
    2. Inspecting the Increment and adapting the Product Backlog Correct answer.
    3. Inspecting how the team collaborated and improving its processes
    4. Estimating the effort for upcoming Sprint Backlog items

    Explanation

    The Sprint Review inspects the outcome of the Sprint and determines future adaptations, focusing on the Increment and adapting the Product Backlog. Process improvement is the focus of the Retrospective.

  40. Question 40Scrum Framework and Theory

    In Scrum, what is the relationship between the Product Goal and the Sprint Goal?

    1. They are unrelated and set by different people
    2. The Sprint Goal must be identical to the Product Goal
    3. The Sprint Goal is a step toward achieving the Product Goal Correct answer.
    4. The Product Goal is derived from each Sprint Goal

    Explanation

    The Product Goal describes a future state of the product, and each Sprint Goal is a step toward it. The Sprint Goal gives the Developers focus for a single Sprint.

  41. Question 41Scrum Framework and Theory

    What is the primary reason the Sprint is a fixed-length event?

    1. To standardize reporting across teams
    2. To ensure every Sprint delivers the same amount of work
    3. To limit risk to the cost of no more than one Sprint Correct answer.
    4. To make budgeting predictable for stakeholders

    Explanation

    Sprints limit risk to the cost of no more than one Sprint. Fixed length provides a consistent cadence for inspection and adaptation.

  42. Question 42Scrum Framework and Theory

    Which statement accurately describes the Increment?

    1. It is only produced at the Sprint Review
    2. It can contain work that does not meet the Definition of Done
    3. It is a concrete stepping stone toward the Product Goal and must meet the Definition of Done Correct answer.
    4. It must be released to production at the end of every Sprint

    Explanation

    An Increment is a concrete stepping stone toward the Product Goal, and each Increment is additive to previous ones. Work cannot be part of an Increment unless it meets the Definition of Done.

  43. Question 43Scrum Framework and Theory

    The Product Owner wants to delegate ordering of the Product Backlog to the Developers. What does Scrum say?

    1. Delegation is prohibited under all circumstances
    2. The Product Owner may delegate the work but remains accountable for the ordering Correct answer.
    3. The Scrum Master must take over the ordering
    4. Only stakeholders may reorder the Product Backlog

    Explanation

    The Product Owner is accountable for effective Product Backlog management and may delegate the work to others, but remains accountable for the outcome.

  44. Question 44Scrum Framework and Theory

    What is the primary purpose of the Sprint Planning event?

    1. To define the Definition of Done for the product
    2. To review the Increment with stakeholders
    3. To identify process improvements from the last Sprint
    4. To define what can be delivered in the Sprint and how the work will be achieved Correct answer.

    Explanation

    Sprint Planning addresses why the Sprint is valuable, what can be done, and how the work will get done. It results in the Sprint Goal and a plan captured in the Sprint Backlog.

  45. Question 45Scrum Framework and Theory

    A Scrum Team works in two-week Sprints. What is the maximum timebox for its Sprint Planning?

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

    Explanation

    Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints the event is usually shorter; for a two-week Sprint, two hours is a reasonable proportional maximum.

  46. Question 46Scrum Framework and Theory

    Which of the following best captures how the three pillars of empiricism apply to the Sprint Review?

    1. Transparency of the Increment, inspection with stakeholders, and adaptation of the Product Backlog Correct answer.
    2. Adaptation of the Definition of Done, inspection of processes, and transparency of velocity
    3. Inspection of individual performance, adaptation of roles, and transparency of budgets
    4. Transparency of the Sprint Goal, inspection of the Daily Scrum, and adaptation of the team charter

    Explanation

    The Sprint Review makes the Increment transparent, allows stakeholders and the Scrum Team to inspect it, and results in adaptation of the Product Backlog for the next Sprint.

  47. Question 47Scrum Framework and Theory

    A Scrum Team delivers an Increment that meets its Definition of Done but the Product Owner decides not to release it. Which statement is true?

    1. The Increment is invalid because it was not released
    2. The Increment still exists and is a step toward the Product Goal Correct answer.
    3. The Definition of Done must be revised to require release
    4. The Sprint must be cancelled

    Explanation

    An Increment is created when work meets the Definition of Done, regardless of whether it is released. Releasing is a separate business decision the Product Owner may make.

  48. Question 48Scrum Framework and Theory

    Which statement best explains why the Sprint Backlog is described as a plan by and for the Developers?

    1. Because the Developers own the plan and update it as more is learned during the Sprint Correct answer.
    2. Because the Product Owner cannot see the Sprint Backlog
    3. Because the Scrum Master writes the Sprint Backlog items
    4. Because only Developers may attend Sprint Planning

    Explanation

    The Sprint Backlog is composed of the Sprint Goal, selected Product Backlog items, and the plan for delivering them. It is owned by the Developers, who update it throughout the Sprint as more is learned.

  49. Question 49Scrum Framework and Theory

    Which statement best describes how Scrum handles the trade-off between the Sprint Goal and the Sprint Backlog when new information emerges?

    1. Both may change at any time without Product Owner involvement
    2. The Sprint Backlog is fixed, while the Sprint Goal may change freely
    3. Both the Sprint Goal and Sprint Backlog must remain unchanged
    4. The Sprint Goal is fixed for the Sprint, while the Sprint Backlog may be adjusted to meet it Correct answer.

    Explanation

    The Sprint Goal is a fixed focus for the Sprint, while the Sprint Backlog is flexible and can be adjusted as more is learned. This allows the team to adapt its plan while preserving the Sprint's purpose.

  50. Question 50Scrum Framework and Theory

    A Scrum Team is asked to add a fifth event to improve coordination. How should the Scrum Master respond?

    1. Explain that Scrum defines exactly five events: the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective Correct answer.
    2. Add the event only if the Product Owner approves
    3. Add the event and document it as a Scrum artifact
    4. Replace the Daily Scrum with the new event

    Explanation

    Scrum prescribes five events: the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Additional meetings may exist but are not Scrum events, and the Sprint itself is the container for the others.

  51. Question 51Scrum Roles and Accountabilities

    Who is responsible for ordering and prioritizing the items in the Product Backlog?

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

    Explanation

    The Product Owner is accountable for maximizing the value of the product, which includes ordering and prioritizing the Product Backlog. This is a single-person accountability so that priorities stay clear.

  52. Question 52Scrum Roles and Accountabilities

    What is the primary accountability of the Scrum Master?

    1. Managing the team's daily task assignments
    2. Approving the Definition of Done
    3. Establishing Scrum as defined in the Scrum Guide Correct answer.
    4. Writing the acceptance criteria

    Explanation

    The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide and for the Scrum Team's effectiveness. This includes coaching and helping the team improve its practices.

  53. Question 53Scrum Roles and Accountabilities

    Which statement best describes the Scrum Team's structure?

    1. It is composed only of Developers and a Product Owner.
    2. It consists of a Product Owner, a Scrum Master, and Developers. Correct answer.
    3. It has three separate committees that report to a program manager.
    4. It is led by a project manager who directs the Developers.

    Explanation

    The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. It is a single self-managing unit with no sub-teams or hierarchy.

  54. Question 54Scrum Roles and Accountabilities

    Who creates the Definition of Done?

    1. The Product Owner alone
    2. The Scrum Master alone
    3. The Scrum Team Correct answer.
    4. The quality assurance group

    Explanation

    The Scrum Team creates the Definition of Done, and if the organization has a standard, all teams must follow it as a minimum. The Developers use it to decide when work is complete.

  55. Question 55Scrum Roles and Accountabilities

    A team member is unsure who should attend the Daily Scrum. Who is expected to participate?

    1. The Developers Correct answer.
    2. Anyone in the organization who is interested
    3. Only the Product Owner
    4. Only the Scrum Master and Product Owner

    Explanation

    The Daily Scrum is an event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. Others may attend only if they are needed or invited by the Developers.

  56. Question 56Scrum Roles and Accountabilities

    Which accountability belongs to the Product Owner?

    1. Ensuring the team follows the Definition of Done
    2. Removing impediments raised by the Developers
    3. Facilitating Scrum events as requested
    4. Maximizing the value of the product Correct answer.

    Explanation

    The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. This is often expressed through effective Product Backlog management.

  57. Question 57Scrum Roles and Accountabilities

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

    1. The team does not need a Product Owner.
    2. The team can ignore the Sprint Goal when convenient.
    3. The team decides internally who does what, when, and how. Correct answer.
    4. The team sets its own working hours outside Scrum events.

    Explanation

    A self-managing team internally decides who does what, when, and how. This autonomy applies to how the team accomplishes its work, not to removing required accountabilities.

  58. Question 58Scrum Roles and Accountabilities

    How many Product Owners does a Scrum Team have?

    1. As many as the organization decides
    2. One per Developer
    3. Two
    4. One Correct answer.

    Explanation

    A Scrum Team has exactly one Product Owner. Having a single owner keeps product direction and priority decisions clear.

  59. Question 59Scrum Roles and Accountabilities

    During a Sprint, the Product Owner wants to add a new high-value item that would require changing the Sprint Goal. What is the appropriate action?

    1. Add it to the current Sprint Backlog and abandon the Sprint Goal.
    2. Ask the Scrum Master to reject the request outright.
    3. Negotiate scope with the Developers while keeping the Sprint Goal intact. Correct answer.
    4. Wait until the next Sprint and never discuss it now.

    Explanation

    Scope may be clarified and renegotiated with the Developers as more is learned, but the Sprint Goal and quality targets should not change mid-Sprint. The Product Owner collaborates with the Developers to adjust scope accordingly.

  60. Question 60Scrum Roles and Accountabilities

    The Developers discover they cannot finish all Sprint Backlog items but can still meet the Sprint Goal. What should happen?

    1. The Product Owner removes the Sprint Goal.
    2. The Scrum Master extends the Sprint by a few days.
    3. The Developers renegotiate scope with the Product Owner. Correct answer.
    4. The Sprint is cancelled immediately.

    Explanation

    If the work turns out different than expected, the Developers collaborate with the Product Owner to negotiate the scope of the Sprint Backlog. The Sprint Goal remains the focus as long as it is still achievable.

  61. Question 61Scrum Roles and Accountabilities

    A stakeholder keeps giving work requests directly to individual Developers. How should the Scrum Master best respond?

    1. Escalate to the stakeholder's manager to stop the requests.
    2. Redirect the requests so the Product Owner can order them in the Product Backlog. Correct answer.
    3. Instruct the Developers to refuse all stakeholder contact.
    4. Add the requests to the Sprint Backlog on the stakeholder's behalf.

    Explanation

    The Product Owner is the single point for ordering work, so new requests should flow through the Product Owner into the Product Backlog. The Scrum Master coaches the organization on this interaction to protect focus.

  62. Question 62Scrum Roles and Accountabilities

    The Developers want to change their working process mid-Sprint. Who decides?

    1. The Product Owner, since it affects value
    2. The Developers, since they own how they do the work Correct answer.
    3. The stakeholders, since it affects delivery
    4. The Scrum Master, since it concerns process

    Explanation

    The Developers are self-managing and decide how to turn backlog items into a valuable Increment. They own their process and internal organization.

  63. Question 63Scrum Roles and Accountabilities

    Who is accountable for ensuring the Scrum events take place and are kept within the timebox?

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

    Explanation

    The Scrum Master is accountable for the Scrum Team's effectiveness, which includes ensuring the events take place and are positive, productive, and kept within the timebox.

  64. Question 64Scrum Roles and Accountabilities

    A Product Owner is unavailable for several Sprints and Developers start making priority decisions themselves. What is the most accurate assessment?

    1. This is fine as long as the Scrum Master approves the priorities.
    2. This is acceptable because the team is self-managing.
    3. This is fine because priorities are optional in Scrum.
    4. This is a gap; the Product Owner accountability must be filled. Correct answer.

    Explanation

    The Product Owner accountability is essential for ordering work and maximizing value; if the person is unavailable, the accountability still must be fulfilled. The Developers deciding priorities creates a conflict with the single-owner model.

  65. Question 65Scrum Roles and Accountabilities

    Which best describes the relationship between the Product Owner and the Developers regarding the Product Backlog?

    1. The Product Owner orders items alone with no Developer input.
    2. The Scrum Master orders items and the Product Owner refines them.
    3. The Developers order items and the Product Owner refines them.
    4. The Product Owner orders items and the Developers help refine them. Correct answer.

    Explanation

    The Product Owner is accountable for ordering the Product Backlog, while the Developers contribute by refining items and estimating. This collaboration improves shared understanding.

  66. Question 66Scrum Roles and Accountabilities

    The organization asks the Scrum Master to also serve as the team's Product Owner to save cost. What is the best guidance?

    1. It conflicts because the accountabilities are distinct and should not be merged. Correct answer.
    2. It is fine because one person can hold both accountabilities easily.
    3. It is required in small organizations.
    4. It is acceptable if the Scrum Master does not facilitate events.

    Explanation

    The Product Owner and Scrum Master are distinct accountabilities serving different purposes, and merging them creates conflicting focus. Scrum expects these to be separate so each is served well.

  67. Question 67Scrum Roles and Accountabilities

    A Developer proposes a technical improvement that is not in the Sprint Backlog. What is the most Scrum-aligned response?

    1. Discuss it with the team, since the Developers own how they build the Increment. Correct answer.
    2. Reject it because only the Product Owner can suggest improvements.
    3. Require the Scrum Master to approve any technical change.
    4. Add it to the Product Backlog and forbid any work on it now.

    Explanation

    The Developers are self-managing and decide how to create the Increment, so technical improvements are within their domain. They coordinate internally on such work while respecting the Sprint Goal.

  68. Question 68Scrum Roles and Accountabilities

    Which statement about the Scrum Master's authority is most accurate?

    1. The Scrum Master approves the Sprint Goal.
    2. The Scrum Master has authority to assign tasks to Developers.
    3. The Scrum Master can override the Product Owner's ordering.
    4. The Scrum Master leads through influence and coaching rather than command. Correct answer.

    Explanation

    The Scrum Master serves the team and organization by coaching, facilitating, and removing impediments, leading through influence rather than direct authority over work. The role does not command the Developers or override the Product Owner.

  69. Question 69Scrum Roles and Accountabilities

    Who is responsible for crafting a clear Sprint Goal?

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

    Explanation

    The Sprint Goal is created collaboratively by the whole Scrum Team during Sprint Planning. It gives the Sprint a single objective that guides the Developers' work.

  70. Question 70Scrum Roles and Accountabilities

    A manager outside the Scrum Team insists on reviewing and approving each Developer's daily work. How does this affect the Scrum Team?

    1. It undermines self-management and should be addressed by the Scrum Master. Correct answer.
    2. It strengthens the team by adding oversight.
    3. It replaces the need for the Daily Scrum.
    4. It is required to keep the Product Owner informed.

    Explanation

    Self-managing teams decide internally how to do their work, so external per-task approval undermines that autonomy. The Scrum Master helps the organization understand and support the team's self-management.

  71. Question 71Scrum Roles and Accountabilities

    The Developers and Product Owner disagree on whether an item meets the Definition of Done. Who ultimately determines completion against the Definition of Done?

    1. The stakeholders, because they use the product
    2. The Developers, because they apply the Definition of Done to the Increment Correct answer.
    3. The Scrum Master, because they enforce process
    4. The Product Owner, because they accept the work

    Explanation

    The Developers are accountable for applying the Definition of Done and determining when work is complete against it. The Product Owner may accept or reject based on value, but completion against the Definition of Done is the Developers' judgment.

  72. Question 72Scrum Roles and Accountabilities

    An organization wants a 'team lead' who directs the Developers and reports progress to the Product Owner. How does this fit Scrum?

    1. It is acceptable if the Scrum Master approves the team lead.
    2. It is compatible if the team lead also attends the Daily Scrum.
    3. It conflicts with self-management and the flat structure of the Scrum Team. Correct answer.
    4. It is required so the Product Owner has a single contact.

    Explanation

    A Scrum Team is a flat, self-managing unit with no sub-teams or hierarchy, so a directing team lead conflicts with Scrum. The Scrum Master coaches the organization to remove such structures.

  73. Question 73Scrum Roles and Accountabilities

    The Product Owner is accountable for the Product Backlog, yet the Developers do most of the refinement work. Which interpretation is most accurate?

    1. The Developers now own the Product Backlog.
    2. The Product Owner remains accountable while delegating refinement work. Correct answer.
    3. Accountability is shared equally between both parties.
    4. The Scrum Master must reclaim the refinement work.

    Explanation

    Accountability for the Product Backlog stays with the Product Owner, who may delegate work such as refinement to the Developers. Delegation of tasks does not transfer the accountability.

  74. Question 74Scrum Roles and Accountabilities

    During Sprint Planning the Developers realize the selected work is more than they can do. What is the most appropriate action within the event?

    1. Negotiate the amount of work with the Product Owner before starting. Correct answer.
    2. Ask the Scrum Master to shorten the Sprint.
    3. Commit to all items and hope to catch up later.
    4. Start the Sprint and drop items without telling anyone.

    Explanation

    Sprint Planning is where the team forecasts and agrees on scope with the Product Owner, so adjusting the amount of selected work during planning is appropriate. This keeps the forecast realistic and the Sprint Goal achievable.

  75. Question 75Scrum Roles and Accountabilities

    A new Scrum Master wants to know which service to the organization is part of the role. Which is correct?

    1. Writing the Sprint Goal for the team
    2. Assigning work to Developers to improve throughput
    3. Leading and coaching the organization in its Scrum adoption Correct answer.
    4. Approving the Product Backlog order

    Explanation

    The Scrum Master serves the organization by leading, training, and coaching it in its Scrum adoption and by helping remove barriers between stakeholders and teams. The other activities belong to different accountabilities.

  76. Question 76Scrum Roles and Accountabilities

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

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

    Explanation

    The Product Owner is the single accountable party for product value, which is the reason the role exists in Scrum. The Scrum Master and Developers serve other accountabilities and do not own value maximization.

  77. Question 77Scrum Roles and Accountabilities

    Which statement best captures the Scrum Master's accountability toward the Scrum Team?

    1. Assigning tasks to Developers at the Daily Scrum
    2. Approving each increment before it is shown to stakeholders
    3. Ensuring the team follows the Scrum Guide exactly as written
    4. Being accountable for the team's effectiveness and continuous improvement Correct answer.

    Explanation

    The Scrum Master is accountable for the Scrum Team's effectiveness, which includes coaching and enabling improvement. The role is not about rigid rule enforcement, approvals, or task assignment.

  78. Question 78Scrum Roles and Accountabilities

    Who decides how the work is turned into an increment of value during a Sprint?

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

    Explanation

    The Developers decide how to transform the selected Product Backlog items into a usable increment. This is a core element of their self-management over the technical work.

  79. Question 79Scrum Roles and Accountabilities

    A Scrum Team consists of which members?

    1. Developers and a Scrum Master only
    2. Developers, a Scrum Master, and a Product Owner Correct answer.
    3. Developers, a Product Owner, and functional managers
    4. Developers, a Scrum Master, a Product Owner, and a project manager

    Explanation

    The Scrum Team is made up of one Scrum Master, one Product Owner, and Developers. No other roles, such as project managers or functional managers, are part of the Scrum Team.

  80. Question 80Scrum Roles and Accountabilities

    What is the primary focus of the Product Owner's accountability for the Product Backlog?

    1. Writing all acceptance tests for the Developers
    2. Facilitating the Daily Scrum
    3. Estimating the effort for every item
    4. Ensuring the backlog is transparent, visible, and understood Correct answer.

    Explanation

    The Product Owner is accountable for the Product Backlog, including its transparency and clarity so the team and stakeholders understand it. Estimating and testing are Developer activities, and the Daily Scrum is not facilitated by the Product Owner.

  81. Question 81Scrum Roles and Accountabilities

    Which accountability belongs to the Developers?

    1. Creating a plan for the Sprint in the Sprint Backlog Correct answer.
    2. Coaching the organization in Scrum adoption
    3. Ordering the Product Backlog to achieve goals
    4. Deciding which stakeholders may attend the Sprint Review

    Explanation

    The Developers are accountable for creating the Sprint Backlog, which is their plan for the Sprint. Ordering the backlog and coaching the organization belong to the Product Owner and Scrum Master respectively.

  82. Question 82Scrum Roles and Accountabilities

    Who is accountable for the Scrum Team's effectiveness?

    1. The team's engineering manager
    2. The Scrum Master Correct answer.
    3. The Product Owner
    4. The most senior Developer

    Explanation

    The Scrum Master is accountable for the Scrum Team's effectiveness, helping it improve its practices and its use of Scrum. Seniority or external management does not transfer this accountability.

  83. Question 83Scrum Roles and Accountabilities

    Which of the following is a service the Scrum Master provides to the organization?

    1. Setting the organization's product strategy
    2. Hiring and firing members of the Scrum Team
    3. Leading and coaching the organization in its Scrum adoption Correct answer.
    4. Managing the organization's budget for the product

    Explanation

    One of the Scrum Master's services to the organization is leading, training, and coaching it in Scrum adoption. Budget, strategy, and staffing decisions are not Scrum Master accountabilities.

  84. Question 84Scrum Roles and Accountabilities

    A Developer finishes a task and starts a different Sprint Backlog item without telling anyone. What does Scrum say about this?

    1. It is acceptable because the Developers self-manage their Sprint work Correct answer.
    2. It is acceptable only if the Product Owner reorders the backlog first
    3. It is a violation because the Scrum Master must approve task changes
    4. It is a violation because the Sprint Backlog is frozen once the Sprint starts

    Explanation

    The Developers own the Sprint Backlog and self-manage how they carry out the work, so adjusting tasks within the Sprint is normal. No approval from the Scrum Master or Product Owner is required for task-level changes.

  85. Question 85Scrum Roles and Accountabilities

    The Product Owner wants to delegate the ordering of the Product Backlog to a senior Developer. Which response is most aligned with Scrum?

    1. The Developers must vote before any delegation is allowed
    2. The Scrum Master must take over the ordering to keep roles separate
    3. The Product Owner remains accountable and may delegate the work but not the accountability Correct answer.
    4. This is fine because ordering is a technical concern

    Explanation

    The Product Owner may delegate tasks such as backlog ordering, but accountability for the Product Backlog stays with the Product Owner. Delegation transfers work, not accountability.

  86. Question 86Scrum Roles and Accountabilities

    During a Sprint Review, a stakeholder asks the Scrum Master to commit the team to a delivery date for a new feature. What is the Scrum Master's best action?

    1. Commit to the date on behalf of the Developers
    2. Redirect the request to the Product Owner, who manages stakeholder expectations and the backlog Correct answer.
    3. Ask the Developers to estimate and commit on the spot
    4. Decline and end the discussion immediately

    Explanation

    Managing stakeholder expectations and Product Backlog decisions is the Product Owner's accountability, so the Scrum Master should route the request there. Committing on the team's behalf would overstep the role.

  87. Question 87Scrum Roles and Accountabilities

    Who is responsible for ensuring that the Scrum Team adheres to the Definition of Done?

    1. The Scrum Master alone
    2. The quality assurance department
    3. The Product Owner alone
    4. The Developers, who create and use it Correct answer.

    Explanation

    The Developers are accountable for the increment and for applying the Definition of Done to their work. If the organization has a standard Definition of Done, all Scrum Teams must use it as a minimum.

  88. Question 88Scrum Roles and Accountabilities

    A Scrum Master notices the Developers rarely talk to the Product Owner and are working from outdated priorities. What is the most appropriate action?

    1. Instruct the Developers to stop work until the Product Owner contacts them
    2. Coach the Scrum Team on the importance of collaboration between the Product Owner and Developers Correct answer.
    3. Escalate to management to replace the Product Owner
    4. Reorder the Product Backlog so the Developers have current priorities

    Explanation

    A key Scrum Master service is coaching the team and the Product Owner toward effective collaboration. Reordering the backlog or escalating would bypass the Product Owner's accountability rather than fix the relationship.

  89. Question 89Scrum Roles and Accountabilities

    Which statement correctly describes the Product Owner's authority over the Sprint Backlog?

    1. The Product Owner sets the order of tasks in the Sprint Backlog
    2. The Product Owner approves every change to the Sprint Backlog
    3. The Product Owner may attend the Daily Scrum but does not manage the Sprint Backlog Correct answer.
    4. The Product Owner writes and maintains the Sprint Backlog

    Explanation

    The Sprint Backlog belongs to the Developers, who self-manage it; the Product Owner does not own or approve changes to it. The Product Owner may attend the Daily Scrum if useful but does not direct the work.

  90. Question 90Scrum Roles and Accountabilities

    An organization has three separate Scrum Teams working on one product. How many Product Owners should exist?

    1. One for the product, with the teams sharing that Product Owner Correct answer.
    2. None, because the Developers can order the backlog themselves
    3. One per team plus a coordinating Product Owner
    4. One per team, so each team has its own priorities

    Explanation

    Each product has one Product Owner, even when several Scrum Teams work on it, so priorities and value decisions stay coherent. Multiple Product Owners on one product create conflicting priorities.

  91. Question 91Scrum Roles and Accountabilities

    A Developer is asked by a stakeholder to add a feature directly to the Sprint. What is the most Scrum-aligned guidance for the Developer?

    1. Add the feature only if it takes less than one day
    2. Refuse to speak with stakeholders at any time
    3. Direct the stakeholder to the Product Owner so the request can be considered against the Sprint Goal Correct answer.
    4. Add the feature and inform the Product Owner afterward

    Explanation

    New requests should flow through the Product Owner, who owns the Product Backlog and value decisions. The Developers protect the Sprint Goal by not unilaterally expanding the Sprint's scope.

  92. Question 92Scrum Roles and Accountabilities

    Which pairing of accountability and role is correct?

    1. Product Owner: managing the Product Backlog Correct answer.
    2. Product Owner: facilitating Scrum events
    3. Developers: coaching the organization in Scrum
    4. Scrum Master: maximizing product value

    Explanation

    The Product Owner is accountable for the Product Backlog, including its content, ordering, and transparency. The other pairings assign accountabilities to the wrong roles.

  93. Question 93Scrum Roles and Accountabilities

    The Scrum Master is asked to decide whether a Product Backlog item is valuable enough to keep. What is the correct response?

    1. Keep the item until the next Sprint Review for stakeholder input
    2. Defer to the Product Owner, who is accountable for Product Backlog value decisions Correct answer.
    3. Decide, because the Scrum Master protects the team from low-value work
    4. Ask the Developers to vote on the item's value

    Explanation

    Value decisions about Product Backlog items belong to the Product Owner. The Scrum Master serves the team through coaching and facilitation, not by making product decisions.

  94. Question 94Scrum Roles and Accountabilities

    Which best describes the Product Owner's involvement in the Daily Scrum?

    1. The Product Owner reviews each Developer's status report after the event
    2. The Product Owner must run the Daily Scrum to track progress
    3. The Product Owner may attend if the Developers find it useful, but does not direct the work Correct answer.
    4. The Product Owner is forbidden from attending the Daily Scrum

    Explanation

    The Daily Scrum is for the Developers to inspect progress toward the Sprint Goal and adapt their plan. The Product Owner may attend if helpful but does not run it or direct the Developers' work.

  95. Question 95Scrum Roles and Accountabilities

    A Scrum Master keeps the team's impediment list and personally resolves every impediment for the Developers. How does this affect the team?

    1. It is required because only the Scrum Master may remove impediments
    2. It risks undermining the Developers' self-management of their own work Correct answer.
    3. It transfers the Scrum Master's accountability to the Developers
    4. It strengthens self-management because impediments are removed quickly

    Explanation

    While the Scrum Master helps remove impediments, taking over every impediment can prevent the Developers from self-managing and solving their own problems. The aim is to grow the team's capability, not create dependency.

  96. Question 96Scrum Roles and Accountabilities

    A line manager tells the Scrum Master that the manager will assign daily tasks to each Developer to ensure efficiency. What is the most accurate assessment?

    1. This is compatible with Scrum if the manager attends the Daily Scrum
    2. This conflicts with the Developers' self-management of their own work Correct answer.
    3. This is acceptable because the Scrum Master can approve the task list
    4. This is required when the team is new to Scrum

    Explanation

    Self-management means the Developers decide how to do the work, so externally assigned daily tasks conflict with Scrum. Attendance at events or team maturity does not change this principle.

  97. Question 97Scrum Roles and Accountabilities

    The Product Owner is accountable for maximizing value but rarely available, so the Scrum Master starts answering stakeholder questions about priorities. What is the most accurate description of the resulting situation?

    1. The Developers should now elect a new Product Owner from among themselves
    2. The Scrum Master has formally become the Product Owner
    3. The Scrum Master is appropriately filling a gap in the Product Owner's availability
    4. Accountabilities are being blurred, which should be addressed by restoring the Product Owner's ownership Correct answer.

    Explanation

    When the Scrum Master answers priority questions, the Product Owner's accountability is effectively bypassed and roles blur. The Scrum-aligned response is to surface and resolve the availability problem so the Product Owner owns those decisions.

  98. Question 98Scrum Roles and Accountabilities

    An organization wants the Scrum Master to also act as the team's line manager, conducting performance reviews that affect Developers' pay. What is the most accurate Scrum guidance?

    1. This is required so the Scrum Master has authority to remove impediments
    2. This is acceptable because the Scrum Master already coaches the team
    3. This is acceptable if the Developers agree to it
    4. Combining these responsibilities creates a conflict with the Scrum Master's coaching stance Correct answer.

    Explanation

    The Scrum Master serves the team through coaching and facilitation; holding pay and performance authority over the same people conflicts with that stance and can suppress openness. The Scrum Guide does not assign line-management duties to the role.

  99. Question 99Scrum Roles and Accountabilities

    During Sprint Planning, the Developers and Product Owner discuss a complex item. The Product Owner insists on a specific technical design. What is the most accurate view?

    1. The Scrum Master should arbitrate and choose the design
    2. The Developers decide how to build the item, so the design choice belongs to them Correct answer.
    3. The Product Owner may dictate the design because they own the value
    4. The design must be deferred to the next Sprint Review

    Explanation

    The Product Owner defines what and why; the Developers decide how, including technical design. The Product Owner may clarify intent and constraints but does not dictate the implementation.

  100. Question 100Scrum Roles and Accountabilities

    A Scrum Team is unsure who should decide whether the Sprint Goal is still achievable and whether to adjust it. Which statement is most accurate?

    1. The Scrum Master decides whether the Sprint Goal remains valid
    2. Stakeholders decide at the Daily Scrum whether the goal is still valid
    3. Only the Product Owner may ever change or cancel a Sprint Goal
    4. The Developers and Product Owner collaborate on the Sprint Goal, and only the Product Owner may cancel a Sprint Correct answer.

    Explanation

    The Sprint Goal is crafted collaboratively during Sprint Planning by the whole Scrum Team, but only the Product Owner has the authority to cancel a Sprint. The Scrum Master and stakeholders do not hold that authority.

  101. Question 101Scrum Events and Artifacts

    What is the maximum length of the Sprint for a product using Scrum?

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

    Explanation

    In Scrum, Sprints are fixed-length iterations of one month or less, and a new Sprint starts immediately after the previous one ends. A month is the outer limit that keeps complexity and risk manageable.

  102. Question 102Scrum Events and Artifacts

    Who is responsible for ordering the items in the Product Backlog?

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

    Explanation

    The Product Owner is accountable for maximizing product value and manages the Product Backlog, including its ordering. Ordering decisions are the Product Owner's call even though others may contribute information.

  103. Question 103Scrum Events and Artifacts

    During the Daily Scrum, which of the following is required?

    1. The Developers inspect progress toward the Sprint Goal and adapt the Sprint Backlog Correct answer.
    2. The Scrum Master records the minutes for the team
    3. Stakeholders are invited to observe and give feedback
    4. Each Developer answers the three classic questions in turn

    Explanation

    The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as needed. The structure and techniques are chosen by the Developers.

  104. Question 104Scrum Events and Artifacts

    What does the Definition of Done provide for the team?

    1. A list of every task required to build a feature
    2. A shared understanding of what it means for work to be complete Correct answer.
    3. A record of who approved each backlog item
    4. A schedule of release dates for the product

    Explanation

    The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It creates a shared understanding of completeness that the team applies to all work.

  105. Question 105Scrum Events and Artifacts

    Which artifact is described as a commitment to the Sprint Goal?

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

    Explanation

    The Sprint Backlog is composed of the Sprint Goal, the selected Product Backlog items, and the plan for delivering them. It is the commitment of the Developers to the Sprint Goal.

  106. Question 106Scrum Events and Artifacts

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

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

    Explanation

    Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint; shorter Sprints usually require less time. The event addresses why, what, and how the Sprint will deliver value.

  107. Question 107Scrum Events and Artifacts

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

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

    Explanation

    The Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint. Shorter Sprints typically result in a shorter Review.

  108. Question 108Scrum Events and Artifacts

    A Developer notices mid-Sprint that the team will not meet the Sprint Goal. What does Scrum recommend?

    1. Wait until the Sprint Review to raise the concern
    2. Cancel the Sprint immediately
    3. Add more Developers to the team
    4. Negotiate the scope of the Sprint Backlog with the Product Owner Correct answer.

    Explanation

    As more is learned during a Sprint, the scope of the Sprint Backlog may be clarified and renegotiated with the Product Owner. Scope may be adjusted as long as the Sprint Goal is not endangered.

  109. Question 109Scrum Events and Artifacts

    Who may cancel a Sprint?

    1. Any stakeholder with budget authority
    2. The Scrum Master
    3. The Product Owner Correct answer.
    4. The Developers by majority vote

    Explanation

    A Sprint can be cancelled only by the Product Owner, typically when the Sprint Goal becomes obsolete. Cancellation is rare and consumes resources, so it is used sparingly.

  110. Question 110Scrum Events and Artifacts

    What is the primary focus of the Sprint Review?

    1. Determining the Definition of Done for future work
    2. Assigning individual performance ratings
    3. Inspecting how the team collaborated during the Sprint
    4. Inspecting the Increment and adapting the Product Backlog Correct answer.

    Explanation

    The Sprint Review is a working session where the team and stakeholders inspect the Increment and collaborate on what to do next, adapting the Product Backlog. It is not a status meeting or a process retrospective.

  111. Question 111Scrum Events and Artifacts

    A team finishes all selected items but the Increment does not meet the Definition of Done. What is the correct Scrum position?

    1. The Sprint Review should be skipped
    2. The work counts as done because the items were selected and finished
    3. The work is not part of the Increment and returns to the Product Backlog Correct answer.
    4. The Definition of Done should be waived for this Sprint

    Explanation

    Work cannot be considered part of the Increment unless it meets the Definition of Done. Undone work is not presented at the Sprint Review and typically returns to the Product Backlog for reordering.

  112. Question 112Scrum Events and Artifacts

    In Scrum, what is the Increment?

    1. A summary of the Sprint Retrospective
    2. A list of defects found during testing
    3. A concrete stepping stone toward the Product Goal that is usable Correct answer.
    4. A document describing the planned release

    Explanation

    An Increment is a concrete, usable stepping stone toward the Product Goal, and each Increment is additive to prior ones. Multiple Increments may be produced within a single Sprint.

  113. Question 113Scrum Events and Artifacts

    Which participants are required at the Daily Scrum?

    1. Everyone on the Scrum Team plus invited guests
    2. The Scrum Master and Product Owner
    3. The Product Owner and stakeholders
    4. The Developers Correct answer.

    Explanation

    The Daily Scrum is an event for the Developers of the Scrum Team. If the Product Owner or Scrum Master attends, they do so to help the Developers as needed, but their presence is not required.

  114. Question 114Scrum Events and Artifacts

    How should the Product Backlog be refined?

    1. Exclusively by the Product Owner without input from the Developers
    2. Continuously, breaking down and further defining items as understanding grows Correct answer.
    3. Only after the Sprint Review is complete
    4. Only during a formal refinement meeting scheduled once per quarter

    Explanation

    Backlog refinement is an ongoing activity in which items are broken down and clarified so they are ready when needed. It is not a mandated event but a continuous practice.

  115. Question 115Scrum Events and Artifacts

    What happens to unfinished Sprint Backlog items when a Sprint is cancelled?

    1. They are automatically marked done to close the Sprint
    2. They carry over unchanged into the next Sprint's commitment
    3. Completed items are reviewed, and incomplete items return to the Product Backlog Correct answer.
    4. They are permanently discarded and never revisited

    Explanation

    When a Sprint is cancelled, any completed Product Backlog items are reviewed, and if potentially releasable they are accepted. All incomplete items return to the Product Backlog for reordering.

  116. Question 116Scrum Events and Artifacts

    Which three topics does Sprint Planning address?

    1. Who will do each task, when it is due, and what it costs
    2. Which risks exist, who owns them, and how to mitigate them
    3. What went well, what went poorly, and what to change
    4. Why is this Sprint valuable, what can be done, and how will the work get done Correct answer.

    Explanation

    Sprint Planning covers why the Sprint is valuable (the Sprint Goal), what can be done this Sprint (selected items), and how the chosen work will get done (the plan). These three topics shape the Sprint Backlog.

  117. Question 117Scrum Events and Artifacts

    A Scrum Team wants to change its Definition of Done mid-Sprint. What is the appropriate guidance?

    1. The Product Owner may unilaterally lower it to ship faster
    2. It can only be changed at the Sprint Review with stakeholder approval
    3. The team may strengthen it, but it must never weaken below organizational standards Correct answer.
    4. Changes are not permitted once a Sprint has started

    Explanation

    The team may refine and strengthen the Definition of Done as it learns, but it cannot relax it below any organizational standard. A shared Definition of Done applies to all work in the Increment.

  118. Question 118Scrum Events and Artifacts

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

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

    Explanation

    The Sprint Retrospective is timeboxed to a maximum of three hours for a one-month Sprint. Shorter Sprints usually require a proportionally shorter Retrospective.

  119. Question 119Scrum Events and Artifacts

    A Product Owner wants to release value before the Sprint ends. Which statement aligns with Scrum?

    1. Release whenever the Increment meets the Definition of Done Correct answer.
    2. Release only with written approval from all stakeholders
    3. Release only at the end of a Sprint, never earlier
    4. Release only after the Sprint Review approves the Increment

    Explanation

    An Increment can be delivered to stakeholders before the end of a Sprint as long as it meets the Definition of Done. The Sprint Review should never be a gate that delays delivering value.

  120. Question 120Scrum Events and Artifacts

    During Sprint Planning, the Developers realize the selected work exceeds what they can complete. What is the most appropriate action?

    1. Commit to the full scope and rely on overtime to finish
    2. Extend the Sprint length by a few days to fit the work
    3. Ask the Scrum Master to assign additional Developers
    4. Negotiate with the Product Owner to reduce scope while preserving the Sprint Goal Correct answer.

    Explanation

    The Developers forecast what they can deliver and collaborate with the Product Owner to select a feasible amount of work. Scope can be adjusted during planning so the Sprint Goal remains achievable.

  121. Question 121Scrum Events and Artifacts

    Which statement correctly distinguishes the Sprint Review from the Sprint Retrospective?

    1. Both events inspect the Increment, but only the Retrospective involves stakeholders
    2. The Review inspects team process; the Retrospective inspects the product Increment
    3. The Review inspects the product Increment; the Retrospective inspects the team's process and interactions Correct answer.
    4. The Review is optional for mature teams, while the Retrospective is mandatory

    Explanation

    The Sprint Review focuses outward on the Increment and the Product Backlog with stakeholders, while the Retrospective focuses inward on how the team works and how to improve. Both are formal Scrum events.

  122. Question 122Scrum Events and Artifacts

    The Scrum Team delivers several Increments during a single Sprint. How does this affect the Sprint Review?

    1. All completed Increments may be inspected, since each is additive and usable Correct answer.
    2. Only the final Increment should be shown at the Review
    3. The Review must be skipped because value was already released
    4. The extra Increments must be rolled into the next Sprint Review

    Explanation

    Multiple Increments can be created within a Sprint, and each is additive to the others. The Sprint Review inspects the resulting Increment and progress toward the Product Goal.

  123. Question 123Scrum Events and Artifacts

    A stakeholder asks the Scrum Master to add an urgent item directly to the current Sprint Backlog. What is the most consistent Scrum response?

    1. Direct the request to the Product Owner, who may renegotiate Sprint scope with the Developers Correct answer.
    2. Hold the item until the next Sprint Retrospective
    3. Add it immediately because urgent work always takes priority
    4. Reject the request because the Sprint Backlog cannot change once the Sprint starts

    Explanation

    New requests flow through the Product Owner, who orders the Product Backlog and can renegotiate Sprint scope with the Developers. The Sprint Backlog may change as long as the Sprint Goal is not endangered.

  124. Question 124Scrum Events and Artifacts

    What is the maximum length of the Daily Scrum for a team whose Sprint lasts one month?

    1. As long as the Developers need
    2. Fifteen minutes Correct answer.
    3. One hour
    4. Thirty minutes

    Explanation

    The Daily Scrum is a 15-minute event for the Developers, and this timebox is fixed regardless of Sprint length. Shorter Sprints use the same 15-minute timebox; it does not scale with Sprint duration.

  125. Question 125Scrum Events and Artifacts

    Which artifact contains the Sprint Goal?

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

    Explanation

    The Sprint Goal is a commitment contained within the Sprint Backlog, alongside the selected Product Backlog items and the plan for delivering them. It gives the Sprint a single objective that the Developers work toward.

  126. Question 126Scrum Events and Artifacts

    Who is responsible for authoring and maintaining the Sprint Backlog during the Sprint?

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

    Explanation

    The Sprint Backlog is owned by the Developers; it is a highly visible real-time picture of the work they plan for the Sprint. They update it throughout the Sprint as more is learned.

  127. Question 127Scrum Events and Artifacts

    What is the primary purpose of the Daily Scrum?

    1. To inspect progress toward the Sprint Goal and adapt the Sprint Backlog Correct answer.
    2. To refine the Product Backlog with the Product Owner
    3. To demonstrate the working Increment to stakeholders
    4. To report status to the Scrum Master

    Explanation

    The Daily Scrum is an event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog accordingly. It is a planning and coordination event, not a status report to management.

  128. Question 128Scrum Events and Artifacts

    During the Sprint, how often should the Developers refine the Product Backlog?

    1. Continuously, at whatever cadence works for them Correct answer.
    2. Only when the Product Owner schedules a formal meeting
    3. Only during the Sprint Review
    4. Once per Sprint during Sprint Planning

    Explanation

    Refinement is an ongoing activity; the Scrum Team decides how and when it happens, and it can occur at any point during the Sprint. It is not tied to a single event or a fixed schedule.

  129. Question 129Scrum Events and Artifacts

    Which statement best describes the Sprint Review?

    1. It is a quality-control checkpoint run by the Scrum Master.
    2. It is an informal working session to inspect the Increment and adapt the Product Backlog. Correct answer.
    3. It is a meeting to assign action items to team members for the next Sprint.
    4. It is a formal gate where the Product Owner approves or rejects the Increment.

    Explanation

    The Sprint Review is an informal session where the Scrum Team and stakeholders inspect the outcome of the Sprint and collaborate on what to do next. It results in an adapted Product Backlog rather than a formal sign-off.

  130. Question 130Scrum Events and Artifacts

    What are the three artifacts defined in Scrum?

    1. Product Goal, Sprint Goal, and Definition of Done
    2. Product Backlog, Sprint Backlog, and Increment Correct answer.
    3. Sprint Backlog, Burndown Chart, and Increment
    4. Product Backlog, Sprint Goal, and Definition of Done

    Explanation

    Scrum defines exactly three artifacts: the Product Backlog, the Sprint Backlog, and the Increment. The Product Goal, Sprint Goal, and Definition of Done are commitments attached to those artifacts, not artifacts themselves.

  131. Question 131Scrum Events and Artifacts

    A Scrum Team works on a product where regulatory sign-off is required before anything can be released. How should this be reflected in the Definition of Done?

    1. It should be tracked only in the Sprint Review minutes.
    2. It should be added to the Definition of Done so every Increment meets the standard. Correct answer.
    3. It should be omitted because it is outside the Developers' control.
    4. It should be documented as a risk in the Sprint Backlog.

    Explanation

    The Definition of Done is the standard that every Increment must meet; if an organization requires regulatory sign-off for release, that criterion belongs in the Definition of Done. This keeps the Increment genuinely releasable at the end of each Sprint.

  132. Question 132Scrum Events and Artifacts

    A Developer wants to add a newly discovered task to the Sprint Backlog in the middle of the Sprint. What is the most appropriate action?

    1. Add it to the Sprint Backlog, since the Developers own and adapt it. Correct answer.
    2. Log it as a change request for the Sprint Review.
    3. Wait until the next Sprint Planning to add it.
    4. Ask the Product Owner to authorize the addition.

    Explanation

    The Developers own the Sprint Backlog and update it as they learn more during the Sprint. Adding newly discovered work needed to meet the Sprint Goal is a normal part of adapting the plan.

  133. Question 133Scrum Events and Artifacts

    The Developers discover during the Sprint that a selected Product Backlog item is far more complex than expected and they cannot finish it. What is the most appropriate action?

    1. Extend the Sprint by a few days to finish the item.
    2. Negotiate the scope of the Sprint with the Product Owner while keeping the Sprint Goal intact. Correct answer.
    3. Ask the Scrum Master to remove the item from the Sprint Backlog.
    4. Silently drop the item and say nothing until the Sprint Review.

    Explanation

    Scope may be clarified and renegotiated with the Product Owner as more is learned, as long as the Sprint Goal is not endangered. The Sprint itself is never extended; the team adapts its plan within the Sprint.

  134. Question 134Scrum Events and Artifacts

    How is the Sprint Backlog best described?

    1. A list of every task the Product Owner has requested.
    2. A forecast of all work for the entire product release.
    3. A fixed contract that cannot change once the Sprint begins.
    4. A plan by and for the Developers that emerges during the Sprint. Correct answer.

    Explanation

    The Sprint Backlog is composed of the Sprint Goal, the selected items, and the plan for delivering them, and it is created by and for the Developers. It is updated throughout the Sprint as more is learned.

  135. Question 135Scrum Events and Artifacts

    A team's Definition of Done is defined by the organization. The Developers want to add a stricter criterion for a particular Sprint. What is the appropriate guidance?

    1. They may not add criteria because the organizational definition is fixed.
    2. They must replace the organizational definition entirely.
    3. They must wait for the next release to change anything.
    4. They may add stricter criteria as long as the organizational minimum is still met. Correct answer.

    Explanation

    If the organization's Definition of Done is a standard, teams must meet it at minimum and may apply a stricter definition. They cannot weaken it, but adding rigor is permitted.

  136. Question 136Scrum Events and Artifacts

    During the Sprint Review, stakeholders raise several new ideas that would change the product's direction. What should happen with these ideas?

    1. They should be captured and considered for ordering in the Product Backlog. Correct answer.
    2. They should be rejected because they were not planned.
    3. They should be handled only by the Scrum Master after the meeting.
    4. They should be added directly to the current Sprint Backlog.

    Explanation

    The Sprint Review produces a revised Product Backlog that defines the probable items for the next Sprint. New ideas from stakeholders feed into that backlog and are ordered by the Product Owner.

  137. Question 137Scrum Events and Artifacts

    Which two artifacts are inspected during the Sprint Review?

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

    Explanation

    The Sprint Review inspects the outcome of the Sprint, which is the Increment, and adapts the Product Backlog for the next Sprint. The Sprint Backlog is the Developers' internal plan and is not the focus of the Review.

  138. Question 138Scrum Events and Artifacts

    A Scrum Team's Sprint is two weeks long. What is the timebox for its Sprint Retrospective?

    1. Two hours
    2. Three hours
    3. Forty-five minutes
    4. One and a half hours Correct answer.

    Explanation

    The Retrospective is timeboxed to a maximum of three hours for a one-month Sprint. For shorter Sprints the event is usually shorter, so a two-week Sprint commonly uses about 90 minutes.

  139. Question 139Scrum Events and Artifacts

    The Developers realize during the Daily Scrum that they are behind on the Sprint Goal. What is the most appropriate outcome of the event?

    1. A decision to cancel the Sprint.
    2. A report to the Product Owner explaining the delay.
    3. An adapted Sprint Backlog and a plan for the next day's work. Correct answer.
    4. A request to extend the Sprint by one day.

    Explanation

    The Daily Scrum exists so the Developers can inspect progress toward the Sprint Goal and adapt the Sprint Backlog. The output is an updated plan for the coming day, not a status report or a change to the Sprint's timebox.

  140. Question 140Scrum Events and Artifacts

    What is the Product Goal?

    1. A metric used to measure team velocity.
    2. A commitment that describes a future state of the product. Correct answer.
    3. A list of features to be delivered in the next Sprint.
    4. A document that records stakeholder feedback.

    Explanation

    The Product Goal is the commitment attached to the Product Backlog and describes a future state of the product that serves as a target. It provides focus and context for the work in the Product Backlog.

  141. Question 141Scrum Events and Artifacts

    A Product Owner wants to change the Product Backlog ordering in the middle of a Sprint. What is the appropriate guidance?

    1. Reordering requires approval from the Scrum Master.
    2. The Product Owner may reorder the Product Backlog at any time. Correct answer.
    3. Reordering must wait until the Sprint Retrospective.
    4. Reordering is allowed only at Sprint Planning.

    Explanation

    The Product Owner is accountable for ordering the Product Backlog and may do so whenever it improves value. The current Sprint's work is protected by its Sprint Goal, but the Product Backlog itself is continuously refined and reordered.

  142. Question 142Scrum Events and Artifacts

    During Sprint Planning, the Developers must decide how much work to select. Which factor is most important in that decision?

    1. The number of items the Product Owner wants completed.
    2. The team's capacity and its ability to meet the Definition of Done. Correct answer.
    3. The team's historical velocity compared with other teams.
    4. The size of the Increment that stakeholders expect.

    Explanation

    The Developers select how much work they can complete based on their capacity and their ability to meet the Definition of Done. The forecast is theirs to make, informed by past performance but not dictated by others.

  143. Question 143Scrum Events and Artifacts

    A Scrum Team produces an Increment that meets the Definition of Done halfway through the Sprint. What does Scrum say about this?

    1. The Definition of Done must be re-evaluated before release.
    2. The Increment must be held until the Sprint Review to be shown.
    3. The Increment may be released to stakeholders before the Sprint ends. Correct answer.
    4. The team must stop work and begin the next Sprint.

    Explanation

    An Increment that meets the Definition of Done is usable and may be released at any time, even before the Sprint ends. Scrum does not require waiting for the Sprint Review to deliver value.

  144. Question 144Scrum Events and Artifacts

    Which statement best captures why the Sprint Backlog is sometimes described as a 'highly visible real-time picture' of the Developers' work?

    1. It is displayed publicly so managers can monitor productivity.
    2. It is finalized at Sprint Planning and then locked.
    3. It is updated continuously as the Developers learn more during the Sprint. Correct answer.
    4. It is archived at the end of each Sprint for audit purposes.

    Explanation

    The Sprint Backlog emerges during the Sprint and is updated continuously as the Developers learn more about the work needed to meet the Sprint Goal. This ongoing adaptation is what makes it a real-time picture of the plan.

  145. Question 145Scrum Events and Artifacts

    A Scrum Team completes all selected Product Backlog items, but one item does not meet the Definition of Done. How should the work be treated at the Sprint Review?

    1. It is counted as part of the Increment because the item was completed.
    2. It is added to the next Sprint Backlog automatically.
    3. It is presented to stakeholders for a release decision.
    4. It is not part of the Increment and returns to the Product Backlog for reordering. Correct answer.

    Explanation

    Work that does not meet the Definition of Done cannot be considered part of the Increment and is not presented as done. It typically returns to the Product Backlog, where the Product Owner can reorder it.

  146. Question 146Scrum Events and Artifacts

    The Developers want to use the Daily Scrum to discuss detailed technical design for an hour each day. What is the most accurate guidance?

    1. The Daily Scrum may be skipped when the team is busy.
    2. The Daily Scrum must stay within 15 minutes; deeper discussions should happen afterward. Correct answer.
    3. The Daily Scrum may be replaced by written status updates.
    4. The Daily Scrum may be extended if the Developers agree.

    Explanation

    The Daily Scrum is timeboxed to 15 minutes for the Developers to inspect progress and adapt the plan. Detailed technical discussions can follow the event, but they are not part of the timeboxed Daily Scrum.

  147. Question 147Scrum Master Accountabilities and Professional Scrum

    Which of the following best describes the Scrum Master's accountability for the Scrum Team's effectiveness?

    1. Assigning daily tasks to each Developer
    2. Enabling the team to improve its practices and effectiveness Correct answer.
    3. Approving the Definition of Done for the team
    4. Reporting team velocity to stakeholders each Sprint

    Explanation

    The Scrum Master is accountable for establishing Scrum and for the Scrum Team's effectiveness, which includes coaching the team toward improvement. Task assignment, DoD approval, and reporting velocity are not Scrum Master accountabilities.

  148. Question 148Scrum Master Accountabilities and Professional Scrum

    A Scrum Master notices that the Product Owner is overwhelmed with stakeholder requests. What is the most appropriate Scrum Master action?

    1. Ask the Developers to prioritize the stakeholders' requests
    2. Escalate to management to reduce stakeholder contact with the Product Owner
    3. Coach the Product Owner on ordering the Product Backlog and engaging stakeholders Correct answer.
    4. Take over Product Backlog management to lighten the load

    Explanation

    The Scrum Master serves the Product Owner by coaching on Product Backlog management and stakeholder engagement techniques. Taking over the backlog or shielding the Product Owner from stakeholders undermines the Product Owner's accountability.

  149. Question 149Scrum Master Accountabilities and Professional Scrum

    Which statement accurately reflects the Scrum Master's relationship to the Scrum Team's self-management?

    1. The Scrum Master assigns a technical lead to guide each Sprint
    2. The Scrum Master coaches the team to self-manage rather than directing its work Correct answer.
    3. The Scrum Master acts as the team's lead and resolves internal disagreements
    4. The Scrum Master decides which team members attend which events

    Explanation

    Scrum Teams are self-managing, and the Scrum Master's role is to coach and enable self-management rather than direct the work. Resolving disagreements, choosing attendees, and appointing technical leads all reduce the team's self-management.

  150. Question 150Scrum Master Accountabilities and Professional Scrum

    The Scrum Master is helping the Scrum Team and organization adopt an empirical approach. Which action best demonstrates this?

    1. Encouraging transparency and inspecting outcomes to adapt the process Correct answer.
    2. Ensuring every Sprint follows an identical set of steps
    3. Documenting a fixed process that the team must follow exactly
    4. Measuring success only by the number of Sprints completed

    Explanation

    Empiricism rests on transparency, inspection, and adaptation so the team can adjust based on what it learns. A rigid, identical process or a count of Sprints does not reflect empirical decision-making.

  151. Question 151Scrum Master Accountabilities and Professional Scrum

    During a Sprint Retrospective, two Developers argue heatedly and the discussion stalls. What should the Scrum Master do?

    1. Decide the improvement on behalf of the team
    2. Report the conflict to the team's manager for disciplinary action
    3. Facilitate the conversation so the team can address the conflict and agree on improvements Correct answer.
    4. End the Retrospective early to avoid further conflict

    Explanation

    The Scrum Master facilitates events and coaches the team in managing conflict so it can reach its own improvements. Ending the event, deciding for the team, or escalating to management removes the team's ownership.

  152. Question 152Scrum Master Accountabilities and Professional Scrum

    What does the Scrum Master primarily remove for the Scrum Team?

    1. Sprint Backlog items that are too large
    2. Technical debt accumulated by the Developers
    3. Product requirements that are unclear to stakeholders
    4. Impediments that hinder the team's progress Correct answer.

    Explanation

    A core Scrum Master service is helping the team by removing impediments to its progress. Requirements, technical debt, and backlog item sizing are matters owned by the Product Owner or Developers.

  153. Question 153Scrum Master Accountabilities and Professional Scrum

    A Scrum Master wants to help the organization understand Scrum. Which action best fits this service?

    1. Instructing every department to reorganize into Scrum Teams immediately
    2. Writing the organization's product strategy on behalf of leadership
    3. Leading the organization in its Scrum adoption and advising on Scrum implementation Correct answer.
    4. Mandating that all teams hold identical Daily Scrums

    Explanation

    The Scrum Master serves the organization by leading, training, and coaching its Scrum adoption and advising on implementation. Mandating reorganizations, writing strategy, or forcing identical practices exceeds the role.

  154. Question 154Scrum Master Accountabilities and Professional Scrum

    Which behavior most clearly indicates that a Scrum Master is enabling Developer self-management?

    1. Selecting which Developer owns each Product Backlog item
    2. Approving the Developers' estimates before the Sprint begins
    3. Setting the team's working hours and meeting schedule
    4. Letting the Developers decide how to organize their work within the Sprint Correct answer.

    Explanation

    Self-managing Developers choose how to organize and perform their work. Assigning owners, setting schedules, and approving estimates all take decisions away from the Developers.

  155. Question 155Scrum Master Accountabilities and Professional Scrum

    A Scrum Master is coaching the Scrum Team on focusing on the current Sprint's goal. Which situation should the Scrum Master address?

    1. Developers pulling in unplanned work that distracts from the Sprint Goal Correct answer.
    2. The Product Owner refining backlog items for future Sprints
    3. The team inspecting its progress toward the Sprint Goal daily
    4. Developers collaborating with stakeholders on feedback

    Explanation

    Coaching toward focus means helping the team keep attention on the Sprint Goal and avoid distractions. Backlog refinement, daily inspection, and stakeholder collaboration all support the Sprint rather than distract from it.

  156. Question 156Scrum Master Accountabilities and Professional Scrum

    How does the Scrum Master best support the Developers in their accountability for quality?

    1. Coaching them to hold each other accountable for a Definition of Done they create Correct answer.
    2. Signing off on completed work before it is shown at the Sprint Review
    3. Reviewing each increment to confirm it meets the Definition of Done
    4. Defining technical standards the Developers must follow

    Explanation

    The Developers create the Definition of Done and are accountable for quality; the Scrum Master coaches them to hold each other accountable. Defining standards, reviewing increments, and signing off remove that accountability from the Developers.

  157. Question 157Scrum Master Accountabilities and Professional Scrum

    Which statement best describes the Scrum Master's stance toward the Scrum Team's decisions?

    1. The Scrum Master requires consensus before any decision is made
    2. The Scrum Master respects the team's decisions and helps it learn from outcomes Correct answer.
    3. The Scrum Master documents decisions for management approval
    4. The Scrum Master overrides decisions that seem risky

    Explanation

    The Scrum Master coaches the team and lets it own its decisions, helping it learn from results. Overriding decisions, seeking management approval, or imposing consensus undermines self-management.

  158. Question 158Scrum Master Accountabilities and Professional Scrum

    A Scrum Master notices the Daily Scrum has become a status report to a manager who attends. What is the best action?

    1. Ask the manager to run the Daily Scrum more efficiently
    2. Cancel the Daily Scrum until the manager stops attending
    3. Move the Daily Scrum to a time the manager cannot attend
    4. Coach the team and manager so the Daily Scrum remains a Developers' event for planning the day Correct answer.

    Explanation

    The Daily Scrum is an event for the Developers to inspect progress and plan the next day's work. Coaching the team and the manager preserves the event's purpose without cancelling or avoiding the issue.

  159. Question 159Scrum Master Accountabilities and Professional Scrum

    What is the Scrum Master's role in the Sprint Planning event?

    1. Ensuring the event happens and is kept within its timebox while the team plans Correct answer.
    2. Estimating the effort for each selected Product Backlog item
    3. Writing the Sprint Goal on behalf of the Product Owner
    4. Deciding which items the team will commit to for the Sprint

    Explanation

    The Scrum Master ensures Scrum events take place and stay within their timeboxes, but the content of planning belongs to the Scrum Team. Selecting items, estimating, and crafting the Sprint Goal are team activities.

  160. Question 160Scrum Master Accountabilities and Professional Scrum

    A Scrum Master is asked by a stakeholder to add an urgent item directly to the Sprint Backlog. What is the most appropriate response?

    1. Ask the Developers to work overtime to fit the item in
    2. Reject the request because the Sprint scope cannot change
    3. Add the item to the Sprint Backlog since the request is urgent
    4. Direct the stakeholder to the Product Owner to discuss ordering the Product Backlog Correct answer.

    Explanation

    Only the Product Owner orders the Product Backlog, and new requests should flow through that accountability. Adding items directly, mandating overtime, or flatly rejecting the request bypasses the Product Owner and the team's ability to decide.

  161. Question 161Scrum Master Accountabilities and Professional Scrum

    Which of the following best illustrates the Scrum Master serving the Scrum Team?

    1. Deciding when the team should adopt new tools
    2. Prioritizing the Product Backlog on the team's behalf
    3. Coaching the team in self-management and helping it focus on creating high-value Increments Correct answer.
    4. Approving which team members may speak at the Sprint Review

    Explanation

    Serving the Scrum Team includes coaching self-management, helping the team focus, and supporting the creation of high-value Increments. Backlog ordering, controlling participation, and mandating tools are outside that service.

  162. Question 162Scrum Master Accountabilities and Professional Scrum

    The Scrum Master observes that the team consistently skips the Sprint Retrospective because of time pressure. What should the Scrum Master do?

    1. Reinforce that the Retrospective is a required event and help the team make it effective Correct answer.
    2. Combine the Retrospective with the Sprint Review to save time
    3. Allow the team to skip it since the team is self-managing
    4. Shorten the Retrospective to five minutes permanently

    Explanation

    The Scrum Master ensures Scrum events take place as prescribed; the Retrospective is a required event. Allowing it to be skipped, merging it with the Review, or truncating it undermines the team's opportunity to improve.

  163. Question 163Scrum Master Accountabilities and Professional Scrum

    What does it mean that the Scrum Master is a "servant-leader"?

    1. The Scrum Master takes orders from the Developers on all process decisions
    2. The Scrum Master serves as the team's manager and approves its work
    3. The Scrum Master serves stakeholders by reporting on team performance
    4. The Scrum Master leads by serving the Scrum Team and organization rather than by directing Correct answer.

    Explanation

    Servant-leadership means the Scrum Master leads through service to the team and organization, not through command or control. Acting as a manager, taking orders, or reporting performance mischaracterizes the role.

  164. Question 164Scrum Master Accountabilities and Professional Scrum

    A Scrum Master is coaching a newly formed team that keeps waiting for instructions. Which coaching approach best fosters self-management?

    1. Provide detailed instructions until the team is comfortable deciding
    2. Assign a rotating leader each Sprint to direct the team
    3. Set up an approval step so the Scrum Master can review team decisions
    4. Help the team discover how to make its own decisions and own the outcomes Correct answer.

    Explanation

    Coaching self-management means guiding the team to make its own decisions and take ownership of outcomes. Providing instructions, assigning leaders, or adding approval steps keeps the team dependent.

  165. Question 165Scrum Master Accountabilities and Professional Scrum

    Which action shows the Scrum Master helping the organization understand the Scrum Team's boundaries and autonomy?

    1. Permitting stakeholders to change the Sprint Goal at will
    2. Allowing managers to reassign Developers between teams mid-Sprint
    3. Educating stakeholders about why they should not direct the Developers' daily work Correct answer.
    4. Encouraging functional managers to approve Sprint Backlog items

    Explanation

    The Scrum Master educates the organization about Scrum so stakeholders respect the team's autonomy and self-management. Allowing reassignment, goal changes at will, or manager approval violates the team's boundaries.

  166. Question 166Scrum Master Accountabilities and Professional Scrum

    The Scrum Master is facilitating a team's adoption of transparency. Which practice best supports transparency?

    1. Making the Product Backlog, Sprint Backlog, and Increment visible and understood by those doing the work Correct answer.
    2. Reporting progress only at the end of the release
    3. Keeping the Definition of Done private to the Developers
    4. Sharing only positive metrics with stakeholders

    Explanation

    Transparency requires that key artifacts be visible and understood by those accountable for them. Selective metrics, a hidden Definition of Done, or end-of-release reporting all reduce transparency.

  167. Question 167Scrum Master Accountabilities and Professional Scrum

    A Scrum Master is asked to help two teams that constantly blame each other for integration failures. What is the most useful Scrum Master action?

    1. Tell each team separately to stop blaming the other
    2. Facilitate a joint session so both teams can surface the problem and agree on shared improvements Correct answer.
    3. Assign one team to own integration so responsibility is clear
    4. Escalate to management to determine which team is at fault

    Explanation

    The Scrum Master facilitates collaboration and helps teams address cross-team conflict so they can agree on improvements. Separating the teams, assigning blame, or unilaterally reassigning ownership does not build shared accountability.

  168. Question 168Scrum Master Accountabilities and Professional Scrum

    Which statement best captures the Scrum Master's accountability regarding Scrum events?

    1. Personally running every event from start to finish
    2. Extending timeboxes whenever the team needs more time
    3. Ensuring all events take place and are kept within their timeboxes Correct answer.
    4. Deciding which events the team may skip

    Explanation

    The Scrum Master ensures the Scrum events take place and are kept within their timeboxes. Running every event, allowing skips, or extending timeboxes at will conflicts with that accountability.

  169. Question 169Scrum Master Accountabilities and Professional Scrum

    A Product Owner wants to skip the Sprint Review because the Increment is incomplete. How should the Scrum Master respond?

    1. Encourage holding the Sprint Review to inspect the Increment and gather feedback Correct answer.
    2. Agree to cancel the event so stakeholders do not see incomplete work
    3. Reschedule the Sprint Review to the next Sprint
    4. Ask the Developers to finish the Increment before any Review occurs

    Explanation

    The Sprint Review is a required event for inspecting the Increment and adapting the Product Backlog, and it is valuable even when work is incomplete. Cancelling, deferring, or demanding completion before the Review undermines inspection and feedback.

  170. Question 170Scrum Master Accountabilities and Professional Scrum

    Which behavior is most consistent with the Scrum Master acting as a coach rather than a director?

    1. Asking questions that help the team reflect and find its own solutions Correct answer.
    2. Telling the team the single best way to run its Sprints
    3. Choosing which improvements the team should implement
    4. Setting performance targets the team must meet

    Explanation

    Coaching uses questions and reflection to help the team find its own solutions and take ownership. Dictating practices, setting targets, or choosing improvements are directive behaviors inconsistent with coaching.

  171. Question 171Scrum Master Accountabilities and Professional Scrum

    The Scrum Master notices that the team's Definition of Done is not being met but the Increment is still presented as complete. What is the most appropriate action?

    1. Lower the Definition of Done so the Increment qualifies as complete
    2. Raise the transparency issue with the team and Product Owner so the gap is addressed Correct answer.
    3. Report the team to management for delivering incomplete work
    4. Quietly fix the work so the Increment meets the Definition of Done

    Explanation

    When work is presented as complete without meeting the Definition of Done, transparency is compromised; the Scrum Master surfaces this with the team and Product Owner. Fixing it quietly, escalating punitively, or weakening the Definition of Done does not restore honest transparency.

  172. Question 172Scrum Master Accountabilities and Professional Scrum

    According to the Scrum Guide, which two areas does the Scrum Master serve?

    1. The stakeholders and the competitors
    2. The Product Owner and the finance department
    3. The Developers and the customers
    4. The Scrum Team and the larger organization Correct answer.

    Explanation

    The Scrum Master serves the Scrum Team in several ways and also serves the organization by helping it adopt and understand Scrum. This dual focus is the core of the accountability.

  173. Question 173Scrum Master Accountabilities and Professional Scrum

    A Scrum Master is helping the Product Owner find techniques for effective Product Goal definition and Product Backlog management. Which service area does this belong to?

    1. Serving external stakeholders
    2. Serving the Developers only
    3. Serving the organization
    4. Serving the Scrum Team Correct answer.

    Explanation

    Coaching the Product Owner on Product Goal definition and backlog management is part of serving the Scrum Team. The Scrum Master helps the whole team, including the Product Owner, work effectively.

  174. Question 174Scrum Master Accountabilities and Professional Scrum

    Which accountability does the Scrum Guide assign specifically to the Scrum Master?

    1. Establishing Scrum as defined in the Scrum Guide Correct answer.
    2. Maximizing the value of the product
    3. Managing the Product Backlog ordering
    4. Approving which items enter the Sprint

    Explanation

    The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, by helping everyone understand Scrum theory and practice. The other listed accountabilities belong to the Product Owner.

  175. Question 175Scrum Master Accountabilities and Professional Scrum

    A Scrum Master is coaching the Scrum Team on how to be more effective and on self-management. Which Scrum value is most directly being enacted when the team takes ownership of its own decisions?

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

    Explanation

    Self-management and ownership of decisions reflect the value of Commitment, where the team commits to achieving its goals and supporting one another. Commitment is about dedicating to the team's goals and accepting the work.

  176. Question 176Scrum Master Accountabilities and Professional Scrum

    A Scrum Master wants to demonstrate servant-leadership while facilitating a conflict between two Developers. Which action best reflects this stance?

    1. Ask the Developers to work it out privately without support
    2. Decide the resolution and instruct both Developers to follow it
    3. Escalate to the Product Owner to impose a decision
    4. Help the Developers surface the issue and choose their own resolution Correct answer.

    Explanation

    Servant-leadership means putting the team's needs first and helping them grow their own problem-solving capacity rather than solving problems for them. Facilitating the conversation while leaving the decision with the Developers supports self-management.

  177. Question 177Scrum Master Accountabilities and Professional Scrum

    A Scrum Master notices that a manager outside the Scrum Team is assigning tasks directly to individual Developers. What is the most appropriate first response?

    1. Coach the manager on how that behavior affects the team's self-management Correct answer.
    2. Report the manager to human resources
    3. Take over the task assignment personally
    4. Tell the Developers to ignore the manager

    Explanation

    Serving the organization includes helping people outside the Scrum Team understand how to interact with it in ways that support self-management. Coaching the manager addresses the root cause while preserving relationships.

  178. Question 178Scrum Master Accountabilities and Professional Scrum

    What does the Scrum Master do to help the Scrum Team improve its practices within the Scrum framework?

    1. Coaches the team and facilitates continuous improvement Correct answer.
    2. Assigns each Developer a specific improvement task
    3. Schedules mandatory overtime to catch up
    4. Writes the team's improvement backlog for them

    Explanation

    The Scrum Master coaches the team on Scrum practices and helps it continually improve. The team itself decides and owns its improvements.

  179. Question 179Scrum Master Accountabilities and Professional Scrum

    A Scrum Master is asked to be the sole person who updates the team's Scrum board so it stays accurate. What is the best response?

    1. Accept, but only update it weekly
    2. Decline and let the Developers maintain their own transparency Correct answer.
    3. Accept, since accuracy matters most
    4. Decline and ask the Product Owner to update it

    Explanation

    Transparency is created by those doing the work, so the Developers should make their work visible. The Scrum Master coaches the team on transparency rather than becoming the record keeper.

  180. Question 180Scrum Master Accountabilities and Professional Scrum

    Which activity best describes the Scrum Master helping the organization remove barriers between stakeholders and the Scrum Team?

    1. Serving the organization Correct answer.
    2. Serving the customers
    3. Serving the Developers
    4. Serving the Product Owner

    Explanation

    Removing barriers between stakeholders and the Scrum Team is part of the Scrum Master's service to the organization, alongside leading and training on Scrum adoption.

  181. Question 181Scrum Master Accountabilities and Professional Scrum

    A Scrum Master is helping the Developers become more cross-functional. Which action best supports this goal?

    1. Keeping each Developer in a single specialty to maximize efficiency
    2. Encouraging Developers to learn skills outside their specialty so the team can deliver end to end Correct answer.
    3. Hiring a specialist to cover gaps permanently
    4. Reassigning work so only one Developer touches each area

    Explanation

    Cross-functionality means the team has all the skills needed to deliver a valuable Increment without depending on others. Encouraging skill growth across specialties builds that capability.

  182. Question 182Scrum Master Accountabilities and Professional Scrum

    Which statement best reflects the Scrum Master's authority over the Scrum Team?

    1. The Scrum Master has authority to approve the team's technical decisions
    2. The Scrum Master can override the Product Owner on backlog ordering
    3. The Scrum Master leads through influence and coaching rather than command Correct answer.
    4. The Scrum Master directs which Developers attend each event

    Explanation

    The Scrum Master is a true leader who serves the team and organization, leading by example and influence rather than by positional authority over the work. Decisions about the work belong to the team and Product Owner.

  183. Question 183Scrum Master Accountabilities and Professional Scrum

    A Scrum Master is preparing to teach a new group of employees the basics of Scrum theory. Which approach best fits the Scrum Master's service to the organization?

    1. Writing the group's Product Backlog for them
    2. Taking over the group's Daily Scrum
    3. Approving the group's Sprint Goals
    4. Leading, training, and coaching the organization in its Scrum adoption Correct answer.

    Explanation

    Serving the organization includes leading, training, and coaching it in Scrum adoption and helping employees and stakeholders understand Scrum. The Scrum Master does not take over the team's work.

  184. Question 184Scrum Master Accountabilities and Professional Scrum

    A Scrum Master observes that the Scrum Team relies on the Scrum Master to decide when to call in outside help. Which coaching move best builds self-management?

    1. Tell the team to never seek outside help
    2. Ask the team to define when and how it will seek outside help Correct answer.
    3. Escalate every request to management
    4. Keep deciding so the team avoids mistakes

    Explanation

    Building self-management means helping the team establish its own agreements and decision rules. Having the team define its escalation approach keeps ownership with the team.

  185. Question 185Scrum Master Accountabilities and Professional Scrum

    Which behavior shows the Scrum Master fostering an environment of psychological safety within the Scrum Team?

    1. Rewarding Developers who never raise problems
    2. Reporting individual mistakes to managers
    3. Discouraging dissent during the Retrospective
    4. Encouraging the team to surface risks and mistakes openly Correct answer.

    Explanation

    Psychological safety lets people speak up about problems and mistakes without fear, which supports transparency and improvement. The Scrum Master fosters this by welcoming open discussion.

  186. Question 186Scrum Master Accountabilities and Professional Scrum

    A Scrum Master is asked by the team to always facilitate the Retrospective so it stays efficient. How should the Scrum Master respond?

    1. Refuse to ever help with the Retrospective
    2. Coach the team to eventually facilitate and own its own Retrospective Correct answer.
    3. Agree to always run it to save the team time
    4. Hand the Retrospective permanently to the Product Owner

    Explanation

    The Scrum Master facilitates as needed but aims to grow the team's ability to run its own events. Coaching the team toward ownership builds self-management over time.

  187. Question 187Scrum Master Accountabilities and Professional Scrum

    Which outcome best indicates that a Scrum Master is succeeding in serving the Scrum Team?

    1. The team waits for the Scrum Master before starting events
    2. The Scrum Master approves all Sprint Backlog changes
    3. The team increasingly manages its own work and improves its practices Correct answer.
    4. The Scrum Master is present in every decision the team makes

    Explanation

    Effective Scrum Masters work themselves out of a job by helping the team become self-managing and continuously improving. Increased team ownership signals success.

  188. Question 188Scrum Master Accountabilities and Professional Scrum

    A Scrum Master notices that the Developers are bypassing the Product Owner and taking direction from a senior stakeholder. What is the most useful action?

    1. Take over the Product Owner's backlog decisions
    2. Coach the Developers to route product decisions through the Product Owner Correct answer.
    3. Tell the stakeholder to stop talking to the Developers entirely
    4. Join the Developers in taking the stakeholder's direction

    Explanation

    The Product Owner is accountable for maximizing value and ordering the backlog, so product direction should flow through that role. The Scrum Master coaches the team and organization to respect that boundary.

  189. Question 189Scrum Master Accountabilities and Professional Scrum

    Which practice most helps a Scrum Master help the organization understand the Scrum Team's autonomy?

    1. Publishing a list of tasks each Developer will do
    2. Explaining to stakeholders how the team selects its own work Correct answer.
    3. Requiring stakeholders to approve each Sprint's scope
    4. Having the Scrum Master approve all team decisions

    Explanation

    Helping the organization understand that the team selects its own work clarifies the boundary between stakeholders and the team. This education is part of serving the organization.

  190. Question 190Scrum Master Accountabilities and Professional Scrum

    What is the Scrum Master accountable for regarding the Scrum framework itself?

    1. Adapting the framework to whatever the team prefers
    2. Adding roles to speed up delivery
    3. Removing events that take too long
    4. Ensuring Scrum is understood and enacted as described Correct answer.

    Explanation

    The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, helping everyone understand and enact it. Tailoring that abandons the framework's rules is not the Scrum Master's role.

  191. Question 191Scrum Master Accountabilities and Professional Scrum

    A Scrum Master is helping the Developers understand how to focus on creating a valuable, useful Increment each Sprint. Which service is this?

    1. Serving the finance team
    2. Serving the customers
    3. Serving the competitors
    4. Serving the Developers Correct answer.

    Explanation

    Helping the Developers focus on high-value Increments and on removing impediments to progress is part of serving the Developers.

  192. Question 192Scrum Master Accountabilities and Professional Scrum

    A Scrum Master wants to help the Scrum Team adopt empiricism. Which action best supports this?

    1. Hiding unfavorable data from stakeholders
    2. Relying on the original plan regardless of new information
    3. Making decisions based on what is transparently observed in the work Correct answer.
    4. Setting Sprint Goals without inspecting past results

    Explanation

    Empiricism holds that decisions are based on observation of transparent facts. The Scrum Master supports this by encouraging inspection of real work and adapting decisions accordingly.

  193. Question 193Scrum Master Accountabilities and Professional Scrum

    A Scrum Master notices the Developers are reluctant to raise impediments because they fear blame. Which action best serves the team?

    1. Wait for impediments to resolve on their own
    2. Create a safe way to surface impediments and coach the team on using it Correct answer.
    3. Report each impediment to senior management
    4. Require written justification for every impediment

    Explanation

    The Scrum Master helps the team remove impediments to progress and fosters an environment where problems can be raised safely. Building a safe channel and coaching its use serves that goal.

  194. Question 194Scrum Master Accountabilities and Professional Scrum

    Which statement best describes how a Scrum Master serves the Product Owner?

    1. By deciding which features maximize value
    2. By attending every stakeholder meeting in place of the Product Owner
    3. By ordering the Product Backlog on the Product Owner's behalf
    4. By helping establish empirical product planning for complex environments Correct answer.

    Explanation

    Serving the Product Owner includes helping establish empirical product planning and facilitating stakeholder collaboration. The Scrum Master supports the role without taking over its accountabilities.

  195. Question 195Scrum Master Accountabilities and Professional Scrum

    A Scrum Master is coaching a team that blames individuals whenever a Sprint Goal is missed. Which approach best reflects the Scrum Master's accountability?

    1. Help the team inspect its system and process rather than blame individuals Correct answer.
    2. Identify the weakest Developer and recommend replacement
    3. Set individual performance targets for each Developer
    4. Add more status meetings to monitor individuals

    Explanation

    The Scrum Master coaches the team to improve as a whole by inspecting its process and environment rather than singling out people. This supports a culture of continuous improvement and safety.

  196. Question 196Scrum Master Accountabilities and Professional Scrum

    What does it mean that the Scrum Master is accountable for the Scrum Team's effectiveness?

    1. The Scrum Master personally delivers the team's work
    2. The Scrum Master helps the team improve its practices and effectiveness Correct answer.
    3. The Scrum Master evaluates each Developer's output
    4. The Scrum Master sets the team's Sprint Goals

    Explanation

    The Scrum Master is accountable for the Scrum Team's effectiveness, which means coaching and enabling the team to improve how it works. The team still performs and owns its work.

PSM I flashcards

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

Three pillars of empiricism
Transparency, inspection, and adaptation. Together they enable decisions based on observed evidence; if any pillar is weak, artifacts and progress become unreliable.
Definition of Scrum values
Commitment, focus, openness, respect, and courage. These five values guide the Scrum Team's behavior and support trust, which underpins empirical process control.
Empiricism definition
A theory asserting that knowledge comes from experience and decisions are made on observed evidence. Scrum applies it through short cycles of inspect and adapt.
Purpose of transparency
A shared, common understanding of the work and its state. Without it, inspection is misleading and adaptation produces decisions that reduce value and raise risk.
Lean thinking in Scrum
A foundation alongside empiricism that reduces waste and focuses on essentials. It keeps the framework minimal and directs effort toward value delivery.
Iterative and incremental delivery
Scrum delivers a usable Increment each Sprint, repeatedly refining the product. This maximizes early feedback and reduces risk from long development cycles.
Why Scrum is incomplete
Scrum defines only the minimum needed to make its processes effective. Teams add practices, templates, and tools as needed rather than following prescribed methods.
Inspection constraint
Inspection must be frequent enough to detect undesirable variance but not so frequent that it disrupts the work. Scrum events are the defined inspection points.
Adaptation trigger
If inspection reveals that a process aspect or product deviates beyond acceptable limits, the process or product must be adjusted as soon as possible.
Three Scrum accountabilities
Product Owner, Scrum Master, and Developers. Together they form one Scrum Team; Scrum defines no other formal roles or sub-teams.
Scrum Team size
Ten or fewer people, self-managing as one unit. Smaller teams communicate better; larger groups need more coordination and are split into multiple teams.
Product Owner accountability
Maximizing product value by effectively managing and ordering the Product Backlog. The Product Owner is one person, may delegate work, but stays accountable.
Scrum Master accountability
Establishing Scrum as defined in the Scrum Guide and improving team effectiveness. The role is a servant-leader and coach, not a project or people manager.
Developer accountability
Creating a usable Increment each Sprint, instilling quality, and self-managing their own work. Developers own the Sprint Backlog and adapt their plan daily.
Product Owner and Product Goal
The Product Owner owns and communicates the Product Goal, the long-term objective for the product that guides backlog ordering and Sprint Goals.
Organization and Product Owner
The wider organization must respect the Product Owner's decisions. The Product Owner may delegate tasks but remains the single accountable person.
No sub-teams rule
The Scrum Team contains no sub-teams or hierarchies. Accountability for outcomes and value delivery is shared across the whole team.
Self-managing Scrum Team
The team decides internally who does what, when, and how. This replaces external direction with the team's own planning and adaptation.
Sprint container event
The Sprint is a fixed period of one month or less that contains all other events. A new Sprint begins immediately after the previous one ends.
Five Scrum events
Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Each has a maximum timebox, a purpose, and participants defined by the framework.
Sprint Planning purpose
It answers why, what, and how for the Sprint and produces the Sprint Goal and Sprint Backlog. Timebox is a maximum of eight hours for a one-month Sprint.
Daily Scrum purpose
A 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is a planning event, not a status report.
Sprint Review purpose
A working session, maximum four hours for a one-month Sprint, where the Increment is inspected and the Product Backlog is adapted with stakeholders.
Sprint Retrospective purpose
A maximum three-hour event for a one-month Sprint that plans ways to increase quality and effectiveness. Top improvements may enter the next Sprint Backlog.
Three Scrum artifacts
Product Backlog, Sprint Backlog, and Increment. Each represents work or value and is designed to maximize transparency of key information.
Artifact commitments
Product Goal commits to the Product Backlog, Sprint Goal to the Sprint Backlog, and Definition of Done to the Increment. Commitments reinforce focus and measure progress.
Definition of Done
A formal description of the Increment's quality state. Work not meeting it is not Done and returns to the Product Backlog for future rework.
Sprint Goal function
A single objective for the Sprint that provides focus and flexibility. It guides Developer planning and is the subject of Daily Scrum inspection.
Scrum Master service to team
Coaching self-management, helping the team focus on valuable Increments, facilitating impediment removal, and ensuring Scrum events are positive and productive.
Scrum Master service to organization
Leading and training Scrum adoption, planning implementation, removing barriers between stakeholders and teams, and helping employees and stakeholders understand empiricism.
Scrum Master service to Product Owner
Helping find techniques for effective Product Backlog management and facilitating stakeholder collaboration as requested or needed, without taking over product decisions.
Professional Scrum emphasis
Professional Scrum stresses empiricism, self-management, and continuous improvement. It values judgment and evidence over rigid prescribed processes or certificates.

PSM I study guide

Scrum Framework and Theory

The empirical core

Scrum is a lightweight framework built on empiricism and lean thinking. Empiricism says knowledge comes from experience and decisions are made on what is observed. Three pillars support it: transparency (the work and process are visible to those accountable for the outcome), inspection (artifacts and progress are checked frequently), and adaptation (adjustment happens quickly when results deviate). Each pillar only works if the one before it does - inspection without transparency is theater, adaptation without inspection is guesswork.

The five values - commitment, focus, openness, respect, courage - are not decoration; questions often test whether a behavior supports or undermines them.

Traps to watch

  • Confusing the framework (fixed: accountabilities, events, artifacts and their rules) with practices (tailorable: estimation technique, tooling, definition of ready).
  • Treating Scrum as a methodology or a process with prescribed technical practices. Scrum deliberately leaves how to the team.
  • Believing transparency means "anyone can see the board." It means a shared, common understanding of what is being done and why.
  • Forgetting that the Definition of Done is the primary instrument of transparency about the increment.

Rule of thumb

When a question asks what to do about a problem, prefer the answer that makes information visible to the people who own the decision over the answer that fixes it for them. Empiricism favors exposing the issue to the accountable role, then adapting the plan at the next suitable event.

Worked example

A stakeholder asks the Scrum Master to add a defect-tracking column to the board so they can see quality. Better answer: ensure the Definition of Done makes quality criteria explicit and that the increment meets it - transparency about the increment, not a new artifact outside the framework.

Scrum Roles and Accountabilities

Three accountabilities, no sub-teams

The Scrum Team is one self-managing, cross-functional unit of ten or fewer people with three accountabilities.

Product Owner - maximizes value by managing the Product Backlog: clearly expressing items, ordering them, and ensuring the team understands them. The PO is one person, not a committee, and is accountable for the what and why. The PO may delegate work but remains accountable.

Scrum Master - accountable for the Scrum Team's effectiveness. Serves the team (coaching self-management, removing impediments), the Product Owner (helping with backlog technique and stakeholder collaboration), and the organization (leading Scrum adoption, removing friction between teams and stakeholders). The SM is a true leader who serves, not a project manager or a secretary.

Developers - the people committed to creating any aspect of a usable Increment each Sprint. They self-manage how to do the work and hold all technical accountabilities.

Traps to watch

  • "Who decides?" The PO orders the backlog; the Developers decide how much they take on and how to build it; nobody tells them how.
  • "Can the SM assign tasks?" No - that is self-management violated.
  • "Can the PO attend the Daily Scrum?" May attend, but must not direct the Developers' plan.
  • "Who can cancel a Sprint?" Only the Product Owner, and only if the Sprint Goal becomes obsolete.
  • Titles like "team lead" or "proxy PO" are not Scrum accountabilities.

Rule of thumb

Match the decision to the accountability: value and ordering → Product Owner; how and how much → Developers; process, effectiveness and impediments → Scrum Master.

Worked example

A manager asks the Scrum Master to reassign developers to hit a date. Correct response: the SM coaches the manager on self-management and helps the Developers and PO re-plan through the backlog, rather than issuing assignments.

Scrum Events and Artifacts

The five events

The Sprint is the container - fixed length of one month or less, with no gaps between Sprints. All other events exist to support it.

  • Sprint Planning - why (Sprint Goal), what (selected backlog items), how (plan). Timeboxed to eight hours for a one-month Sprint.
  • Daily Scrum - 15 minutes, for the Developers, to inspect progress toward the Sprint Goal and adapt the plan. It is not a status report to anyone.
  • Sprint Review - inspect the Increment with stakeholders and adapt the Product Backlog. It is a working session, not a demo or a gate.
  • Sprint Retrospective - inspect how the last Sprint went regarding people, process, tools and Definition of Done; identify improvements.

The three artifacts and their commitments

Product Backlog → Product Goal; Sprint Backlog → Sprint Goal; Increment → Definition of Done. Each artifact has a commitment that gives it focus and transparency. The Sprint Backlog is a plan by and for the Developers and updates during the Sprint.

Traps to watch

  • Events are timeboxed, not targets - ending early is fine if the purpose is met.
  • The Sprint Review is about the product, the Retrospective about the process; don't swap them.
  • The Daily Scrum is not the only time Developers may meet or adapt their plan.
  • Timeboxes scale with Sprint length; a shorter Sprint shortens every event proportionally.

Rule of thumb

Ask "which artifact does this event inspect, and which commitment does it serve?" If the answer is unclear, the proposed activity probably belongs inside an existing event.

Worked example

A team wants a separate "bug triage" meeting. Better: handle triage inside refinement of the Product Backlog, and let the Sprint Review adapt the backlog based on stakeholder feedback.

Scrum Master Accountabilities and Professional Scrum

Serving three directions

The Scrum Master is accountable for the Scrum Team's effectiveness. That shows up as service to the team (coaching self-management and cross-functionality, causing the removal of impediments, ensuring events are positive, productive and kept within timebox), to the Product Owner (helping find techniques for effective goal and backlog management, facilitating stakeholder collaboration), and to the organization (leading, training and coaching Scrum adoption; planning and advising on implementation; removing barriers between stakeholders and teams).

Professional Scrum mindset

The exam rewards a servant-leader, coaching stance. The SM does not command, does not own the backlog, does not assign work, and does not act as a gatekeeper between the team and stakeholders. When something is wrong, the SM makes the problem visible, teaches the why behind the framework, and lets those accountable decide - while still protecting the team's ability to self-manage.

Traps to watch

  • Doing instead of coaching - "the SM reorganizes the board" is usually wrong; "the SM helps the team see the problem and choose" is usually right.
  • Removing impediments means causing them to be removed, which may include escalation, not personally fixing everything.
  • Protecting the Sprint does not mean shielding the team from all feedback; it means protecting the Sprint Goal from unmanaged change.
  • Confusing the SM with a project manager, tech lead, or HR function.

Rule of thumb

For any scenario, ask: "Does this action increase the team's ability to solve the problem itself?" If yes, it is likely the intended answer. If it solves it for them and removes their ownership, it usually is not.

Worked example

A team keeps overcommitting. Weak answer: the SM caps the Sprint Backlog. Strong answer: the SM facilitates the Retrospective so the team examines why, and coaches them on using the Sprint Goal and past data to forecast - the team owns the fix.

PSM I cheat sheet

Quick reference

Scrum Framework and Theory

  • Scrum is a lightweight framework founded on empiricism and lean thinking; empiricism asserts knowledge comes from experience and decisions are made on observed evidence.

  • The three empirical pillars are transparency, inspection, and adaptation; if any pillar is missing, the resulting artifacts and progress are unreliable.

  • Scrum is built on three process-control pillars plus five values: commitment, focus, openness, respect, and courage.

  • The framework is intentionally incomplete; it defines only the minimum required to make its processes and roles effective, leaving practices to the team.

  • Scrum is deliberately iterative and incremental, delivering a usable Increment each Sprint to maximize opportunities for feedback.

  • Lean thinking in Scrum reduces waste and focuses on essentials; it is one of the two theoretical foundations alongside empiricism.

  • Transparency requires a shared, common understanding of work; low transparency leads to decisions that diminish value and increase risk.

  • Inspection must be frequent enough to detect undesirable variance without disrupting the work itself; Scrum events are the inspection points.

  • Adaptation follows inspection: if a process aspect or product deviates beyond acceptable limits, the process or product must be adjusted as soon as possible.

Quick reference

Scrum Roles and Accountabilities

  • Scrum defines exactly three accountabilities: Product Owner, Scrum Master, and Developers; together they form the Scrum Team.

  • The Scrum Team is one self-managing unit of ten or fewer people; smaller teams communicate better, and larger teams need more coordination.

  • Product Owner accountability: maximize product value by managing and ordering the Product Backlog effectively; the PO is one person, not a committee.

  • The Product Owner owns the Product Goal and may delegate work but remains accountable; the entire organization must respect the PO's decisions.

  • Scrum Master accountability: establish Scrum as defined in the Scrum Guide and improve team effectiveness through coaching, teaching, and facilitation.

  • The Scrum Master is a true leader who serves the Scrum Team and the wider organization; the role is not a project manager or a people manager.

  • Developers are accountable for creating a usable Increment each Sprint, instilling quality, and self-managing their own work.

  • Developers own the Sprint Backlog and adapt their plan daily; only Developers create the Increment, though they may involve others.

  • No sub-teams or hierarchies exist inside the Scrum Team; accountability is shared for the whole team's outcomes and value delivery.

Quick reference

Scrum Events and Artifacts

  • The Sprint is the container event for all other events; it is a fixed length of one month or less, and a new Sprint starts immediately after the previous one.

  • Five events exist: Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective; each has a maximum timebox and a clear purpose.

  • Sprint Planning (max 8 hours for a one-month Sprint) answers why, what, and how; it produces the Sprint Goal and the Sprint Backlog.

  • The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog; it is not a status meeting.

  • The Sprint Review (max 4 hours) inspects the Increment and adapts the Product Backlog; it is a working session, not a presentation.

  • The Sprint Retrospective (max 3 hours) plans ways to increase quality and effectiveness; the most impactful improvements may be added to the next Sprint Backlog.

  • Three artifacts exist: Product Backlog, Sprint Backlog, and Increment; each has a commitment: Product Goal, Sprint Goal, and Definition of Done.

  • The Definition of Done is a formal description of the Increment's quality state; if an item is not Done, it returns to the Product Backlog for rework.

  • Artifacts represent work or value and are designed to maximize transparency; commitments attach to them to reinforce focus and measure progress.

Quick reference

Scrum Master Accountabilities and Professional Scrum

  • The Scrum Master serves the Scrum Team by coaching self-management, helping focus on valuable Increments, and facilitating removal of impediments.

  • The Scrum Master serves the Product Owner by helping find effective Product Backlog management techniques and facilitating stakeholder collaboration.

  • The Scrum Master serves the organization by leading Scrum adoption, removing barriers between stakeholders and teams, and planning Scrum implementation.

  • The Scrum Master causes removal of impediments but does not act as the team's decision-maker; the team remains self-managing.

  • Professional Scrum emphasizes empiricism, self-management, and continuous improvement over prescribed processes or certifications.

  • The Scrum Master teaches and coaches Scrum in both the team and the organization, ensuring the framework is understood and enacted.

  • A key Scrum Master activity is facilitating Scrum events as requested or needed, keeping them timeboxed and productive without controlling content.

  • The Scrum Master helps the team and organization become more empirical by increasing transparency and enabling frequent inspection and adaptation.

Quick reference

Scrum Framework and Theory

  • Scrum is a lightweight framework founded on empiricism and lean thinking; empiricism asserts knowledge comes from experience and decisions are made on observed evidence.

  • The three empirical pillars are transparency, inspection, and adaptation; if any pillar is missing, the resulting artifacts and progress are unreliable.

  • Scrum is built on three process-control pillars plus five values: commitment, focus, openness, respect, and courage.

  • The framework is intentionally incomplete; it defines only the minimum required to make its processes and roles effective, leaving practices to the team.

  • Scrum is deliberately iterative and incremental, delivering a usable Increment each Sprint to maximize opportunities for feedback.

  • Lean thinking in Scrum reduces waste and focuses on essentials; it is one of the two theoretical foundations alongside empiricism.

  • Transparency requires a shared, common understanding of work; low transparency leads to decisions that diminish value and increase risk.

  • Inspection must be frequent enough to detect undesirable variance without disrupting the work itself; Scrum events are the inspection points.

  • Adaptation follows inspection: if a process aspect or product deviates beyond acceptable limits, the process or product must be adjusted as soon as possible.

Quick reference

Scrum Roles and Accountabilities

  • Scrum defines exactly three accountabilities: Product Owner, Scrum Master, and Developers; together they form the Scrum Team.

  • The Scrum Team is one self-managing unit of ten or fewer people; smaller teams communicate better, and larger teams need more coordination.

  • Product Owner accountability: maximize product value by managing and ordering the Product Backlog effectively; the PO is one person, not a committee.

  • The Product Owner owns the Product Goal and may delegate work but remains accountable; the entire organization must respect the PO's decisions.

  • Scrum Master accountability: establish Scrum as defined in the Scrum Guide and improve team effectiveness through coaching, teaching, and facilitation.

  • The Scrum Master is a true leader who serves the Scrum Team and the wider organization; the role is not a project manager or a people manager.

  • Developers are accountable for creating a usable Increment each Sprint, instilling quality, and self-managing their own work.

  • Developers own the Sprint Backlog and adapt their plan daily; only Developers create the Increment, though they may involve others.

  • No sub-teams or hierarchies exist inside the Scrum Team; accountability is shared for the whole team's outcomes and value delivery.

Quick reference

Scrum Events and Artifacts

  • The Sprint is the container event for all other events; it is a fixed length of one month or less, and a new Sprint starts immediately after the previous one.

  • Five events exist: Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective; each has a maximum timebox and a clear purpose.

  • Sprint Planning (max 8 hours for a one-month Sprint) answers why, what, and how; it produces the Sprint Goal and the Sprint Backlog.

  • The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog; it is not a status meeting.

  • The Sprint Review (max 4 hours) inspects the Increment and adapts the Product Backlog; it is a working session, not a presentation.

  • The Sprint Retrospective (max 3 hours) plans ways to increase quality and effectiveness; the most impactful improvements may be added to the next Sprint Backlog.

  • Three artifacts exist: Product Backlog, Sprint Backlog, and Increment; each has a commitment: Product Goal, Sprint Goal, and Definition of Done.

  • The Definition of Done is a formal description of the Increment's quality state; if an item is not Done, it returns to the Product Backlog for rework.

  • Artifacts represent work or value and are designed to maximize transparency; commitments attach to them to reinforce focus and measure progress.

Quick reference

Scrum Master Accountabilities and Professional Scrum

  • The Scrum Master serves the Scrum Team by coaching self-management, helping focus on valuable Increments, and facilitating removal of impediments.

  • The Scrum Master serves the Product Owner by helping find effective Product Backlog management techniques and facilitating stakeholder collaboration.

  • The Scrum Master serves the organization by leading Scrum adoption, removing barriers between stakeholders and teams, and planning Scrum implementation.

  • The Scrum Master causes removal of impediments but does not act as the team's decision-maker; the team remains self-managing.

  • Professional Scrum emphasizes empiricism, self-management, and continuous improvement over prescribed processes or certifications.

  • The Scrum Master teaches and coaches Scrum in both the team and the organization, ensuring the framework is understood and enacted.

  • A key Scrum Master activity is facilitating Scrum events as requested or needed, keeping them timeboxed and productive without controlling content.

  • The Scrum Master helps the team and organization become more empirical by increasing transparency and enabling frequent inspection and adaptation.

Quick reference

Scrum Framework and Theory

  • Scrum is a lightweight framework founded on empiricism and lean thinking; empiricism asserts knowledge comes from experience and decisions are made on observed evidence.

  • The three empirical pillars are transparency, inspection, and adaptation; if any pillar is missing, the resulting artifacts and progress are unreliable.

  • Scrum is built on three process-control pillars plus five values: commitment, focus, openness, respect, and courage.

  • The framework is intentionally incomplete; it defines only the minimum required to make its processes and roles effective, leaving practices to the team.

  • Scrum is deliberately iterative and incremental, delivering a usable Increment each Sprint to maximize opportunities for feedback.

  • Lean thinking in Scrum reduces waste and focuses on essentials; it is one of the two theoretical foundations alongside empiricism.

  • Transparency requires a shared, common understanding of work; low transparency leads to decisions that diminish value and increase risk.

  • Inspection must be frequent enough to detect undesirable variance without disrupting the work itself; Scrum events are the inspection points.

  • Adaptation follows inspection: if a process aspect or product deviates beyond acceptable limits, the process or product must be adjusted as soon as possible.

Quick reference

Scrum Roles and Accountabilities

  • Scrum defines exactly three accountabilities: Product Owner, Scrum Master, and Developers; together they form the Scrum Team.

  • The Scrum Team is one self-managing unit of ten or fewer people; smaller teams communicate better, and larger teams need more coordination.

  • Product Owner accountability: maximize product value by managing and ordering the Product Backlog effectively; the PO is one person, not a committee.

  • The Product Owner owns the Product Goal and may delegate work but remains accountable; the entire organization must respect the PO's decisions.

  • Scrum Master accountability: establish Scrum as defined in the Scrum Guide and improve team effectiveness through coaching, teaching, and facilitation.

  • The Scrum Master is a true leader who serves the Scrum Team and the wider organization; the role is not a project manager or a people manager.

  • Developers are accountable for creating a usable Increment each Sprint, instilling quality, and self-managing their own work.

  • Developers own the Sprint Backlog and adapt their plan daily; only Developers create the Increment, though they may involve others.

  • No sub-teams or hierarchies exist inside the Scrum Team; accountability is shared for the whole team's outcomes and value delivery.

Quick reference

Scrum Events and Artifacts

  • The Sprint is the container event for all other events; it is a fixed length of one month or less, and a new Sprint starts immediately after the previous one.

  • Five events exist: Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective; each has a maximum timebox and a clear purpose.

  • Sprint Planning (max 8 hours for a one-month Sprint) answers why, what, and how; it produces the Sprint Goal and the Sprint Backlog.

  • The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog; it is not a status meeting.

  • The Sprint Review (max 4 hours) inspects the Increment and adapts the Product Backlog; it is a working session, not a presentation.

  • The Sprint Retrospective (max 3 hours) plans ways to increase quality and effectiveness; the most impactful improvements may be added to the next Sprint Backlog.

  • Three artifacts exist: Product Backlog, Sprint Backlog, and Increment; each has a commitment: Product Goal, Sprint Goal, and Definition of Done.

  • The Definition of Done is a formal description of the Increment's quality state; if an item is not Done, it returns to the Product Backlog for rework.

  • Artifacts represent work or value and are designed to maximize transparency; commitments attach to them to reinforce focus and measure progress.

Quick reference

Scrum Master Accountabilities and Professional Scrum

  • The Scrum Master serves the Scrum Team by coaching self-management, helping focus on valuable Increments, and facilitating removal of impediments.

  • The Scrum Master serves the Product Owner by helping find effective Product Backlog management techniques and facilitating stakeholder collaboration.

  • The Scrum Master serves the organization by leading Scrum adoption, removing barriers between stakeholders and teams, and planning Scrum implementation.

  • The Scrum Master causes removal of impediments but does not act as the team's decision-maker; the team remains self-managing.

  • Professional Scrum emphasizes empiricism, self-management, and continuous improvement over prescribed processes or certifications.

  • The Scrum Master teaches and coaches Scrum in both the team and the organization, ensuring the framework is understood and enacted.

  • A key Scrum Master activity is facilitating Scrum events as requested or needed, keeping them timeboxed and productive without controlling content.

  • The Scrum Master helps the team and organization become more empirical by increasing transparency and enabling frequent inspection and adaptation.

PSM I key terms

Empiricism

The approach of basing decisions on what is observed, experienced, and measured rather than on theory or prediction. In Scrum, progress is assessed from actual evidence so that the team can adapt to reality.

Related: Inspection, Adaptation, Transparency
Transparency

The property of making the process, work, and outcomes visible to everyone doing or receiving the work. Without it, inspection produces misleading conclusions and adaptation leads the team in the wrong direction.

Related: Empiricism, Inspection, Artifact
Inspection

The regular, careful examination of Scrum artifacts and progress toward agreed goals. It is frequent enough to detect unwanted deviation early but not so frequent that it disrupts the work itself.

Related: Transparency, Adaptation, Sprint Review
Adaptation

Adjusting process or work as soon as inspection reveals that one or more aspects are unacceptable or off course. The team changes what it does, not just what it says, to stay on target.

Related: Empiricism, Inspection, Sprint Retrospective
Lean Thinking

A mindset that focuses on reducing waste, limiting work in progress, and delivering value continuously. It underpins Scrum's emphasis on small batches, flow, and respecting people.

Related: Scrum Values, Sprint
Scrum Values

Commitment, Focus, Openness, Respect, and Courage. These five qualities guide how team members behave and make the empirical pillars of transparency, inspection, and adaptation possible in practice.

Related: Empiricism, Scrum Team
Scrum Team

A small, self-managing group made up of one Scrum Master, one Product Owner, and Developers. The whole team is collectively accountable for delivering a valuable, useful Increment each Sprint.

Related: Product Owner, Scrum Master, Developers
Product Owner

The single person accountable for maximizing the value of the product resulting from the Scrum Team's work. This role owns the Product Goal, orders the Product Backlog, and decides what the team builds next.

Related: Product Backlog, Product Goal, Scrum Team
Scrum Master

The person accountable for establishing Scrum as described in the Scrum Guide and for the team's effectiveness. This role serves the team and organization by coaching, teaching, and removing impediments rather than directing work.

Related: Scrum Team, Servant Leadership, Impediment
Developers

The team members who create any aspect of a usable Increment each Sprint. They self-manage their work, decide how to turn backlog items into value, and hold each other accountable as professionals.

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

The characteristic of a Scrum Team that chooses internally who does what, when, and how. The team is given a goal and the authority to decide how to reach it, without a manager assigning tasks.

Related: Scrum Team, Sprint Backlog
Servant Leadership

A style of leading that puts the needs of the team and its customers first. The Scrum Master practices this by helping others grow, facilitating their success, and removing obstacles rather than commanding.

Related: Scrum Master, Impediment, Coaching
Coaching

Helping individuals and teams improve through questioning, feedback, and guided reflection rather than by giving answers or instructions. It is a core way a Scrum Master develops the team's capability over time.

Related: Servant Leadership, Scrum Master, Facilitation
Facilitation

Designing and guiding group interactions so participants can reach their own decisions and outcomes. The Scrum Master uses it to keep events productive without imposing content or controlling the discussion.

Related: Coaching, Scrum Events, Impediment
Impediment

Anything blocking or slowing the team's progress toward its goal. The Scrum Master helps the team identify and remove these obstacles, escalating beyond the team when the cause lies elsewhere.

Related: Servant Leadership, Scrum Master, Sprint
Scrum Events

The five formal ceremonies: the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Each has a purpose and a timebox, and together they create regularity and minimize unplanned meetings.

Related: Sprint, Timebox, Sprint Retrospective
Sprint

A fixed-length period of one month or less in which the team turns backlog items into a usable Increment. It is the container event inside which all other Scrum events occur.

Related: Scrum Events, Sprint Goal, Increment
Sprint Planning

The event that opens a Sprint, where the team agrees on why the Sprint is valuable, what can be delivered, and how the work will be done. It produces the Sprint Goal and the Sprint Backlog.

Related: Sprint Goal, Sprint Backlog, Sprint
Daily Scrum

A 15-minute event for the Developers, held each working day of the Sprint, to inspect progress toward the Sprint Goal and adapt the plan. It is for the Developers, not a status report to managers.

Related: Sprint Backlog, Sprint Goal, Developers
Sprint Review

A working session near the end of the Sprint where the team and stakeholders inspect the Increment and adapt the Product Backlog. Its purpose is collaboration and feedback, not a formal sign-off presentation.

Related: Increment, Product Backlog, Sprint Retrospective
Sprint Retrospective

The closing event of a Sprint, where the team inspects how it worked and identifies improvements to apply immediately. It focuses on people, process, tools, and the Definition of Done.

Related: Adaptation, Definition of Done, Sprint Review
Timebox

A fixed maximum amount of time set for an event or activity. The event ends when the timebox expires, which keeps Scrum events focused and prevents one topic from consuming unlimited discussion.

Related: Scrum Events, Daily Scrum
Artifact

One of the three things Scrum defines to represent work or value: the Product Backlog, the Sprint Backlog, and the Increment. Each carries a commitment that gives it focus and purpose.

Related: Product Backlog, Sprint Backlog, Increment
Product Backlog

An ordered, ever-evolving list of what is needed to improve the product. It is the single source of work for the team, and its ordering reflects value, risk, and priority as judged by the Product Owner.

Related: Product Owner, 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 picture of the work and is updated as more is learned during the Sprint.

Related: Sprint Planning, Sprint Goal, Daily Scrum
Increment

The sum of completed, usable work produced during a Sprint. Each Increment adds to previous ones, must be in a usable condition, and is delivered as soon as it meets the Definition of Done.

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

A long-term target describing a future state of the product that the team works toward. It gives direction to the Product Backlog and is the commitment associated with that artifact.

Related: Product Backlog, Product Owner, Sprint Goal
Sprint Goal

A single objective for the Sprint that explains why the Sprint is valuable. It gives the team focus and flexibility, and it is the commitment associated with the Sprint Backlog.

Related: Sprint Backlog, Sprint Planning, Sprint
Definition of Done

An agreed, shared description of the quality state an Increment must reach to be considered complete. It makes transparency real and is the commitment associated with the Increment.

Related: Increment, Sprint Retrospective, Transparency
Backlog Refinement

The ongoing activity of breaking down and clarifying Product Backlog items so they are ready for future Sprints. It is not a formal Scrum event, and the team decides how much time to spend on it.

Related: Product Backlog, Product Owner
Product Backlog Item

A single entry in the Product Backlog describing something of value to build, such as a feature, fix, or improvement. Items are ordered and refined until they are small enough to be done within a Sprint.

Related: Product Backlog, Backlog Refinement
Stakeholder

A person or group with an interest in the product, such as customers, users, or business sponsors. Stakeholders give feedback in the Sprint Review and influence the ordering of the Product Backlog.

Related: Sprint Review, Product Owner
Velocity

A measure of how much work a team completes per Sprint, often expressed in story points. It is a planning aid the team derives for itself, not a performance target imposed by others.

Related: Increment, Sprint
Story Point

A relative unit teams use to size backlog items by effort, complexity, and uncertainty rather than by clock time. Points support forecasting and conversation; they are not a measure of individual productivity.

Related: Velocity, Product Backlog Item
Burndown Chart

A visual showing work remaining over time within a Sprint or release. It helps the team inspect progress empirically and adapt its plan, but it is a tool, not a required Scrum artifact.

Related: Sprint Backlog, Velocity
Scrum Board

A physical or digital display of the Sprint Backlog, often organized into workflow columns. It makes work visible for inspection at the Daily Scrum, supporting transparency and self-management.

Related: Sprint Backlog, Daily Scrum, Transparency
Professional Scrum

The practice of Scrum with genuine mastery of the framework and its values, rather than mechanical ceremony-following. It emphasizes craftsmanship, continuous improvement, and honest empiricism over rigid process compliance.

Related: Scrum Values, Empiricism, Scrum Master

PSM I study plan

8 weeks · About 7 hours per week

Week 1

Scrum Framework and Theory

  • Define empirical process control and explain how transparency, inspection, and adaptation interlock

  • Distinguish the three pillars from the five Scrum values and give a workplace example of each value

  • Map the Scrum framework's accountabilities, events, and artifacts and state the purpose of each in one sentence

  • Identify which parts of Scrum are mandatory versus optional

Your checkpoint

A one-page hand-drawn diagram of the Scrum framework with a one-sentence purpose statement for every accountability, event, and artifact

Week 2

Scrum Framework and Theory & Scrum Events and Artifacts

  • Explain how each Scrum event exists to enable inspection and adaptation

  • Describe how the Sprint acts as a container for all other events and why a fixed length matters

  • Compare the Sprint Goal to the Definition of Done and state what each protects

  • Order the five events by timebox and justify each timebox

Your checkpoint

A table listing all five events with timebox, participants, purpose, and the artifact each one inspects

Week 3

Scrum Roles and Accountabilities

  • Contrast the Product Owner, Scrum Master, and Developers by accountability rather than job title

  • Explain why the Product Owner is one person and how that differs from a committee

  • Describe what Developers are accountable for as a self-managing group

  • Explain servant leadership and true facilitation as practiced by a Scrum Master

  • Distinguish a Scrum Master from a project manager and from a team lead

Your checkpoint

A three-column comparison write-up of the three accountabilities including two common misconceptions per role

Week 4

Scrum Events and Artifacts

  • Explain how the Product Backlog is refined and ordered and who is accountable for it

  • Distinguish Product Goal, Sprint Goal, and Definition of Done as commitments

  • Describe how the Sprint Backlog emerges during Sprint Planning

  • Explain why the Increment must be usable and how the Definition of Done creates transparency

Your checkpoint

A written scenario in which you correctly assign each backlog item, goal, and commitment to its artifact, checked against your week 1 diagram

Week 5

Scrum Master Accountabilities and Professional Scrum

  • Identify at least five ways a Scrum Master removes impediments without taking ownership of the work

  • Explain how a Scrum Master coaches the Product Owner on backlog management and value maximization

  • Describe how to help a team that is not self-managing without issuing directives

  • Explain how a Scrum Master protects the Sprint from scope changes mid-Sprint

Your checkpoint

A coaching log of five realistic impediment scenarios with a Scrum Master response for each, each response justified by a Scrum principle

Week 6

Scrum Master Accountabilities and Professional Scrum & Scrum Roles and Accountabilities

  • Explain how the Scrum Master serves the organization beyond the team

  • Describe how to facilitate a Retrospective that produces actionable improvements

  • Distinguish facilitation from instruction when helping a team adopt Scrum

  • Explain how a Scrum Master addresses a Product Owner who bypasses the Developers

Your checkpoint

A facilitation plan for one Retrospective, including format, timebox, and how you would handle a dominant participant

Week 7

Scrum Framework and Theory & Scrum Events and Artifacts

  • Trace how a change in the Definition of Done affects the Increment and transparency

  • Explain what happens when the Sprint Goal becomes obsolete and who decides

  • Describe the consequences of skipping refinement or retrospectives

  • Resolve at least ten scenario questions about events and artifacts using only the Scrum Guide's logic

Your checkpoint

A set of ten original scenario questions you wrote yourself, each with the correct answer and a one-line rule-based justification

Week 8

Scrum Roles and Accountabilities & Scrum Master Accountabilities and Professional Scrum

  • Review all four domains and close gaps flagged in earlier weeks

  • Practice explaining each accountability to a non-Scrum colleague in plain language

  • Diagnose common anti-patterns such as a Scrum Master assigning tasks or a Product Owner changing scope mid-Sprint

  • Confirm readiness by scoring consistently on original practice scenarios

Your checkpoint

A final self-assessment sheet rating confidence 1-5 in each domain, with a remediation note for any domain below 4

Milestones

Week 2: Can draw the full Scrum framework from memory and state the purpose of every element without notes

Week 4: Can correctly assign any artifact, goal, or commitment to its owner and explain why in one sentence

Week 6: Can respond to five impediment or coaching scenarios with principle-based answers, scoring at least 4 of 5

Week 8: Scores at least 85 percent on your own original scenario set across all four domains and has no domain rated below 4

PSM I exam day

Your checklist

Government-issued photo ID

Bring the exact ID type the provider names for your delivery mode. For online-proctored testing, the name on the ID must match your registration exactly. Confirm with the provider which ID types are accepted and whether a secondary ID is required.

Know your test delivery mode and login path

Confirm whether you are testing at a test center or online with a remote proctor, and how you will launch the exam (email link, account dashboard, or installed software). Do a dry run of the login path the day before. Confirm with the provider if anything is unclear.

Run the system/equipment check (online proctoring)

If testing remotely, complete any required system readiness check on the same computer and network you will use. Install required software ahead of time. Confirm minimum bandwidth and supported browsers/operating systems with the provider.

Quiet, private, well-lit room (online proctoring)

Use a space with a closed door, no other people, and a clear desk. Remove notes, books, second screens, and phones from the area. Proctors commonly require a room scan; confirm the specific rules with the provider.

Stable internet and a backup plan

Have a wired or reliable connection and a fallback (mobile hotspot or phone number for support). Know the provider's support contact before you start. Confirm reconnect/reschedule policy with the provider.

Note the start time in your local time zone

Convert the scheduled time to your local clock and plan to be ready early. Arrive/log in ahead of the appointment; confirm with the provider how early to check in and what happens if you are late.

Know the exam format and time budget

PSM I is a multiple-choice, closed-book assessment with a time limit. Confirm the current number of questions, time limit, and passing score on the official Scrum.org page before exam day, since these can change.

Prepare scratch materials only if allowed

Many proctored exams prohibit paper and pens. Do not assume scratch paper is permitted; confirm with the provider. If not allowed, practice doing the reasoning mentally.

Plan for breaks and physical needs

Eat, hydrate, and use the restroom before starting. Confirm with the provider whether any breaks are permitted and whether the clock stops during them.

Silence devices and notifications

Turn off phones, smartwatches, and desktop notifications, and close other applications. Unauthorized devices in the testing area can void a session.

Read the candidate agreement / rules in advance

Review the conduct and integrity rules you agreed to at registration. Confirm with the provider what is and is not allowed in your testing environment.

Know your result and retake process

Understand how results are reported and what the retake policy is. Confirm current retake terms with the provider rather than relying on memory.

Plan the day

Final 72 hours

Stop learning new material. Review the Scrum Guide end to end and re-read the sections you are least sure about, focusing on accountabilities, events, and artifacts and their commitments. Revisit your own notes on why each rule exists, not just what it says.

Final 72 hours

Do a timed practice set under exam-like conditions to calibrate your pacing. Review every wrong answer to find the underlying misunderstanding rather than memorizing the question.

Final 72 hours

Confirm logistics: appointment time in your local zone, delivery mode, ID requirements, and any software or system checks. Resolve open questions with the provider now, not on exam day.

Final 24 hours

Do a light review only: skim the Scrum Guide, your summary notes, and a short list of commonly confused distinctions (e.g., who owns what, which event serves which purpose). Then stop.

Final 24 hours

Prepare your environment and equipment: charge devices, test your connection, install or update required software, and set out your ID. Get a full night of sleep.

Morning of

Eat a normal meal, hydrate, and avoid cramming new material. Do a short, calm review of your one-page summary if it helps you settle.

Morning of

Set up your space and devices, close everything unnecessary, silence notifications, and log in ahead of your appointment time. Have your ID and support contact within reach.

During the test

Read each question fully and watch for qualifiers like 'best', 'most likely', 'not', and 'first'. Answer from the Scrum Guide's framework and values, not from your current workplace's habits.

During the test

Manage the clock: note your time limit and question count, set a rough per-question pace, and avoid getting stuck. Flag uncertain items and return to them if the format allows.

During the test

For scenario questions, identify the accountable role and the relevant event or artifact, then choose the option most consistent with empiricism, self-management, and focus on value. Eliminate answers that add process, roles, or artifacts the framework does not define.

During the test

Before submitting, review flagged questions and confirm you have answered all items. Submit, then follow the provider's process for receiving your result.

Rules to check

  • Bring the ID the provider requires and ensure the name matches your registration exactly; confirm accepted ID types and any secondary-ID requirement with the provider before exam day.

  • The exam is closed-book. Do not use notes, search engines, AI tools, messaging apps, or help from another person during the test; treat this as an integrity commitment.

  • Follow all proctor instructions, including room scans and showing your workspace if asked. If a proctor instruction conflicts with your assumptions, follow the proctor and confirm policy with the provider afterward.

  • Do not communicate with anyone during the session, and keep unauthorized devices out of the testing area. Doing so can invalidate your attempt.

  • Confirm break rules with the provider before starting; if breaks are not permitted, plan to complete the exam in one sitting and understand whether the timer runs continuously.

  • Understand the scoring before you begin: confirm the current question count, time limit, and passing threshold on the official provider page, as these details can change.

  • If you hit a technical problem, pause and contact provider support using the channel given at check-in rather than improvising; ask about reconnect or reschedule options.

  • Results and retake terms are set by the provider. Confirm how results are delivered and what the retake policy is rather than relying on secondhand information.

PSM I FAQ

How many Professional Scrum Master I practice questions are available?

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

How many Professional Scrum Master I flashcards are available?

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

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

The Professional Scrum Master I study material has 4 sections, including Scrum Framework and Theory, Scrum Roles and Accountabilities, and Scrum Events and Artifacts.

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

The catalog lists these item types: multiple choice for the Professional Scrum Master I exam.