I85PREP
⌘ K
PSD study materials
PSD study resources

PSD practice questions

One question at a time. Build your PSD understanding.

First 50 of 200 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 framework applied to software development

In Scrum, 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 and estimate items for the next Sprint
  3. To demonstrate completed work to the customer
  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 accordingly. It is a working session for the team, not a status report to outsiders. Refinement and reviews of work happen elsewhere.

Question 2Scrum theory and framework applied to software development

A software team finishes all Sprint Backlog items early and the Product Owner wants to add a new feature mid-Sprint. Which statement reflects Scrum theory?

  1. The scope of a Sprint may be clarified and renegotiated with the Product Owner as more is learned Correct answer.
  2. New work must wait until the next Sprint because scope never changes
  3. The Sprint Backlog is frozen once the Sprint starts and no changes are allowed
  4. Only the Scrum Master can authorize adding new items to the Sprint

Explanation

Scrum allows the scope of a Sprint to be clarified and renegotiated with the Product Owner as more is learned, while the Sprint Goal remains fixed. This reflects empiricism: plans are adjusted as understanding grows. Freezing the backlog or routing changes through the Scrum Master contradicts the framework.

Question 3Scrum theory and framework applied to software development

Which three pillars underpin the empirical process control in Scrum?

  1. Transparency, inspection, and adaptation Correct answer.
  2. Estimation, commitment, and velocity
  3. Planning, execution, and closure
  4. Design, development, and deployment

Explanation

Scrum is founded on empiricism, which rests on transparency, inspection, and adaptation. These pillars let the team control risk and optimize predictability. The other sets describe project phases or practices, not Scrum's theoretical foundation.

Question 4Scrum theory and framework applied to software development

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

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

Explanation

The Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint, and shorter for shorter Sprints. The Daily Scrum is fifteen minutes, and the Sprint Retrospective is three hours. Eight hours exceeds any Scrum event timebox.

Question 5Scrum theory and framework applied to software development

A Developer identifies an impediment that blocks progress on the Sprint Goal. According to Scrum, who is accountable for helping remove it?

  1. The Product Owner, who reprioritizes the Product Backlog
  2. The Scrum Master, who serves the team by causing impediment removal Correct answer.
  3. The stakeholders, who approve additional budget
  4. The Developers, who must resolve all blockers alone

Explanation

The Scrum Master serves the Scrum Team by helping remove impediments to progress. This is a core part of the servant-leadership stance in Scrum. Others may assist, but the Scrum Master is accountable for causing removal to happen.

Question 6Scrum theory and framework applied to software development

Which artifact is described as a commitment by the Developers to the Sprint Goal and their forecast of work?

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

Explanation

The Sprint Backlog is composed of the Sprint Goal, the selected Product Backlog items, and the plan for delivering them. It represents the Developers' forecast and commitment for the Sprint. The Product Backlog is the ordered list of what is needed to improve the product.

Question 7Scrum theory and framework applied to software development

What is the purpose of the Sprint Retrospective in a software team?

  1. To plan ways to increase quality and effectiveness for the next Sprint Correct answer.
  2. To review the product increment with stakeholders
  3. To estimate the effort for upcoming backlog items
  4. To approve the Definition of Done for the release

Explanation

The Sprint Retrospective is held to inspect how the last Sprint went regarding individuals, interactions, processes, tools, and the Definition of Done, then plan improvements. Its output is actionable improvements, often added to the next Sprint Backlog. Reviewing the increment with stakeholders is the Sprint Review's role.

Question 8Scrum theory and framework applied to software development

A Scrum Team consists of which accountabilities?

  1. Developers only, with the Product Owner external to the team
  2. One Scrum Master, one Product Owner, and Developers Correct answer.
  3. A project manager, a product manager, and testers
  4. A Scrum Master, a tech lead, and a QA manager

Explanation

The Scrum Team is a small team of people with three accountabilities: the Scrum Master, the Product Owner, and the Developers. There are no sub-teams or hierarchies such as tech leads or QA managers. The Product Owner is part of the Scrum Team, not external to it.

Question 9Scrum theory and framework applied to software development

In Scrum, what does the Definition of Done provide for a software increment?

  1. A schedule of release dates agreed with stakeholders
  2. A list of every task the Developers plan to perform
  3. A record of defects found during testing
  4. A shared quality standard that the Increment must meet to be considered complete 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 creates transparency so everyone shares the same understanding of what complete means. It is not a task list, schedule, or defect log.

