Agile Delivery, Backlog, and Roadmapping
Free AIPMM Certified Digital Product Manager practice — 6 questions on Agile Delivery, Backlog, and Roadmapping, with explanations. No sign-up. Full 12-question mixed test →
A team uses WSJF for prioritization. Feature A has Cost of Delay = 40 and job size (duration) = 8. Feature B has Cost of Delay = 30 and job size = 5. Which should be sequenced first, and why?
WSJF = Cost of Delay ÷ Job Size (duration). Feature A: 40/8 = 5. Feature B: 30/5 = 6. Feature B delivers more value per unit of effort per unit time, so it should be sequenced first even though its raw Cost of Delay is lower.
During Kano-based user research, respondents report that increasing page load speed produces a steady, linear increase in satisfaction, while slow load times cause a proportional increase in dissatisfaction — with no extra 'delight' from speeds far exceeding expectations. Which Kano category best fits this attribute?
Performance (one-dimensional) attributes show a linear relationship: more of the feature yields proportionally more satisfaction, and less of it yields proportionally more dissatisfaction. Page load speed as described matches this pattern exactly.
A digital product manager notices growing technical debt is slowing delivery velocity each sprint. Which action best reflects the PM's appropriate role in managing this debt?
Effective PMs treat technical debt as a backlog item with business consequences (risk, velocity loss, customer impact) and negotiate ongoing capacity allocation with engineering rather than either ignoring it or over-engineering rigid rituals around it.
A product team is entering a highly uncertain, fast-changing market and wants to avoid making false-precision commitments to stakeholders about exact feature dates. Which roadmap approach best fits this constraint?
Now-Next-Later roadmaps communicate relative sequencing and intended outcomes without committing to specific dates or detailed scope, which matches the need to avoid false precision under high uncertainty.
A team suspects work is sitting idle for long periods between design handoff, development, and QA, even though each stage individually seems efficient. Which technique is best suited to diagnosing this specific problem?
Value stream mapping specifically visualizes the flow of work across all stages, exposing wait time and non-value-added handoff delays between teams — exactly the symptom described.
Team A's next user story requires an API endpoint that Team B is currently building, with delivery expected in two sprints. As Team A's product owner, what is the best way to manage this cross-team dependency?
Best practice for managing cross-team dependencies is to sequence dependent work realistically against the upstream team's committed timeline and surface the dependency transparently so both teams can plan around it.
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 →