Learn planning meeting vocabulary: quarterly planning, PI planning (SAFe), portfolio review, planning horizon, and rough-cut capacity planning used in agile and enterprise environments.
0 / 10 completed
1 / 10
In SAFe (Scaled Agile Framework), multiple Agile teams gather for a 2-day event to align on goals, identify dependencies, and plan the next 8–12 weeks of work across an Agile Release Train. What is this event called?
PI Planning (Program Increment Planning) is the heartbeat event of SAFe, held every 8–12 weeks. All teams in an Agile Release Train (ART) meet face-to-face (or virtually) to plan the next Program Increment — typically 4–6 sprints. Outputs include PI Objectives (team-level OKRs), a Programme Board showing features and dependencies, and team iteration plans. SAFe describes it as 'the most important event in SAFe.'
2 / 10
Before committing to a quarterly plan, a team checks whether their total workload fits within available person-days after accounting for holidays, support duties, and meeting overhead. What is this activity called?
Rough-cut capacity planning (RCCP) is a high-level check that estimated workload does not exceed available capacity. It does not schedule individual tasks — it just answers 'can we do this much work in this period?' Steps: calculate available person-days, subtract overhead (support, meetings, PTO), then compare to estimated effort of planned items. RCCP is common in PI Planning and quarterly planning to prevent over-commitment.
3 / 10
During a quarterly planning meeting, the VP of Product asks: 'Are we allocating enough to the three-year horizon, or are we only thinking about the next 90 days?' She is raising a concern about ___________ balance.
Planning horizon refers to how far ahead a plan extends. Organisations typically maintain multiple horizons: H1 (now, 0–3 months, high confidence), H2 (next, 3–12 months, directional), H3 (later, 1–3 years, exploratory). A common pitfall is horizon collapse — where all planning energy goes to the immediate quarter and no strategic thinking happens for H2/H3. Portfolio reviews often include a horizon health check.
4 / 10
At the end of a quarter, executives and portfolio managers review which initiatives delivered value, which should be continued, which should be stopped, and where to reallocate investment. What is this meeting typically called?
A Portfolio Review (also called a Quarterly Business Review or QBR in many organisations) is where senior stakeholders evaluate the portfolio of initiatives against strategic goals and business outcomes. Unlike a Sprint Review (team-level) or retrospective (process-focused), a portfolio review asks: 'Are we investing in the right things?' It often results in start/stop/continue decisions on epics and funding reallocations.
5 / 10
During quarterly planning, a team announces they can deliver Feature X in Q2 only if the infrastructure team completes the database migration in Q1. In planning vocabulary, this cross-team timing constraint is called a ___________.
A cross-team dependency is a scheduling constraint where one team's deliverable is required before another team can complete their work. In PI Planning, cross-team dependencies are captured on a Programme Board (a physical or digital board showing features on a timeline with dependency arrows between teams). Unresolved cross-team dependencies are the primary cause of Program Increment delays in scaled agile environments.
6 / 10
Sarah from the frontend team is drafting a PR description for a new UI component. She wants to clearly communicate the purpose of the change and any dependencies. Which phrase best describes her intention when writing: 'This commit addresses usability issues related to user onboarding by introducing a streamlined welcome flow.'?
This question assesses Sarah's ability to use precise language when describing code changes. The correct option highlights that 'precise' indicates a clear statement of the problem being solved and the solution implemented. The other options represent unclear or incomplete phrasing, which are less effective in communication, especially within a code review context where understanding is paramount. It corrects the misconception that PR descriptions should simply detail technical implementation.
7 / 10
Mark, the Scrum Master, is facilitating a daily standup. A developer states: 'I'm blocked on getting access to the staging environment.' Mark responds with: 'Okay, let's add that to the action items for today and see if we can get it resolved by the end of the day.' What does 'add that to the action items' primarily mean in this scenario?
This tests understanding of action item tracking. 'Adding it to the action items' signifies that Mark is acknowledging the blocker, documenting it for follow-up, and assigning responsibility (to himself) to ensure resolution. The other options represent more proactive or potentially disruptive responses. It corrects the misconception that an action item simply means a request without assigned ownership.
8 / 10
David, the API developer, receives this response from a third-party service: `{"status": "403", "message": "Forbidden - Insufficient permissions."}`. What does 'Insufficient permissions' most accurately describe in this context?
This question focuses on interpreting API response messages. 'Insufficient permissions' is a common status code indicating that the user attempting to access the resource doesn't have the necessary credentials or rights. The other options represent different types of problems, but authentication errors are the most direct interpretation of this specific error message. It corrects the misconception that 403 always represents a network issue.
9 / 10
Emily is leading a sprint planning meeting. The team estimates that delivering Feature Y will require 15 story points and involves significant integration with another team's API. She states: 'We need to account for potential delays due to dependencies on the external team.' What's the most appropriate term to describe this consideration?
This probes understanding of risk management in planning. 'Risk mitigation' accurately reflects Emily's statement – acknowledging a potential problem (dependencies leading to delays) and taking steps to manage it proactively. Scope creep and concurrency management represent alternative interpretations that don't fully capture the essence of her concern. It corrects the misconception that dependency management is solely about coordinating activities.
10 / 10
John is writing a PR description for a refactoring effort to improve code readability and maintainability. He writes: 'This commit enhances the codebase by implementing improved naming conventions and consistent formatting.' What does this primarily emphasize?
This focuses on the importance of describing refactoring work accurately. 'Technical debt reduction' is the most relevant description because this commit's focus is on improving the *quality* of the existing code (readability and maintainability), which directly addresses technical debt. The other options describe features or security enhancements, not the core purpose of a refactoring task. It corrects the misconception that all PR descriptions must detail new functionality.
What will I learn from the "Planning Meetings Vocabulary" exercise?
Learn planning meeting vocabulary: quarterly planning, PI planning (SAFe), portfolio review, planning horizon, and rough-cut capacity planning used in agile and enterprise environments.
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.