Question 10Scrum theory and framework applied to software development

What is the maximum length of a Sprint in Scrum?

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

Explanation

Sprints are fixed-length events of one month or less to create consistency. A new Sprint starts immediately after the previous one concludes. Longer cycles increase complexity and risk, which is why Scrum caps them at one month.

Question 11Scrum theory and framework applied to software development

A team's Product Backlog has grown large with many low-value items. Which action best reflects Scrum guidance on managing the Product Backlog?

  1. Keep it ordered by value and refine items just in time rather than fully detailing everything Correct answer.
  2. Delete the backlog and rebuild it each Sprint
  3. Assign each item a fixed deadline during initial planning
  4. Fully specify every item in detail before any Sprint begins

Explanation

The Product Backlog is emergent and should be ordered by value, with refinement done continuously and just in time. Detailing every item upfront wastes effort and reduces adaptability. Rebuilding or hard-scheduling items undermines empiricism.

Question 12Scrum theory and framework applied to software development

During a Sprint, the Developers realize a selected backlog item is far more complex than expected. What does Scrum recommend?

  1. Escalate to the Scrum Master to decide which item to drop
  2. Silently drop the item and pick a different one without informing anyone
  3. Extend the Sprint by a week to finish the work
  4. Collaborate with the Product Owner to renegotiate scope while protecting the Sprint Goal Correct answer.

Explanation

Scope may be clarified and renegotiated with the Product Owner as more is learned, while the Sprint Goal stays fixed. This keeps the team aligned with value while adapting to new information. Unilateral changes or extending the Sprint violate Scrum's fixed cadence.

Question 13Scrum theory and framework applied to software development

Which statement best describes self-managing Developers in Scrum?

  1. They wait for the Scrum Master to assign tasks each day
  2. They rotate a single designated lead who assigns all work
  3. They decide internally who does what, when, and how to accomplish the Sprint Goal Correct answer.
  4. They follow a plan fixed by the Product Owner at Sprint Planning

Explanation

Self-managing Developers choose how to do the work, including who does what, when, and how, to accomplish the Sprint Goal. This autonomy is central to Scrum's empiricism. Task assignment by the Scrum Master, Product Owner, or a rotating lead contradicts self-management.

Question 14Scrum theory and framework applied to software development

What is the main purpose of the Sprint Review?

  1. To decide whether the Sprint Goal was met and assign blame
  2. To finalize the Definition of Done for the team
  3. To inspect the Increment and adapt the Product Backlog based on stakeholder feedback Correct answer.
  4. To estimate the next Sprint's items in detail

Explanation

The Sprint Review inspects the outcome of the Sprint and determines future adaptations, with stakeholders collaborating on what to do next. It results in a revised Product Backlog. It is not a blame session, an estimation meeting, or where the Definition of Done is finalized.

Question 15Scrum theory and framework applied to software development

A Product Owner wants to maximize value but keeps interrupting Developers with new urgent requests mid-Sprint. What does Scrum suggest?

  1. Order the Product Backlog so urgent items are handled through proper Sprint scope negotiation, not constant interruption Correct answer.
  2. Let Developers ignore the Product Owner until the Sprint ends
  3. Allow interruptions freely because value always trumps the Sprint Goal
  4. Have the Scrum Master block all communication with the Product Owner

Explanation

The Product Owner maximizes value through ordering the Product Backlog and collaborating on Sprint scope, not by interrupting daily work. Constant interruption erodes focus and the Sprint Goal. Blocking communication or ignoring the Product Owner both damage collaboration.

Question 16Scrum theory and framework applied to software development

Which of the following best describes an Increment in Scrum?

  1. A prototype shown only to the Scrum Team
  2. A document listing all completed tasks in the Sprint
  3. A branch of code that has not yet been integrated
  4. A concrete, usable step toward the product goal that meets the Definition of Done Correct answer.

Explanation

An Increment is a concrete stepping stone toward the Product Goal, and each Increment is additive and verified against the Definition of Done. Multiple Increments may be produced within a Sprint. It must be usable, not merely an internal document, prototype, or unintegrated branch.

Question 17Scrum theory and framework applied to software development

How does Scrum treat the Sprint Goal?

  1. It is a contract that forbids any change to scope
  2. It is optional and may be skipped if the team is busy
  3. It is a single objective for the Sprint that provides focus and flexibility on the why Correct answer.
  4. It is a fixed list of every task to be completed

