First 50 of 198 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1Scrum theory and Professional Scrum
In Scrum, what does empiricism mean for how decisions are made?
- Decisions rest on the senior manager's judgement when the team cannot agree
- Decisions rest on the signed contract that fixes scope, cost, and date at the start
- Decisions rest on observation, experience, and experimentation rather than on up-front prediction Correct answer.
- Decisions rest on the detailed specification approved before development begins
Explanation
Empiricism holds that knowledge comes from experience and that decisions should be based on what is observed and tested. Scrum applies this through transparency, inspection, and adaptation so that plans are adjusted as evidence appears, rather than being locked in by prediction.
Question 2Scrum theory and Professional Scrum
Which three pillars underpin every element of Scrum?
- Planning, execution, and control
- Estimation, scheduling, and reporting
- Documentation, approval, and sign-off
- Transparency, inspection, and adaptation Correct answer.
Explanation
Scrum is founded on empiricism, and empiricism rests on the three pillars of transparency, inspection, and adaptation. Each Scrum event exists to enable inspection of a transparent artifact and to trigger adaptation when the outcome deviates.
Question 3Scrum theory and Professional Scrum
A team keeps its Sprint Backlog in a private spreadsheet that stakeholders cannot see, and the Increment is never demonstrated. Which pillar is most directly undermined?
- Adaptation
- Self-management
- Timeboxing
- Transparency Correct answer.
Explanation
Transparency requires that significant aspects of the process be visible to those responsible for the outcome, using a shared definition of what is being seen. Hidden work and an undemonstrated Increment prevent meaningful inspection, which in turn blocks useful adaptation.
Question 4Scrum theory and Professional Scrum
What is the primary purpose of inspection in Scrum?
- To confirm that every team member has completed assigned tasks
- To verify that the original scope has not changed
- To collect metrics for the annual performance review
- To detect undesirable variances in progress toward agreed goals Correct answer.
Explanation
Inspection means frequently examining Scrum artifacts and progress toward the Sprint Goal and Product Goal to detect undesirable variances. It is not a performance-audit mechanism, and inspection should be frequent enough to catch deviations early without getting in the way of the work.
Question 5Scrum theory and Professional Scrum
Who is accountable for maximizing the value of the product resulting from the Scrum Team's work?
- The Scrum Master
- The most senior developer
- The stakeholders who fund the product
- The Product Owner Correct answer.
Explanation
The Product Owner is accountable for maximizing product value and for effective Product Backlog management. The role carries decision authority over ordering and clarity of backlog items so that value is the guiding criterion.
Question 6Scrum theory and Professional Scrum
Which statement best describes the Scrum Master's accountability?
- Establishing Scrum as defined in the Scrum Guide and improving team effectiveness Correct answer.
- Approving the Definition of Done for the organization
- Maximizing the value delivered by each Increment
- Owning and ordering the Product Backlog
Explanation
The Scrum Master is accountable for the Scrum Team's effectiveness, coaching the team and the wider organization in Scrum theory and practice. This is a leadership and facilitation accountability, not a command role over the team's work.
Question 7Scrum theory and Professional Scrum
Within a Scrum Team, what does self-managing mean?
- The team decides who does what, when, and how Correct answer.
- The team decides which customers to serve without constraint
- The team may ignore the Definition of Done when under pressure
- The team sets its own salaries and working hours
Explanation
A self-managing Scrum Team internally decides who does what, when, and how. This autonomy applies to how the team turns backlog items into an Increment, while the Sprint Goal, Definition of Done, and organizational constraints still apply.
Question 8Scrum theory and Professional Scrum
A Scrum Team has eight developers, one Product Owner, and one Scrum Master. Which statement about its size is accurate?
- It must add a second Product Owner to balance the workload
- It exceeds the maximum because developers may not number more than five
- It is within the typical guidance of ten or fewer people in total Correct answer.
- It is too small to satisfy the rule of at least twelve members
Explanation
Scrum guidance suggests a Scrum Team of ten or fewer people in total; smaller teams communicate better and are more productive. This team totals ten, so it sits at the upper edge of that guidance rather than violating a hard cap.
Question 9Scrum theory and Professional Scrum
Which combination correctly lists the Scrum events?
- Sprint Planning, Daily Standup, Backlog Grooming, Sprint Review, and Release Retrospective
- The Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective Correct answer.
- Kickoff, Sprint Planning, Daily Scrum, Demo, and Sign-off
- The Sprint, Product Backlog Refinement, Daily Scrum, Sprint Review, and Retrospective
Explanation
Scrum defines five events: the Sprint, Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective. The Sprint is the container event within which the other four occur.
Question 10Scrum theory and Professional Scrum
What is the timebox for the Sprint Review when a Sprint lasts four weeks?
- A maximum of two hours
- A maximum of one hour
- A maximum of four hours Correct answer.
- A maximum of eight hours
Explanation
The Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint; shorter Sprints usually mean a shorter event. The timebox scales with Sprint length rather than being fixed regardless of duration.
Question 11Scrum theory and Professional Scrum
A team runs two-week Sprints. What is the maximum timebox for Sprint Planning?
- Four hours Correct answer.
- One hour
- Two hours
- Eight hours
Explanation
Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint, and it is typically shorter for shorter Sprints. For a two-week Sprint, a common proportional maximum is four hours.
Question 12Scrum theory and Professional Scrum
What is the maximum timebox for the Daily Scrum?
- Thirty minutes
- There is no timebox
- Fifteen minutes Correct answer.
- One hour
Explanation
The Daily Scrum is timeboxed to fifteen minutes for every Sprint length. It is a short event for developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog accordingly.
Question 13Scrum theory and Professional Scrum
Who is required to attend the Daily Scrum?
- The Product Owner and all stakeholders
- The developers of the Scrum Team Correct answer.
- The Scrum Master and the line managers
- Everyone in the organization who is interested
Explanation
The Daily Scrum is an event for the developers of the Scrum Team to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. Others may attend only if the developers find it useful, and attendance is never mandated for them.
Question 14Scrum theory and Professional Scrum
What is the purpose of the Sprint Retrospective?
- To obtain approval to release the current Increment
- To decide which backlog items enter the next Sprint
- To plan ways to increase quality and effectiveness Correct answer.
- To demonstrate the finished Increment to stakeholders
Explanation
The Sprint Retrospective is held to inspect how the last Sprint went regarding individuals, interactions, processes, tools, and the Definition of Done, and to identify the most helpful changes to improve effectiveness. Concrete improvements may be added to the Sprint Backlog for the next Sprint.
Question 15Scrum theory and Professional Scrum
A Scrum Team is halfway through a Sprint when a stakeholder asks for an urgent new feature. What does Scrum prescribe?
- The Sprint is cancelled automatically so the item can be planned
- The developers must immediately stop work and start the requested feature
- The Product Owner may renegotiate scope with the developers while the Sprint Goal stays intact Correct answer.
- The Scrum Master adds the item to the Sprint Backlog on the stakeholder's behalf
Explanation
During a Sprint, scope may be clarified and renegotiated with the Product Owner as more is learned, but the Sprint Goal and quality targets remain fixed. The Product Owner weighs the request against the Sprint Goal rather than letting it disrupt the Sprint arbitrarily.
Question 16Scrum theory and Professional Scrum
Under what condition may a Sprint be cancelled?
- When the Product Owner wants to add more backlog items
- When the developers fall behind the burndown line
- When the Sprint Goal becomes obsolete Correct answer.
- When a team member leaves the organization
Explanation
A Sprint can be cancelled only if the Sprint Goal becomes obsolete, and only the Product Owner has the authority to cancel. Cancellation consumes resources, so it is a rare decision, after which completed work is reviewed and potentially released.
Question 17Scrum theory and Professional Scrum
Which statement about the Sprint Goal is correct?
- It is written by the Scrum Master before Sprint Planning begins
- It replaces the Product Goal once the Sprint starts
- It is a single objective for the Sprint that provides focus and flexibility Correct answer.
- It is a fixed list of every backlog item committed for the Sprint
Explanation
The Sprint Goal is the single objective for the Sprint, created during Sprint Planning and giving the developers a shared focus while allowing flexibility on the exact work. It does not replace the longer-lived Product Goal.
Question 18Scrum theory and Professional Scrum
What is the Product Goal in Scrum?
- A commitment agreed with the customer that may not change
- A long-term objective describing a future state of the product that guides the Product Backlog Correct answer.
- A short statement of the revenue target for the next quarter
- A list of acceptance criteria attached to each backlog item
Explanation
The Product Goal describes a future state of the product that serves as a target for the Scrum Team to plan against. It is a commitment of the Product Backlog, is long-term, and may be updated as the team learns.
Question 19Scrum theory and Professional Scrum
Which artifact is described as a commitment by the developers to produce a usable Increment that meets the Definition of Done?
- The Product Goal
- The Sprint Goal
- The Sprint Backlog Correct answer.
- The Product Backlog
Explanation
The Sprint Backlog is composed of the Sprint Goal, the selected Product Backlog items, and the plan for delivering them; it is a highly visible real-time picture of the work and represents the developers' commitment to the Sprint Goal.
Question 20Scrum theory and Professional Scrum
What is the Definition of Done?
- A checklist the Product Owner uses to accept or reject individual developers' work
- A formal description of the state of the Increment when it meets the quality measures required for the product Correct answer.
- A schedule of test cases maintained by the quality assurance group
- A document listing every requirement the customer requested
Explanation
The Definition of Done is a formal description of the quality state required for the Increment, and the moment a backlog item meets it an Increment is born. If the organization has no standard, the Scrum Team creates one, and all work must satisfy it.
Question 21Scrum theory and Professional Scrum
A developer argues that an item is complete because coding is finished, even though the Definition of Done requires automated regression tests to pass. What is the correct Scrum position?
- The Scrum Master decides whether the Definition of Done applies to this item
- The item is not done and cannot be counted in the Increment until it meets the Definition of Done Correct answer.
- The Definition of Done can be waived for one Sprint to maintain velocity
- The item is done because the developer judges the code to be finished
Explanation
Work cannot be considered part of an Increment unless it meets the Definition of Done, which is applied uniformly to every backlog item. Partial work is returned to the Product Backlog for future consideration rather than being presented as complete.
Question 22Scrum theory and Professional Scrum
What does the Product Backlog represent?
- A frozen requirements baseline agreed at project start
- A schedule of releases approved by management
- A record of defects only, maintained by testers
- An emergent, ordered list of what is needed to improve the product Correct answer.
Explanation
The Product Backlog is an emergent, ordered list of what is needed to improve the product, and it is the single source of work undertaken by the Scrum Team. It is never complete and is refined continuously as understanding grows.
Question 23Scrum theory and Professional Scrum
Which statement about the Increment is accurate?
- It is the sum of the usable completed work produced during a Sprint and must meet the Definition of Done Correct answer.
- It is created only once at the end of the project
- It may be delivered to users only after the final Sprint Review
- It is a document describing what the team intends to build next
Explanation
An Increment is a concrete stepping stone toward the Product Goal, consisting of the usable work that meets the Definition of Done, and multiple Increments may be produced within a single Sprint. It is available for inspection and can be released before the Sprint ends.
Question 24Scrum theory and Professional Scrum
Why does Scrum prescribe timeboxes for its events?
- To guarantee that every event uses its full allotted duration
- To allow managers to compare teams by meeting length
- To replace the need for a Definition of Done
- To create regularity and to minimize the need for meetings that are not defined in Scrum Correct answer.
Explanation
Timeboxing creates regularity so that the team inspects and adapts on a predictable cadence, and it constrains events to the essential content. Events are containers for inspection and adaptation, not meetings that must run to their limit.
Question 25Scrum theory and Professional Scrum
A Product Owner repeatedly assigns tasks to individual developers and requires daily written status reports. Which Scrum principle does this most directly conflict with?
- The Scrum Team is self-managing and organizes its own work Correct answer.
- The Sprint Review must be held at the end of every Sprint
- The Definition of Done must be created by the organization
- The Product Backlog must be ordered by business value
Explanation
Self-management means the team internally decides who does what, when, and how, so task assignment by the Product Owner and mandated status reporting undercut it. The Product Owner focuses on what and why through backlog ordering, leaving the how to the developers.
Question 26Scrum theory and Professional Scrum
Which statement describes the three pillars of empirical process control in Scrum?
- Planning, execution, and closure
- Transparency, inspection, and adaptation Correct answer.
- Estimation, commitment, and control
- Documentation, approval, and audit
Explanation
Scrum is founded on empiricism, which rests on three pillars: transparency, inspection, and adaptation. Transparency means the process and work are visible to those doing and receiving it; inspection means artifacts and progress are frequently examined; adaptation means adjustments are made when inspection reveals deviation. The other triples describe generic project phases or bureaucratic controls, not Scrum's empirical foundation.
Question 27Scrum theory and Professional Scrum
According to Scrum theory, why is transparency essential to the empirical approach?
- It allows inspection to produce useful decisions based on a shared, accurate view of the work Correct answer.
- It ensures the team's velocity keeps increasing every Sprint
- It removes the need for a Definition of Done on the Increment
- It guarantees stakeholders approve every decision the team makes
Explanation
Inspection only yields good decisions if what is inspected is genuinely visible and understood the same way by everyone. Transparency therefore means a shared, accurate view of the artifacts and progress. Without it, inspection is based on a false picture and adaptation becomes misdirected.
Question 28Scrum theory and Professional Scrum
Which statement best captures the Scrum values adopted by the Scrum Team?
- Autonomy, hierarchy, documentation, control, and reporting
- Commitment, focus, openness, respect, and courage Correct answer.
- Innovation, efficiency, quality, profit, and growth
- Speed, competition, compliance, seniority, and secrecy
Explanation
Scrum is supported by five values: commitment, focus, openness, respect, and courage. These shape the behavior of the Scrum Team and make the empirical pillars work in practice. The other lists mix business goals, management controls, or organizational virtues that Scrum does not prescribe as its values.
Question 29Scrum theory and Professional Scrum
A Scrum Team is deciding how to organize its own work during a Sprint. Which Scrum value most directly supports team members speaking up about problems they see in how the work is being done?
- Respect
- Courage Correct answer.
- Commitment
- Focus
Explanation
Courage is the value that supports team members in raising difficult issues, admitting problems, and challenging the status quo. Focus concerns concentrating on the Sprint's work, respect concerns treating colleagues as capable people, and commitment concerns dedication to goals. When the question is about voicing uncomfortable truths, courage is the value at play.
Question 30Scrum theory and Professional Scrum
What does the term 'Scrum Team' refer to in the Scrum framework?
- The Scrum Master and Product Owner only, who manage the Developers
- Any group of people who attend the Sprint Review
- The Developers plus the stakeholders who fund the product
- A self-managing team of one Scrum Master, one Product Owner, and Developers Correct answer.
Explanation
The Scrum Team is a single self-managing unit consisting of one Scrum Master, one Product Owner, and Developers. There are no sub-teams or hierarchies within it. Stakeholders, managers, and customers are outside the Scrum Team even though the team interacts with them.
Question 31Scrum theory and Professional Scrum
A Scrum Team has a Scrum Master who also carries a large share of the development work each Sprint. How does Scrum theory regard this arrangement?
- It is forbidden because the Scrum Master must never touch the product work
- It is required, because the Scrum Master must model technical excellence for the team
- It is allowed only if the Product Owner approves it in writing each Sprint
- It is acceptable, since the Scrum Team is cross-functional and accountable as a whole Correct answer.
Explanation
Scrum does not prohibit a Scrum Master from contributing to development work; the framework emphasizes that the Scrum Team is cross-functional and collectively accountable. What matters is that the Scrum Master's accountability for establishing Scrum is still served. Scrum is intentionally lightweight and does not legislate such staffing details.
Question 32Scrum theory and Professional Scrum
In Scrum, what does 'cross-functional' mean for the Developers?
- The team depends on external specialists to finish the Increment
- Each developer works across several projects at the same time
- Every developer is certified in all technologies the product uses
- The team collectively has all the skills needed to create a valuable Increment each Sprint Correct answer.
Explanation
Cross-functional means the Developers as a group possess the skills necessary to create value each Sprint, so they are not dependent on people outside the team for their work. It describes collective capability, not individual certification or multitasking. Dependence on outside specialists for the Increment contradicts the idea.
Question 33Scrum theory and Professional Scrum
How does Scrum describe the relationship between the Product Owner and the Developers?
- The Product Owner directs the Developers by assigning them individual tasks
- The Product Owner sets daily work assignments while the Scrum Master approves them
- The Product Owner and Developers collaborate closely, with the Product Owner accountable for maximizing product value Correct answer.
- The Developers report to the Product Owner in a formal line-management hierarchy
Explanation
The Product Owner is accountable for maximizing the value of the product and manages the Product Backlog, while Developers decide how to turn backlog items into an Increment. They collaborate closely, but Scrum does not create a command-and-control task-assignment relationship or a line-management hierarchy. Daily work organization belongs to the Developers.
Question 34Scrum theory and Professional Scrum
Which statement about the Scrum Master's stance toward the Scrum Team is consistent with Scrum theory?
- The Scrum Master acts as the team's representative to management and reports its performance
- The Scrum Master directs the team's technical decisions to ensure quality
- The Scrum Master serves the team by coaching and removing impediments rather than commanding it Correct answer.
- The Scrum Master prioritizes the Product Backlog on the Product Owner's behalf
Explanation
The Scrum Master is a servant leader who helps the team and organization apply Scrum effectively, coaching and helping remove impediments. The Scrum Master does not command technical work, act as the team's reporting channel, or take over Product Backlog ordering. Those activities would undermine self-management and the Product Owner's accountability.
Question 35Scrum theory and Professional Scrum
A manager asks the Scrum Master to send weekly individual performance ratings of each Developer. Which response is most consistent with Scrum theory?
- Ask the Developers to rate each other and forward the results
- Decline, because Scrum has no role for reporting individual performance and the team is accountable collectively Correct answer.
- Provide the ratings, since managers own performance data
- Provide the ratings only for Developers who missed the Sprint Goal
Explanation
The Scrum Team is self-managing and collectively accountable for its work; Scrum does not create individual performance reporting through the Scrum Master. The Scrum Master serves the team and organization by helping them apply Scrum, which includes protecting the team from practices that undermine self-management. Supplying individual ratings, in any variant, contradicts that stance.
Question 36Scrum theory and Professional Scrum
Which statement about the Scrum Team's size is consistent with Scrum guidance?
- Exactly seven people are required for a valid Scrum Team
- Larger teams are always better because they can do more work per Sprint
- Smaller than about ten total people is generally more effective, though Scrum does not set a fixed number Correct answer.
- Team size is irrelevant as long as the Scrum Master is experienced
Explanation
Scrum guidance suggests that a Scrum Team is typically around ten or fewer people, small enough to remain nimble and large enough to complete significant work within a Sprint. The framework does not mandate an exact headcount. Larger groups tend to need more coordination and communication overhead, which reduces effectiveness.
Question 37Scrum theory and Professional Scrum
A Scrum Team keeps its Sprint Backlog in a shared tool, but the Developers frequently disagree about what a backlog item actually requires. Which pillar is most directly weakened?
- Transparency, because the shared understanding of the work is not accurate Correct answer.
- Inspection, because the Sprint Review is too long
- Commitment, because the Product Owner is absent
- Adaptation, because the Sprint Goal is missing
Explanation
When team members interpret the same backlog items differently, the visible artifact does not convey a shared, accurate understanding, which is a failure of transparency. Inspection and adaptation built on that unclear view will be unreliable. The scenario says nothing about a missing Sprint Goal, event timeboxes, or Product Owner absence.
Question 38Scrum theory and Professional Scrum
How does Scrum theory treat the plan produced at Sprint Planning?
- It is created by the Product Owner alone and handed to the Developers
- It is an emergent plan that the Developers update as more is learned during the Sprint Correct answer.
- It is a fixed contract that may not change once the Sprint starts
- It is optional and only needed for long Sprints
Explanation
The Sprint Backlog is a plan by and for the Developers that emerges and is updated throughout the Sprint as more is learned. Scrum embraces change within the Sprint as understanding grows, provided the Sprint Goal is respected. It is neither a fixed contract nor a document produced by someone outside the Developers.
Question 39Scrum theory and Professional Scrum
Which statement best explains why Scrum favors empirical process control over predictive planning for complex product work?
- Complex work involves too many unknowns for a detailed long-term plan to stay accurate, so frequent inspection and adaptation are more effective Correct answer.
- Empiricism removes the need to estimate or forecast at all
- Predictive planning is prohibited by the Scrum Guide in all circumstances
- Empirical control guarantees the product will succeed commercially
Explanation
Complex work has too many variables and unknowns for a detailed long-range plan to remain reliable, so Scrum uses short cycles of inspection and adaptation to steer toward value. This does not forbid forecasting, nor does it promise commercial success. It is a pragmatic choice for complexity, not a prohibition on planning.
Question 40Scrum theory and Professional Scrum
A Scrum Team finishes its Sprint work early and the Developers want to pull an additional Product Backlog item into the Sprint. What does Scrum theory support?
- They must cancel the Sprint and start a new one
- They may add the item if they agree it is feasible and it does not endanger the Sprint Goal Correct answer.
- They need the Scrum Master to approve any scope change in writing
- They must wait for the next Sprint because scope may never change mid-Sprint
Explanation
Scrum allows scope to be clarified and renegotiated with the Product Owner as more is learned during the Sprint, provided the Sprint Goal is not endangered. Adding feasible work when capacity allows is consistent with empiricism and self-management. Cancelling the Sprint or requiring formal written approval is not prescribed for this situation.
Question 41Scrum Guide accountabilities, events, and artifacts
In the Scrum Guide, which accountability is responsible for maximizing the value of the product resulting from the work of the Scrum Team?
- The Developers
- The Product Owner Correct answer.
- The Scrum Master
- The stakeholders
Explanation
The Product Owner is accountable for maximizing product value and for managing the Product Backlog effectively. The Scrum Master serves the team's effectiveness, while Developers create the Increment. Value maximization is explicitly a Product Owner accountability.
Question 42Scrum Guide accountabilities, events, and artifacts
How many accountabilities does the Scrum Guide define within a Scrum Team?
- Two
- Three Correct answer.
- Five
- Four
Explanation
The Scrum Guide defines exactly three accountabilities: Product Owner, Scrum Master, and Developers. Together they form one self-managing Scrum Team with no sub-teams or hierarchies. Roles such as project manager or tech lead are not part of the framework.
Question 43Scrum Guide accountabilities, events, and artifacts
What is the maximum length of a Sprint in Scrum?
- One month Correct answer.
- Three months
- Two weeks
- Six weeks
Explanation
A Sprint is fixed at one month or less to keep the horizon short and limit risk. Shorter Sprints are common and generate more learning cycles. The one-month ceiling is the only hard limit the guide sets.
Question 44Scrum Guide accountabilities, events, and artifacts
Which event is described as the heart of Scrum because it enables inspection and adaptation of progress toward the Sprint Goal?
- The Sprint Retrospective
- The Daily Scrum Correct answer.
- The Sprint Review
- The Sprint Planning
Explanation
The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is held every working day of the Sprint at the same time and place. Planning, Review, and Retrospective serve different inspection purposes.
Question 45Scrum Guide accountabilities, events, and artifacts
Who is accountable for creating the Increment during a Sprint?
- The Developers Correct answer.
- The Product Owner
- The Scrum Master
- The whole Scrum Team collectively
Explanation
The Developers are accountable for creating a usable Increment that meets the Definition of Done each Sprint. They are also accountable for instilling quality and adapting their plan daily. The Product Owner and Scrum Master support the work but do not build the Increment.
Question 46Scrum Guide accountabilities, events, and artifacts
Which two artifacts does the Scrum Guide require to contain a commitment? Choose the answer that names a valid artifact-commitment pair.
- Increment committed to the Sprint Goal
- Sprint Backlog committed to the Product Goal
- Sprint Backlog committed to the Definition of Done
- Product Backlog committed to the Product Goal Correct answer.
Explanation
Each artifact carries a commitment: the Product Backlog commits to the Product Goal, the Sprint Backlog to the Sprint Goal, and the Increment to the Definition of Done. The pairings in the other options mismatch artifact and commitment. These commitments reinforce transparency and focus.
Question 47Scrum Guide accountabilities, events, and artifacts
A Scrum Team wants to add a fourth accountability for a technical architect. According to the Scrum Guide, what is the correct response?
- The team cannot add accountabilities; the guide defines exactly three within the Scrum Team Correct answer.
- The team may add it if the Product Owner approves
- The team may add it during the Retrospective
- The team may add it if the Scrum Master agrees
Explanation
The Scrum Guide defines only three accountabilities and states there are no sub-teams or hierarchies within the Scrum Team. Accountability for architecture can be held by Developers as part of their work. Creating a separate role would contradict the framework's structure.
Question 48Scrum Guide accountabilities, events, and artifacts
What is the primary purpose of Sprint Planning?
- To define why the Sprint is valuable, what can be done, and how the work will be done Correct answer.
- To synchronize the Developers and adapt the Sprint Backlog daily
- To review the Increment with stakeholders and collect feedback
- To inspect how the last Sprint went and plan improvements
Explanation
Sprint Planning addresses three topics: the why (Sprint Goal), the what (items selected from the Product Backlog), and the how (a plan for delivering them). The event is timeboxed to eight hours or less for a one-month Sprint. The other options describe the Review, Retrospective, and Daily Scrum.
Question 49Scrum Guide accountabilities, events, and artifacts
Which statement best describes the Definition of Done?
- A formal description of the state of the Increment when it meets the quality measures required for the product Correct answer.
- A checklist the Scrum Master maintains to verify each Developer's task completion
- A list of acceptance criteria negotiated with stakeholders for each backlog item
- A contract that the Product Owner signs at the end of every Sprint
Explanation
The Definition of Done is a formal description of quality measures that the Increment must meet to be considered complete. It creates shared understanding of what work is finished and is used by the team to assess the Increment. If an item does not meet it, it is not part of the Increment.
Question 50Scrum Guide accountabilities, events, and artifacts
The Developers realize mid-Sprint that they cannot meet the Sprint Goal. What does Scrum prescribe?
- They extend the Sprint by one week to finish the work
- They add new items to the Sprint Backlog to compensate
- They cancel the Sprint immediately and start a new one
- They negotiate the scope of the Sprint Backlog with the Product Owner and adapt toward the Sprint Goal Correct answer.
Explanation
Scope may be clarified and renegotiated with the Product Owner as more is learned, while the Sprint Goal and quality targets remain fixed. Only the Product Owner has the authority to cancel a Sprint, and only when the goal becomes obsolete. Adapting the Sprint Backlog is the normal response to new insight.