Projektový manažér v IT drží delivery — kedy, kto, čo blokuje, čo eskalovať. Angličtina pre projektových manažerov nie je to isté ako product manager (scope a priority) ani line manažér (ľudia a 1-on-1). Tu: milestones, dependencies, status a RAID.
Kontext: Angličtina pre IT. Meeting po anglicky. Ako viesť meeting.
Projektový manažér scenáre
<a id="section-0"></a>
| Scenár | Kľúčové frázy |
|---|---|
| Weekly status | Green/amber/red, accomplishments |
| Milestone review | On track / slipped / at risk |
| Dependency | Waiting on X from Y |
| Resource conflict | Need 2 more QA for sprint 3 |
| Steering committee | Decision needed, budget |
| Go-live | Cutover, rollback, hypercare |
Status report — šablóna
<a id="section-1"></a>
Project: ERP Integration Phase 2
Period: Week 12
Overall: 🟡 Amber — timeline at risk
Accomplishments:
- UAT environment ready
- 80% test cases executed
- Training materials draft complete
Planned next week:
- Complete remaining UAT
- Fix P1 defects from backlog
- Stakeholder sign-off session Thursday
Risks / Issues:
- Vendor API documentation still incomplete — impacts integration tests
- Two key testers on leave next week
Decisions needed:
- Approve extension of UAT by 5 business days?
- Confirm hypercare support model for go-live week
Milestones a timeline
<a id="section-2"></a>
- Milestone M3 — data migration — due March 28, currently on track.
- M4 slipped by one week — dependency on legal contract signature.
- Critical path runs through integration testing — any delay there hits go-live.
- We're building float into the plan — 3 days buffer before launch.
Dependencies
<a id="section-3"></a>
- We're dependent on the client's SSO team for test credentials — requested March 1, still pending.
- Upstream: design assets must be frozen before dev sprint 4.
- Downstream: marketing needs final URLs 2 weeks before launch for campaign.
Escalation:
- I've escalated to the client's project sponsor — no response in 5 days.
- This dependency is now a project risk — logged in RAID #R-12.
RAID log — rýchlé frázy
<a id="section-4"></a>
Risk: Vendor may miss SLA on patch — probability medium, impact high.
Assumption: Client IT will provide VPN access by week 2 — if not, onsite work blocked.
Issue: Production-like data not approved for UAT — testing with synthetic data only.
Dependency: Payment gateway certification requires signed paperwork from finance.
Steering committee — opening
<a id="section-5"></a>
- Good morning — agenda today: project health, M3–M4 status, budget variance, and decision on UAT extension.
- Overall we're amber — recoverable, but need your decision on the UAT window.
- Slides and full status report were sent yesterday — happy to dive into any section.
Resource a budget
<a id="section-6"></a>
- We need to add one senior dev for 4 weeks to close the integration gap.
- Budget is 5% under plan YTD — contingency still available.
- Forecast: slight overrun if UAT extends — estimate +15k EUR.
Go-live a cutover
<a id="section-7"></a>
- Go-live date: April 15, 06:00 CET — cutover window 4 hours.
- Rollback criteria: payment failures above 2% for 30 minutes.
- Hypercare: dedicated war room first 48 hours post-launch.
- Communication plan: status page, client email template, internal Slack channel.
Kompletný príklad: weekly call (B2)
<a id="section-8"></a>
Quick status — overall amber. Good news: UAT environment stable, 80% tests done. Challenge: vendor API docs gaps slowed integration tests by three days. Mitigation: daily sync with vendor, internal workaround for two endpoints. Decision: can we extend UAT to April 5? Without it, go-live April 15 is at risk. I'll send RAID update after the call.
E-mail status (krátky)
<a id="section-9"></a>
Hi all,
Week 12 status — Amber
Done: UAT 80%, training draft ready.
Next: close UAT, P1 fixes, sign-off Thu.
Risk: vendor API docs — see RAID R-12.
Action: Please confirm UAT extension by Wed COB.
Full report attached.
Thanks,
Petra
Precvičenie
<a id="section-10"></a>
- Napíš one-page status report — green/amber/red.
- Pridaj 2 risks a 1 decision needed.
- 3-minútový steering opening nahlas.
- Vyskúšaj manager scenár — status update.
Súvisiace články
<a id="section-11"></a>
| Téma | Článok |
|---|---|
| Product manager | Angličtina pre product managerov |
| Manažeri | Angličtina pre manažerov |
| Progress | Progress update po anglicky |
Záver
<a id="section-12"></a>
Angličtina pre projektových manažerov = jasný status, transparentné riziká a konkrétne decisions. Sponsor nečíta 20 strán — číta amber, dôvod a čo má schváliť. Milestones, dependencies a RAID v jednoduchých bullet points šetria calle a eskalácie.