Cut the fluff in Scrum meetings: master the English that gets results in standups, retros, and refinements. Learn exactly what to say—and how to say less—so your tech team hears impact, not noise.
Try Amélie free →Non-native speakers often over-explain in standups, hedge in retros, or fill silence with 'um' and 'you know.' For French speakers, directness feels rude, so you add filler words until your idea vanishes. Example: Instead of 'I shipped the login feature,' you hear yourself say 'I kind of finished, like, the login thing, maybe?' In refinement, you soften 'This story needs splitting' to 'I'm not sure, but like, could this be a bit complex?' Your message is buried. This course rewires how you communicate impact in technical meetings—fast, clear, and confident.
Replace 'I kind of,' 'sort of,' 'I guess,' 'maybe,' 'perhaps,' 'I think,' 'I mean,' and 'like' with nothing. Say it straight: 'I fixed the bug' not 'I kind of fixed, like, the bug, maybe.' French speakers add these out of politeness—they don't soften your point in English, they bury it. Record yourself for one day and count the hedges. Delete them all.
Your standup turn should be three sentences max: What you finished. What you're starting. Any blocker. Native speakers say it in 15 seconds. If you're taking 45 seconds, you're over-explaining. Agile meetings scale by compression, not clarity. 'I shipped the payments module. Starting tax calculation today. No blockers.' Done.
In English, 'working on' signals incompleteness, struggle, or future tense. Switch to the simple past for finished work: 'I fixed,' 'I shipped,' 'I deployed,' 'I reviewed.' The tense itself carries confidence. French speakers often stay in 'j'ai travaillé sur' (working on), which translates to 'I was working on'—a habit that makes your past sound unfinished.
In retro, you're asked to improve the sprint. If you soften disagreement ('maybe,' 'perhaps,' 'I'm not sure, but'), it reads as lack of conviction. Say: 'The standups are too long. We should time-box to 10 minutes.' Not: 'I kind of think maybe standups could, like, be a bit shorter?' Retros expect friction. Direct is healthy.
Instead of 'Um, could you maybe explain, like, what you mean by that?' say 'I'm not clear on how that impacts the sprint deadline.' Statements are faster and sound more like you know what's at stake. French learners often turn statements into questions to be polite. In tech, polite kills clarity.
Silence after you speak is not a failure. It's thinking time. French speakers jump in with 'um,' 'uh,' 'you know' to kill silence—a transfer from French conversation norms. Pause for two full seconds after a point. The team will speak. The silence looks confident, not weak.
If explaining something takes more than three sentences in a meeting, pause and reschedule it async. Example: 'The API refactor needs 3 sprints. I'll post the breakdown in Jira, and we'll discuss in standup tomorrow.' Then write it down. Meetings are not the place for details. Agile values speed; detail lives in tickets.
Lead with the outcome, not the journey. Say: 'The CI pipeline is broken because of the database schema change,' then explain why. French storytelling goes beginning-middle-end; English technical communication goes point-proof-point. Agile meetings need the reverse. Outcome first, details second, or skip the details entirely.
No. One or two per meeting is human. Twenty is a speech tic that buries your message. The goal is 'professional pauses,' not silence. Record yourself for a week and count the filler words. Most French learners at B1-C1 average 15-20 per hour-long meeting. Cut to 2-4. That's clarity, not robotics.
Not in tech. French meeting culture values politeness over speed; English tech culture values clarity over courtesy. 'I disagree and here's why' is expected in English retros. 'I kind of think maybe we could possibly...' is seen as indecision. Directness shows confidence and respect for people's time.
Correct it the next time it matters. Say: 'I said we should time-box standups to 10 minutes. That's not working because we're cutting off blockers. Let's try 15.' That's integrity. French speakers fear being wrong in a second language, so they hedge the first time. Pre-hedge means you can't course-correct—you're stuck in wishy-washy land.
Separate certainty from tone. 'I don't have that data yet. I'll get back to you by EOD.' You're uncertain about the answer, but certain about the commitment. That's confidence. Never fake knowledge. French learners often say 'I think...' or 'maybe...' instead of admitting they don't know. In English tech, 'I don't know' is faster and more respected than 'I kind of think perhaps maybe.'
The only AI English coach that catches L1 transfer errors. 19,99€/mo — first session free.
Get started →