I85PREP
⌘ K
COPR ACP study materials
COPR ACP study resources

COPR ACP practice questions

One question at a time. Build your COPR 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 and Lean Foundations

In Lean thinking, what does the term 'muda' refer to?

  1. The rate at which a process delivers finished items to the customer
  2. Any activity that consumes resources without creating value for the customer Correct answer.
  3. The cross-functional team that owns a value stream
  4. The visual signal used to trigger replenishment of materials

Explanation

Muda is the Japanese term for waste, meaning work that consumes resources but adds no value in the eyes of the customer. Lean practice seeks to identify and eliminate such activity so that effort flows toward value creation.

Question 2Agile and Lean Foundations

A team building a payroll feature discovers that a required compliance approval takes three weeks and blocks release. Which Lean waste category does this waiting most directly represent?

  1. Inventory
  2. Over-production
  3. Delay and waiting Correct answer.
  4. Defects

Explanation

Time spent idle because an approval is pending is the waste of waiting, one of the classic Lean wastes. The work cannot advance, so lead time grows without any value being added.

Question 3Agile and Lean Foundations

Which statement best captures the Agile Manifesto value regarding documentation?

  1. Documentation must be produced only after release
  2. Comprehensive documentation is prohibited on Agile projects
  3. Documentation replaces the need for customer collaboration
  4. Working software is valued over comprehensive documentation Correct answer.

Explanation

The manifesto values working software over comprehensive documentation while still acknowledging value in documentation. The point is relative priority, not elimination of written artifacts.

Question 4Agile and Lean Foundations

A Scrum team finishes its sprint review and the product owner wants to reorder the backlog based on what customers said. Which Agile principle most directly supports this?

  1. Deliver working software frequently
  2. Simplicity is essential
  3. Responding to change over following a plan Correct answer.
  4. Build projects around motivated individuals

Explanation

Adapting priorities based on fresh customer feedback reflects the value of responding to change over rigidly following a plan. Agile planning is deliberately revisable as new information arrives.

Question 5Agile and Lean Foundations

What is the primary purpose of a value stream map in a Lean transformation?

  1. To document the organizational reporting hierarchy
  2. To assign individual performance ratings to each worker
  3. To replace the product backlog with a fixed schedule
  4. To make the end-to-end flow of work and its delays visible Correct answer.

Explanation

A value stream map depicts the steps, handoffs, queues, and delays from request to delivery so the team can see where value is added and where it is not. It is a diagnostic tool for improving flow, not a personnel or hierarchy document.

Question 6Agile and Lean Foundations

A kanban board shows a column with a work-in-progress limit of three, and it currently holds three items. A developer wants to start a fourth. What does the limit require?

  1. Split the fourth item into smaller tasks and start them
  2. Move an item backward to an earlier column
  3. Wait until an item leaves the column before pulling new work Correct answer.
  4. Start the fourth item and raise the limit to four

Explanation

A WIP limit constrains how many items may occupy a stage at once, so new work can only be pulled after existing work exits. This pull discipline exposes bottlenecks and keeps flow steady.

Question 7Agile and Lean Foundations

In Lean, what does 'kaizen' describe?

  1. Continuous incremental improvement by the people doing the work Correct answer.
  2. A formal audit of compliance with process standards
  3. A method for estimating effort in story points
  4. A one-time reorganization led by external consultants

Explanation

Kaizen means continuous improvement, typically driven by the people closest to the work making small, ongoing changes. It contrasts with large episodic change programs imposed from outside.

Question 8Agile and Lean Foundations

A team measures its cycle time and finds it varies widely, with some items finishing in one day and others taking three weeks. Which Lean action best addresses this?

  1. Add a final inspection step before release
  2. Limit work in progress and standardize the size of work items Correct answer.
  3. Extend the sprint length to absorb the variance
  4. Increase the number of items started each week

Explanation

Reducing batch size and capping work in progress smooths flow and reduces the spread of cycle times. Variance usually comes from too many concurrent items and inconsistent item size.

Question 9Agile and Lean Foundations

Which of the following best describes 'pull' in a Lean system?

  1. Work is pushed to the next stage as soon as it is ready
  2. Work is released when downstream capacity becomes available Correct answer.
  3. The backlog is frozen for the duration of a release
  4. Managers assign each task to a named individual

Explanation

