I85PREP
⌘ K
ACP Corporate study materials
ACP Corporate study resources

ACP Corporate practice questions

One question at a time. Build your ACP Corporate 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 1Agile mindset and corporate culture

A team adopts an agile mindset. Which belief most directly reflects that mindset rather than a specific ceremony?

  1. A detailed project charter must be signed before any development begins
  2. Estimates should be locked early so leadership can hold teams accountable
  3. Success is judged by how closely the team follows the documented process
  4. Customer feedback delivered through working software is the primary measure of progress Correct answer.

Explanation

An agile mindset values working software and customer collaboration over comprehensive documentation and rigid plans. It treats validated learning from real users as the true signal of progress. Ceremonies such as standups or charters are practices that may support the mindset but do not define it.

Question 2Agile mindset and corporate culture

A newly formed team is told to be 'agile' but its manager still assigns every task and approves every decision. Which cultural obstacle does this best illustrate?

  1. Insufficient tooling for continuous integration
  2. A command-and-control leadership style that blocks self-organization Correct answer.
  3. An overly broad product backlog
  4. A lack of automated regression tests

Explanation

Agile culture depends on teams having authority to decide how to do their work. When a manager retains all decision rights, the team cannot self-organize regardless of which practices it adopts. The other options describe technical or backlog issues, not the cultural pattern of centralized control.

Question 3Agile mindset and corporate culture

Which behavior best demonstrates psychological safety within an agile team?

  1. Members rotate facilitation so no one person owns the retrospective
  2. Members escalate every technical decision to the delivery manager
  3. Members avoid raising risks so the daily standup stays short
  4. Members surface bad news early because they expect discussion rather than blame Correct answer.

Explanation

Psychological safety means people believe they can speak up about problems, mistakes, or uncertainty without punishment. Surfacing bad news early is the clearest signal that this belief is present. Rotation of facilitation and escalation habits are unrelated to whether people feel safe to speak.

Question 4Agile mindset and corporate culture

An organization wants to move from annual performance rankings to a culture that supports agile teams. Which change is most consistent with that goal?

  1. Increase the number of approval gates before release
  2. Replace individual rankings with feedback focused on team outcomes and growth Correct answer.
  3. Reward teams for the volume of story points they complete
  4. Rank individuals against each other to preserve competitive drive

Explanation

Agile culture favors collaboration and shared accountability, so performance conversations that emphasize team outcomes and individual growth align better than forced rankings. Rankings can discourage the cross-team help and transparency agile work requires. Point-volume rewards and extra gates both distort behavior rather than support the culture shift.

Question 5Agile mindset and corporate culture

In an agile corporate culture, what is the primary purpose of a retrospective?

  1. To inspect how the team works and choose improvements to try next Correct answer.
  2. To re-estimate every item remaining in the backlog
  3. To demonstrate completed features to stakeholders
  4. To assign blame for defects found during the sprint

Explanation

A retrospective is a team reflection event where members examine their process and interactions and select experiments for improvement. It is about learning and adapting the way the team works, not about blaming people or reporting status. Demonstrations and re-estimation happen in other events.

Question 6Agile mindset and corporate culture

A company says it values transparency but requires all team metrics to be approved by a communications department before sharing. Which tension does this create for agile culture?

  1. It prevents the team from choosing its own definition of done
  2. It reduces trust and delays the flow of information the team needs to self-correct Correct answer.
  3. It slows the build pipeline and increases integration risk
  4. It forces the team to adopt a waterfall lifecycle

Explanation

Transparency in agile culture means information about progress and problems is visible and flows quickly. A pre-approval filter on metrics adds delay and signals distrust, which weakens the team's ability to inspect and adapt. It does not directly affect pipeline speed, the definition of done, or the choice of lifecycle.

Question 7Agile mindset and corporate culture

Which statement best captures the agile preference for responding to change?

  1. Plans are useful but should be revised as new information arrives Correct answer.
  2. Scope should be frozen at kickoff to protect the schedule
  3. Change requests should be batched and reviewed once per quarter
  4. Only the sponsor may approve changes to requirements

Explanation

Agile culture treats plans as valuable but provisional, updating them as learning and feedback arrive. The mindset is not anti-planning; it rejects the idea that an early plan must remain fixed. Batching, freezing, and single-approver models all resist timely adaptation.

Question 8Agile mindset and corporate culture

