Facilitujesz daily z zespołem rozproszonym po Europie — ale nie wiesz jak poprowadzić retrospektywę po angielsku

Cisza po pytaniu "Let's start the retro — what went well this sprint?" Połowa zespołu jest z Niemiec, product owner z Holandii, a Ty — Scrum Master z Warszawy — szukasz słów, żeby przeprowadzić zespół przez ćwiczenie Start/Stop/Continue w sposób, który faktycznie coś zmieni.

Jeśli jesteś Scrum Masterem, Agile Coachem, RTE (Release Train Engineer) lub Product Ownerem prowadzącym ceremonie, ten artykuł daje Ci język do skutecznej facylitacji — nie tylko poprawnej gramatycznie.

Framework i artefakty — 11 terminów

EN Term	PL	Przykład zdania
sprint	sprint	"We're starting Sprint 23 on Monday — the sprint goal is to complete the payment integration."
product backlog	rejestr produktu	"The product backlog has 147 items — only the top 30 are estimated and ready for planning."
sprint backlog	rejestr sprintu	"Everything in the sprint backlog has a clear owner and an acceptance criterion."
user story	historyjka użytkownika	"This user story doesn't have a clear acceptance criterion — let's refine it before planning."
epic	epik	"The checkout redesign is an epic spanning three sprints."
story points	punkty historyjki	"The team estimated the API integration at 8 story points — the largest item in the sprint."
velocity	prędkość zespołu	"Our average velocity over the last six sprints is 42 points."
burndown chart	wykres spalania	"The burndown chart shows we're behind by 8 points — we need to reassess scope."
definition of done (DoD)	definicja ukończenia	"According to our DoD, every story needs unit tests and a passing CI pipeline before it's done."
definition of ready (DoR)	definicja gotowości	"This story doesn't meet the Definition of Ready — acceptance criteria are missing."
backlog refinement	pielęgnacja backlogu	"Backlog refinement is on Wednesdays — bring your questions and estimation proposals."

Ceremonie i metryki — 11 terminów

EN Term	PL	Przykład zdania
sprint planning	planowanie sprintu	"Sprint planning starts at 9AM — we'll time-box it to two hours for a two-week sprint."
daily standup	codzienny standup	"The daily standup is a 15-minute sync, not a status report — focus on blockers."
sprint review	przegląd sprintu	"The sprint review is for stakeholders to inspect the increment and provide feedback."
sprint retrospective	retrospektywa	"The retrospective is a safe space — what's said in retro stays in retro."
PI planning	planowanie PI (SAFe)	"PI planning brings all Agile teams together for two days to align on the next Program Increment."
cycle time	czas cyklu	"Our average cycle time is 4.2 days — the bottleneck is code review, not development."
lead time	czas realizacji	"Lead time from idea to production is 18 days — we want to get it under 10."
throughput	przepustowość zadań	"Team throughput has been stable at 12 stories per sprint for the last quarter."
cumulative flow diagram	diagram skumulowanego przepływu	"The CFD shows a growing queue in the review column — that's your bottleneck."
team capacity	pojemność zespołu	"Three people are on leave next sprint — team capacity is 60% of normal."
impediment	przeszkoda / bloker	"I've identified an impediment outside the team's control — I'll escalate it today."

Prowadzenie ceremonii po angielsku

a) Daily standup — 8 zwrotów

"Let's start today's standup. Who'd like to go first?"
"Can you keep your update to two minutes, please? We have a full board today."
"Is there anything blocking you that the team can help with?"
"Let's take that offline — it sounds like a conversation for the two of you after standup."
"We're at 15 minutes — let's wrap up. Any last blockers?"
"That sounds like an impediment. I'll follow up with you after the standup to see how I can help remove it."
"Yesterday's items — is everything still on track, or do we need to adjust the sprint backlog?"
"It looks like we have a dependency on the Platform team. I'll reach out to their Scrum Master today."

b) Sprint planning — 6 zwrotów

"Based on our velocity, we can commit to approximately 34 story points this sprint."
"What's the sprint goal? We need one sentence that describes what we want to achieve."
"This story has 8 points — is everyone comfortable with that estimate, or does it need more refinement?"
"We're over capacity. Which items should we move to the next sprint?"
"Does this story meet the Definition of Ready? I'm not seeing clear acceptance criteria."
"Let's time-box the planning session — we have 90 minutes left. Let's focus on the top 10 items."

c) Retrospektywa — 8 zwrotów

"Welcome to the sprint retrospective. This is a safe space — everything said here stays within the team."
"Let's start with 'What went well'. Take 5 minutes to add your sticky notes — one idea per note."
"I'm seeing a theme around communication between the front-end and back-end. Does the team agree?"
"Let's dot-vote on the top three issues to focus on — you each have three votes."
"For each action item, we need a clear owner and a due date. Who can take this one?"
"We raised this same issue in Sprint 20. Let's check — was the action item from last retro completed?"
"Before we close, let's rate the retrospective itself. How useful was this session on a scale of 1 to 5?"
"The action items are noted. I'll add them to the team board and follow up at next week's standup."

