Communication: 'this roadmap is directional — not a commitment to dates', 'we're de-scoping X to protect Y'
0 / 10 completed
1 / 10
A product manager explains to a new engineer: "We use OKRs to align the team. Each Objective is a qualitative statement of what we want to achieve. Each Key Result is a measurable outcome that tells us whether we got there. We set a confidence score from 0.0 to 1.0 — right now this KR is at 0.4, which means we think there's a 40% chance we'll hit it." What is the difference between an Objective and a Key Result in OKRs?
Objective: a qualitative, inspiring statement of what you want to achieve. It answers "where are we going?" Examples: "Make our API the most reliable in the industry", "Become the go-to data platform for mid-market companies." Key Result: a specific, measurable outcome that signals whether you reached the Objective. Must be a result, not a task. Example KR: "Reduce API p99 latency from 800ms to 200ms." Bad KR (task): "Deploy the new caching layer." OKR vocabulary: Confidence score — a probability (0.0–1.0) of hitting the KR by end of period. 0.5 = on track; <0.3 = at risk; >0.7 = sandbagging. Committed OKR — expected to be achieved 100%; failure is a problem. Aspirational OKR (stretch goal) — 70% achievement = success; designed to push beyond comfort. OKR check-in — weekly or bi-weekly update of confidence scores and progress. KR owner — individual accountable for tracking and moving the KR. In conversation: "Our confidence on the latency KR dropped to 0.3 — we need to escalate the infrastructure blocker."
2 / 10
An engineering manager presents at a quarterly planning: "Our roadmap this quarter has three horizons. Horizon 1 is committed work — shipped features we're supporting and optimising. Horizon 2 is the bets we're actively building. Horizon 3 is exploratory — prototypes we might or might not productise. I want to be clear: the Horizon 3 items are directional, not commitments." What does directional mean in roadmap vocabulary?
Directional: indicates intent and likely direction without constituting a firm commitment. The opposite is committed — work that will be delivered. Roadmap vocabulary: Now/Next/Later — a three-horizon roadmap format. "Now" = committed, in-progress; "Next" = prioritised, likely next; "Later" = directional, exploratory. Horizon 1/2/3 — strategic time horizons: H1 = optimise existing business (0–12 months); H2 = build new growth (12–36 months); H3 = explore future options (3–5 years). Theme-based roadmap — organises work around customer outcomes/themes rather than specific features; avoids over-committing to implementation details. Feature freeze — a deadline after which no new features are added to the release scope. Descope — removing a feature from a release to protect the deadline. In conversation: "The Horizon 3 items help stakeholders understand where we might go — but they're not on the delivery plan."
3 / 10
A senior PM explains prioritisation to the team: "We're using RICE to rank these features. RICE stands for Reach, Impact, Confidence, and Effort. Feature A has Reach=500 users/quarter, Impact=3, Confidence=80%, Effort=2 person-weeks — so its RICE score is 500 × 3 × 0.8 / 2 = 600. Feature B scores 240. We're doing Feature A first." What does Confidence represent in the RICE scoring framework?
RICE score = (Reach × Impact × Confidence) / Effort. RICE vocabulary: Reach — how many users/customers will this affect per period? (people/quarter). Impact — how much does it move the needle per user? (scale: 0.25=minimal, 0.5=low, 1=medium, 2=high, 3=massive). Confidence — how certain are you about the Reach and Impact estimates? (100% = high evidence; 80% = medium; 50% = low). Acts as a discount factor for uncertainty. Effort — total person-weeks/months of work. Other prioritisation frameworks: MoSCoW — Must have (non-negotiable), Should have (important), Could have (nice-to-have), Won't have (explicitly out of scope). WSJF (Weighted Shortest Job First) — used in SAFe: Cost of Delay / Job Duration. Prioritises fast-to-deliver items with high cost of delay. Value vs. effort matrix — 2×2 quadrant. "Quick wins" (high value, low effort) first. In conversation: "The confidence score is only 50% because we haven't user-tested the assumption yet — we should validate before committing to Horizon 2."
4 / 10
During backlog grooming, a tech lead says: "This epic is too big to put on the roadmap as a single item — let's break it into initiatives. The first initiative is the foundation: authentication and data model. The second is the user-facing features. Each initiative should have a clear milestone we can point to. We can use the milestone as a forcing function for the quarterly review." How do epic, initiative, and milestone relate in planning vocabulary?
Planning hierarchy (most common interpretation): Initiative — a large strategic bet or programme of work aligned to a business goal. May span multiple quarters. Example: "Launch self-serve analytics." Epic — a large body of work within an initiative, typically 2–8 weeks. Contains multiple user stories. Example: "Build the query builder." User story — a small, user-centred slice of work delivered in 1–5 days. Milestone — a key checkpoint marking meaningful, demonstrable progress. Not a feature — a state: "users can query their own data." Vocabulary: Backlog grooming / refinement — the process of reviewing, estimating, and prioritising backlog items. Sprint goal — a single, clear objective for a sprint that the team commits to. Forcing function — an event or constraint that compels action. Example: a quarterly review as a deadline for reaching a milestone. In conversation: "The milestone is 'users can log in and see their dashboard' — that's what we're committing to for the quarterly demo."
5 / 10
A product director explains to stakeholders why a feature is being delayed: "We're de-scoping the reporting module from Q3. I know that's disappointing, but the core payments flow has to be right first — it's blocking 200 customers. We're re-prioritising based on what moves our north star metric most. The reporting module is still on the roadmap for Q4 — it's not cancelled." What does de-scope mean in a roadmap context?
De-scope: to remove an item from the current delivery commitment — a release, sprint, or quarter. It is not cancellation. The item typically moves to a future period or the backlog. Roadmap communication vocabulary: De-scope — "we're removing X from this release." Reprioritise — "X is now more important than Y; Y moves down." Stretch goal — "if we finish early, we'll tackle this bonus item." Committed vs. aspirational — committed = will be done; aspirational = best-case scenario. North star metric — the single metric that best captures the core value the product delivers to users. Everything is measured against its impact on the north star. Backlog — the ordered list of all remaining work. Ice box — ideas deprioritised indefinitely, not actively groomed. Phrases: "We're de-scoping to protect the Q3 launch date." "This feature is de-prioritised, not cancelled." "We'll revisit in the next quarterly planning cycle."
6 / 10
Code Review Comment: 'This PR needs more clarity around the performance impact of this new API call. The documentation doesn't specify how it affects latency and throughput. We need to track key results like 'Reduce average API response time by 15%' to ensure we're meeting our goals.' What does the comment *primarily* focus on regarding the PR?
This comment directly addresses the PR's impact on key results – specifically, performance. While design and style are important, this feedback is laser-focused on tracking measurable outcomes defined within an OKR framework. The reviewer wants to ensure the new API call contributes positively to a defined KR related to latency and throughput.
7 / 10
Slack Message from @jane_doe: 'Hey team, just wanted to flag that the 'User Profile v2' OKR (reduce profile load times by 20%) is currently at 0.2. We need a plan to get this back on track – maybe we can revisit the data caching strategy?' What does Jane's message imply about the current status of the User Profile v2 OKR?
Jane's message highlights a concerning situation: the KR value of 0.2 indicates a failure to meet the target. This implies that the current progress is far below the desired 20% reduction in profile load times, necessitating immediate attention and a revised strategy.
8 / 10
API Response (JSON): '{
"status": "error",
"code": 400,
"message": "Invalid input - Confidence score must be between 0.0 and 1.0.",
"key_result": "Increase user engagement by 10%"
}' What does the error message in this API response suggest about a potential problem with an OKR?
The API response explicitly states that the 'Confidence score' is out of range. This strongly suggests an error in how the KR was defined or configured – a key result requires valid numerical input within specified boundaries. A misconfigured KR would likely trigger this kind of validation error.
9 / 10
PR Description: 'This commit implements the 'Dark Mode' feature as part of Horizon 3 - a potential future enhancement. It's purely a proof-of-concept and doesn't directly impact our current Q3 roadmap metrics. We're tracking progress via a new KR focused on UI/UX exploration.' What is the *primary* purpose of including this PR within Horizon 3?
Horizon 3 items are defined as 'exploratory' – meaning they're focused on experimentation and validation. This PR is explicitly described as a 'proof-of-concept,' indicating its primary function is not to deliver a finished feature but to gather insights and data for potential future roadmap decisions.
10 / 10
Standup Update from @mark_smith: 'Yesterday, I spent the morning refining the RICE score for the new search algorithm. Initially it was a 600, but after further analysis, we've reduced the Reach to 400 and adjusted the Confidence to 90%, bringing the total down to 360.' What does Mark's update primarily demonstrate about his work?
Mark describes a process of refining and adjusting a key metric – the RICE score. This demonstrates his focus on data analysis and iterative optimization to improve the potential impact of a feature based on the scoring framework. It's not about achieving the highest possible score, but rather informed adjustments.
What does the "Technical Roadmap & OKR Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to technical roadmap & okr vocabulary through 10 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 10 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.