A leader wants to model servant leadership on an agile program. Which action best fits that model?

  1. Remove organizational blockers the team has escalated Correct answer.
  2. Decide the technical design of each feature
  3. Approve which team members may speak at reviews
  4. Set the team's daily task assignments each morning

Explanation

Servant leadership in agile settings focuses on enabling the team by clearing impediments and providing what it needs to succeed. The leader works for the team rather than directing its tasks. Assigning work, controlling who speaks, and dictating design all take authority away from the team.

Question 9Agile mindset and corporate culture

A large organization has agile teams but requires a 12-page business case and a steering committee sign-off before any experiment can run. Which cultural pattern is most limiting here?

  1. An insufficient number of certified scrum masters
  2. Too much emphasis on pair programming
  3. A backlog that is refined too frequently
  4. Excessive upfront control that discourages fast, low-cost learning Correct answer.

Explanation

Agile culture favors small, reversible experiments that generate learning quickly, which requires tolerance for low-ceremony decisions. Heavy business cases and committee gates raise the cost of trying anything, so teams avoid experiments. The other options describe staffing or practice choices that are not the constraint described.

Question 10Agile mindset and corporate culture

Two teams depend on the same shared service and blame each other for delays. Which cultural response best supports agile values?

  1. Escalate to senior management so one team is designated at fault
  2. Add a contract that formally specifies every interface before work continues
  3. Split the shared service so the teams never need to communicate again
  4. Bring both teams together to make the dependency and its impact visible, then agree on a joint improvement Correct answer.

Explanation

Agile culture encourages collaboration and shared ownership of problems rather than blame. Making the dependency transparent and agreeing on a joint improvement addresses the system, not the people. Escalation for fault-finding and heavy contracts both reinforce defensive behavior.

Question 11Agile mindset and corporate culture

A product owner is pressured to promise a fixed scope and date to sales before the team has refined the work. Which agile response is most appropriate?

  1. Add buffer to every estimate so the date is always met
  2. Share a forecast with explicit assumptions and review it as the team learns more Correct answer.
  3. Refuse to give sales any information until the release is finished
  4. Commit to the fixed scope and absorb any overrun with overtime

Explanation

Agile planning accepts uncertainty and communicates forecasts alongside the assumptions behind them, revisiting as evidence accumulates. This keeps sales informed without converting a forecast into a rigid commitment. Overtime, silence, and padded estimates all hide uncertainty rather than manage it.

Question 12Agile mindset and corporate culture

Which practice most directly reinforces a culture of continuous improvement rather than periodic big-bang change?

  1. Running small experiments each iteration and keeping what works Correct answer.
  2. Holding a single annual process review with external consultants
  3. Waiting for a crisis before revisiting team practices
  4. Rewriting all standards whenever a new framework becomes popular

Explanation

Continuous improvement in agile culture happens through frequent, small experiments whose results inform the next change. This creates a steady learning loop owned by the team. Annual reviews, wholesale rewrites, and crisis-driven change are episodic and rarely build lasting capability.

Question 13Agile mindset and corporate culture

A team's stakeholders attend reviews only to ask whether the date is still on track. Which change would most improve the review's value to an agile culture?

  1. Limit the demo to features that are fully complete and risk-free
  2. Move the review to a monthly cadence to reduce meeting load
  3. Replace the review with a written status report
  4. Invite stakeholders to discuss the increment and give feedback that shapes the backlog Correct answer.

Explanation

A review exists to inspect the increment and gather feedback that informs what comes next. Turning it into a genuine conversation about the product, rather than a date check, restores that purpose. Status reports and reduced frequency both shrink the feedback loop.

Question 14Agile mindset and corporate culture

An enterprise introduces agile teams but keeps a culture where leaders are expected to have all the answers. Which consequence is most likely?

  1. Retrospectives will become unnecessary and be dropped
  2. Teams will experiment more freely because direction is clear
  3. Team members will defer decisions upward, slowing response to feedback Correct answer.
  4. The definition of done will become stricter over time

Explanation

When leaders are expected to be the sole source of answers, teams learn that deciding is risky and escalate instead. That upward deferral slows decisions and weakens the team's ability to respond to feedback quickly. Experimentation, retrospectives, and quality standards are not improved by this pattern.

Question 15Agile mindset and corporate culture

