What if I disagree with someone's point?

Acknowledge their view and add yours: "I see it differently. From my experience, [X]." Keep it constructive.

How do I bring up a sensitive issue?

Use "I" language and focus on impact: "I noticed [behavior]. It affected [outcome]. I'd like us to try [suggestion]."

Should I mention individual performance?

Focus on team and process. For individual feedback, use 1-on-1s.

What if I have nothing to add?

You can add to someone else's point: "I agree with that. I'd add that [X]."

How do I suggest an improvement?

Be specific: "I suggest we [action]. That could help with [problem]."

Retrospective

Quick answers

What is a retrospective?: A team meeting to reflect on what went well, what didn't, and what to improve in the next sprint.
When do retros happen?: Typically at the end of each sprint or iteration.
What do you say in a retro?: Share what went well, what didn't, and concrete suggestions for improvement.

What it is

Retros (or retros) are a core agile practice. The team looks back at the last sprint or cycle and discusses: What went well? What didn't? What will we do differently? The focus is on learning and continuous improvement, not blame.

Why it matters

Retros help teams get better over time. Contributing clearly—both positives and improvements—shows you're engaged and thoughtful. Many non-native speakers stay quiet; practice helps you share observations and suggestions confidently.

Instead of → Say

Instead of	Say
It was bad	The deployment process took longer than expected—we had several rollbacks
We should fix it	I suggest we add a pre-deploy checklist to reduce rollbacks
Communication was poor	We could improve by having a dedicated Slack channel for deployment updates
X did a good job	The pairing sessions with Sarah helped unblock the frontend work
We need to do better	Let's aim to reduce cycle time by focusing on smaller PRs next sprint

Example dialogue

Facilitator: What went well this sprint?

You: I thought our pairing on the API migration worked well. We caught a lot of edge cases early.

Facilitator: What didn't go well?

You: The deployment to staging was delayed twice. I think we need a clearer handoff from dev to DevOps.

Facilitator: Any suggestions for next sprint?

You: I'd suggest a short sync before each deployment. Even 15 minutes could help align everyone.

Common mistakes

Staying silent—your perspective matters
Blaming individuals instead of processes
Being vague—"communication" or "process" without examples
Only criticizing—call out wins too
Not following up on action items

Frequently asked questions

What if I disagree with someone's point?: Acknowledge their view and add yours: "I see it differently. From my experience, [X]." Keep it constructive.
How do I bring up a sensitive issue?: Use "I" language and focus on impact: "I noticed [behavior]. It affected [outcome]. I'd like us to try [suggestion]."
Should I mention individual performance?: Focus on team and process. For individual feedback, use 1-on-1s.
What if I have nothing to add?: You can add to someone else's point: "I agree with that. I'd add that [X]."
How do I suggest an improvement?: Be specific: "I suggest we [action]. That could help with [problem]."

Ready to practice?

Start practicing with our available scenarios and get instant feedback.

Start practicing