Skip to content
Tech Interview Prep
Technical interview guide

Prioritization Frameworks (RICE, MoSCoW)

Structured ways to decide what to build next when everything looks important.

Read
30 min
Practice MCQs
25
Interview Q&A
25
Edition
v4
Editorial status
Reviewed

Scope: RICE, Agile Business Consortium MoSCoW, SAFe WSJF, Scrum Guide 2020, NIST RMF, GAO cost guidance, and DORA guidance current 2026-08-31.

Curated: · Written: · Reviewed:

25 questions

MCQ-13A product team sorts candidate features with the Kano model. Which category holds features that users treat as the price of entry: their absence draws complaints, yet polishing them past an adequate baseline wins no additional approval?
MCQ-7A team is scoping a two-week release of a billing service. The release runs in shadow mode: it recomputes every invoice from the production event stream but sends nothing to customers. Which candidate item is a Must Have for this release?
MCQ-12A team scores two backlog items. Item A has cost of delay 8 and job size 8; item B has cost of delay 8 and job size 2. Neither is mandatory and both are valuable. Which ordering does WSJF produce, and on what basis?
MCQ-3A team is scoring a feature for RICE. Their analytics show 30,000 monthly active users on the web app and 20,000 on mobile; 6,000 users are active on both. They define reach as distinct users in a 30-day window. What reach should they enter?
MCQ-2Two features are up for the next quarter. Feature A reaches 2,000 users, has an impact rating of 2, a confidence of 80%, and costs 4 person-weeks. Feature B reaches 5,000 users, has an impact rating of 1, a confidence of 100%, and costs 10 person-weeks. Using RICE, which feature should the team build first, and why?
MCQ-5A team sizes RICE effort in person-weeks and is scoring bulk invoice export before committing to it. Reach is 300 accounts per quarter, Impact is 1, and Confidence is 80%. The delivery plan is two backend engineers for three weeks each, one frontend engineer for two weeks, one designer for one week, one QA engineer for one week, a technical writer for half a week, and 1.5 person-weeks of rollout and on-call handover, all inside a single four-week cycle. What RICE score should go in the sheet?
MCQ-1Three engineers plan a 13-week quarter and reserve 20% of capacity for on-call and support. They score 60 backlog items by impact/effort and commit to the top 20, whose effort estimates total 140 engineer-weeks. Roughly how many of the top 20 can the team finish this quarter?
MCQ-19A CI pipeline has four jobs. Job A takes 10 minutes and has no dependencies. Job B has a hard dependency on A and takes 5 minutes. Job C has a hard dependency on B and takes 5 minutes. Job D is independent of the others and takes 12 minutes. The pipeline has two runners that can each run one job at a time. What is the minimum wall-clock time to finish all four jobs if jobs are scheduled as early as their dependencies allow?
MCQ-25A platform team has four candidate work items for next quarter and enough capacity to run all four, but it must choose the order. It sequences by WSJF: cost of delay divided by job duration in weeks. | item | cost of delay (value points) | job duration (weeks) | | --- | --- | --- | | A | 24 | 4 | | B | 40 | 5 | | C | 60 | 15 | | D | 6 | 2 | In what order should the team run them?
MCQ-11A payments team scores three candidate features on a 1–10 scale for business value, time criticality, and risk reduction, and estimates job size in story points: | Feature | Business value | Time criticality | Risk reduction | Job size | | --- | --- | --- | --- | --- | | A | 9 | 9 | 2 | 20 | | B | 6 | 5 | 4 | 5 | | C | 6 | 3 | 2 | 4 | The team sequences work by WSJF. What is the WSJF of the feature it starts first?
MCQ-10A team is picking which of five candidate features to start next iteration, and only one can start. Each feature is scored on SAFe's relative scales: user-business value, time criticality, and risk reduction/opportunity enablement, each 1–10: with job size in points: | Feature | User-business value | Time criticality | Risk reduction / opportunity enablement | Job size | | --- | --- | --- | --- | --- | | A | 10 | 1 | 1 | 8 | | B | 2 | 2 | 2 | 2 | | C | 6 | 8 | 6 | 5 | | D | 9 | 5 | 9 | 13 | | E | 3 | 10 | 3 | 10 | Using WSJF, which feature should the team sequence first?
MCQ-6Three vendors are scored 1–10 on cost, latency and support, weighted 0.5 / 0.3 / 0.2. Vendor A scores 8 / 5 / 6, B scores 6 / 9 / 7, C scores 7 / 7 / 8, putting C first at 7.2. A stakeholder argues the weights should be 0.4 / 0.4 / 0.2. What does re-running the model show?
MCQ-4Your payments team is choosing one feature for next quarter. Both candidates use the same RICE inputs except for impact and confidence. Feature A: saved-card autofill at checkout: reach 2,000 checkouts/quarter, impact 2, confidence 100% (a two-week A/B test on 5% of traffic lifted conversion 1.8%, p < 0.01), effort 2 person-weeks. Feature B: one-click checkout for returning buyers: reach 2,000 checkouts/quarter, impact 3, confidence 50% (estimate taken from a competitor's published case study; no test on this team's traffic), effort 2 person-weeks. Which feature should the team build?
MCQ-18Your team triages bugs by the share of monthly active users each one touches, then fixes the top of that list. Two bugs are open, and both cost the same engineering effort to fix. Bug A corrupts a saved document for 0.4% of the product's 2,000,000 monthly active users; each affected user hits it once and spends about 3 hours redoing the work. Bug B misaligns a toolbar icon for 35% of monthly active users; each affected user hits it once and spends about 20 seconds working around it. Reach ranks B first, 87× ahead of A. Which bug should the team fix first?
MCQ-9A team runs MoSCoW on a 40-item backlog for an upcoming release; every item is classified Must. What does this indicate?
MCQ-8A team is planning a six-week release with a fixed capacity of 240 engineer-days, and the Must, Should and Could items already consume all of it. SAML single sign-on sits in Won't Have at an estimated 30 engineer-days. Two weeks before the plan freezes, the largest prospect says they will not sign without SAML, and the product owner asks to add it. What does the Won't Have classification require?
MCQ-14A payments team must ship a regulatory change by a date six weeks out that cannot move. Scope is still open, and the team's estimates have historically been off by 2–3x, so effort-based ranking keeps misordering the work. They want a prioritization approach that produces a committed set for the date and a named set that is deferred. Which fits?
MCQ-15One platform team has one quarter of capacity and can run exactly one project this quarter; none of the candidates can be split or started part-time. Three candidates are on the board: - Checkout rewrite: +$1.2M first-year gross profit. - Enterprise SSO: +$1.8M first-year gross profit, but blocked on a vendor SAML fix that ships in Q3, so it cannot start this quarter. - Self-serve trial flow: +$900k first-year gross profit. The team ships the checkout rewrite this quarter. What is the opportunity cost of that decision, measured over the first year?
MCQ-16A payments team has spent $600k over 18 months building an in-house ledger service. Finishing it needs three more months and $200k, after which it runs at $25k/month in infrastructure and on-call. A vendor sells the same capability for $40k/month with no build cost. The team has no capacity to run both. Over the next 24 months, what should the team do?
MCQ-17Your team has shipped 3 of 8 planned features this quarter. A sales rep forwards an enterprise prospect's vendor security questionnaire: it lists 'SOC 2 Type II report' as a requirement, the deal is $400k ARR, and signature is targeted 5 weeks out. Your company has never had an audit; the auditor's scoping call says a Type II needs a 3-month observation window, so the earliest report is about 4 months away. What should you do?
MCQ-20A platform team's board has no WIP limit: on average 18 tickets sit in progress and the team completes 6 a week, and stakeholders complain that work takes weeks to land. The team caps the In Progress column at 6, and over the following month it still completes 6 tickets a week. What should they expect for average cycle time?
MCQ-23A platform team plans its quarter with a monthly re-prioritization checkpoint and ranks backlog items by WSJF (cost of delay ÷ job size). Two items are in play: A, token-bucket rate limiting for the auth service, sized at 3 weeks with a cost of delay of $40k/week driven by a compliance deadline in week 10; and B, a retry budget for the payments client, sized at 1 week with a cost of delay of $12k/week. In week 3 the compliance deadline slips to week 16, cutting A's cost of delay to $8k/week; a sales engineer asks for a demo of an already-shipped feature; and a staff engineer raises B's estimate from 1 week to 2 weeks. What should the team do?
MCQ-21Sprint 22 of a ten-working-day Sprint is on day 6. The Sprint Goal is to cut checkout p99 from 900 ms to 400 ms, all six items in the Sprint Backlog serve it, and four of them are still unstarted. A customer escalation leads the Product Owner to move item #18, a 5-point currency-rounding fix, from rank 31 to rank 1. The Developers judge that taking item #18 into this Sprint would leave either the p99 target or one of the checkout items unfinished. In Scrum, what happens to item #18?
MCQ-22A platform team ranks quarterly work by WSJF = cost of delay ÷ job size, with cost of delay in dollars per week and size in person-weeks. Two items lead the sheet: | item | cost of delay | size | WSJF | | --- | --- | --- | --- | | Partner SSO | $12k/week | 2 | 6.0 | | Cert rotation | $4k/week | 1 | 4.0 | The public API's TLS certificate expires in 10 days. On expiry every partner integration fails; the outage costs $250k/week and clearing it by hand takes one engineer-week. The team wants to schedule cert rotation ahead of SSO. Which action should it take?
MCQ-24A team estimated a self-serve onboarding flow at 8 engineer-weeks, expecting activation to rise from 30% to 45% of new signups and onboarding support tickets to fall from 1,200 to 600 per quarter. It shipped in 14 engineer-weeks; the next quarter showed activation at 33% and 1,050 tickets. Which change to the next estimate does this calibration data support?