A team celebrates a failed experiment because it produced a clear learning that changed the roadmap. Which cultural value does this most directly reflect?

  1. Tolerance for well-run failure as a source of learning Correct answer.
  2. A commitment to fixed scope
  3. A preference for avoiding documentation
  4. An emphasis on individual heroics

Explanation

Agile culture distinguishes between failure from carelessness and failure from deliberate, well-run experiments that yield knowledge. Celebrating the latter encourages teams to test assumptions early. It says nothing about documentation habits, scope rigidity, or individual heroics.

Question 16Agile mindset and corporate culture

Which meeting design best supports an agile team's cross-functional collaboration?

  1. Separate status meetings for each functional silo
  2. A weekly manager-only planning session that sets team priorities
  3. A short daily event where members coordinate work and surface impediments together Correct answer.
  4. A monthly all-hands where each department reports its own progress

Explanation

Cross-functional collaboration improves when people with different specialties coordinate directly and frequently. A short daily event where the whole team syncs and raises blockers supports that. Siloed status meetings and manager-only planning keep information and decisions separated by function.

Question 17Agile mindset and corporate culture

A department measures agile adoption by counting how many ceremonies each team runs. Why is this a weak cultural indicator?

  1. Ceremonies are optional in every agile framework
  2. Counting events measures activity rather than the behaviors and outcomes agile culture aims for Correct answer.
  3. Teams always run more ceremonies than they report
  4. Ceremony counts cannot be automated

Explanation

Ceremony counts show that meetings happen, not whether teams collaborate, learn, and deliver value. A culture shift is better assessed through behaviors such as transparency, fast feedback, and customer outcomes. Ceremonies are generally expected in agile frameworks, and automation is irrelevant to the point.

Question 18Agile mindset and corporate culture

A team member repeatedly raises concerns that turn out to be unfounded. How should an agile leader respond to preserve a culture of candor?

  1. Track how often each person's concerns prove valid
  2. Publicly correct the person so others learn to be more careful
  3. Thank the person for raising the concern and examine it briefly before moving on Correct answer.
  4. Ask the person to route future concerns through their manager first

Explanation

Candor survives when raising a concern is cheap and safe, even if the concern turns out to be wrong. Acknowledging the input and checking it quickly keeps the cost of speaking up low. Public correction, added approval layers, and accuracy tracking all raise that cost and suppress future warnings.

Question 19Agile mindset and corporate culture

An organization wants teams to own their outcomes. Which structural change best supports that ownership?

  1. Give teams authority over how they do the work within agreed constraints Correct answer.
  2. Require every team decision to be reviewed by a program office
  3. Rotate team members between teams every two weeks
  4. Standardize every team's process down to the minute

Explanation

Ownership requires that teams can decide how to meet their commitments within clear boundaries. Granting that authority while keeping constraints explicit lets teams take responsibility for outcomes. Central review, constant rotation, and minute-level standardization all remove the discretion ownership depends on.

Question 20Agile mindset and corporate culture

A company's agile transformation is led entirely by external consultants while internal managers wait to see what happens. Which risk does this pattern most clearly create?

  1. The change is not owned internally, so it fades when the consultants leave Correct answer.
  2. Too many retrospectives being scheduled
  3. The product backlog will grow too slowly
  4. Teams will adopt too many engineering practices

Explanation

Cultural change persists only when the people who remain own it and adapt it to their context. If managers stay passive observers, the new behaviors are tied to the consultants and disappear with them. The other options are unrelated to who owns the transformation.

Question 21Agile mindset and corporate culture

A team's definition of done requires peer review and automated tests, but managers reward shipping features with no review to hit monthly targets. What is the most likely cultural outcome?

  1. The team will raise its quality bar to match the definition of done
  2. The team will stop using a definition of done entirely
  3. The team will reduce its monthly feature output
  4. The team will quietly abandon the agreed standard to satisfy the reward system Correct answer.

Explanation

When incentives and stated standards conflict, people follow the incentives, so the agreed quality bar erodes. Agile culture requires leaders to align rewards with the standards they expect teams to keep. Raising quality or reducing output is unlikely when the reward pushes the other way, and the standard is more likely to be bypassed than formally dropped.

Question 22Agile mindset and corporate culture

Which statement best describes how agile culture treats documentation?

  1. Documentation is valued when it adds lasting value, but working software and conversation come first Correct answer.
  2. Documentation is prohibited because it slows delivery
  3. Only architects may write documentation
  4. Documentation must be complete before development starts