In a pull system, downstream demand signals when upstream work should start, preventing queues from building. Work is not released simply because someone finished the previous step.

Question 10Agile and Lean Foundations

A product owner asks the team to estimate the relative size of backlog items without assigning hours. Which Agile estimation approach is being used?

  1. Earned value analysis
  2. Story point relative estimation Correct answer.
  3. Gantt scheduling
  4. Critical path method

Explanation

Story points express relative size, complexity, and uncertainty rather than elapsed time. Teams compare items against each other to keep estimates fast and consistent.

Question 11Agile and Lean Foundations

During a retrospective the team notes that a defect escaped because testing happened only after all development was complete. Which Lean principle most directly addresses this?

  1. Build quality in rather than inspect it at the end Correct answer.
  2. Freeze requirements before development starts
  3. Increase the size of the test team
  4. Maximize the number of releases per quarter

Explanation

Building quality in means preventing defects through practices such as test-first development and continuous verification rather than catching them in a late inspection phase. Late inspection adds cost and delay.

Question 12Agile and Lean Foundations

What does the Agile Manifesto value 'individuals and interactions over processes and tools' primarily emphasize?

  1. People and communication matter more than prescribed procedures Correct answer.
  2. Processes and tools should be removed from all projects
  3. Tools must be open source to be acceptable
  4. Interactions should be limited to formal written channels

Explanation

The value statement ranks people and their communication above reliance on prescribed process and tooling, while still recognizing that process and tools have a place. It is a statement of relative emphasis.

Question 13Agile and Lean Foundations

A team adopts a practice of stopping the whole line when a serious defect is found so the cause can be fixed immediately. Which Lean concept does this reflect?

  1. Andon and stop-the-line Correct answer.
  2. Cost-center accounting
  3. Batch-and-queue processing
  4. Annual capacity planning

Explanation

Stopping the line when a problem appears, often signaled by an andon, prevents defective work from flowing downstream and forces immediate root-cause correction. It embodies the principle of building quality in.

Question 14Agile and Lean Foundations

Which pairing of a Lean waste with an Agile software example is correct?

  1. Inventory - undeployed features sitting finished but unreleased Correct answer.
  2. Over-processing - a team deciding to write no documentation
  3. Motion - a customer changing requirements mid-sprint
  4. Waiting - automating a repetitive build step

Explanation

In software, inventory corresponds to finished but undelivered work, such as completed features waiting for release. It ties up effort without yet delivering value.

Question 15Agile and Lean Foundations

A Scrum team's burndown chart shows the line flat for several days mid-sprint and then dropping sharply at the end. What does this pattern most likely indicate?

  1. The product owner is adding too few items
  2. The team is estimating too conservatively
  3. The sprint goal has already been met
  4. Work is being finished in a large batch near the end rather than flowing steadily Correct answer.

Explanation

A flat-then-steep burndown suggests items are completed in a late batch, which hides risk until the end of the sprint. Smoother flow would show a more even downward slope.

Question 16Agile and Lean Foundations

What is the main purpose of a daily standup in an Agile team?

  1. To estimate the remaining backlog items
  2. To approve changes to the sprint scope
  3. To synchronize the team on progress and impediments Correct answer.
  4. To report status upward to management

Explanation

The daily standup is a short synchronization event where the team coordinates work and surfaces blockers. It is peer-to-peer communication, not a management status report.

Question 17Agile and Lean Foundations

Which Agile principle addresses the ideal of technical excellence and good design?

  1. Working software is the primary measure of progress
  2. Business people and developers must work together daily
  3. Deliver working software frequently
  4. Continuous attention to technical excellence and good design enhances agility Correct answer.

Explanation

One of the twelve principles explicitly states that continuous attention to technical excellence and good design enhances agility. Good design keeps change inexpensive over time.

Question 18Agile and Lean Foundations

A team using kanban wants to know how long items typically take from start to finish. Which metric should they examine?

  1. Number of open defects
  2. Cycle time Correct answer.
  3. Velocity in story points per sprint
  4. Team headcount

Explanation

Cycle time measures elapsed time from when work starts to when it finishes, which is exactly the question being asked. Velocity measures throughput per iteration rather than duration per item.

Question 19Agile and Lean Foundations

