The MVP and the terms around it
An MVP exists to learn something. It can be narrow, rough, even partly manual behind the scenes, as long as it answers the question the team is unsure about: will people use this, pay for it, change a habit for it. Related labels such as minimum valuable product or most viable product show the usual confusion. Viable here means able to test the idea, not ready for wide sale.
A release is a set of increments that reach users together. A roadmap shows the order of releases over time and the direction behind them, and it is reviewed as each release teaches the team something. The product usually outlives the projects that build it; that distinction starts on project basics and life cycles.
Prioritization feeds both. MoSCoW, the Kano model, weighted scoring and cost of delay sort the same backlog by different questions, and the backlog itself is on iterations, backlog and agile tracking.
A roadmap for an invented product
Now
MVP: book a garden plot
One community garden, web only, payments collected by hand. The question it answers: will members book online at all?
Next quarter
Release 1: payments and a waitlist
Built only if the MVP shows steady bookings. Scope is firm enough to estimate in ranges.
Later this year
Release 2: several gardens
A theme with an outcome attached, such as a shorter waitlist. The features underneath are not decided yet.
Someday
Partner integrations
Listed so that the stakeholders who asked can see it was heard. No date, on purpose.
The business analyst in predictive and adaptive work
| Aspect | Predictive | Adaptive |
|---|---|---|
| Main artifact | Requirements documentation traced in an RTM | Product backlog of user stories with acceptance criteria |
| Who orders the work | The plan and its baseline, changed through change control | The product owner, reordering the backlog |
| How change arrives | A change request against the scope baseline | A new or reordered backlog item |
| Shape of delivery | One major delivery, sometimes in phases | Frequent releases of usable increments |
Cards on this topic
Roadmap and release cards come from both sides of the methodology line, and a release question on a stage-gated project has a different best answer from the same question on a team that ships every iteration.
Practice cards here are written for study, not taken from PMI. The real CAPM mixes multiple choice with drag-and-drop, hot spot, comic-strip and video items.
Card 01 of 23 · 0 done · 0 right
To do 23
Doing
Card 01 of 23
Banking app users never praise secure login, but they are very dissatisfied when it fails. In the Kano model, how is secure login classified?
Note on A
Correct: In the Kano model, a basic feature is expected; it causes strong dissatisfaction when it fails but earns little praise when it works.
Note on B
Users clearly care about secure login, since its failure upsets them, so it is not indifferent.
Note on C
Performance features raise satisfaction as they improve, but users do not praise secure login.
Note on D
Excitement features delight when present and are not missed when absent, the opposite of this pattern.
Card 02 of 23
A project is being delivered with a predictive life cycle. Requirements were formally documented and approved early, and the project uses stage gates with sponsor sign off. The project manager must plan how stakeholders will validate the requirements as the work progresses. Which activity is most appropriate?
Note on A
Automated integration tests check the build technically but do not have stakeholders validate requirements.
Note on B
Sprint reviews belong to adaptive delivery, not a predictive project with stage gates.
Note on C
Correct: In a predictive life cycle, stakeholders validate requirements through formal reviews at phase gates before the next stage starts.
Note on D
Daily stand-ups coordinate the team’s work and do not involve stakeholder validation of requirements.
Card 03 of 23
A steering committee must decide how to meet a fixed regulatory deadline that cannot move. The full scope cannot be delivered in time. Which format best presents the trade-off with the constraints and options attached?
Note on A
Asking for more funding avoids the trade-off and does not help when the date is fixed.
Note on B
A status report describes the past; it does not lay out options for the decision the committee must make.
Note on C
A long list of estimates leaves the committee to work out the trade-off on its own.
Note on D
Correct: A conditional statement ties scope to the fixed date and makes the trade-off explicit, so the committee can choose.
Card 04 of 23
After reweighting business value by plus or minus twenty percent, the composite ranking of two candidate requirements reverses. What should the project manager or business analyst do next?
Note on A
Picking whichever weighting gives the higher total chooses the answer you want instead of resolving the uncertainty.
Note on B
A prior approval does not make a fragile ranking reliable, and filing the result away ignores what the analysis revealed.
Note on C
Correct: A ranking that flips under small weight changes is not robust, so stakeholders need to know and confirm the weights before scope is committed.
Note on D
Averaging two rankings hides the sensitivity instead of resolving which weights are right.
Card 05 of 23
Stakeholders label every requirement a must-have. The business analyst wants each requirement placed into one of four groups, including an explicit ‘not in this release’ group. Which technique should the BA use?
Note on A
Multivoting ranks options by vote counts and does not create named categories.
Note on B
The 100-point method spreads points across requirements to rank them, not to put them into groups.
Note on C
The Kano model groups features by how they affect customer satisfaction, not into release categories.
Note on D
Correct: MoSCoW sorts requirements into Must, Should, Could, and Won’t, including an explicit not-this-release group.
Card 06 of 23
A release decision was based on single-point cost estimates; when the actual costs arrived, the ranking collapsed and the sponsor lost confidence in the prioritization. What should the analyst have done differently?
Note on A
Freezing uncertain estimates guarantees the ranking breaks when actual costs differ.
Note on B
A flat contingency shifts every number equally and does not show which items are sensitive to cost changes.
Note on C
Correct: Ranges and sensitivity analysis show how the ranking changes as costs vary, so stakeholders can see which decisions are robust.
Note on D
Sponsor ownership of the numbers does not make single-point estimates any more accurate.
Card 07 of 23
A business analyst will present the product roadmap to executives and, separately, to the development team. What should differ between the two presentations?
Note on A
The release goals are the same for both audiences; changing them would create conflicting expectations.
Note on B
Correct: The same roadmap is tailored in detail: executives see outcomes and timing, while the team sees more about features and dependencies.
Note on C
Changing priorities to please each audience sends conflicting messages and damages trust.
Note on D
Different audiences need different levels of detail, so one identical version rarely serves both.
Card 08 of 23
On a predictive project, when does the business analyst typically perform most requirements elicitation and documentation?
Note on A
Acceptance testing confirms requirements were met; it is far too late to start eliciting them.
Note on B
Spreading elicitation evenly across phases fits adaptive work, not a predictive approach.
Note on C
Correct: In a predictive approach, most requirements are elicited and documented early so design and planning can build on them.
Note on D
Just-in-time elicitation for each iteration describes adaptive delivery.
Card 09 of 23
A release has a fixed date and fixed capacity, and its scope was prioritized using MoSCoW. If the team runs short of time, which items are dropped FIRST?
Note on A
Correct: Could-have items are the lowest priority among planned work, so they are the first to be dropped.
Note on B
Must-haves are essential to the release and are protected.
Note on C
Should-haves are important, so they are dropped only after the could-haves.
Note on D
Won’t-haves were never planned for this release, so there is nothing to drop.
Card 10 of 23
A project team is transitioning from a predictive methodology to an agile framework for their next major software release. How should the project manager adapt the requirements validation process to align with this new methodology?
Note on A
Formal phase-end gates belong to predictive delivery and delay feedback in an agile framework.
Note on B
Validating only at the end with scripts removes stakeholders from the loop and finds problems too late.
Note on C
Correct: In agile delivery, requirements are validated continually as stakeholders see working increments at sprint reviews and demos.
Note on D
Agile teams still document acceptance criteria; conversations add to them rather than replace them.
Card 11 of 23
A product roadmap is organized around outcomes, such as ‘cut loan processing time by 30%’, rather than specific features. What is the MAIN benefit of this approach?
Note on A
An outcome-based roadmap still needs a backlog to hold the work the team selects.
Note on B
Correct: Framing the roadmap around outcomes leaves the team free to choose and change solutions as it learns what moves the result.
Note on C
Outcomes describe goals, not fixed dates, so this approach does not by itself make delivery more predictable.
Note on D
Sprint-level detail belongs in the backlog, not on an outcome-based roadmap.
Card 12 of 23
A product owner wants each release to include at least one feature that is small but valuable enough for customers to use and pay for on its own. What is such a feature called?
Note on A
A spike is a timeboxed investigation to reduce uncertainty, not a sellable feature.
Note on B
An MVP is the smallest product built to test a hypothesis and learn, not a single feature customers pay for on its own.
Note on C
Correct: A minimum marketable feature (MMF) is a small unit of functionality valuable enough on its own that customers would use and pay for it.
Note on D
An epic is a large body of work that gets split into smaller items, not a small sellable feature.
Card 13 of 23
During release planning, a capability was classified in the Won’t category. Mid-sprint, a new regulation is published that requires the capability before the product can be sold in the target market. What should the project manager do first?
Note on A
Leaving it out would block sales in the target market, so postponing it is not acceptable.
Note on B
Waiting for a formal letter delays action on a requirement that is now clearly essential.
Note on C
Correct: A legal requirement for sale makes the capability essential, so it becomes a Must and the release scope is rebalanced.
Note on D
A legal requirement is not optional, so treating it as a Could is wrong.
Card 14 of 23
Which item would be found in a product management plan but NOT in a project management plan?
Note on A
Correct: A product management plan spans the whole product life cycle, including releases planned well beyond any single project.
Note on B
Change control for project work belongs in the project management plan.
Note on C
Scope, schedule, and cost baselines are core parts of the project management plan.
Note on D
Subsidiary plans such as risk and quality are components of the project management plan.
Card 15 of 23
A product team planned its roadmap on the documented assumption that customers would rapidly adopt a subscription model. Midway through delivery, market data shows that customers strongly prefer one-time purchases. The roadmap and backlog are built entirely around the subscription assumption. What should the project manager do?
Note on A
Logging and monitoring is not enough once evidence shows a core assumption is wrong.
Note on B
Updating baselines alone does not revisit the product direction the assumption drove.
Note on C
A signed baseline does not justify building toward a direction the market has rejected.
Note on D
Correct: When evidence contradicts a key assumption, the team confirms it with stakeholders and reorders the backlog toward what customers actually value.
Card 16 of 23
A product backlog contains a Must item that cannot function without a Should item that supplies the data it consumes. The team must define a viable Minimum Marketable Product for the first release within a fixed budget and schedule. What should the team do?
Note on A
Downgrading the Must item does not solve the dependency and weakens the product’s core.
Note on B
Correct: The Must item cannot work without the Should item, so the Should item has to be in the first release for the product to be viable.
Note on C
Moving both items out guts the product, since the Must item is needed in the first release.
Note on D
Releasing the Must item alone delivers something that cannot function.
Card 17 of 23
An agile team validates requirements only once, during the final release review, arguing that demonstrating the product to stakeholders earlier would waste effort. The product owner is concerned. Which statement best describes the problem with this validation cadence?
Note on A
Working software is valuable precisely because stakeholders can see it often and give feedback.
Note on B
Stage gates before every sprint add predictive overhead and are not the agile remedy.
Note on C
Fully baselining requirements before validation is predictive practice and slows learning.
Note on D
Correct: Agile teams validate requirements every iteration so misunderstandings are caught early, not at the final release.
Card 18 of 23
A team selects release requirements based only on business value, and the release then overcommits several expensive items that cannot be delivered within the approved budget. Which action best addresses the root cause of the problem?
Note on A
Correct: Scoring value against cost and risk makes expensive, risky items compete fairly, which keeps the release from selecting more than the budget can deliver.
Note on B
Weakening acceptance criteria lowers quality instead of fixing how items were selected.
Note on C
Extending the timeline treats the symptom; the selection method that ignored cost stays the same.
Note on D
Adding developers raises cost further and leaves the selection method that ignored cost unchanged.
Card 19 of 23
Which item is MOST appropriate to show on a product roadmap?
Note on A
Correct: Roadmaps show high-level themes and their target timeframes, such as a mobile check-in theme for Q2.
Note on B
An estimated story is backlog detail, too granular for a roadmap.
Note on C
Individual defects are tracked in the backlog, not on a product roadmap.
Note on D
A database index is a technical task, far below the level a roadmap communicates.
Card 20 of 23
A stakeholder group must shrink a list of 40 candidate features to about 10, quickly and with everyone’s input. Which technique is MOST suitable?
Note on A
Correct: Multivoting lets each participant spread a set number of votes across items, quickly narrowing a long list with everyone’s input.
Note on B
MoSCoW sorts items into categories but does not quickly reduce a long list to a set number.
Note on C
The Kano model needs customer surveys, which makes it slow for a quick narrowing exercise.
Note on D
Pairwise comparison of 40 features means hundreds of comparisons, which is not quick.
Card 21 of 23
As items on a product roadmap move closer to the time they will be developed, what should happen to them?
Note on A
Roadmap items stay flexible; freezing them works against adaptive planning.
Note on B
Correct: As items approach development, they are progressively elaborated into smaller, detailed backlog items the team can deliver.
Note on C
Roadmap items do not need change control board approval as they get closer to development.
Note on D
The risk register tracks uncertain events, not upcoming product work.
Card 22 of 23
A project manager who has led only predictive projects is now leading an agile product team with a stable product owner, a prioritized backlog, and two week iterations. During planning the project manager proposes several practices for the team to adopt. Which proposed practice is least appropriate for this agile project?
Note on A
User stories with acceptance criteria are standard agile practice and fit this team.
Note on B
Correct: Baselining all scope before the first iteration conflicts with adaptive delivery, where scope emerges through backlog refinement.
Note on C
A burnup chart is a useful agile way to show cumulative progress against scope.
Note on D
A prioritized backlog refined each iteration is a core agile practice.
Card 23 of 23
A project manager completes a weighted prioritization of candidate features and presents stakeholders with one ranked list and a recommendation to approve. Stakeholders approve it without discussion, then later express surprise that valuable features were deferred. Why is presenting a single ranking problematic?
Note on A
The problem is not whether stakeholders approved the criteria in advance, but that no alternatives were shown.
Note on B
Correct: A single ranked list hides the trade-offs, so stakeholders approved without seeing what they were giving up.
Note on C
Nothing suggests the ranking used cost instead of value; the problem is the lack of options.
Note on D
The number of items is not the cause; stakeholders were surprised because the trade-offs were never laid out.
Done 0
MVPs and roadmaps: short answers
What separates an MVP from a prototype?
A prototype shows or tests an idea and is usually thrown away. An MVP is a working product released to real users so the team can learn from what they do.
Is a minimum valuable product the same thing?
It is a close relative. Teams that use the term want to stress that the first release must deliver value by itself, beyond testing a hypothesis. Usage varies, so read a scenario for what the first release is meant to achieve.
Who owns the product roadmap?
Usually the product manager or product owner, with the business analyst supplying analysis such as dependencies, value estimates and requirement gaps. Where funding depends on the direction, the sponsor approves it.
Does a roadmap carry dates?
Near items often carry a target release or quarter; later items carry less, because a date far out carries little information. Firm dates belong in release plans, which draw on the requirements described on requirements gathering and traceability.