Explanation

Agile culture does not reject documentation; it weighs the value of documents against working software and direct conversation. Documentation that helps future understanding is kept, while documents produced only for their own sake are questioned. Prohibition, upfront completeness, and role restriction all misstate that balance.

Question 23Agile mindset and corporate culture

A program has five teams that each optimize their own throughput, and end-to-end delivery time keeps rising. Which cultural shift is most needed?

  1. More frequent team-level status reporting
  2. Stronger individual team incentives for higher velocity
  3. A shift from local optimization to shared accountability for end-to-end flow Correct answer.
  4. A larger backlog for each team to choose from

Explanation

When teams optimize only their own output, work queues between them and overall delivery slows. Agile culture at scale asks teams to share responsibility for the value stream rather than their local numbers. Stronger local incentives and more reporting would reinforce the same fragmentation.

Question 24Agile mindset and corporate culture

A leader asks teams to be 'fully transparent' but then uses the shared metrics to single out low performers in company-wide meetings. What is the most accurate analysis of this situation?

  1. The leader has confused visibility with safety, so teams will soon manage the numbers rather than the work Correct answer.
  2. Transparency has been implemented correctly because metrics are visible
  3. The teams should stop publishing any metrics until the leader changes
  4. The problem is that too few metrics are being collected

Explanation

Transparency only produces honest information when people feel safe being seen. Using metrics to single people out teaches teams to optimize what is measured and hide problems. Withdrawing all metrics would remove useful information, and the issue is not the quantity collected.

Question 25Agile mindset and corporate culture

An agile coach notices that teams comply with every ceremony but never challenge priorities set by leadership. Which diagnosis best fits an agile culture assessment?

  1. The teams have too much autonomy over their backlog
  2. The teams lack sufficient ceremony facilitation skills
  3. The teams show surface compliance while decision-making authority remains centralized Correct answer.
  4. The teams need more detailed process documentation

Explanation

Practicing ceremonies without influencing priorities is a sign that authority has not moved to the team, a pattern often called cargo-cult adoption. Agile culture requires teams to have real influence over what they work on and how. Facilitation skill, excessive autonomy, and more documentation do not explain the absence of challenge.

Question 26Agile mindset and corporate culture

An agile organization wants its values to shape daily decisions rather than sit on a poster. Which cultural signal most reliably shows that stated values are actually operating?

  1. The values are reviewed annually by a culture committee and reissued with updated wording
  2. Leaders make trade-off decisions that visibly follow the stated values, even when those choices cost time or money Correct answer.
  3. Teams recite the values at the start of each retrospective
  4. The values are printed on cards and displayed in every meeting room

Explanation

Culture is revealed by what leaders actually reward and choose when competing pressures collide, not by artifacts or rituals. When a value drives a costly trade-off, people learn it is real and start using it to guide their own decisions. Displaying or reciting values changes behavior only if decisions consistently back them up.

Question 27Agile mindset and corporate culture

A newly formed agile team keeps waiting for the manager to assign tasks and approve technical choices. Which cultural shift should the organization most directly encourage?

  1. Increasing the frequency of status reports sent to the manager
  2. Requiring the team to document each decision before acting
  3. Moving decision authority to the team and having the manager coach rather than direct Correct answer.
  4. Adding a second manager to share the approval workload

Explanation

Agile culture distributes authority to the people doing the work and reframes management as coaching and removing impediments. If the team must wait for assignment and approval, self-organization cannot develop regardless of how many ceremonies are run. Shifting decision rights, not adding oversight, is the cultural change required.

Question 28Agile mindset and corporate culture

A team's retrospective actions are consistently chosen by the scrum master alone, and team members describe the meeting as something done to them. Which change best rebuilds a culture of shared ownership of improvement?

  1. Rotating the retrospective facilitator among external agile coaches
  2. Letting the team choose which improvements to pursue and who owns each one Correct answer.
  3. Having the manager select the improvement actions to ensure they align with strategy
  4. Shortening the retrospective so it fits within a strict thirty-minute slot

Explanation

Continuous improvement depends on the team owning both the diagnosis and the resulting actions, which is what makes commitments stick. When one person selects the actions, the rest of the team becomes an audience and accountability disappears. Team-selected actions with named owners restore shared responsibility for change.

