A well-written agenda item answers: what will be discussed, what decision needs to be made, who owns it, and how long it will take. Option B is specific about the topic (Q3 database migration plan), explicitly frames the decision (rolling vs. maintenance window), names an owner (@priya), and has a time box (15 min). Option A is a single word — it gives no context. Option C has no decision framing and is informal ("talk about"). Option D adds "(important)" as if any agenda item would be unimportant — the label adds no information.
2 / 14
Complete the agenda intro: "This meeting _____ (aim) to _____ (reach) a decision on the caching strategy. By the end, we _____ (have) a chosen approach and a list of next steps. Please _____ (read) the RFC document before _____ (join)."
Aims (present simple) describes the meeting's purpose as a designed fact. To reach — after "aim", English uses the to-infinitive: "aims to reach". Will have (future simple) — a concrete outcome promised by the end of the meeting. Read (base form imperative) — giving a pre-meeting instruction. Joining — after "before", use the gerund (verb-ing): "before joining". Option C uses "to join" (infinitive) after "before" which is grammatically wrong — "before" as a preposition must be followed by a gerund, not an infinitive. Option B uses "is aiming" which sounds like the meeting is currently in progress.
3 / 14
Which set of agenda sections follows meeting best practices for a 1-hour technical design meeting?
A good technical meeting agenda uses time-boxed sections with named owners, a clear purpose, and an explicit decision point. Option B: every section has a time box (5/15/15/10/10/5), owners are named (RFC-12, @alex), the decision is explicitly framed (choose between A and B), action items are a dedicated section (not afterthought), and a buffer exists. Option A is typical of meetings that have no agenda — "Discussion" is not an agenda item. Option C uses "AOB" (Any Other Business) which is a trap — it becomes a dumping ground that derails timing. Option D is circular — "agenda review" at the start of the agenda serves no purpose.
4 / 14
You are sending a meeting invite for a sprint retrospective. Which pre-meeting note is most useful?
Pre-meeting notes should give attendees specific, actionable preparation tasks with links and context on how those inputs will be used. Option B: numbered tasks (clear count), specific actions (add 2–3 items to FunRetro), format guidance (Start/Stop/Continue), a link to the board, a second task (velocity chart), and timing context (used in first 10 min — so attendees know it matters immediately). Option A is too vague. Option C is a social nicety with no content. Option D contradicts itself: "no preparation required" cancels the instruction to "think about" things.
5 / 14
Choose the correct phrasing for a time-check during a meeting: "We _____ (have) about 5 minutes left on this item. _____ (be) there any final points before we _____ (move) on? If we _____ (not/reach) consensus now, I _____ (suggest) we _____ (table) it for async follow-up."
We have (present simple) for a current, factual time statement. Are there — plural question form ("points" is plural). Before we move on — present simple in the before-clause (not "will move"). If we don't reach — present simple in the if-clause (zero/first conditional: if + present simple, … present/will). I suggest — present simple for a real-time procedural suggestion. We table — after "suggest" + that-clause, English uses the base form (subjunctive): "I suggest we table it" not "I suggest we will table it". Option C uses "will move" in the before-clause which is wrong. Option B uses "is there" (singular) but "points" is plural.
6 / 14
Liam sent the following Slack message to the team before a code review: 'Okay, let's look at this PR. The main issue is the data validation logic – it's not robust enough. Can everyone focus on that during the review?'
Which of the following agenda items would be MOST appropriate for Sarah to add *immediately* after Liam's message to ensure a productive code review discussion?
The core issue identified by Liam (lack of robust data validation) needs immediate prioritization. Option B is correct because requesting a breakdown forces the team to directly address the problem and understand the specifics. Options A and D are less immediate; scheduling a follow-up or providing documentation doesn't tackle the *current* discussion point. This demonstrates how to quickly surface critical issues during a code review – it's about focusing the conversation, not just providing background information.
7 / 14
Liam sent the following Slack message to the team before a code review: 'Okay, let's look at this PR. The main issue is the data validation logic – it's not robust enough. Can everyone focus on that during the review?'
Which of the following agenda items would be MOST appropriate for Sarah to add *immediately* after Liam's message to ensure a productive code review discussion?
The core issue identified by Liam (lack of robust data validation) needs immediate prioritization. Option B is correct because requesting a breakdown forces the team to directly address the problem and understand the specifics. Options A and D are less immediate; scheduling a follow-up or providing documentation doesn't tackle the *current* discussion point. This demonstrates how to quickly surface critical issues during a code review – it's about focusing the conversation, not just providing background information.
8 / 14
Liam sent the following Slack message to the team before a code review: 'Okay, let's look at this PR. The main issue is the data validation logic – it's not robust enough. Can everyone focus on that during the review?'
Which of the following agenda items would be MOST appropriate for Sarah to add *immediately* after Liam's message to ensure a productive code review discussion?
The core issue identified by Liam (lack of robust data validation) needs immediate prioritization. Option B is correct because requesting a breakdown forces the team to directly address the problem and understand the specifics. Options A and D are less immediate; scheduling a follow-up or providing documentation doesn't tackle the *current* discussion point. This demonstrates how to quickly surface critical issues during a code review – it's about focusing the conversation, not just providing background information.
9 / 14
Liam sent the following Slack message to the team before a code review: 'Okay, let's look at this PR. The main issue is the data validation logic – it's not robust enough. Can everyone focus on that during the review?'
Which of the following agenda items would be MOST appropriate for Sarah to add *immediately* after Liam's message to ensure a productive code review discussion?
The core issue identified by Liam (lack of robust data validation) needs immediate prioritization. Option B is correct because requesting a breakdown forces the team to directly address the problem and understand the specifics. Options A and D are less immediate; scheduling a follow-up or providing documentation doesn't tackle the *current* discussion point. This demonstrates how to quickly surface critical issues during a code review – it's about focusing the conversation, not just providing background information.
10 / 14
Sarah is drafting the agenda for a sprint planning meeting. Which of these statements best describes the purpose of including a 'Risk Assessment' section? It's crucial to proactively identify potential roadblocks and develop mitigation strategies before the sprint begins, ensuring the team stays on track and minimizes disruptions.
The primary goal of a risk assessment in sprint planning isn't just listing potential problems. It's to proactively identify them, assign ownership for mitigation, and establish contingency plans – this demonstrates a strategic approach to sprint success. Option A is insufficient because it lacks the action-oriented element; options C and D misrepresent the role of risk assessments.
11 / 14
You're preparing a Slack message to announce the agenda for tomorrow's code review meeting. Write a concise (under 50 words) message that clearly states the focus and expected outcomes. Use appropriate phrasing for requesting attention.
A well-crafted Slack message for a meeting agenda should be direct and informative. The example provided clearly states the topic (Module X), outlines the desired outcomes (root causes & solutions) and includes a polite request for attention. Option A is too long; options C and D lack essential details.
12 / 14
During a technical design meeting, David sends the following message in the shared document: 'Let's discuss the API endpoint design. We need to ensure it adheres to version 2.0 specifications and handles at least 10,000 requests per second.' Which of the following best reflects how this information should be incorporated into the agenda? Consider the level of detail needed for a design discussion
For a design meeting, it's crucial to clearly articulate the requirements and constraints. Adding 'API Endpoint Design & Performance Requirements (v2.0, 10k RPS)' provides context and directs the discussion effectively. Option A is too vague; options C and D miss key elements of the design process.
13 / 14
Mark needs to update his team during a daily standup. Which sentence would be most appropriate for conveying that there's an agenda item regarding the upcoming database migration? Focus on clarity and action orientation
Standup updates should be concise and action-oriented. This response clearly states the topic (database migration), outlines the goal (finalize rollback strategy) and sets expectations for further discussion. Option A is too vague; options C and D are inappropriate for a standup format.
14 / 14
You're writing the PR description for a code change that fixes a bug. Which of the following phrases best describes how to incorporate agenda items into your PR description? Focus on context and impact
A PR description should provide context and highlight the impact of the change. Referencing a previous discussion (issue #123) connects the fix to the larger agenda and provides valuable information for reviewers. Option A is too narrow; options C and D lack crucial connections.
What does the "Meeting Agendas — Writing Exercise" exercise cover?
Practice writing effective meeting agendas: agenda items with owners and time boxes, pre-meeting notes, and section structure. 5 interactive exercises.
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.
How many questions are in "Meeting Agendas — Writing Exercise"?
This exercise has 14 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Email & Writing exercises?
Browse the full Email & Writing hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.