Explanation

The Sprint Goal is the single objective for the Sprint, giving the team a shared purpose while allowing flexibility on how to achieve it. It is created during Sprint Planning and is not a task list. It is required, and it does not forbid scope clarification.

Question 18Scrum theory and framework applied to software development

A team claims it is doing Scrum but has no Sprint Retrospective and deploys only once a year. Which Scrum principle is most directly undermined?

  1. The existence of a separate QA department
  2. Inspection and adaptation through regular events and short feedback loops Correct answer.
  3. The practice of writing detailed specifications
  4. The use of story points for estimation

Explanation

Skipping the Retrospective and deploying yearly removes the regular inspection and adaptation that Scrum's events and short Sprints provide. Scrum relies on frequent feedback loops to control risk. Story points, QA departments, and detailed specs are not Scrum principles being violated here.

Question 19Scrum theory and framework applied to software development

During Sprint Planning, the Developers forecast work but are unsure about a complex integration. What is the most Scrum-aligned approach?

  1. Refuse to start until every uncertainty is fully resolved
  2. Commit to a fixed scope regardless of new findings
  3. Ask the Scrum Master to guarantee the estimate
  4. Forecast based on current understanding and adapt the Sprint Backlog as more is learned Correct answer.

Explanation

Sprint Planning produces a forecast, not a guarantee; the Sprint Backlog emerges as understanding grows. Waiting for total certainty or treating the forecast as fixed contradicts empiricism. The Scrum Master cannot guarantee estimates made by the Developers.

Question 20Scrum theory and framework applied to software development

Which statement correctly distinguishes the Product Owner from the Scrum Master in a software organization?

  1. The Product Owner maximizes product value, while the Scrum Master enables effective Scrum practice Correct answer.
  2. The Product Owner runs the Retrospective, while the Scrum Master runs the Review
  3. The Product Owner assigns daily tasks, while the Scrum Master writes code
  4. The Product Owner removes impediments, while the Scrum Master orders the backlog

Explanation

The Product Owner is accountable for maximizing value and managing the Product Backlog, while the Scrum Master coaches the team and organization in effective Scrum. Impediment removal and backlog ordering are swapped in the wrong option. Neither role assigns daily tasks or writes code by default.

Question 21Scrum theory and framework applied to software development

A stakeholder complains that the team's velocity dropped this Sprint. How should the Scrum Team interpret velocity in Scrum terms?

  1. As a contractual commitment that must increase every Sprint
  2. As an internal planning aid that can inform forecasts but is not a performance target Correct answer.
  3. As a metric the Product Owner must report to management weekly
  4. As the primary measure of individual developer productivity

Explanation

Velocity is a planning aid the team may use to forecast, not a performance target or contract. Treating it as a commitment or reporting it as individual productivity distorts behavior and undermines empiricism. Scrum does not mandate velocity as an official metric.

Question 22Scrum theory and framework applied to software development

Which scenario best demonstrates transparency, one of Scrum's pillars?

  1. The team hides unfinished work to protect its velocity number
  2. The Definition of Done is shared and the Increment is visible to stakeholders each Sprint Correct answer.
  3. Developers report progress only at the end of the quarter
  4. The Product Owner keeps the backlog private from Developers

Explanation

Transparency means the process and work are visible to those responsible for the outcome, supported by a shared Definition of Done and a visible Increment. Hiding work, concealing the backlog, or reporting only quarterly all reduce transparency and weaken inspection.

Question 23Scrum theory and framework applied to software development

A Scrum Team is distributed across time zones. Which adaptation best preserves Scrum's empirical events?

  1. Cancel the Retrospective until the team is co-located
  2. Lengthen the Daily Scrum to one hour to accommodate everyone
  3. Keep events within their timeboxes and use collaboration tools so inspection and adaptation still occur Correct answer.
  4. Replace the Sprint Review with asynchronous written status reports

Explanation

Scrum events should remain within their timeboxes regardless of distribution, using tools to enable real inspection and adaptation. Extending timeboxes, replacing the Review with status reports, or canceling the Retrospective weakens the empirical loop. Distribution is not a reason to drop events.

Question 24Scrum theory and framework applied to software development