Question 29Agile mindset and corporate culture

A product manager learns mid-sprint that a competitor released a feature that changes customer expectations. Which response best reflects an agile culture of responding to change?

  1. Finish the committed sprint exactly as planned and schedule a discussion for the next quarterly planning
  2. Add the new work on top of existing commitments without removing anything
  3. Ask the team to assess the new information with the product owner and adjust priorities transparently Correct answer.
  4. Freeze the backlog until the annual strategy review confirms the new direction

Explanation

Responding to change means evaluating new information quickly and deliberately reordering work with the people who do it, while keeping priorities visible. This preserves both adaptability and the team's ability to finish what it starts. Ignoring the change or silently overloading the team both damage trust and predictability.

Question 30Agile mindset and corporate culture

An organization adopts agile terminology but its reward system still pays managers only for utilization of their staff and for on-time completion of fixed annual plans. Which analysis best explains why agile behaviors are not taking hold?

  1. The culture is being shaped by the incentive system, which rewards predictability and busyness over outcomes and adaptation Correct answer.
  2. The teams lack sufficient tooling to track their work at the required level of detail
  3. The organization has not yet hired enough certified agile coaches
  4. The ceremonies are being run incorrectly and need refresher training

Explanation

Structure and metrics teach people what the organization genuinely values, and they outweigh slogans and training. Paying for utilization and fixed-plan compliance rewards exactly the behaviors that agile culture asks people to unlearn, so training alone cannot shift behavior. Realignment of incentives toward outcomes and learning is the leverage point.

Question 31Value-driven delivery and prioritisation

In value-driven delivery, what does the term 'minimum viable product' (MVP) primarily describe?

  1. The internal prototype that is never shown to customers
  2. The lowest-cost version of the product with reduced quality
  3. The final release containing every feature requested by the sponsor
  4. The smallest release that delivers enough value to test a hypothesis and gather validated learning Correct answer.

Explanation

An MVP is the smallest increment that lets a team deliver real value and learn from actual customer use. It is defined by learning value, not by cost-cutting or feature completeness.

Question 32Value-driven delivery and prioritisation

A team is choosing which backlog items to deliver first. Which approach best reflects value-driven prioritisation?

  1. Rank items by expected value relative to effort and risk Correct answer.
  2. Deliver items in the order they were originally requested
  3. Sequence items alphabetically by feature name
  4. Prioritise the items that are easiest to estimate

Explanation

Value-driven prioritisation ranks work by the value it is expected to create against its cost, effort and uncertainty. Request order, ease of estimation and naming conventions carry no information about value.

Question 33Value-driven delivery and prioritisation

Which statement best captures the purpose of a prioritised product backlog in an agile delivery?

  1. It freezes scope so that change requests can be rejected
  2. It records the team's velocity history for reporting to stakeholders
  3. It documents every requirement that must be delivered before launch
  4. It provides an ordered list of work with the highest-value items positioned for early delivery Correct answer.

Explanation

The backlog is ordered so that the most valuable work is available for early delivery, and it stays dynamic as learning occurs. It is not a fixed scope document, a metrics log, or a change-control barrier.

Question 34Value-driven delivery and prioritisation

A product owner needs to compare backlog items with very different sizes and value. Which technique is designed specifically to rank items by value relative to cost of delay and effort?

  1. Earned value analysis (EVA)
  2. Root cause analysis (RCA)
  3. Critical path method (CPM)
  4. Weighted shortest job first (WSJF) Correct answer.

Explanation

WSJF ranks items by dividing the cost of delay by job size, producing a value-per-effort ordering. EVA and CPM are schedule and cost control techniques, and RCA is a problem-solving tool.

Question 35Value-driven delivery and prioritisation

What is the primary reason an agile team slices large features into smaller backlog items?

  1. To avoid the need for stakeholder reviews
  2. To allow value to be delivered incrementally and feedback to arrive sooner Correct answer.
  3. To keep the backlog permanently fixed in size
  4. To increase the number of story points in each sprint

Explanation

Smaller slices let the team release value earlier and learn from feedback before investing in the whole feature. Slicing is about flow of value and learning, not about inflating metrics or avoiding reviews.

Question 36Value-driven delivery and prioritisation

