Product Definition and Requirements
Free AIPMM Certified Product Manager practice — 6 questions on Product Definition and Requirements, with explanations. No sign-up. Full 12-question mixed test →
A product manager discovers during UAT that a requirement traced to a top customer's contractual commitment was removed from the release backlog three sprints ago without documentation or approval. Which action BEST addresses the root cause of this problem?
The underlying failure is a broken change-control and traceability process that allowed a contractually significant requirement to be silently dropped. A traceability matrix with mandatory sign-off before removal prevents recurrence by fixing the process gap, not just the symptom.
Which statement correctly differentiates the Market Requirements Document (MRD) from the Product Requirements Document (PRD) as used in the AIPMM product definition process?
The MRD is the market-facing artifact describing customer problems, market opportunity, and buyer/user needs at a business level, while the PRD converts those validated needs into specific, testable functional and non-functional specifications for the build team.
Which of the following is the BEST rewritten version of the poorly written requirement: "The system should be fast and easy to use"?
This version is specific, measurable, and verifiable — it defines exact performance thresholds and a concrete usability metric, making it directly testable by QA and engineering.
A stakeholder submits this requirement: "The platform must support 10,000 concurrent users during peak sign-up events without page load time degrading beyond 3 seconds." How should this requirement be classified and documented?
This requirement describes a quality attribute (capacity and performance under load) rather than a specific feature or behavior, making it non-functional. Because it includes measurable, testable engineering criteria, it belongs in the PRD's performance/scalability specifications.
In AIPMM's product definition practices, which statement correctly distinguishes a use case from a persona?
A persona is a representative archetype capturing the goals, motivations, and behaviors of a user segment, while a use case is a functional narrative describing the steps an actor takes to interact with the system and accomplish a goal — they serve complementary but distinct purposes in requirements definition.
During release scope negotiation, engineering confirms it can deliver only 60% of the prioritized backlog by the committed launch date. The backlog was previously prioritized using MoSCoW. Which approach BEST protects the product's ability to deliver its core value proposition at launch?
MoSCoW prioritization exists precisely to enable this kind of trade-off decision — protecting the Must Have requirements that define the minimum viable value proposition while trimming lower-priority Could Have and Should Have items to fit the fixed date.
Ready for the real thing?
The full course: two full-length practice tests, video lessons for every exam domain, hands-on labs and detailed explanations.
$109.99 $34.99 with code FREETEST33 — valid through September 7.
Get my $34.99 deal →