What happens immediately after a Sprint ends?

  1. The team waits for management approval to start again
  2. A new Sprint begins, with planning for the next Sprint occurring right away Correct answer.
  3. The Product Backlog is frozen until the next quarter
  4. There is a mandatory two-week cooling-off period

Explanation

Sprints are consecutive; a new Sprint starts immediately after the previous one concludes, beginning with Sprint Planning. There is no cooling-off period or management gate in Scrum. Freezing the backlog would contradict its emergent nature.

Question 25Scrum theory and framework applied to software development

A team wants to add a mandatory security review step to every increment. Where does this belong in Scrum?

  1. In the Definition of Done, so every Increment is verified against it Correct answer.
  2. In the Sprint Review agenda as a stakeholder discussion
  3. In the Daily Scrum as a daily status item
  4. In the Product Backlog as a single one-off item

Explanation

Work needed to make an Increment conform to quality standards belongs in the Definition of Done, which applies to every Increment. A recurring quality step is not a one-off backlog item, a status topic, or merely a Review discussion. This keeps transparency about what complete means.

Question 26Scrum theory and framework applied to software development

In Scrum, what is the timebox for the Daily Scrum and who is required to attend it?

  1. As long as needed, for the Developers and any stakeholder who wants to raise impediments
  2. Fifteen minutes, for the whole Scrum Team, with the Product Owner chairing the discussion
  3. Thirty minutes, for the whole Scrum Team including the Product Owner and Scrum Master
  4. Fifteen minutes, for the Developers; the Product Owner and Scrum Master may attend if they are working on the Sprint Backlog Correct answer.

Explanation

The Daily Scrum is a 15-minute event for the Developers, held every working day of the Sprint to inspect progress toward the Sprint Goal. The Product Owner and Scrum Master may attend only if they are actively working on items in the Sprint Backlog; they are not required participants.

Question 27Scrum theory and framework applied to software development

A Scrum Team is defining its Definition of Done for a web application. Which characteristic best matches Scrum's intent for this artifact?

  1. A wish list of improvements the team hopes to reach in a future release
  2. A shared, explicit checklist of quality criteria that every Increment must satisfy before it counts as done Correct answer.
  3. A project schedule listing the dates by which each feature will be complete
  4. A per-developer coding standard that each engineer applies to their own commits

Explanation

The Definition of Done is a formal, shared description of the state the Increment must reach for the work to be considered complete. It creates transparency so everyone applies the same quality bar, and it is used to verify the Increment at the Sprint Review.

Question 28Scrum theory and framework applied to software development

A Scrum Master notices that the Developers wait for the Scrum Master to assign tasks each morning. Which action best reflects the Scrum Master's accountability?

  1. Coach the Developers toward self-management so they select and organize their own work Correct answer.
  2. Ask the Product Owner to allocate tasks among the Developers
  3. Escalate to management so a technical lead can direct the daily work
  4. Assign tasks personally each day to keep the Sprint predictable

Explanation

The Scrum Master serves the Scrum Team by coaching it in self-management and helping people understand Scrum theory and practice. Self-managing Developers choose how to do the work, so task assignment by the Scrum Master or others undermines the framework.

Question 29Scrum theory and framework applied to software development

Which statement describes the relationship between the Sprint Backlog and the Sprint Goal?

  1. The Sprint Goal is written after the Sprint Backlog is complete so it can summarize the tasks
  2. The Sprint Backlog is a fixed list of tasks that cannot be changed once the Sprint starts
  3. The Sprint Backlog is composed of the Sprint Goal, the selected Product Backlog items, and the plan for delivering them Correct answer.
  4. The Sprint Backlog belongs to the Product Owner, who updates it daily to reflect priorities

Explanation

The Sprint Backlog is a plan by and for the Developers; it contains the Sprint Goal (why), the selected items (what), and the actionable plan (how). It is updated throughout the Sprint as more is learned.

Question 30Scrum theory and framework applied to software development

During Sprint Planning, how is the forecast of work created according to Scrum?

  1. Stakeholders vote on the backlog items they consider highest priority for the Sprint
  2. The Product Owner assigns each item to a named developer based on technical specialty
  3. The Scrum Master calculates capacity and dictates how many items the team must take
  4. The Developers select items and forecast by discussing, refining, and estimating together with the Product Owner available to clarify Correct answer.

Explanation

Sprint Planning is a collaborative event where the Developers decide what can be done and how, with the Product Owner on hand to discuss the Product Backlog and clarify value. The forecast is the Developers' own commitment, not an external allocation.

