Prioritisation Frameworks — Vocabulary and Language
Learn vocabulary for product prioritisation frameworks: RICE, MoSCoW, WSJF, and prioritisation discussion language.
0 / 10 completed
1 / 10
What does 'RICE' stand for in prioritisation vocabulary?
RICE score = (Reach x Impact x Confidence) / Effort. Reach: how many users affected per time period. Impact: estimated effect per user (0.25x to 3x). Confidence: how certain you are (100% certain = 1.0). Effort: person-months of work. RICE prevents gut-feel prioritisation and makes trade-offs explicit.
2 / 10
What is the 'MoSCoW' prioritisation method?
MoSCoW: Must Have (without this, the release fails — non-negotiable), Should Have (high value, included if possible), Could Have (nice to have — first to cut if timeline is at risk), Won't Have this time (explicitly acknowledged but out of scope for now). Useful for scope conversations with stakeholders.
3 / 10
What is 'WSJF' (Weighted Shortest Job First) in agile prioritisation?
WSJF = Cost of Delay / Job Size (duration or complexity). Cost of Delay = User-Business Value + Time Criticality + Risk Reduction/Opportunity Enablement. WSJF prioritises work that is: high value AND time-sensitive AND short — avoiding long valuable projects when short valuable-but-time-critical work is available.
4 / 10
What does 'opportunity cost' mean in prioritisation discussions?
Opportunity cost in prioritisation: choosing to build Feature A means NOT building Feature B in the same time. 'If we spend Q3 on the enterprise SSO integration, we cannot also run the retention experiment. The opportunity cost of SSO is the retention improvements we defer.' Making opportunity costs explicit improves prioritisation quality.
5 / 10
What is 'stack ranking' in prioritisation vocabulary?
Stack ranking forces true prioritisation: if everything is Priority 1, nothing is prioritised. A stack-ranked backlog has one item at position 1, one at position 2, etc. This surfaces real trade-offs and prevents priority inflation. The stack rank is the authoritative answer to 'what should we work on next?'
6 / 10
Sarah from Product Management just posted this comment on your pull request: 'We need to address the high-priority bug affecting user login before anything else. This is a blocker for our upcoming marketing campaign.' What prioritization framework is Sarah primarily referencing?
Sarah is utilizing a framework that assesses priorities by quantifying factors like Reach (user base), Impact (severity of the bug), Confidence (certainty of resolution), and Effort (development time). This aligns directly with RICE scoring, which aims to provide a data-driven basis for decision-making regarding feature prioritization. The other options represent different frameworks with distinct approaches.
7 / 10
You're in a Slack channel discussing the development of a new API endpoint. David asks: 'Should we implement the full reporting functionality now, or just the basic data retrieval?' You respond with: 'We should consider the opportunity cost – delaying this feature could mean missing out on valuable insights and potentially impacting key metrics.' Which prioritization technique does this statement best illustrate?
David's question directly relates to assessing trade-offs – what's gained by doing one thing versus another. 'Opportunity cost' captures exactly this concept: it acknowledges that every decision has an alternative benefit lost. While Cost-Benefit Analysis is related, opportunity cost is a more specific element of prioritizing based on potential gains.
8 / 10
As the lead developer for a new mobile app update, you're writing the PR description. You want to clearly communicate the prioritization of bug fixes versus new features. Which statement would be MOST effective in conveying this?
Option B provides specific details about the prioritization – it clearly states that security/performance came first, followed by user feedback. The other options are vague and don't communicate the underlying rationale for the order of work. Using precise language like 'prioritized' is key here.
9 / 10
During a daily standup meeting, Mark says: 'I'm going to focus on finishing the user authentication flow today. It's blocking other team members from accessing the system.' What prioritization framework is he implicitly employing?
Mark's statement highlights the concept of WSJF – prioritizing tasks that have the greatest impact (blocking other team members) relative to their effort (finishing the authentication flow). WSJF is commonly used in agile contexts where speed and efficiency are paramount. While Scrum provides a framework, Mark's focus directly embodies its prioritization principles.
10 / 10
You're reviewing a code change submitted by Elena. She's implemented a new feature that improves data processing speed but has added several complex dependencies. You note: 'This is a great improvement for performance, but the increased complexity introduces significant technical debt.' Which term best describes your concern regarding this prioritization decision?
'Technical debt' refers to the implicit cost of shortcuts taken during development – in this case, the increased complexity introduced by the new dependencies. Elena prioritized performance (a desirable outcome) without fully considering the long-term implications for maintainability and future development. Strategic Alignment is related but focuses on broader business goals.
What will I learn from the "Prioritisation Frameworks — Vocabulary and Language" exercise?
Learn vocabulary for product prioritisation frameworks: RICE, MoSCoW, WSJF, and prioritisation discussion language.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall required.
How many questions are in this exercise?
This set contains 10 multiple-choice questions, each with a detailed explanation shown after you answer.
Do I need to create an account to track my progress?
No account is required. Your progress bar and score reset each time you reload the page, but you can retry the exercise as many times as you like.
Who is this Roadmap & OKR exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss roadmap & okr topics confidently at work.
What happens if I answer a question incorrectly?
You will see the correct answer highlighted along with a detailed explanation of why it is correct -- so every wrong answer becomes a learning moment, not just a lost point.
Can I retry this exercise?
Yes -- click "Try again" on the results screen at any time to reset your score and go through all the questions again.
How long does this exercise take to complete?
Most learners finish all 10 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more Roadmap & OKR exercises?
See the full Roadmap & OKR exercises hub for more vocabulary drills on this topic.
Is this exercise mobile-friendly?
Yes -- the exercise works on any device with a modern browser, including phones and tablets, with no app download required.