A team is asked to deliver a large feature and decides to slice it into thin vertical increments that each deliver user value. Which Lean idea does this most directly apply?

  1. Reducing batch size to improve flow and feedback Correct answer.
  2. Deferring all integration until the end of the quarter
  3. Increasing specialization among team members
  4. Standardizing the number of hours worked per day

Explanation

Smaller batches shorten feedback loops, reduce risk, and let value reach users sooner. Thin vertical slices are a practical application of reducing batch size.

Question 20Agile and Lean Foundations

In the context of Lean software development, what does 'defer commitment' advise?

  1. Avoid making any decisions until the project ends
  2. Commit to a fixed scope at project kickoff
  3. Keep options open and decide at the last responsible moment Correct answer.
  4. Assign decision rights to a single senior architect

Explanation

Deferring commitment means preserving flexibility by deciding as late as responsibly possible, when more information is available. It does not mean never deciding.

Question 21Agile and Lean Foundations

A team's retrospective actions from the last three sprints have not been implemented. Which observation best reflects Lean and Agile thinking about this situation?

  1. Retrospectives should be discontinued because they produce no value
  2. Action items should be dropped in favor of velocity tracking
  3. The Scrum Master should write the action items alone
  4. The team should inspect why follow-through fails and adapt its improvement process Correct answer.

Explanation

Inspection without adaptation is incomplete; the team should examine why commitments are not met and adjust how improvement work is chosen and tracked. Continuous improvement requires follow-through, not abandonment of the ceremony.

Question 22Agile and Lean Foundations

Which of the following is an example of 'over-processing' waste in software delivery?

  1. Producing detailed documents that no one reads or uses Correct answer.
  2. Rebuilding a feature because of a misread requirement
  3. Leaving finished code undeployed for weeks
  4. Waiting for a security review before release

Explanation

Over-processing means doing more work on an item than the customer needs, such as documentation with no consumer. The effort adds cost without adding value.

Question 23Agile and Lean Foundations

How does the Agile principle about frequent delivery of working software treat the delivery interval?

  1. It requires delivery only at project completion
  2. It leaves delivery timing to the finance department
  3. It mandates a fixed twelve-month release cycle
  4. It favors shorter intervals, from a couple of weeks to a couple of months Correct answer.

Explanation

The principle calls for delivering working software frequently, preferring shorter timescales such as a couple of weeks to a couple of months. The emphasis is on shortening the interval to gain feedback.

Question 24Agile and Lean Foundations

A team notices that work items sit in a 'ready for test' column for days while testers are occupied elsewhere. Which analysis is most consistent with Lean flow thinking?

  1. The queue proves that testing should be removed from the process
  2. The solution is to add more items to the development column
  3. The queue indicates a capacity mismatch and should be addressed by limiting WIP and balancing work Correct answer.
  4. The queue is harmless because work is still technically in progress

Explanation

A growing queue between stages signals a bottleneck where downstream capacity is lower than upstream output. Lean flow thinking addresses this by limiting WIP and balancing capacity across stages rather than ignoring the queue.

Question 25Agile and Lean Foundations

What is the purpose of a sprint review in an Agile team?

  1. To discuss individual performance issues
  2. To estimate the effort for the next sprint
  3. To inspect the increment with stakeholders and adapt the backlog Correct answer.
  4. To decide who will be promoted this quarter

Explanation

The sprint review is a working session where the team and stakeholders inspect what was built and adjust the backlog accordingly. It is a collaborative inspection of the product, not an internal status or personnel meeting.

Question 26Agile and Lean Foundations

Which statement captures the core idea of the Lean principle 'eliminate waste'?

  1. Add approval steps so that every change is reviewed by a manager
  2. Remove any activity that does not add value for the customer Correct answer.
  3. Increase the number of features delivered per sprint regardless of demand
  4. Keep every work item in progress so that nobody is ever idle

Explanation

Lean defines waste as any activity that consumes resources without creating value for the customer, so the principle directs teams to find and remove such activity. Value is judged from the customer's perspective, not from internal busyness or output volume.

Question 27Agile and Lean Foundations

An Agile team must satisfy a regulatory audit while also responding quickly to changing requirements. Which interpretation of the Agile Manifesto's value statements fits best?

  1. The right-hand items must be eliminated whenever a conflict arises
  2. The left-hand items matter more, while the right-hand items still retain value Correct answer.
  3. Both sides are weighted equally in every situation without exception
  4. The right-hand items take priority because they are more concrete

Explanation