Question 31Scrum theory and framework applied to software development

Which statement best describes the Product Backlog?

  1. A list of tasks generated by the Developers for the current Sprint
  2. A complete specification that is frozen at project kickoff and then implemented over many Sprints
  3. An emergent, ordered list of what is needed to improve the product, with the most valuable items typically refined first Correct answer.
  4. A record of defects only, maintained separately from new feature requests

Explanation

The Product Backlog is the single source of work for the product; it is emergent and ordered by value and other factors. Items near the top are usually smaller and better understood so they can be selected for upcoming Sprints.

Question 32Scrum theory and framework applied to software development

What does the Scrum Team inspect and adapt during the Sprint Review?

  1. The Increment and the impact of the work on progress toward the Product Goal, with stakeholders providing feedback Correct answer.
  2. Individual developer performance ratings and compensation decisions
  3. The accuracy of each developer's time estimates compared with actual hours logged
  4. The team's processes and working relationships, using a facilitator to surface interpersonal issues

Explanation

The Sprint Review is a working session where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog. Discussion centers on progress toward the Product Goal and what to do next, not on individual performance.

Question 33Scrum theory and framework applied to software development

Which statement best captures an empirical process control approach in Scrum?

  1. Decisions are based on the number of story points completed in past Sprints alone
  2. Decisions are based on observation of working software and real outcomes, adjusting as evidence emerges Correct answer.
  3. Decisions are based on the seniority of the person proposing the change
  4. Decisions are based on a detailed upfront plan that is followed without change

Explanation

Empiricism holds that knowledge comes from experience and decisions should be based on what is observed. Scrum applies this through transparency, inspection, and adaptation of real increments rather than adherence to a fixed upfront plan.

Question 34Scrum theory and framework applied to software development

A Product Owner is refining a backlog item that is too large to finish in one Sprint. Which action is most consistent with Scrum?

  1. Keep it as one item and accept that it will carry over across several Sprints
  2. Split the item into smaller items that can each be completed within a Sprint Correct answer.
  3. Move it to the bottom of the backlog until someone else breaks it down
  4. Estimate it precisely and add it to the Sprint Backlog with a longer timebox

Explanation

Product Backlog items that may be worked on in the near future should be refined and decomposed so they can be completed within a Sprint. Large items are split rather than carried across Sprints as partial work.

Question 35Scrum theory and framework applied to software development

Which statement correctly describes the relationship between the Sprint Goal and the Developers' flexibility during a Sprint?

  1. The Developers may change the Sprint Goal whenever a more interesting feature appears
  2. The Developers must complete every selected item even if the Sprint Goal is no longer achievable
  3. The Developers may extend the Sprint by a few days if they are close to finishing the goal
  4. The Developers may adjust the Sprint Backlog and negotiate scope with the Product Owner as long as the Sprint Goal is met Correct answer.

Explanation

The Sprint Goal gives the Developers flexibility on the what and how: scope may be clarified and renegotiated with the Product Owner while the goal remains the focus. The Sprint itself is not extended, and the goal is not casually replaced.

Question 36Scrum theory and framework applied to software development

A team's Sprint Review has become a slide presentation with no working software shown. Which change best restores the event's purpose?

  1. Move the Review to the end of the project so a full product can be shown
  2. Demonstrate the actual Increment and invite stakeholders to inspect it and discuss what to do next Correct answer.
  3. Replace the Review with a written status report emailed to stakeholders
  4. Shorten the Review so only the Product Owner speaks about progress

Explanation

The Sprint Review is a working session to inspect the Increment and adapt the Product Backlog with stakeholders. Showing the real Increment enables genuine inspection and feedback rather than status reporting.

Question 37Scrum theory and framework applied to software development

A Scrum Team works on a regulated product that requires independent penetration testing before release. Where does this requirement best belong in Scrum?

  1. In a separate quality phase after several Sprints have produced increments
  2. In the Sprint Retrospective action list, tracked but not enforced
  3. In the Product Owner's private notes, applied only when a release is scheduled
  4. In the Definition of Done, so no Increment is considered complete until the testing passes Correct answer.

Explanation

If an organization, standard, or product requires certain activities for a release, they belong in the Definition of Done so every Increment meets the same bar. This keeps the increment transparent and truly releasable.

Question 38Scrum theory and framework applied to software development

