PMI-ACP Product — Timed 20 Questions

Question 1

A team is struggling to prioritize value because stakeholders have conflicting perspectives on what is most critical. Which technique best facilitates alignment?

Accepted Answer

Weighted Shortest Job First (WSJF).. Weighted Shortest Job First (WSJF) is a prioritization technique from SAFe that ranks work by cost of delay divided by job duration, producing an objective, value-based order that helps stakeholders align on what matters most. It uses relative scoring across dimensions like user-business value, time criticality, and risk reduction/opportunity enablement. This makes trade-offs explicit and reduces subjective lobbying.

Answer

Simply follow the highest-paid person's opinion.

Answer

Prioritize based on whichever stakeholder screams the loudest.

Answer

Average the rankings provided by all stakeholders.

Question 2

A user story is written as: 'As a user, I want to use the login page so that I can see my profile.' What is missing from this story?

Accepted Answer

The acceptance criteria.. The story follows the 'As a [role], I want [feature] so that [benefit]' format but lacks acceptance criteria—the conditions that must be met for the story to be considered done. Acceptance criteria define the boundaries, edge cases, and testable outcomes, enabling the team to verify the story meets the user's needs. Without them, the story is ambiguous and prone to rework.

Answer

The technical architecture.

Answer

The user role.

Answer

The development team's estimate.

Answer

The role.

Question 3

Which TWO of the following are primary goals of a Product Roadmap?

Accepted Answer

To communicate the product's strategic direction.. Option A is correct because a Product Roadmap's core purpose is to communicate the product's strategic direction, aligning stakeholders on the vision, target outcomes, and priorities over time. Option C is correct because a roadmap also provides a timeline of planned releases, showing when features or increments are expected to be delivered across upcoming periods. The remaining options do not belong: B is wrong because a roadmap supplements, not replaces, daily team communication such as standups and backlog refinement; D is wrong because a roadmap is a flexible planning artifact that is regularly updated, not an unchangeable contract; and E is wrong because a roadmap operates at a strategic level and never enumerates every line of code.

Answer

To replace the need for daily team communication.

Answer

To act as a contract that cannot be changed.

Answer

To provide a list of every single line of code.

Question 4

A product vision has become outdated due to market shifts. How should the Product Owner proceed?

Accepted Answer

Collaborate with stakeholders to revise the product vision.. The product vision is owned by the Product Owner but shaped with stakeholders, so when market shifts invalidate it, the Product Owner should collaborate with stakeholders to revise it. This keeps the vision aligned with business value and customer needs while preserving stakeholder buy-in. The Product Owner remains accountable for the vision, but revising it is a collaborative, not unilateral, act.

Answer

Allow developers to decide the new vision.

Answer

Wait until the end of the project to change the vision.

Answer

Ignore the shift and continue with the original plan.

Question 5

A user story lacks specific acceptance criteria. What is the risk to the development team?

Accepted Answer

The team will not know when the story meets requirements.. Acceptance criteria define the conditions a story must satisfy to be considered done, so without them the team has no objective way to know when the work is complete or whether it meets the user's needs. This ambiguity leads to rework, scope disputes, and stories that pass code review but fail acceptance because 'done' was never defined.

Answer

The sprint will end earlier than expected.

Answer

The velocity will artificially increase.

Answer

The story will be too small to estimate.

Question 6

Which document acts as the single source of truth for all work to be performed by the development team?

Accepted Answer

The product backlog.. The product backlog is the single source of truth for all work the development team may perform. It is a prioritized, ordered list of everything that might be needed in the product, owned by the Product Owner and refined continuously. In Scrum and most Agile frameworks, the sprint backlog is derived from the product backlog, and no work should be done that is not represented there.

Answer

The sprint burndown chart.

Answer

The communication plan.

Answer

The project charter.

Question 7

When writing user stories, which criteria ensure the story is ready for the development team to estimate?

Accepted Answer

The story must meet the Definition of Ready.. The Definition of Ready (DoR) is an agile team's explicit checklist that a user story must satisfy before it can be pulled into a sprint for estimation and development. It typically covers INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable), acceptance criteria being defined, dependencies identified, and the story being small enough to complete in one iteration. Meeting the DoR is the agreed signal that the team has enough shared understanding to size the work reliably.

