Standup et réunions 1:1

Les trois parties du standup

Le standup est le rythme quotidien de la plupart des équipes à distance. Le format standard est Yesterday/Today/Blockers, environ 1-2 minutes par personne.

Yesterday (ce que j’ai fait hier)

Framework de base :

Yesterday, I [action] [what] and [result/impact].

Exemples :

✅ "Yesterday I fixed the auth timeout bug in the login flow.
   Tests are passing and QA is reviewing."

✅ "I completed the database migration for user_profiles and deployed
   to staging for testing."

À éviter :

❌ "Yesterday I did some work on the bug"  (trop vague)
❌ "I was working on stuff"  (complètement inutile)

Today (ce que je ferai aujourd’hui)

Framework :

Today I'm going to [action] [what], and I'll [next step if needed].

Exemples :

✅ "Today I'm finishing the caching layer for search results,
   then I'll review the PR from Sarah."

✅ "I'm writing tests for the new payment endpoint, then we're
   doing a design review at 2pm."

Mots clés :

I’m going to / I’ll — plans futurs
then — ensuite
by EOD / by this afternoon — estimation de temps
assuming no blockers — condition

Blockers (qu’est-ce qui me bloque)

Ne mentionnez que ce qui vous bloque vraiment.

Exemples :

✅ "Blocker: I'm waiting for the Stripe API credentials from finance.
   Can't start the payment integration until then."

✅ "I'm stuck on the database migration. The column rename is causing
   a foreign key constraint error. Anyone familiar with this?"

Scénarios de réunion 1:1

Scénario 1 : Rapport de progression

Hey, I wanted to give you an update on the payment integration.
We're about 60% complete. The core logic is done, but we're still
working on edge cases and error handling. I'm on track to finish
by next Friday.

Expressions clés :

I wanted to give you an update on… — commencer le rapport
We’re X% complete — pourcentage d’avancement
on track to… — dans les délais

Scénario 2 : Signaler une difficulté

I wanted to discuss the timeline on the mobile app redesign.
We realized the scope is bigger than we initially estimated.
I'm worried we'll slip the deadline without more resources.
Have we considered bringing in a contractor?

Expressions clés :

I’m worried about… — exprimer une préoccupation
Have we considered… — suggérer une solution

Scénario 3 : Demander des ressources

I need your help on something. The API integration is proving more
complex than expected. Could we bring in Alice, who has experience
with this library?

Expressions de temps et de progression

Expression	Signification
by EOD (end of day)	avant la fin de la journée
by Friday	d’ici vendredi
on track to…	sur la bonne voie pour
ahead of schedule	en avance
at risk of slipping	risque de glisser

Erreurs courantes

Erreur	Meilleure version
”Yesterday I was working on the bug"	"Yesterday I fixed the bug"
"I did something on the API"	"I completed the API refactoring"
"There is a problem"	"We’re blocked on the API credentials”