I85PREP
⌘ K
PMI-ACP study materials
PMI-ACP study resources

PMI-ACP practice questions

One question at a time. Build your PMI-ACP 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 Principles and Mindset

Which statement expresses one of the four values of the Agile Manifesto?

  1. Detailed contracts over customer collaboration
  2. Process compliance and tools over individual interaction and skills
  3. Following a plan over responding to change
  4. Working software over comprehensive documentation Correct answer.

Explanation

The Agile Manifesto values individuals and interactions, working software, customer collaboration, and responding to change over their counterparts. Working software over comprehensive documentation is one of the four stated values. The other pairings reverse the manifesto's stated preference.

Question 2Agile Principles and Mindset

According to the principles behind the Agile Manifesto, what is the highest priority of an agile team?

  1. Producing comprehensive documentation so that auditors can verify every delivered feature
  2. Satisfying the customer through early and continuous delivery of valuable software Correct answer.
  3. Meeting the schedule and cost baseline that was approved at project initiation
  4. Maximizing the number of features completed in each iteration

Explanation

The first principle states that the highest priority is to satisfy the customer through early and continuous delivery of valuable software. Feature counts and baseline adherence are means, not the stated priority. Documentation serves delivery rather than replacing it.

Question 3Agile Principles and Mindset

Which three elements are the pillars of empirical process control?

  1. Transparency, inspection, and adaptation Correct answer.
  2. Scope, schedule, and cost
  3. Planning, executing, and closing
  4. Vision, backlog, and increment

Explanation

Empirical process control rests on making the process and its artifacts visible, inspecting them frequently enough to detect deviation, and adapting the process or product based on what is found. The other sets describe process groups, traditional constraints, or agile artifacts rather than control mechanisms.

Question 4Agile Principles and Mindset

What is a timebox in agile practice?

  1. A budget ceiling set by the sponsor that limits spending within an iteration
  2. A deadline by which every user story committed for the iteration must be finished and accepted
  3. A fixed period, after which the event ends regardless of whether the work is complete Correct answer.
  4. A commitment to deliver a fixed scope on a fixed date regardless of what is learned

Explanation

A timebox is a maximum, fixed duration for an event such as an iteration, daily stand-up, or retrospective. When the time is up, the event ends, and any unfinished work is carried forward or re-planned rather than extending the box. This protects cadence and forces focus.

Question 5Agile Principles and Mindset

What does it mean for an agile team to be cross-functional?

  1. The team collectively holds all the skills needed to deliver a working increment Correct answer.
  2. The team reports to several functional managers who each own a portion of the work
  3. Every member is trained to perform every role so that anyone can replace anyone else on demand
  4. Team members are assigned to multiple projects at the same time to share expertise

Explanation

Cross-functional means the team as a whole possesses the range of skills required to take an item from idea to a working, tested increment. It does not require every individual to be interchangeable. Shared responsibility for delivery is what reduces handoffs and external dependencies.

Question 6Agile Principles and Mindset

In an agile context, what is the primary role of a servant leader?

  1. Approving technical design decisions before the team implements them
  2. Escalating every team conflict to senior management so that decisions are made consistently
  3. Assigning work to each individual and monitoring utilization against the plan
  4. Removing impediments and creating the conditions for the team to succeed Correct answer.

Explanation

Servant leadership shifts the leader's focus to enabling the team: clearing obstacles, protecting the team, and fostering growth and self-management. The team retains authority over how it does the work. Directive task assignment and decision approval work against that intent.

Question 7Agile Principles and Mindset

What is the purpose of a retrospective?

  1. To inspect how the team works together and choose improvements for the next iteration Correct answer.
  2. To estimate the effort required for the items proposed for the next iteration
  3. To review the project budget and update the schedule baseline before the next funding gate
  4. To demonstrate completed features to stakeholders and collect their feedback

Explanation

A retrospective is a team event focused on the process and working relationships: what went well, what did not, and what to change. Its output is a small set of improvement actions the team owns. Product demonstration and estimation belong to other events.

Question 8Agile Principles and Mindset