Answer

The story must be at least 10 pages long.

Answer

The story must be approved by the CEO.

Answer

The story must be assigned to a specific developer.

Question 8

A Product Owner notices that the product backlog has grown significantly, making it difficult to find relevant work items. Which action should the Product Owner take to improve visibility?

Accepted Answer

Group related user stories under larger epics.. Grouping related user stories under larger epics improves backlog visibility by creating a hierarchical structure that reduces clutter while preserving detail at the story level. This is a standard backlog refinement technique that helps the Product Owner and team navigate large backlogs. It maintains traceability from high-level themes to granular work items.

Answer

Archive the entire backlog and start a new one.

Answer

Increase the number of items per page in the tool.

Answer

Delete all old user stories to clear the clutter.

Question 9

A project is mid-way, and stakeholders want to add a feature that was not in the original product roadmap. What is the appropriate response?

Accepted Answer

Evaluate the feature's value and impact on the backlog priority.. In agile, the product backlog is emergent and can change as new information and stakeholder needs arise. The appropriate response to a mid-project feature request is to evaluate its value and impact on backlog priority, then let the product owner decide where it fits relative to existing items. This preserves the team's ability to deliver the highest-value work while remaining responsive to change.

Answer

Reject the request because it was not in the roadmap.

Answer

Immediately add the feature to the current sprint.

Answer

Refer the request to the project manager for approval.

Question 10

During a sprint planning session, the team realizes a user story is too large to complete in one sprint. What is the most effective approach to handle this?

Accepted Answer

Decompose the story into smaller, independently deliverable user stories.. Decomposing the story into smaller, independently deliverable user stories is correct because it allows the team to complete valuable increments within the sprint, maintains flow, and adheres to the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable). This approach enables continuous delivery and reduces batch size, which is a core Agile principle.

Answer

Mark the story as blocked and move to the next sprint.

Answer

Extend the sprint duration to accommodate the story size.

Answer

Ask the developers to work overtime to finish it.

Question 11

A team has high velocity but the customer reports the product is not meeting their needs. What is the most likely cause?

Accepted Answer

The product backlog is not prioritized based on customer value.. High velocity with poor customer satisfaction most likely indicates that the team is building the wrong things—the product backlog is not prioritized based on customer value. Velocity measures output, not outcome. If the backlog is not aligned with customer needs, the team can efficiently deliver features that miss the mark.

Answer

The sprint duration is too short.

Answer

The team is lacking a project manager.

Answer

The team is not using enough automated tests.

Question 12

In the context of the product roadmap, what is the primary purpose of a release plan?

Accepted Answer

To provide a high-level view of when features will be available.. A release plan provides a high-level view of when features or feature sets will be available to users, bridging the product roadmap and sprint execution. It communicates intended release dates and scope at a coarse granularity without committing to exact daily tasks. This helps stakeholders align on delivery expectations while preserving agile flexibility.

Answer

To replace the need for sprint planning.

Answer

To dictate the exact daily tasks for each developer.

Answer

To guarantee that all features will be completed on time.

Question 13

Which persona is primarily responsible for ensuring the product backlog reflects the needs of the stakeholders and customers?

Accepted Answer

The Product Owner.. The Product Owner is the single persona accountable for maximizing product value and ensuring the product backlog reflects stakeholder and customer needs. In Scrum and agile practice, the PO owns backlog content, ordering, and refinement. This role is explicitly defined in the Scrum Guide and PMI-ACP materials as the voice of the customer.

Answer

The Project Sponsor.

Answer

The Scrum Master.

Answer

The Lead Developer.

Question 14

What is the primary function of the 'Product Vision'?

Accepted Answer

To define the long-term purpose and goal of the product.. The Product Vision is a concise, aspirational statement describing the long-term purpose, target customers, key benefits, and differentiators of the product. It aligns the team and stakeholders on the 'why' behind the product and guides prioritization decisions. It is not a feature list, budget tracker, or meeting agenda—those are artifacts of other processes.