How does Scrum describe the Scrum Master's service to the wider organization?

  1. Owning the product vision and deciding which features enter the Product Backlog
  2. Setting the Definition of Done unilaterally for all teams in the company
  3. Managing the Developers' daily assignments and approving their time off
  4. Leading, training, and coaching the organization in its Scrum adoption and helping remove barriers between stakeholders and the Scrum Team Correct answer.

Explanation

The Scrum Master serves the organization by leading and coaching its Scrum adoption, planning and advising implementations, and helping remove barriers between stakeholders and Scrum Teams. Product direction and task assignment are not part of this accountability.

Question 39Scrum theory and framework applied to software development

A Scrum Team wants to improve how it works. Which approach best reflects the purpose of the Sprint Retrospective?

  1. Review each developer's code quality and assign corrective tasks to the weakest performer
  2. Present the Increment to customers and gather feature requests
  3. Re-plan the Product Backlog order for the next quarter with stakeholders
  4. Inspect how the last Sprint went regarding individuals, interactions, processes, tools, and the Definition of Done, then identify the most impactful improvements Correct answer.

Explanation

The Retrospective is a timeboxed event where the Scrum Team inspects how the last Sprint went and identifies the most helpful changes to improve effectiveness. Improvements with the greatest impact are addressed as soon as possible.

Question 40Scrum theory and framework applied to software development

Which statement best explains why Scrum prescribes fixed-length Sprints?

  1. A consistent cadence creates regularity for inspection and adaptation and limits risk to the cost of one Sprint Correct answer.
  2. A fixed length allows the Product Owner to change priorities only at the Sprint boundary
  3. A fixed length guarantees the team will finish all selected items on time
  4. A fixed length removes the need for a Sprint Goal in short Sprints

Explanation

Sprints are fixed-length events of one month or less that provide consistency and limit risk to the cost of a single Sprint. The cadence supports regular inspection and adaptation rather than guaranteeing delivery of all selected work.

Question 41Scrum theory and framework applied to software development

A team argues that it can skip the Daily Scrum because members already talk throughout the day. Which response is most consistent with Scrum?

  1. Replace it with a weekly written status update to the Scrum Master
  2. Skip it permanently, since communication already happens continuously
  3. Hold the Daily Scrum as prescribed to inspect progress toward the Sprint Goal and adapt the plan, even if informal conversations continue Correct answer.
  4. Extend it to an hour so every technical detail can be discussed

Explanation

The Daily Scrum is a required event that creates focus on the Sprint Goal and lets the Developers inspect progress and adapt the Sprint Backlog. Informal conversations do not replace this structured inspection and adaptation.

Question 42Scrum theory and framework applied to software development

A Product Owner wants to predict delivery dates for a large product. Which use of historical Sprint data is most consistent with Scrum?

  1. Use the highest single-Sprint velocity ever recorded as the planning baseline
  2. Use observed throughput and cycle time as empirical inputs for forecasting, while communicating the uncertainty in the forecast Correct answer.
  3. Convert story points directly into hours and commit to an exact delivery date
  4. Promise the date first, then require the Developers to increase velocity to meet it

Explanation

Empirical forecasting uses observed data such as throughput and cycle time while acknowledging uncertainty. Story points are relative estimates and are not convertible into hours, and demanding a velocity increase inverts the empirical approach.

Question 43Scrum theory and framework applied to software development

Which statement correctly describes who owns the Sprint Backlog and how it changes?

  1. The Product Owner owns it and reorders it whenever priorities shift
  2. Stakeholders own it and add requests during the Sprint Review
  3. The Developers own it and update it throughout the Sprint as they learn more Correct answer.
  4. The Scrum Master owns it and records impediments as tasks

Explanation

The Sprint Backlog is a plan by and for the Developers, who own and update it as more is learned during the Sprint. It is the Developers' real-time picture of the work needed to achieve the Sprint Goal.

Question 44Scrum theory and framework applied to software development

A Scrum Team is developing a payment service and discovers late in a Sprint that a selected item depends on an external API that is unavailable. What is the most appropriate action?

  1. Collaborate with the Product Owner to adjust scope while keeping the Sprint Goal in focus, and update the Sprint Backlog Correct answer.
  2. Deliver the incomplete item as done and note the gap in the Retrospective
  3. Stop the Sprint and wait for the next Sprint to begin before doing anything
  4. Silently extend the Sprint by a week so the dependency can be resolved