What does self-organization mean for an agile team?

  1. The team sets its own salaries and working hours without any management oversight or accountability
  2. The team decides how to accomplish its work rather than being directed task by task Correct answer.
  3. The team works without a defined goal or any external accountability for outcomes
  4. The team selects its own customers and negotiates the commercial contract directly

Explanation

Self-organization means the people closest to the work decide how to plan and execute it, within the boundaries set by the organization and the product goal. Accountability for outcomes remains, and direction on what to build still comes from the product owner and stakeholders.

Question 9Agile Principles and Mindset

What does the Shu-Ha-Ri model describe?

  1. The flow of value from concept through delivery to realized customer benefit
  2. The sequence of forming, storming, norming, and performing in a new team
  3. The iterative cycle of plan, do, check, and act used for process improvement
  4. The progression from following rules, to deliberately breaking them, to transcending rules in mastery Correct answer.

Explanation

Shu-Ha-Ri is a model of skill acquisition: in Shu the learner follows established rules, in Ha the learner understands principles and departs from rules, and in Ri the practitioner operates fluidly beyond formal rules. It informs how a coach matches guidance to a team's maturity.

Question 10Agile Principles and Mindset

Which statement best characterizes adaptive planning?

  1. Planning is performed once by the sponsor and then delegated to the delivery team
  2. A detailed schedule for every iteration is produced during initiation and then frozen until closure
  3. Plans are rewritten from scratch at every stand-up meeting to stay current
  4. Plans are progressively refined as knowledge and feedback increase Correct answer.

Explanation

Adaptive planning treats the plan as a living artifact that is elaborated at the last responsible moment and revised as new information arrives. Rolling-wave elaboration replaces one-time detailed forecasting. It does not mean planning is abandoned or redone constantly.

Question 11Agile Principles and Mindset

In the agile triangle of competing constraints, which elements are typically held firm while scope and schedule are allowed to vary?

  1. Value and quality Correct answer.
  2. Scope and cost
  3. Schedule and staffing levels
  4. Documentation and process rigor

Explanation

Agile approaches invert the traditional iron triangle: value and quality are protected as fixed, while scope and schedule flex to fit the fixed time and cost of iterations. This keeps the emphasis on delivering a high-quality, valuable increment rather than on hitting a pre-committed scope.

Question 12Agile Principles and Mindset

The principle 'Simplicity-the art of maximizing the amount of work not done-is essential' most directly calls for a team to:

  1. Reduce the number of team members so that coordination overhead and meeting time are lowered
  2. Keep design documents short so that the team can spend more time writing code
  3. Deliver fewer increments so that testing and review effort are minimized
  4. Build only what is needed and defer or eliminate features that add no value Correct answer.

Explanation

The principle targets unnecessary work of any kind, including unneeded features and speculative requirements. The team should satisfy the need with the simplest thing that works and defer or drop the rest. Cutting documentation or headcount is not what the principle is about.

Question 13Agile Principles and Mindset

What does the agile principle of sustainable pace require of a team?

  1. Each iteration should consume the team's full maximum capacity so no slack remains
  2. Velocity should increase every iteration so the team remains competitive against other teams
  3. The team should be able to maintain a constant pace indefinitely without burning out Correct answer.
  4. Overtime is acceptable whenever the product owner approves it at iteration planning

Explanation

The principle states that agile processes promote sustainable development and that sponsors, developers, and users should be able to maintain a constant pace indefinitely. Chronic overwork degrades quality and predictability. Occasional extra effort does not make sustained overtime a practice.

Question 14Agile Principles and Mindset

A distributed team relies almost entirely on written tickets and email to clarify requirements. What should an agile coach recommend?

  1. Rich real-time conversation, such as video sessions and pairing, wherever possible Correct answer.
  2. More detailed written specifications with formal sign-off at each stage
  3. Longer documentation templates reviewed by the project management office
  4. A stricter change-control board to review all requirement updates

Explanation

The principles state that the most efficient and effective method of conveying information is face-to-face conversation, and this intent carries to distributed teams through the richest channel available. Real-time dialogue resolves ambiguity far faster than document exchange. Additional documentation and control add latency rather than clarity.

