Future Language in Technical Roadmaps and Planning
0 / 25 completed
1 / 25
A product manager announces: "We _____ release API v3 next quarter — the decision was made in last week's planning session." Which future form signals a pre-made plan?
Are going to release is correct. Going to signals a plan or intention that has already been decided — "the decision was made in last week's planning session" confirms this. "Will release" signals a decision made at the moment of speaking, or a general prediction. "Are releasing" (present continuous) also signals a fixed arrangement — and is actually a close second here — but "going to" more explicitly marks pre-planned intention. Simple present "release" is used for scheduled events (timetables), less common for roadmap discussions.
2 / 25
An SRE says in a sprint planning meeting: "I've just looked at the monitoring data — we _____ hit our storage limit within 48 hours." Which future form best signals a prediction based on current evidence?
Are going to hit is correct. Going to is used when there is current evidence pointing strongly towards a future outcome — "I've just looked at the data" is the evidence. This is the prediction-from-evidence use of "going to." "Will hit" is a general prediction or a decision — without the sense that the speaker has concrete evidence at this moment. "Are hitting" (present continuous) would imply we are already exceeding limits now. Simple present "hit" is not standard for this future prediction.
3 / 25
A tech lead writes in a release announcement: "The v2 API _____ be deprecated on 1 March — plan your migration accordingly." Which future form is most appropriate for announcing a scheduled event?
Will is correct. "Will" is standard for official release announcements, scheduled future events, and public commitments. It is direct and decisive — appropriate for a deprecation notice. "Is going to" is correct for plans but sounds slightly less formal in an official announcement context. "Would" signals conditionality, not a confirmed schedule. "Might" expresses uncertainty — unacceptable for a firm deprecation date.
4 / 25
In a standup, an engineer says: "I _____ demo the new authentication flow to the team at 2pm today — the calendar invite is out." Which future form best signals a fixed, arranged event?
Am demoing is correct. Present continuous for future time signals a fixed arrangement — something scheduled and confirmed, often with external evidence (here: the calendar invite). It is the natural choice for scheduled meetings, demos, and booked events. "Will demo" signals a decision made now or a prediction. "Am going to demo" signals a plan/intention but is less strong than present continuous for confirmed arrangements. Simple present "demo" would be appropriate for very fixed schedules (like timetables) but less natural for one-off arranged events.
5 / 25
A roadmap document states: "By Q4, the team _____ migrated all legacy endpoints to the new platform." Which future form is correct?
Will have migrated is correct. Future perfect (will have + past participle) describes an action that will be completed before a future reference point. "By Q4" is the deadline — and "will have migrated" signals that the migration will be finished before or at that point. "Will migrate" is a simple future prediction without the completion-before-deadline meaning. "Are migrating" is present continuous — signals current or arranged activity, not a completed future state. Simple present "migrates" cannot express future completion.
6 / 25
An architect says: "Look at these CPU graphs — the service _____ crash before end of day if we don't scale the instances." Which future form is best?
Is going to crash is correct. The architect is pointing to evidence ("Look at these CPU graphs") to support an imminent prediction — the classic use of "going to." "Will crash" is also grammatically possible but is weaker in this context because it lacks the sense of "I have evidence right now." "Crashes" (present simple) would imply a general or habitual pattern, not an imminent specific prediction. "Is crashing" describes what is happening right now, not what is about to happen.
7 / 25
Which future form is INCORRECT in this technical context?
Option D is incorrect. "Are going to be migrating" (going to + continuous) is grammatically possible but awkward and redundant for a scheduled arrangement. When you have a fixed, pre-arranged event — especially with a specific time ("midnight on Friday") — use present continuous: "We are migrating all user data at midnight on Friday." Going to + continuous overcomplicates the meaning unnecessarily. Options A, B, and C all use appropriate future forms for their contexts.
8 / 25
A release manager writes: "We _____ be about to start the deployment window — please freeze all code changes." Which future form fits this notification?
Are is correct. "Are about to" is a fixed phrase meaning "will happen very soon / imminently." "We are about to start" signals imminent action — ideal for a deployment window notification. "Will be about to" (option A combining will + be about to) is not standard — "about to" already covers imminence without needing "will". "Are going to be about to" (option C) is also redundant. "Have about to" (option D) is ungrammatical.
9 / 25
A sprint retrospective note reads: "By the end of this sprint, we _____ resolved 12 of the 15 backlog items." Which future form is correct for a completion projection?
Will have resolved is correct. "By the end of this sprint" is the deadline, and "will have resolved" (future perfect) expresses completion before that point. This is a common structure in sprint projections: "By end of Q2, we will have shipped X features." "Will resolve" lacks the completion-by-deadline meaning. "Are going to resolve" signals a plan but does not convey the completion aspect. Simple present "resolve" cannot convey the future completion concept.
10 / 25
An engineering manager writes in a team announcement: "The team _____ scale to 12 engineers by end of year — we have budget approval." Which future form best conveys a planned, confirmed outcome?
Will scale is correct. For official announcements of planned outcomes with confirmed resources ("we have budget approval"), "will" is appropriate — it communicates certainty and commitment. "Is scaling" would imply the scaling is happening right now. "Might scale" introduces uncertainty that contradicts "we have budget approval." "Scaled" is simple past — impossible for a future outcome. Note: "is going to scale" would also be acceptable, but "will scale" is the more natural choice for a formal team announcement.
11 / 25
Sarah (Lead DevOps) posted this to Slack: 'Okay team, we're anticipating a major outage with the database server. We need to immediately implement a rollback strategy.' Which future form best reflects Sarah's urgent concern and prediction?
The correct answer, 'anticipated,' accurately captures Sarah's reaction. It indicates a belief about a future event (the outage) based on current observations. The other options use different tenses that don't fit the urgency and predictive nature of her message; 'planned' suggests a deliberate action already in progress, while 'predicted' is too general without referencing specific data.
12 / 25
During a sprint review, David (Backend Engineer) said: 'The new microservice will handle approximately 50% more requests than the existing system.' Which future form is most appropriate for this statement?
The 'conditional' form is the most accurate. David is expressing a belief about future performance based on anticipated increased load. 'Future' implies a completed action, 'present continuous' describes ongoing activity, and 'predictive' is too vague without a connection to observable data or a specific scenario.
13 / 25
A technical document states: 'The platform will automatically update to version 2.5 on December 1st.' Which future form is most suitable for this announcement?
The 'scheduled' form best reflects the document's intention. It clearly indicates that the update has a predetermined date and time. The other options convey different levels of uncertainty or lack of control over the event; 'probable' suggests a low likelihood, while 'expected' is subjective and 'potential' implies an optional action.
14 / 25
Mark (Junior Dev) writes in a PR description: 'This change will resolve the intermittent login failures.' Which future form best describes the intended outcome of this code?
The 'resolved' form accurately conveys Mark's intention. It indicates that the code is designed to eliminate a specific problem or error. 'Completed' implies the action is finished, while 'ongoing' describes an active process and 'predicted' offers no concrete guarantee of the change's effectiveness.
15 / 25
A release manager sends a notification: 'The deployment will begin at 08:00 GMT tomorrow.' Which future form best fits this announcement?
The 'scheduled' form is the most precise. It clearly states that the deployment has a specific start time and is not subject to change. The other options indicate varying degrees of uncertainty or lack of control over the event; 'proposed' suggests a suggestion, 'anticipated' is a prediction and 'predicted' relies on assumptions about progress.
16 / 25
Sarah (Lead DevOps) posted this to Slack: 'Okay team, we're anticipating a major outage with the database server. We need to immediately implement a rollback strategy.' Which future form best reflects Sarah's urgent concern and prediction?
The correct answer, 'anticipated,' accurately captures Sarah's reaction. It indicates a belief about a future event (the outage) based on current observations. The other options use different tenses that don't fit the urgency and predictive nature of her message; 'planned' suggests a deliberate action already in progress, while 'predicted' is too general without referencing specific data.
17 / 25
During a sprint review, David (Backend Engineer) said: 'The new microservice will handle approximately 50% more requests than the existing system.' Which future form is most appropriate for this statement?
The 'conditional' form is the most accurate. David is expressing a belief about future performance based on anticipated increased load. 'Future' implies a completed action, 'present continuous' describes ongoing activity, and 'predictive' is too vague without a connection to observable data or a specific scenario.
18 / 25
A technical document states: 'The platform will automatically update to version 2.5 on December 1st.' Which future form is most suitable for this announcement?
The 'scheduled' form best reflects the document's intention. It clearly indicates that the update has a predetermined date and time. The other options convey different levels of uncertainty or lack of control over the event; 'probable' suggests a low likelihood, while 'expected' is subjective and 'potential' implies an optional action.
19 / 25
Mark (Junior Dev) writes in a PR description: 'This change will resolve the intermittent login failures.' Which future form best describes the intended outcome of this code?
The 'resolved' form accurately conveys Mark's intention. It indicates that the code is designed to eliminate a specific problem or error. 'Completed' implies the action is finished, while 'ongoing' describes an active process and 'predicted' offers no concrete guarantee of the change's effectiveness.
20 / 25
A release manager sends a notification: 'The deployment will begin at 08:00 GMT tomorrow.' Which future form best fits this announcement?
The 'scheduled' form is the most precise. It clearly states that the deployment has a specific start time and is not subject to change. The other options indicate varying degrees of uncertainty or lack of control over the event; 'proposed' suggests a suggestion, 'anticipated' is a prediction and 'predicted' relies on assumptions about progress.
21 / 25
Sarah (Lead DevOps) posted this to Slack: 'Okay team, we're anticipating a major outage with the database server. We need to immediately implement a rollback strategy.' Which future form best reflects Sarah's urgent concern and prediction?
The correct answer, 'anticipated,' accurately captures Sarah's reaction. It indicates a belief about a future event (the outage) based on current observations. The other options use different tenses that don't fit the urgency and predictive nature of her message; 'planned' suggests a deliberate action already in progress, while 'predicted' is too general without referencing specific data.
22 / 25
During a sprint review, David (Backend Engineer) said: 'The new microservice will handle approximately 50% more requests than the existing system.' Which future form is most appropriate for this statement?
The 'conditional' form is the most accurate. David is expressing a belief about future performance based on anticipated increased load. 'Future' implies a completed action, 'present continuous' describes ongoing activity, and 'predictive' is too vague without a connection to observable data or a specific scenario.
23 / 25
A technical document states: 'The platform will automatically update to version 2.5 on December 1st.' Which future form is most suitable for this announcement?
The 'scheduled' form best reflects the document's intention. It clearly indicates that the update has a predetermined date and time. The other options convey different levels of uncertainty or lack of control over the event; 'probable' suggests a low likelihood, while 'expected' is subjective and 'potential' implies an optional action.
24 / 25
Mark (Junior Dev) writes in a PR description: 'This change will resolve the intermittent login failures.' Which future form best describes the intended outcome of this code?
The 'resolved' form accurately conveys Mark's intention. It indicates that the code is designed to eliminate a specific problem or error. 'Completed' implies the action is finished, while 'ongoing' describes an active process and 'predicted' offers no concrete guarantee of the change's effectiveness.
25 / 25
A release manager sends a notification: 'The deployment will begin at 08:00 GMT tomorrow.' Which future form best fits this announcement?
The 'scheduled' form is the most precise. It clearly states that the deployment has a specific start time and is not subject to change. The other options indicate varying degrees of uncertainty or lack of control over the event; 'proposed' suggests a suggestion, 'anticipated' is a prediction and 'predicted' relies on assumptions about progress.
What will I practise in "Future Language in Technical Roadmaps — Grammar Exercise"?
Practice will, going to, present continuous, future perfect, and be about to for roadmap discussions, sprint planning, and release announcements.
How many exercises are in this module?
This module has 25 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
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.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the grammar rule and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Grammar exercises?
Browse the full Grammar hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain grammar rules in prose; this exercise tests and reinforces those rules through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.