Explanation

When new information emerges, the Developers and Product Owner collaborate to adjust the Sprint Backlog and scope while maintaining focus on the Sprint Goal. The Sprint timebox itself is not extended.

Question 45Scrum theory and framework applied to software development

Which situation best demonstrates the Scrum value of courage in a software team?

  1. A team avoids discussing difficult topics to keep meetings short
  2. A developer agrees with every estimate to avoid conflict
  3. A manager approves all decisions before the team acts on them
  4. A developer raises a serious quality risk to the Product Owner even though it may delay a promised feature Correct answer.

Explanation

Courage in Scrum means doing the right thing and working on tough problems, including surfacing risks and bad news. Avoiding hard topics, avoiding conflict, and requiring managerial approval all reflect the absence of courage.

Question 46Scrum theory and framework applied to software development

A Scrum Team has grown to twelve developers and coordination is suffering. Which action is most consistent with Scrum guidance?

  1. Reduce the number of Scrum events so the larger team has more working time
  2. Consider splitting into multiple Scrum Teams that share the same Product Backlog, Product Owner, and Definition of Done Correct answer.
  3. Add a project manager to coordinate the developers' tasks
  4. Keep one team but have the Scrum Master assign all work to reduce confusion

Explanation

Scrum recommends keeping the Scrum Team small, typically ten or fewer people, because larger groups need more coordination and communication overhead. If scaling is needed, multiple Scrum Teams can share one Product Backlog, one Product Owner, and a common Definition of Done.

Question 47Scrum theory and framework applied to software development

A stakeholder asks the Scrum Team to report percentage completion of the whole product by summing story points delivered against a total estimate. Why is this measure problematic in Scrum?

  1. Because percentages are allowed only in the Sprint Review, not in other reports
  2. Because story points are only valid when the Product Owner assigns them
  3. Because estimates are relative and emergent, so a points-based percentage implies a precision and fixed scope that Scrum does not assume Correct answer.
  4. Because Scrum forbids measuring progress on the Product Backlog entirely

Explanation

Scrum uses relative estimation and an emergent backlog, so summing points against a fixed total creates false precision and assumes a scope that will change. Progress toward the Product Goal is better assessed through the Increment and empirical forecasting.

Question 48Scrum theory and framework applied to software development

Midway through a Sprint, the Product Owner concludes that the Sprint Goal has become obsolete because of a major regulatory change. What does Scrum prescribe?

  1. The Developers must finish the Sprint as planned regardless of the change
  2. The Scrum Master decides whether to cancel the Sprint after consulting stakeholders
  3. The team pauses the Sprint and resumes it once new requirements are written
  4. The Product Owner may cancel the Sprint, and any completed items are reviewed for potential release Correct answer.

Explanation

A Sprint can be cancelled only if the Sprint Goal becomes obsolete, and the Product Owner has the authority to cancel it. If part of the work is done, it is reviewed and potentially released before the Sprint ends.

Question 49Scrum theory and framework applied to software development

A team claims to be self-managing but its Product Owner writes detailed technical tasks and approves each pull request. Which analysis best fits Scrum?

  1. The team is self-managing, because the Product Owner is part of the Scrum Team and may direct technical work
  2. The team is self-managing as long as the Scrum Master facilitates the pull-request approvals
  3. The team is self-managing because it holds a Daily Scrum and a Retrospective each Sprint
  4. The team is not self-managing, because choosing how to do the work belongs to the Developers, while the Product Owner is accountable for value and backlog ordering Correct answer.

Explanation

Self-managing Developers decide how to turn backlog items into value, including technical and process decisions. The Product Owner is accountable for maximizing value and ordering the Product Backlog, not for dictating technical tasks or approving every change.

Question 50Scrum theory and framework applied to software development

An organization wants a single Definition of Done shared by several Scrum Teams building one product. What is the most accurate Scrum position?

  1. If the Definition of Done is an organizational standard, all teams must follow it as a minimum and may add stricter criteria Correct answer.
  2. Only the Product Owner may define the Definition of Done for all teams
  3. A shared Definition of Done is not permitted because it reduces team autonomy
  4. Each team must invent its own Definition of Done independently, with no shared minimum

Explanation

When an organization defines a Definition of Done as a standard, all Scrum Teams must follow it as a minimum; teams may then add stricter criteria. This supports a single releasable Increment when multiple teams work on the same product.