Question 15Agile Principles and Mindset

What is the main benefit of osmotic communication in a colocated agile team?

  1. It requires the team to hold additional status meetings so that everyone stays informed
  2. It removes the need for a shared definition of done agreed by the team
  3. Information is absorbed by overhearing nearby conversations, giving rapid awareness at low effort Correct answer.
  4. It guarantees that every decision is documented and available for audit and compliance review

Explanation

Osmotic communication describes information flowing into a person's awareness simply by being physically near the work and conversations. It reduces the cost of staying informed and speeds up coordination. It complements, but does not replace, explicit agreements and records.

Question 16Agile Principles and Mindset

Why is emotional intelligence important in an agile team?

  1. It is used mainly to score team members objectively during performance reviews
  2. Self-awareness and empathy help the team self-manage conflict and give candid feedback Correct answer.
  3. It lets the coach suppress open disagreement so that the team reaches consensus more quickly
  4. It replaces the need for working agreements and agreed team norms

Explanation

Self-organizing teams must handle disagreement, give and receive feedback, and sustain trust without a manager arbitrating every issue. Emotional intelligence supplies the self-awareness and empathy that make those interactions productive. It does not remove the need for explicit norms.

Question 17Agile Principles and Mindset

How is tacit knowledge most effectively shared within an agile team?

  1. A detailed wiki that documents every procedure the team follows
  2. Pairing, mentoring, and working alongside experienced colleagues Correct answer.
  3. A lessons-learned repository that is reviewed at the end of the project
  4. Individual self-study of archived project reports and specifications

Explanation

Tacit knowledge is the know-how that is difficult to write down, so it transfers through shared experience and observation. Pairing, mentoring, and collaborative work place people side by side so the knowledge moves. Written artifacts capture explicit knowledge much better than tacit knowledge.

Question 18Agile Principles and Mindset

A vendor and a customer have signed a fixed-price contract for an agile engagement. How should the principle of customer collaboration over contract negotiation be applied?

  1. Treat the contract terms as the primary measure of project success and enforce them strictly
  2. Decline to sign contracts, because agile practice is incompatible with formal agreements
  3. Protect the relationship with frequent collaboration while honoring the contract's intent Correct answer.
  4. Renegotiate the scope every iteration so the customer absorbs all the uncertainty

Explanation

The manifesto values customer collaboration over contract negotiation, which means the contract is a framework for an ongoing working relationship rather than a weapon. Frequent collaboration and transparency let both sides adjust as knowledge grows. This reduces the need for adversarial enforcement.

Question 19Agile Principles and Mindset

A team reports that a feature is '80 percent complete,' but nothing has been demonstrated or tested end to end. What is the most appropriate agile response?

  1. Ask for a demonstrable, tested increment as the true measure of progress Correct answer.
  2. Accept the figure because earned value analysis reliably predicts final completion
  3. Increase documentation of the remaining work so progress can be verified by reviewers
  4. Convert the percentage into story points and plot it on the burndown chart

Explanation

Agile principles state that working software is the primary measure of progress, because partial work carries hidden rework and integration risk. Progress should be evidenced by an increment that is built, tested, and demonstrable. Percentage-complete figures rest on assumptions rather than evidence.

Question 20Agile Principles and Mindset

The principle 'Build projects around motivated individuals' suggests the organization should:

  1. Support and trust the team and remove obstacles so they can get the job done Correct answer.
  2. Provide detailed task assignments so that no team member is ever idle
  3. Tie individual bonuses to the number of lines of code each developer writes
  4. Require each individual to submit a daily status report so progress is always visible to managers

Explanation

The principle states that projects should be built around motivated individuals, who should be given the environment and support they need and trusted to get the job done. Trust plus obstacle removal is the enabling condition. Micromanagement and individual output metrics undermine motivation.

Question 21Agile Principles and Mindset