A stakeholder insists that a low-value compliance report be built before a high-value customer feature. The report is legally required by a fixed date three months away. What is the most appropriate response?

  1. Reject the report because it delivers no direct customer value
  2. Ask the team to build both simultaneously regardless of capacity
  3. Build the report immediately because any compliance item always outranks feature work
  4. Defer the report until just before its regulatory deadline and keep the high-value feature first Correct answer.

Explanation

Value-driven prioritisation accounts for cost of delay, and a deadline three months away means the report can wait without penalty. Sequencing it just before the deadline protects the higher-value feature while meeting the legal obligation.

Question 37Value-driven delivery and prioritisation

A team has limited capacity and two candidate items. Item A has a cost of delay of 60,000 per month and a job size of 3. Item B has a cost of delay of 40,000 per month and a job size of 1. Using WSJF, which item should be prioritised?

  1. Item B, because its WSJF score of 40,000 exceeds Item A's 20,000 Correct answer.
  2. Item A, because larger job sizes always signal more strategic value
  3. Neither; the team should split capacity equally between them
  4. Item A, because its absolute cost of delay is higher

Explanation

WSJF is cost of delay divided by job size: Item A scores 20,000 and Item B scores 40,000. The higher ratio means Item B delivers more value per unit of effort, so it should be sequenced first.

Question 38Value-driven delivery and prioritisation

A product owner is refining a backlog and finds a story that bundles several unrelated capabilities. What is the best value-driven action?

  1. Estimate it at the maximum story point value and proceed
  2. Split it into smaller stories that each deliver a testable increment of value Correct answer.
  3. Move it to the bottom of the backlog until it can be estimated
  4. Leave it intact to preserve the original scope

Explanation

Splitting a bundled story into value-bearing slices makes it easier to prioritise, estimate and release incrementally. Keeping it whole delays feedback and obscures which part carries the value.

Question 39Value-driven delivery and prioritisation

Which practice best supports continuous value delivery in a flow-based agile team?

  1. Starting new work whenever a team member becomes free
  2. Limiting work in progress so items move to completion faster Correct answer.
  3. Batching all releases to a single annual event
  4. Measuring success only by the number of items started

Explanation

Limiting work in progress reduces multitasking and queue time, allowing items to finish and deliver value sooner. Starting work freely, large release batches and counting started items all slow the flow of completed value.

Question 40Value-driven delivery and prioritisation

A sponsor asks why the team is releasing a feature with only the most-used 40 percent of the planned capabilities. Which explanation best reflects value-driven delivery?

  1. Releasing early captures value sooner and allows the remaining scope to be reshaped by real feedback Correct answer.
  2. The remaining capabilities will be delivered without further prioritisation
  3. Partial releases are always required by agile contracts
  4. The team was unable to build the remaining capabilities in time

Explanation

Early release of the highest-value portion starts value realisation and generates feedback that informs the rest of the scope. It is a deliberate value decision rather than a capacity failure or contractual formality.

Question 41Value-driven delivery and prioritisation

During a review, data shows a delivered feature is used by only two percent of customers despite high projected value. What is the most value-driven response?

  1. Increase the projected value estimate to justify the prior decision
  2. Reassess the backlog and reallocate effort toward items with stronger evidence of value Correct answer.
  3. Remove the feature from the product without further analysis
  4. Continue investing in the feature as planned because it was already prioritised

Explanation

Value-driven delivery relies on empirical evidence, so weak adoption should trigger re-prioritisation toward better-evidenced items. Persisting, deleting without analysis, or inflating estimates all ignore the data.

Question 42Value-driven delivery and prioritisation

Which metric best indicates whether a team is delivering value rather than merely producing output?

  1. Percentage of released features that achieve their target outcome Correct answer.
  2. Total lines of code written by the team
  3. Number of story points completed per sprint
  4. Count of meetings held with stakeholders

Explanation

Outcome-based measures such as the share of features hitting their intended business result show whether output translated into value. Story points, code volume and meeting counts measure activity or output only.

Question 43Value-driven delivery and prioritisation

A product owner uses MoSCoW to classify backlog items. Which category should contain items that are useful but can be deferred without breaking the release?

  1. Could have Correct answer.
  2. Should have
  3. Won't have this time
  4. Must have

Explanation

In MoSCoW, 'Could have' items are desirable but non-essential and can be dropped without invalidating the release. 'Must have' items are mandatory, 'Should have' items are important but not critical, and 'Won't have' items are explicitly excluded.