d) Eskalacja impedimentów — 4 zwroty

"This is a blocker outside the team's control — I'll escalate it to management today."
"The dependency on the Legal team has been unresolved for two sprints. I need to escalate this to the programme level."
"I've removed the technical blocker. The Ops team has updated the environment configuration."
"This impediment is systemic — I'd like to raise it at the next Scrum of Scrums."

Krótki dialog — Scrum Master facylituje retrospektywę z konfliktem

Scrum Master: "We've identified communication breakdowns as our main theme this sprint. Before we jump to solutions — does everyone feel safe to speak openly here?"

Dev A: "Honestly, I felt like my pull requests weren't being reviewed. Three PRs sat open for four days."

Scrum Master: "Thank you for raising that — that's exactly what retro is for. Dev B, from your side — what was blocking the reviews?"

Dev B: "I didn't know they were urgent. There's no visibility into what's blocking the sprint."

Scrum Master: "So the action item is: add a 'needs review' label to PRs on the sprint critical path. Can you two agree on that process before Monday?"

Both: "Yes."

SAFe i skalowany Agile — 6 terminów

EN Term	PL	Przykład zdania
Agile Release Train (ART)	pociąg wydań Agile	"Our Agile Release Train consists of six Scrum teams and one Platform team."
Program Increment (PI)	przyrost programu	"At the end of each PI we deliver a working system that's been tested and integrated."
Inspect & Adapt	inspekcja i adaptacja	"The Inspect & Adapt workshop is the retrospective at the PI level."
IP Sprint	sprint innowacji i planowania	"The IP Sprint is a buffer for innovation, technical debt and PI Planning preparation."
Release Train Engineer (RTE)	inżynier pociągu wydań	"The RTE is the Scrum Master for the entire Agile Release Train."
System Demo	demo systemowe	"The system demo at the end of each PI shows the integrated increment from all teams."

Najczęstsze błędy Polaków

1. "make a standup" → "run / facilitate a standup". ❌ "I made a standup at 9AM." → ✅ "I ran / facilitated the standup at 9AM."

2. "story" vs "user story". W codziennej komunikacji z teamem story jest akceptowalne. W dokumentacji i onboardingu używaj pełnego user story.

3. "we have impediment" → brakuje przedimka. ❌ "We have impediment." → ✅ "We have an impediment."

4. "the team doesn't have capacity" → nieidiomatyczne. ❌ "The team doesn't have capacity for this." → ✅ "The team is at capacity this sprint." / ✅ "We're over capacity — we need to descope."

5. "retrospective" vs "retro". Retro jest standardowym skrótem w Agile — całkowicie profesjonalny w rozmowie z teamem. Używaj pełnego retrospective w dokumentacji i komunikacji ze stakeholderami spoza IT.

Quick Reference Table

EN Term	PL Tłumaczenie	Kontekst
sprint	sprint	framework
product backlog	rejestr produktu	artefakt
sprint backlog	rejestr sprintu	artefakt
user story	historyjka użytkownika	artefakt
epic	epik	artefakt
story points	punkty historyjki	estymacja
velocity	prędkość zespołu	metryki
burndown chart	wykres spalania	metryki
definition of done	definicja ukończenia	framework
definition of ready	definicja gotowości	framework
backlog refinement	pielęgnacja backlogu	ceremonia
sprint planning	planowanie sprintu	ceremonia
daily standup	codzienny standup	ceremonia
sprint review	przegląd sprintu	ceremonia
sprint retrospective	retrospektywa	ceremonia
PI planning	planowanie PI	SAFe
cycle time	czas cyklu	metryki
lead time	czas realizacji	metryki
throughput	przepustowość zadań	metryki
cumulative flow diagram	diagram skumul. przepływu	metryki
team capacity	pojemność zespołu	planowanie
impediment	przeszkoda / bloker	operacje
Agile Release Train	pociąg wydań Agile	SAFe
Program Increment	przyrost programu	SAFe
Inspect & Adapt	inspekcja i adaptacja	SAFe
IP Sprint	sprint innowacji i planowania	SAFe
Release Train Engineer	inżynier pociągu wydań	SAFe

Podsumowanie

Efektywna facylitacja po angielsku to nie kwestia gramatyki — to znajomość rytmu i języka ceremonii Agile. Kiedy wiesz jak przeprowadzić retrospektywę, eskalować impediment i prowadzić sprint planning z rozproszonym zespołem, Twoja rola Scrum Mastera jest widoczna i wartościowa niezależnie od lokalizacji uczestników.

Więcej kontekstu dla środowisk IT znajdziesz w artykule o angielskim dla analityka biznesowego IT. Jeśli prowadzisz regularne spotkania z zagranicznymi stakeholderami, sprawdź też angielski na spotkaniach biznesowych.

Gotowe fiszki z terminologią Scrum znajdziesz w ścieżce Scrum Master w sekcji IT & Programowanie.

Angielski dla Scrum Mastera — ceremonie Agile i facilitacja po angielsku