A team faces a situation in which cause and effect are only visible in retrospect and no recognized best practice applies. According to the Cynefin framework, what is the appropriate response?

  1. Probe with safe-to-fail experiments, then sense and respond to what emerges Correct answer.
  2. Act immediately to impose order before any analysis or experimentation is attempted
  3. Sense the situation, categorize it against known patterns, and respond with best practice
  4. Analyze the situation thoroughly, then apply expert-designed good practice

Explanation

This describes the complex domain, where patterns emerge only after action. The Cynefin response there is to probe with safe-to-fail experiments, sense what happens, and amplify what works. Categorization and analysis-based responses belong to the complicated or simple domains.

Question 22Agile Principles and Mindset

Which situation is the clearest example of the lean waste known as partially done work?

  1. A feature is rebuilt because the requirement was misunderstood the first time
  2. A developer idles for an hour while waiting for a build to finish running
  3. Features that are coded but never integrated or tested, sitting in a queue Correct answer.
  4. Extra approval signatures are added to a deployment process that no one has questioned

Explanation

Partially done work is inventory that has been started but not finished, such as code that is written but unintegrated and therefore delivers no value while still accumulating risk and carrying cost. Waiting, rework, and unnecessary approvals are different categories of waste.

Question 23Agile Principles and Mindset

A specialist team completes its work rapidly, but the downstream testing group is first starved of work and then flooded with a large batch. What does a systems-thinking perspective suggest?

  1. Measure each stage on its own utilization and reward the stage with the highest utilization
  2. Place large buffers of unfinished work between every stage to absorb the variation
  3. Optimize the flow of the whole value stream rather than the throughput of one stage Correct answer.
  4. Increase the specialist team's capacity further so the downstream queue never empties

Explanation

Systems thinking holds that optimizing one component in isolation degrades the performance of the whole, because local speed creates queues downstream. The remedy is to manage flow across the value stream, for example by limiting work in progress and right-sizing batches. Local efficiency metrics reinforce the problem.

Question 24Agile Principles and Mindset

Research on motivation summarized by Daniel Pink suggests that for creative knowledge work, rewards should be designed so that:

  1. Pay is tied to individual velocity so that engagement rises with output
  2. Extrinsic and intrinsic motivators are equally effective for all types of tasks
  3. Piece-rate bonuses are the strongest driver of complex problem solving
  4. Intrinsic motivators outperform contingent if-then rewards for creative work Correct answer.

Explanation

Pink's synthesis of the research is that once pay is sufficient and fair, autonomy, mastery, and purpose drive creative work more effectively than contingent rewards, which can narrow focus and reduce performance on complex tasks. This supports self-organizing teams and purpose-driven goals. Contingent rewards remain appropriate mainly for simple, routine tasks.

Question 25Agile Principles and Mindset

A team's retrospectives keep producing fixes for symptoms, yet the same problems return every few iterations. What would double-loop learning have the team do?

  1. Track the defects more precisely so that the trend is clearly visible over time
  2. Repeat the same corrective actions more consistently until the process finally stabilizes
  3. Question the underlying assumptions, policies, and norms that produce the recurring problems Correct answer.
  4. Escalate each recurring symptom to management so it can be fixed more quickly

Explanation

Single-loop learning corrects errors within existing assumptions, while double-loop learning examines and changes the governing assumptions, policies, and norms that generate the errors. Recurring problems are a signal that the underlying rules, not just the actions, need revision. This is how a team becomes a learning organization.

Question 26Agile Principles and Mindset

According to the Agile Manifesto, which item is valued more highly than comprehensive documentation?

  1. Processes and tools
  2. Contract negotiation
  3. Working software Correct answer.
  4. Following a plan

Explanation

The Manifesto's value statements rank working software above comprehensive documentation, while still recognizing that documentation has value. The other three items belong to different pairings in the same set of value statements, each also placed on the lower-weighted side of its pair.

Question 27Agile Principles and Mindset

Under schedule pressure, a team proposes dropping code reviews and refactoring for the next two iterations so it can finish more stories. What response is most consistent with agile principles?

  1. Replace code reviews with a dashboard metric that reports review coverage for each developer on the team
  2. Defer the decision to the product owner, who can weigh the quality practices against the schedule cost for each release
  3. Accept the proposal, since any quality debt can be repaid in a single hardening iteration before release
  4. Reject the proposal and keep investing in technical excellence, because agility depends on a codebase that stays cheap to change Correct answer.

