🔥 Warm-Up (5 minutes)
- Think of a project you were involved in that fell behind schedule. What was the main cause—unclear requirements, resource constraints, or something else?
- How do you typically communicate a delay or a change in scope to stakeholders? What makes that conversation easier or harder?
📖 Key Vocabulary
| English | Type | Example Sentence |
|---|---|---|
| milestone | n. | Completing the beta release on schedule was a critical milestone that reassured the client the project was back on track. |
| scope creep | n. | Without a rigorous change-control process, scope creep can quietly erode both the budget and the timeline. |
| stakeholder buy-in | n. | Securing stakeholder buy-in before the kickoff meeting prevented the kind of last-minute objections that derailed the previous rollout. |
| deliverable | n. | Each deliverable was tied to a specific milestone, so slipping one inevitably pushed back the next. |
| contingency plan | n. | The program office insisted on a contingency plan in case the vendor's testing environment wasn't ready in time. |
| expedite | v. | To expedite approval, the team routed the change request directly to the steering committee rather than waiting for the weekly review. |
| bottleneck | n. | The single sign-off requirement turned out to be a bottleneck that delayed every downstream task. |
| mitigate | v. | Reassigning two senior engineers to the critical path helped mitigate the risk of further slippage. |
| defer | v. | Rather than compromise quality, the committee chose to defer the launch by two weeks. |
| accountable | adj. | Under the revised governance structure, each workstream lead is individually accountable for their deliverables. |
🧠 Grammar / Strategy Focus
In formal and written business English, certain negative or restrictive adverbials—such as 'not only,' 'rarely,' 'seldom,' 'under no circumstances,' 'not until,' and 'hardly... when'—trigger subject-auxiliary inversion when they open a clause, mirroring the word order of a question (adverbial + auxiliary + subject + main verb). This construction adds emphasis and formality, and is common in reports, memos, and policy statements where a strong prohibition or a striking contrast needs to be foregrounded. For example: 'Under no circumstances should the project scope be altered without written sign-off from all stakeholders,' or 'Not only did the vendor miss the deadline, but the revised specifications also introduced significant scope creep.' Note that inversion applies only when the adverbial begins the clause; if it is moved to the end or middle of the sentence, normal word order returns (e.g., 'The scope should not be altered under any circumstances without sign-off').
✏️ Part 5 Practice
Incomplete Sentences
📝 Part 6 Practice
Text Completion (Subject: Revised Timeline for the Atlas CRM Migration)
To: All Workstream Leads
From: Priya Nair, Program Director
Subject: Revised Timeline for the Atlas CRM Migration
As most of you are aware, the vendor's delayed delivery of the data-mapping specifications has (1) a two-week slip in the integration testing phase. Not only has this pushed back the original go-live date, but it has also placed considerable strain on the QA team, who must now compress a four-week test cycle into ten working days.
In light of these constraints, the steering committee has approved an interim measure: two developers currently assigned to the reporting module will be (2) to integration testing until the revised milestone is met. Workstream leads whose deliverables depend on the reporting module should adjust their own schedules (3).
It is imperative that any further changes to scope (4) approved in writing by the change control board before implementation. Given the tight margin remaining before the client-facing demonstration, unauthorized deviations will not be tolerated.
Please direct questions to my office by end of day Thursday.
📰 Part 7 Practice
Reading Comprehension
A recent survey of more than 400 program managers across Southeast Asia found that nearly half of large-scale software implementations exceed their originally approved timeline by at least six weeks, with scope creep cited as the single most common culprit. Respondents overwhelmingly attributed the phenomenon not to poor planning at the outset, but to an accumulation of seemingly minor requests—an additional report field here, a new approval workflow there—that individually appeared negligible yet collectively derailed even the most meticulously sequenced schedules. Only when the cumulative effect became undeniable, researchers noted, did project sponsors typically intervene, by which point remediation was both costly and disruptive.
To curb this pattern, the survey's authors recommend that organizations formalize a change-control mechanism at the very inception of a project, one that obliges any party requesting a modification to submit a written impact assessment addressing cost, schedule, and downstream dependencies before the request is entertained. Equally critical, they argue, is securing unambiguous stakeholder buy-in on the initial scope statement, since ambiguity at that stage tends to resurface, often magnified, during the execution phase. Firms that adopted both measures reported a marked reduction in schedule slippage, underscoring the extent to which upfront discipline, rather than downstream heroics, ultimately determines whether a deliverable ships on time.
🎧 Listening Practice
Conversation (Part 3 style)
Teacher: read the script aloud twice (or record it) at natural speed, then ask students the questions below.
Man: So I looked over the numbers you sent, and if I'm reading this right, we're not just behind on the mobile module—we're looking at the whole rollout slipping by at least three weeks.
Woman: That's roughly where we landed too, though I'd push back slightly on 'the whole rollout.' It's really just the two workstreams that depend on the vendor's API documentation, which still hasn't come through.
Man: Right, but those two happen to be on the critical path, so functionally it amounts to the same thing, doesn't it?
Woman: Fair point. What I'm proposing is that we pull a couple of developers off the reporting dashboard—since that's not due until phase two anyway—and have them shore up the integration work in the meantime.
Man: I can live with that, provided we flag it to the client before they notice the dashboard's gone quiet. The last thing we need is another surprise landing on their desk.
Woman: Agreed. I'll draft the status update this afternoon and loop in the account lead before it goes out.