Question 44Value-driven delivery and prioritisation

A team's backlog contains a high-value item that depends on a platform capability not yet available. How should the product owner handle prioritisation?

  1. Ignore the dependency and start the value item immediately
  2. Rank the enabling platform work appropriately so the value item can be delivered sooner Correct answer.
  3. Move the value item to the bottom of the backlog permanently
  4. Remove the dependency from the backlog to simplify reporting

Explanation

Enabling work that unblocks high-value items should be prioritised in its own right, since it protects the cost of delay of the dependent value. Ignoring or hiding the dependency guarantees delay.

Question 45Value-driven delivery and prioritisation

Which statement correctly distinguishes output from outcome in value-driven delivery?

  1. Output is the change in business results; outcome is the work produced
  2. Output and outcome are interchangeable terms for delivered features
  3. Output is the work or features produced; outcome is the resulting change in behaviour or results Correct answer.
  4. Outcome refers only to the number of releases shipped

Explanation

Output describes what the team produced, while outcome describes the change in customer or business results that the output causes. Confusing the two leads teams to optimise activity rather than value.

Question 46Value-driven delivery and prioritisation

A team must choose between two features of similar value, but Feature X can be delivered in one week while Feature Y requires three months. Assuming equal cost of delay per month, which should be prioritised and why?

  1. Feature Y, because longer work demonstrates greater commitment
  2. Feature Y, because larger efforts always yield more learning
  3. Either, because duration is irrelevant when value is equal
  4. Feature X, because its shorter duration reduces the time before value is realised and lowers risk Correct answer.

Explanation

With equal value and equal cost of delay per month, the shorter item returns value sooner and carries less exposure to change and risk. Duration therefore favours Feature X under WSJF-style reasoning.

Question 47Value-driven delivery and prioritisation

In a Kanban system, a column has a work-in-progress limit of three and currently holds three items. A team member finishes one item. What should happen next?

  1. The completed item is returned to the column until the sprint ends
  2. The team member starts a second item in the same column without pulling
  3. A new item is pulled into the column from the upstream queue Correct answer.
  4. The WIP limit is raised to four to keep everyone busy

Explanation

When an item leaves a column, capacity becomes available and the next item is pulled from upstream, preserving the WIP limit. Raising limits or starting extra work defeats the purpose of limiting WIP.

Question 48Value-driven delivery and prioritisation

A product owner is asked to justify why a regulatory item sits below a revenue item in the backlog even though the regulatory item is mandatory. What is the strongest justification?

  1. The regulatory deadline is far enough away that its cost of delay is currently lower than the revenue item's Correct answer.
  2. Revenue items always carry more legal risk than regulatory items
  3. Regulatory items should be excluded from the backlog entirely
  4. Mandatory items are never prioritised until all revenue work is complete

Explanation

Prioritisation is driven by cost of delay, and a distant deadline means the regulatory item can wait without penalty while the revenue item cannot. Mandatory status sets a floor on when work must happen, not an automatic top rank.

Question 49Value-driven delivery and prioritisation

A team applies WSJF and finds that a large architectural enabler scores lower than several feature items. Leadership wants the enabler prioritised anyway. What is the most defensible value-driven argument?

  1. The enabler should be split or its cost of delay re-examined, since enablers gain value by accelerating dependent items Correct answer.
  2. The WSJF score should be ignored entirely for technical items
  3. The enabler should always be prioritised because technical work outranks features
  4. The features should be delayed indefinitely until the enabler is complete

Explanation

Enablers create value indirectly by reducing the cost of delay of dependent items, so their true cost of delay may be understated. Splitting the enabler or reassessing its cost of delay yields a defensible ranking rather than an arbitrary override.

Question 50Value-driven delivery and prioritisation

A programme has three teams whose backlogs share a critical dependency on one shared component. Which prioritisation approach best protects overall value delivery?

  1. The teams jointly sequence the shared component's work ahead of dependent items across backlogs Correct answer.
  2. Dependent items are started in parallel to shorten the overall timeline
  3. The shared component is deprioritised because it delivers no end-user value itself
  4. Each team prioritises independently and resolves conflicts at integration time

Explanation

Shared dependencies should be sequenced jointly so that enabling work lands before the dependent items that carry the value. Independent prioritisation and parallel starts create blocked work and integration delays.