The Manifesto states that while there is value in the items on the right, the items on the left are valued more. This is a relative weighting, not a rejection of process, documentation, contracts, or plans. Teams therefore keep necessary governance artifacts while favoring working software and responsiveness.

Question 28Agile and Lean Foundations

What is the primary purpose of value stream mapping in a Lean software organization?

  1. To make the end-to-end flow of work visible and expose delays and waste Correct answer.
  2. To replace the product backlog with a fixed set of tasks
  3. To calculate the total cost of each feature before development starts
  4. To assign individual performance ratings based on output volume

Explanation

Value stream mapping charts the steps, queues, and handoffs from request to delivery so the team can see where time is lost. It highlights delay and non-value-adding steps, which then become candidates for improvement. It is a flow-visualization and improvement tool, not a costing or appraisal mechanism.

Question 29Agile and Lean Foundations

A team member is the only person who understands a critical billing module, and every change to it waits for her availability. Which Lean response addresses this situation most directly?

  1. Route all billing changes through an external approval committee
  2. Add the module to a deferred backlog for a future quarter
  3. Spread knowledge of the module across several team members Correct answer.
  4. Increase the work-in-progress limit on the billing column

Explanation

Lean treats dependence on a single person as a constraint that creates waiting and blocks flow, and it responds by building shared knowledge and cross-skilling. Reducing that constraint lets work proceed without queuing behind one individual. The other options add delay or hide the problem rather than relieve it.

Question 30Agile and Lean Foundations

A team delivers a small increment every few days and adjusts its plans based on what customers actually use. Which combination of Lean and Agile ideas does this behavior best illustrate?

  1. Individual output incentives combined with annual planning
  2. Large batch releases combined with centralized control
  3. Iterative delivery combined with fast feedback and short batch sizes Correct answer.
  4. Detailed up-front design combined with stage-gate approvals

Explanation

Small, frequent increments shrink batch size and shorten the feedback loop, which are central to both Lean flow thinking and Agile iteration. Rapid feedback lets the team inspect real usage and adapt plans instead of committing far in advance. The behavior therefore reflects short batches plus learning from feedback.

Question 31Value-Driven Delivery

In value-driven delivery, what does the term "value" most directly refer to?

  1. The benefit an outcome delivers to the customer or organization relative to its cost Correct answer.
  2. The count of stakeholders who approved the plan
  3. The total number of features delivered in a release
  4. The percentage of budget consumed by a project

Explanation

Value-driven delivery focuses on outcomes that produce benefit for the customer or organization, weighed against the cost and effort required to produce them. Feature counts, budget consumption, and approval counts are activity or process measures, not value itself.

Question 32Value-Driven Delivery

A team is choosing which of several candidate features to build first. Which approach best reflects value-driven prioritization?

  1. Build the features in the order they appear in the original requirements document
  2. Build the features that are technically easiest so progress looks fast
  3. Build the features requested by the most senior stakeholder first
  4. Build the features that deliver the highest expected value relative to effort first Correct answer.

Explanation

Value-driven prioritization ranks work by the benefit it is expected to deliver relative to the effort or cost of delivering it. Document order, ease of build, and seniority of the requester are not measures of value.

Question 33Value-Driven Delivery

What is the primary purpose of defining measurable success criteria for a project?

  1. To provide a fixed baseline that prevents any scope change
  2. To allow the sponsor to assign blame if the project fails
  3. To create a basis for objectively evaluating whether the intended value was realized Correct answer.
  4. To satisfy documentation requirements in the project charter

Explanation

Measurable success criteria let the team and stakeholders judge, with evidence, whether the intended outcomes and benefits were achieved. They support evaluation of value rather than freezing scope or assigning blame.

Question 34Value-Driven Delivery

A product owner wants to confirm that a delivered increment actually solves the customer's problem. Which action best supports this?

  1. Increase the number of automated unit tests in the codebase
  2. Collect feedback from real users on the delivered increment Correct answer.
  3. Add the increment to the risk register for later review
  4. Extend the sprint length so more work can be completed

Explanation

Validation of value requires evidence from the people who use the product, so direct user feedback on a delivered increment is the strongest signal. Internal testing, risk logging, and schedule changes do not by themselves demonstrate that the customer problem is solved.

Question 35Value-Driven Delivery

