A stakeholder asks about the "critical path" of a project timeline. Which explanation is correct?
The critical path is a specific project-management term: the longest chain of dependent tasks, which sets the minimum project duration. Understanding it correctly means knowing that delays on the critical path directly delay the whole project, while delays on non-critical tasks (which have "slack" or "float") may not.
Useful phrase: "That task has slack, so a small delay there won't move our end date — but this other task is on the critical path, so any slip there pushes everything back."
2 / 5
You need to describe a project milestone in a status update. Which sentence correctly uses milestone vocabulary?
A milestone is a significant, named checkpoint in a timeline (not a task itself) used to track progress at a coarser grain than individual tasks. Reporting on milestones should name them specifically, state whether they were hit on schedule, and preview the next one with its target date and any built-in slack.
Vocabulary: "milestone" (checkpoint marking significant progress), "on schedule / ahead of schedule / behind schedule", "slack / buffer" (built-in flexibility), "target date" (as opposed to a hard commitment).
3 / 5
A dependency on another team is at risk of slipping. Which is the correct way to communicate this dependency risk in a timeline update?
Cross-team dependency risk should be flagged proactively, naming the specific dependency, the owning team, the risk signal observed, and the downstream impact on your own timeline. This turns a silent risk into a visible, trackable item rather than a surprise later.
Formula: "Our timeline depends on [team] delivering [thing] by [date]. [Risk signal]. If that happens, [downstream impact]. Flagging now so it's visible."
4 / 5
You are asked to explain why a Gantt chart shows two tasks running in parallel with a connecting line between them. Which explanation correctly describes this?
A dependency line in a Gantt chart shows a relationship between tasks — most commonly "finish-to-start" (task B can't begin until task A finishes) but also "start-to-start" (B can't begin until A begins) or "finish-to-finish." Correctly reading and explaining these relationships is essential to understanding why moving one task cascades into others.
Vocabulary: "dependency" (a task-to-task relationship), "finish-to-start / start-to-start / finish-to-finish" (dependency types), "predecessor / successor" (the earlier/later task in a dependency pair).
5 / 5
Leadership asks for a timeline commitment three weeks before requirements are finalised. Which response correctly balances honesty with usefulness?
Under high uncertainty (pre-requirements), the correct response gives a range based on comparable past work, explains when a firmer number will be available, and explicitly explains why a hard commitment now would be unreliable — rather than either refusing to answer or giving false precision.
Formula: "Based on [comparable data], I'd estimate [range]. I can give a firmer number [when]. I'd avoid a hard commitment before then because [reason]." This mirrors the "cone of uncertainty" concept — commitments should tighten as more information becomes available.
What does the "Project Timeline Communication — Estimation Language Exercise" exercise cover?
Practise Gantt chart vocabulary, milestones, critical path, slack time, and cross-team dependency risk communication in professional English. 5 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 "Project Timeline Communication — Estimation Language Exercise"?
This exercise has 5 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 Estimation Language exercises?
Browse the full Estimation Language 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.