Answer

To list every feature to be built in the product.

Answer

To track the budget spent on the development team.

Answer

To provide the specific daily meeting agenda.

Question 15

An organization is transitioning from project-based funding to product-based funding. How does this impact the Product Owner's role?

Accepted Answer

The Product Owner focuses on long-term product value rather than project milestones.. Moving from project-based to product-based funding shifts the Product Owner's focus from delivering against fixed project milestones and budgets to maximizing long-term product value and outcomes. Funding becomes continuous and tied to product strategy, so the PO prioritizes the backlog around value streams, customer outcomes, and lifecycle economics rather than one-time project completion.

Answer

The Product Owner is now responsible for the annual budget.

Answer

The Product Owner no longer manages the backlog.

Answer

The Product Owner now reports to the finance department.

Question 16

A stakeholder demands that a feature be completed by next week. The team identifies this as a high-risk task. What should the Product Owner do?

Accepted Answer

Discuss the risks with the stakeholder and negotiate the timeline or scope.. When a stakeholder demands a high-risk feature on a tight timeline, the Product Owner should discuss the risks with the stakeholder and negotiate timeline or scope, because the PO is accountable for maximizing value while protecting the team's sustainable pace. This preserves transparency and allows informed trade-offs rather than committing to an unrealistic date. It also respects the team's self-management and the empirical nature of agile planning.

Answer

Force the team to work overtime to ensure completion.

Answer

Delegate the task to a junior developer to save costs.

Answer

Agree to the request to satisfy the stakeholder.

Question 17

An agile team is using 'Story Points' for estimation. Why is this preferred over 'Hours' for backlog items?

Accepted Answer

It accounts for complexity, effort, and uncertainty without needing precise time forecasting.. Story points are a relative, unitless measure that captures complexity, effort, and uncertainty together, which is why they are preferred over hours for backlog estimation. Because humans are better at comparing items than forecasting absolute durations, relative sizing produces more reliable estimates and avoids false precision. Story points also decouple estimation from individual time tracking, supporting team-based planning.

Answer

It is required by the project management office.

Answer

It makes it easier to track individual performance.

Answer

It ensures that every story takes exactly the same amount of time.

Question 18

During a sprint, a team member discovers a small bug. Where should this task be added?

Accepted Answer

To the product backlog.. In Scrum, the product backlog is the single source of truth for all work that may be needed in the product, including new features, enhancements, and bug fixes. A bug discovered during a sprint should be added to the product backlog so the Product Owner can prioritize it against other items. This keeps all work transparent and prioritized in one place.

Answer

To the personal notepad of the Scrum Master.

Answer

To a separate bug-tracking document outside of the product tool.

Answer

To the project charter.

Question 19

Which of the following is an effective technique for eliciting requirements from stakeholders?

Accepted Answer

Conducting user interviews or focus groups.. Conducting user interviews or focus groups is a direct, interactive elicitation technique that draws requirements straight from stakeholders through structured conversation, allowing the analyst to probe, clarify, and uncover latent needs. PMI-ACP and the Agile Manifesto emphasize 'individuals and interactions over processes and tools,' so face-to-face techniques like interviews and focus groups align with agile values. These methods produce rich, high-quality information that can be validated immediately with the stakeholder.

Answer

Building the entire product first and asking for feedback later.

Answer

Guessing the requirements based on past projects.

Answer

Waiting for the stakeholders to send an email.

Question 20

A team is struggling to keep their backlog refined. What is a sign of poor backlog refinement?

Accepted Answer

The team frequently asks for clarification during the sprint.. Frequent mid-sprint clarification requests signal that stories were not sufficiently refined—lacking clear acceptance criteria, dependencies, or shared understanding—before entering the sprint. Effective backlog refinement (grooming) ensures the team understands the 'what' and 'why' of upcoming stories, typically through the Definition of Ready. When the team constantly interrupts the PO during the sprint, it indicates refinement was superficial or skipped.

Answer

The team finishes all stories in the sprint.

Answer

The backlog is sorted by priority.

Answer

The product owner is involved in refinement.