Which statement best describes the relationship between scope and value in value-driven delivery?

  1. Delivering all planned scope guarantees that full value is realized
  2. Scope and value always increase together at the same rate
  3. Scope is a means to value, and delivering less scope can still maximize value Correct answer.
  4. Value is realized only after every requirement has been signed off

Explanation

Scope is instrumental: the goal is the benefit produced, and delivering a smaller set of high-value items can outperform delivering everything. Completing all scope does not guarantee benefit, and the two do not move in lockstep.

Question 36Value-Driven Delivery

What is the main reason an agile team delivers in short increments?

  1. To obtain early feedback and realize value sooner Correct answer.
  2. To keep individual team members from becoming specialists
  3. To avoid documenting decisions and requirements
  4. To reduce the number of meetings held during the project

Explanation

Short increments allow the team to put usable outcomes in front of stakeholders early, generating feedback and capturing value sooner. Reducing meetings, skipping documentation, and preventing specialization are not the rationale for incremental delivery.

Question 37Value-Driven Delivery

A team tracks a burn-up chart showing scope growing faster than completed work. What does this most likely indicate about value delivery?

  1. The team has too few automated tests
  2. Scope is expanding without a corresponding increase in delivered value Correct answer.
  3. The team is realizing value faster than planned
  4. The project is guaranteed to finish ahead of schedule

Explanation

A burn-up chart plots delivered work against total scope, so scope rising faster than completion signals that commitments are outpacing delivery. This threatens value realization rather than confirming it, and it says nothing directly about schedule certainty or test coverage.

Question 38Value-Driven Delivery

Which of the following is an example of a leading indicator of value?

  1. Number of active users adopting a newly released feature Correct answer.
  2. Customer complaints logged in the prior fiscal year
  3. Profit reported in last year's audited financial statements
  4. Revenue already booked from the previous quarter

Explanation

Leading indicators are forward-looking signals that anticipate future outcomes, such as early adoption of a new feature. Historical revenue, past profit, and prior complaints are lagging indicators that describe what has already happened.

Question 39Value-Driven Delivery

A team is estimating the value of three backlog items. Item A is expected to return 300,000 with effort of 3 weeks; Item B, 200,000 with effort of 1 week; Item C, 500,000 with effort of 10 weeks. Using value per unit of effort, which item should be prioritized first?

  1. Item A
  2. Item B Correct answer.
  3. All three should be started simultaneously
  4. Item C

Explanation

Value per week is 100,000 for A, 200,000 for B, and 50,000 for C, so B yields the greatest benefit per unit of effort and should go first. Starting everything at once spreads capacity thin and delays the earliest value.

Question 40Value-Driven Delivery

A project sponsor asks the team to demonstrate return on investment for a new customer portal. Which combination best supports a credible value case?

  1. The team's velocity history from the previous three sprints
  2. Estimated benefits, estimated costs, assumptions, and a plan to measure actual outcomes Correct answer.
  3. The number of stakeholders who attended the kickoff meeting
  4. A list of all requested features with their story point estimates

Explanation

A credible value case pairs quantified benefits and costs with explicit assumptions and a measurement plan so results can later be verified. Feature lists, velocity, and attendance are process data that do not establish return on investment.

Question 41Value-Driven Delivery

Mid-project, a team learns that a planned compliance feature will deliver far less customer value than expected because regulations changed. What is the most value-driven response?

  1. Double the team size so the feature and other work both finish
  2. Continue building it as planned because it was in the approved baseline
  3. Reassess the item with stakeholders and reprioritize or remove it Correct answer.
  4. Move the feature to the end of the backlog without discussion

Explanation

When new information changes expected value, the team should reassess with stakeholders and adjust priorities so effort flows to higher-value work. Clinging to a baseline or silently deferring the item ignores the new evidence, and adding people does not address misplaced value.

Question 42Value-Driven Delivery

Which practice best keeps a product backlog aligned with value over time?

  1. Freezing the backlog after the initial release plan is approved
  2. Ordering items strictly by the date they were first requested
  3. Assigning each item a fixed priority that never changes
  4. Regularly refining and reordering items based on new learning and feedback Correct answer.

Explanation

Continuous refinement and reordering let the backlog reflect current understanding of value as feedback and market conditions change. Freezing, date-ordering, and permanently fixed priorities all prevent the backlog from tracking value.

Question 43Value-Driven Delivery