Explanation

Agile principles call for continuous attention to technical excellence and good design, precisely because the ability to respond to change later depends on a design that has not been allowed to decay. Quality practices are therefore treated as an enabler of speed rather than as optional overhead that can be traded away for short-term output.

Question 28Agile Principles and Mindset

A team reliably completes every story it commits to, yet usage data shows customers rarely use the new features. Which conclusion best reflects agile thinking?

  1. Value is unproven, so the backlog should be reshaped around measured customer outcomes Correct answer.
  2. Delivery capability has been proven, so the team should raise its commitment level for the next iteration
  3. The product owner should add acceptance criteria requiring usage data to be collected for every story
  4. The team should shorten its iterations so that more features reach customers sooner in each release

Explanation

Agile practice measures progress by value delivered to the customer, not by volume of completed work, so high throughput with low adoption signals a problem in what is being built rather than how fast. The appropriate response is to inspect the outcome data and reorder or rewrite the backlog so that the next increments address validated customer needs.

Question 29Value-Driven Delivery

What is the primary purpose of a minimum viable product (MVP)?

  1. To minimize the number of defects found in production
  2. To document every requirement before development begins
  3. To test the core value hypothesis with the least effort Correct answer.
  4. To release a feature-complete product to the widest audience

Explanation

An MVP is the smallest thing a team can build that allows it to validate assumptions about customer value with real feedback. Its purpose is learning, not completeness or polish.

Question 30Value-Driven Delivery

A product owner must compare two candidate features that have different costs and different expected benefits. Which measure expresses expected benefit as a proportion of the investment?

  1. Return on investment Correct answer.
  2. Break-even point
  3. Payback period
  4. Net present value

Explanation

Return on investment divides the net benefit by the cost, so features of very different sizes can be compared on a common ratio. The other measures describe timing or absolute money amounts rather than benefit per unit invested.

Question 31Value-Driven Delivery

In MoSCoW prioritization, which category contains items required for the release to be acceptable at all?

  1. Could have
  2. Should have
  3. Must have Correct answer.
  4. Will not have this time

Explanation

Must-have items are non-negotiable: without them the release fails its purpose and cannot be shipped. Should-have and could-have items are important or desirable but their absence does not invalidate the release.

Question 32Value-Driven Delivery

What is the main value-related benefit of delivering a product incrementally rather than in a single final release?

  1. It allows the team to work without a product backlog
  2. It guarantees that scope will not change during the project
  3. It removes the need for regression testing between releases
  4. It realizes benefits earlier and allows course correction from feedback Correct answer.

Explanation

Incremental delivery converts completed work into realized value sooner and exposes the product to real usage, which informs the next decisions. The earlier the feedback, the cheaper it is to change direction.

Question 33Value-Driven Delivery

What role does an agreed definition of done play in value-driven delivery?

  1. It authorizes the product owner to reject the sprint goal
  2. It sets a shared quality bar so each increment is releasable Correct answer.
  3. It records the tasks the team will perform each day
  4. It lists the acceptance tests for one specific user story

Explanation

A definition of done applies to every increment and prevents partially finished work from being counted as value delivered. Story-level acceptance criteria are narrower and exist per item.

Question 34Value-Driven Delivery

How does a minimum marketable feature differ from a minimal viable product?

  1. It is the smallest feature that delivers value on its own Correct answer.
  2. It is a prototype built only to test technical feasibility
  3. It is the smallest unit of work in a sprint backlog
  4. It is a document describing the full product scope

Explanation

A minimum marketable feature is the smallest piece of functionality that a customer would value and could use independently. A minimal viable product is typically a collection of such features sufficient to validate a hypothesis.

Question 35Value-Driven Delivery

When a backlog is ordered by business value, which items should generally be delivered first?

  1. The items producing the highest value relative to cost and risk Correct answer.
  2. The items the most senior stakeholder requested
  3. The items that are easiest for the team to build
  4. The items with the largest number of acceptance criteria