A team must choose between two features with similar expected value. Feature X can be delivered in two weeks; Feature Y requires six weeks and carries significant technical uncertainty. Which consideration most supports starting with Feature X?

  1. Technical uncertainty should be avoided in all circumstances
  2. Faster delivery enables earlier value capture and earlier learning Correct answer.
  3. Shorter features are always worth more than longer features
  4. Similar value means the choice has no effect on the project

Explanation

Delivering sooner captures value earlier and produces feedback that informs subsequent decisions, which is a core value-driven rationale. Duration alone does not determine worth, uncertainty can be worth confronting deliberately, and similar value does not make the choice irrelevant.

Question 44Value-Driven Delivery

What role does a minimum viable product play in value-driven delivery?

  1. It is the final release containing every planned feature
  2. It delivers the smallest offering that allows validated learning about customer value Correct answer.
  3. It is a prototype that is never released to users
  4. It is the cheapest version the team can build regardless of customer need

Explanation

A minimum viable product is the smallest thing that lets the team test real demand and learn what customers value before investing further. It is not defined by minimal cost alone, it is released to real users, and it is not the complete final product.

Question 45Value-Driven Delivery

A stakeholder insists on adding a low-value feature that will delay a high-value release by one month. What is the most appropriate value-driven action?

  1. Accept the request because stakeholders outrank the team
  2. Reject the request without explaining the impact
  3. Add the feature and remove all testing to protect the date
  4. Make the trade-off explicit and let the sponsor decide with full information Correct answer.

Explanation

Value-driven delivery requires transparent trade-offs so the decision maker can weigh the benefit of the feature against the cost of delaying higher-value work. Unquestioning acceptance, unexplained rejection, and cutting quality all undermine informed decisions.

Question 46Value-Driven Delivery

Which set of measures best evaluates whether a delivered feature produced value?

  1. Hours spent in refinement sessions
  2. Adoption rate, task completion, and outcome metrics tied to the business goal Correct answer.
  3. Number of defects found during testing
  4. Story points completed and velocity trend

Explanation

Value is evidenced by whether users adopt the feature and whether the intended business outcome moves, so adoption, usage completion, and outcome metrics are the right measures. Velocity, defect counts, and meeting hours describe delivery effort or quality rather than realized benefit.

Question 47Value-Driven Delivery

A team uses a weighted scoring model to rank backlog items. Which risk most threatens the model's usefulness?

  1. Weights and scores that reflect opinion rather than evidence Correct answer.
  2. Including too many stakeholders in the scoring workshop
  3. Documenting the scoring criteria in the backlog tool
  4. Reviewing the scores at every iteration

Explanation

A scoring model is only as good as its inputs, so weights and scores driven by opinion rather than data can mislead prioritization. Broad participation, documentation, and regular review generally improve rather than undermine the model.

Question 48Value-Driven Delivery

What is the purpose of a value stream mapping exercise in a delivery organization?

  1. To assign individual performance ratings to team members
  2. To identify where time and effort are consumed without adding customer value Correct answer.
  3. To calculate the exact budget for the next fiscal year
  4. To replace the product backlog with a process diagram

Explanation

Value stream mapping visualizes the flow of work to expose delays, handoffs, and steps that consume effort without adding customer value. It is not a performance-rating tool, a budgeting method, or a substitute for the backlog.

Question 49Value-Driven Delivery

A team has been delivering features on schedule, but usage data shows customers rarely use them. What conclusion best follows?

  1. The team should increase velocity to fix the problem
  2. The usage data must be incorrect because the schedule was met
  3. The features should be rebuilt with more automated tests
  4. The team is delivering output efficiently but not realizing value Correct answer.

Explanation

On-time delivery of unused features demonstrates efficient output production without corresponding benefit, which is the central failure value-driven delivery seeks to avoid. Questioning valid data, increasing velocity, or adding tests does not address the mismatch between output and use.

Question 50Value-Driven Delivery

Which action best reflects the principle of delivering value early and often?

  1. Releasing a usable subset of functionality to a pilot group before the full rollout Correct answer.
  2. Delaying feedback collection until after project closure
  3. Holding all releases until the annual planning cycle
  4. Waiting until every feature is complete before any user sees the product

Explanation

Releasing a usable subset early lets the organization begin capturing benefit and gathering feedback while the remainder is built. Waiting for completeness, batching releases annually, and deferring feedback all postpone value and learning.