Explanation

Value-driven ordering weighs expected benefit against the effort and uncertainty of achieving it, so the best return is realized earliest. Effort alone, rank alone, or document size alone are not measures of value.

Question 36Value-Driven Delivery

In Kano analysis, how is a delighter attribute described?

  1. Its absence goes unnoticed but its presence delights customers Correct answer.
  2. Its presence and absence are noticed equally by customers
  3. Its absence causes strong dissatisfaction, but its presence adds little
  4. It is a requirement mandated by external regulation

Explanation

Delighters are unexpected attributes whose absence causes no dissatisfaction but whose presence creates disproportionate satisfaction. Basic attributes behave in the opposite way, causing dissatisfaction when missing.

Question 37Value-Driven Delivery

A team scores four items. Item P: cost of delay 9, job size 3. Item Q: cost of delay 6, job size 3. Item R: cost of delay 8, job size 8. Item S: cost of delay 4, job size 1. Using weighted shortest job first, which item should be sequenced first?

  1. Item P
  2. Item S Correct answer.
  3. Item R
  4. Item Q

Explanation

Weighted shortest job first ranks work by cost of delay divided by job size. The scores are S = 4.0, P = 3.0, Q = 2.0 and R = 1.0, so S has the highest economic priority.

Question 38Value-Driven Delivery

A team maps its delivery process and finds that code waits an average of eight days for review while development work itself takes two days. What does the value stream map reveal?

  1. Most elapsed time is waiting, so the review queue is the key target Correct answer.
  2. The process is balanced and no improvement is warranted
  3. The team's development work is the largest source of delay
  4. The team should add development capacity to cut total lead time

Explanation

Value stream maps separate processing time from waiting time, and here roughly eighty percent of lead time is queueing for review. Improving the constraint shortens total lead time far more than speeding up an activity that is already short.

Question 39Value-Driven Delivery

A kanban board has a testing column with a strict work-in-progress limit of three, while six finished development items wait to be tested. What is the most appropriate value-driven response?

  1. Stop starting new work and help clear the testing bottleneck Correct answer.
  2. Ask testers to work overtime until the queue is cleared
  3. Raise the work-in-progress limit so all finished items can enter testing
  4. Move the waiting items back to development so the board looks balanced

Explanation

A full downstream column signals a constraint; the value-driven response is to stop feeding the system and swarm on the bottleneck. Raising limits or hiding the queue preserves the problem and increases lead time.

Question 40Value-Driven Delivery

An average of twelve items are in progress and the team completes an average of four items per week. Using Little's Law, what is the approximate average cycle time?

  1. 0.33 weeks
  2. 16 weeks
  3. 4 weeks
  4. 3 weeks Correct answer.

Explanation

Little's Law states that average cycle time equals work in progress divided by throughput. Dividing twelve items in progress by four items per week gives three weeks.

Question 41Value-Driven Delivery

On a cumulative flow diagram the band for work in test has widened steadily for several weeks while the done band grows only slightly. What does this indicate?

  1. The team's velocity is increasing steadily
  2. The team is completing work faster than it starts it
  3. Work is accumulating in testing, which is now the constraint Correct answer.
  4. The project scope has been reduced

Explanation

Band width represents the quantity of work in a state, so a widening test band means arrivals exceed departures there. The system constraint has moved to testing and overall throughput will suffer until it is relieved.

Question 42Value-Driven Delivery

A project has a planned value of 200,000, an earned value of 150,000 and an actual cost of 180,000. What do these figures show?

  1. The project is behind schedule and over budget Correct answer.
  2. The project is ahead of schedule but over budget
  3. The project is ahead of schedule and under budget
  4. The project is behind schedule but under budget

Explanation

Schedule variance is earned value minus planned value, giving minus 50,000, so work is behind plan. Cost variance is earned value minus actual cost, giving minus 30,000, so spending exceeds the value earned.

Question 43Value-Driven Delivery

Two candidate projects have the same total undiscounted cash inflow, but project X receives its cash earlier than project Y. Assuming the same discount rate, which statement is correct?

  1. Project X has the higher net present value because its cash arrives sooner Correct answer.
  2. Project Y has the higher net present value because it runs longer
  3. Net present value cannot be compared unless payback periods are equal
  4. Both projects have identical net present value because total inflow is equal

Explanation

Discounting reduces the present worth of money received later, so earlier cash flows retain more value. With equal totals, the project with the faster inflow has the higher net present value.

Question 44Value-Driven Delivery

A feature costs 60,000 to build and is expected to generate 5,000 of benefit per month. What is its simple payback period?

  1. 6 months
  2. 60 months
  3. 12 months Correct answer.
  4. 5 months

Explanation

Simple payback divides the investment by the periodic benefit, so 60,000 divided by 5,000 gives twelve months. It measures time to recover cost, not the total return.

Question 45Value-Driven Delivery

Two features require equal development effort. Feature A would generate 20,000 of value per month and feature B would generate 8,000 per month. What does cost of delay analysis imply?

  1. Both should wait until the full release is ready
  2. The decision should be based only on story point totals
  3. Feature B should go first because it is cheaper to delay
  4. Feature A should go first because delaying it costs more each month Correct answer.

Explanation

Cost of delay expresses the value lost per unit of time a feature is not available, so the larger monthly value creates the larger penalty for waiting. When effort is equal, the higher cost of delay is sequenced first.

Question 46Value-Driven Delivery

A team arranges stories along a horizontal backbone of user activities and slices them vertically into releases. What is the main benefit of this arrangement?

  1. It removes dependencies between teams
  2. It replaces the need for a product backlog
  3. It guarantees that every story has the same estimate
  4. It reveals which end-to-end slices form a viable first release Correct answer.

Explanation

A story map shows the user journey and the depth of functionality needed at each step, which makes whole, usable slices visible. Teams use that view to choose a first release that delivers a coherent outcome.

Question 47Value-Driven Delivery

How does a risk-adjusted backlog differ from one ordered purely by business value?

  1. It orders items by the seniority of the requesting stakeholder
  2. It ranks items by the number of defects they are expected to cause
  3. It removes all high-risk items from the backlog
  4. It brings high-risk items forward so uncertainty falls sooner Correct answer.

Explanation

Risk adjustment raises the priority of work that can retire significant uncertainty early, because late discovery of a problem is expensive. The aim is to buy information soon, not to avoid risky work.

Question 48Value-Driven Delivery

A team is deciding whether to spend an iteration reducing technical debt instead of building new features. Which reasoning best reflects value-driven delivery?

  1. Technical debt is invisible to customers, so it can be deferred indefinitely
  2. Repay debt where accumulated interest threatens future value Correct answer.
  3. Technical debt must always be repaid in full before new features
  4. Debt repayment is a quality activity owned solely by testers

Explanation

Technical debt behaves like financial debt: the interest shows up as slower delivery, rising defects and higher change costs. Value-driven decisions target the debt whose interest most endangers future delivery rather than treating all debt identically.

Question 49Value-Driven Delivery

A financial product must satisfy a regulatory reporting requirement before any customer-facing feature can be released. How should this be handled in a value-driven backlog?

  1. Treat it as a release-gating constraint and plan it early Correct answer.
  2. Defer it until the final release because it adds no customer value
  3. Replace it with a story about reporting convenience
  4. Assign it to the team with the lowest workload regardless of sequence

Explanation

Mandatory constraints do not compete on ordinary value ranking because no value is realized if the release cannot legally ship. They are sequenced as gates and completed before dependent work.

Question 50Value-Driven Delivery

A team faces significant uncertainty about whether a new payment provider can meet performance needs. What is the most appropriate value-driven action?

  1. Build the full feature and measure performance in production
  2. Estimate the feature and commit to delivering it next iteration
  3. Run a time-boxed spike to test feasibility before further investment Correct answer.
  4. Escalate the decision to the sponsor without investigation

Explanation

A time-boxed spike buys information about a technical unknown at low cost before the team commits larger effort. Committing ahead of the answer risks building on an assumption that may fail.