Reuniones diarias y comunicacion 1:1

Las tres partes de una reunion diaria (Standup)

La reunion diaria es el ritmo cotidiano de la mayoria de los equipos remotos. El formato estandar es Yesterday/Today/Blockers, cada persona de 1 a 2 minutos.

Yesterday (que hice ayer)

Marco basico:

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

Ejemplos:

"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."

"I paired with Bob on the API refactoring and got the first three
   endpoints converted to the new schema."

No diga:

"Yesterday I did some work on the bug"  (demasiado vago)
"I was working on stuff"  (completamente inutil)

Today (que voy a hacer hoy)

Marco:

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

Ejemplos:

"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."

"I'm investigating the memory leak in the background worker.
   If I find it, I'll have a fix by EOD."

Palabras clave:

I’m going to / I’ll — Planes futuros
then — A continuacion
by EOD / by this afternoon — Estimacion de tiempo
assuming no blockers — Condicion (si no hay problemas)

Blockers (hay algo que nos bloquea?)

Solo mencione lo que realmente le bloquea. Los problemas menores no cuentan como blocker.

Indicadores de un Blocker:

No puede continuar trabajando (esta esperando a alguien o alguna decision)
Necesita ayuda para resolver un problema tecnico
Un proceso esta atascado (por ejemplo, fallo en el despliegue)

Ejemplos:

"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?"

"QA found a critical bug in staging. We need to decide if we rollback
   or hotfix."

No es un Blocker:

"I'm not sure about the design decision for X"  (es una pregunta, no un blocker)
"The timezone handling is complex"  (dificil no es lo mismo que bloqueado)

Escenarios de reunion uno a uno (1:1)

La reunion 1:1 es su discusion privada con su gerente (o colega). Generalmente se usa para reportar progreso, discutir dificultades, buscar retroalimentacion y solicitar recursos.

Escenario 1: Reportar progreso

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.

Expresiones clave:

I wanted to give you an update on… — Iniciar el reporte
We’re X% complete — Porcentaje de progreso
on track to… — En camino de completar a tiempo
ahead of schedule — Adelantado al cronograma

Escenario 2: Plantear dificultades

Encuentra dificultades en el proyecto, no son problemas tecnicos sino de proceso, recursos u otros obstaculos.

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?

Expresiones clave:

I wanted to discuss… — Iniciar un tema delicado con cortesia
We realized… — Nueva informacion que surgio
I’m worried about… — Expresar preocupacion
Have we considered… — Sugerir una solucion

Escenario 3: Solicitar recursos o ayuda

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? Or would I have more time if we pushed back
the deadline by two weeks?

Expresiones clave:

I need your help on… — Solicitud directa
Could we…? — Sugerencia cortez
Would I have more time if…? — Preguntar sobre alternativas

Escenario 4: Dar retroalimentacion (cuando usted es el senior)

Quiere dar retroalimentacion a su gerente o colega de manera amigable y constructiva.

I wanted to share some feedback on the last standup. I noticed
the discussion on technical details went pretty long. Maybe we
could move those to a separate meeting, and keep standup focused
on blockers and progress? Just a thought.

Expresiones clave:

I wanted to share feedback on… — Iniciar
I noticed… — Describir la observacion
Maybe we could… — Sugerencia
Just a thought — Expresion suave (no es una orden)

Modo Express en reuniones

Tiene una idea y quiere expresarla en ingles, pero no esta seguro de la fraseologia. Use el modo Express para obtener tres opciones rapidamente:

Ejemplo: Quiere decir “No estimamos bien esta tarea”

Input: "No estimamos bien esta tarea, es mucho mas dificil de lo que pensabamos"

Basic (Direct):
  "The task is harder than we estimated"

Intermediate (Natural):
  "This task is more complex than we initially thought"

Native (Idiomatic):
  "We underestimated the scope. The API integration turned out to be
   trickier than we expected."
  Tip: Use "underestimate" en lugar de "didn't estimate well", mas profesional

En la reunion 1:1 use la version “Native”:

I wanted to give you an update on the payment integration.
We underestimated the scope. The API integration turned out to be
trickier than expected. I'm thinking we need another week.

Expresiones comunes para temas de 1:1

Guarde estas expresiones en la etiqueta standup o 1:1 de su cuaderno de palabras:

Relacionadas con progreso

on track to finish...
ahead of schedule
we underestimated...
scope creep
I'm 80% done with...
blocked by...

Solicitudes/sugerencias

Could we...?
Would it be possible to...?
Have you considered...?
I'd like to propose...
What if we...?

Dificultades/preocupaciones

I'm worried about...
I'm concerned that...
We might run into...
There's a risk that...
I need help with...

Retroalimentacion positiva

I really appreciate...
Great job on...
This went better than expected
I'm impressed by...

Expresiones de tiempo y progreso

Estimar tiempo de finalizacion

Expresion	Significado
by EOD (end of day)	Antes del final del dia
by Friday	Para este viernes
by next Tuesday	Para el proximo martes
in 2 weeks	En dos semanas
mid-April	A mediados de abril
on track to…	En camino de completar a tiempo
ahead of schedule	Adelantado
at risk of slipping	En riesgo de retrasarse

Porcentaje de progreso

We're 20% done
40% complete
roughly halfway through
almost finished
just getting started
nearly there

Errores comunes en la reunion diaria

Interferencia comun de hablantes de espanol

Error	Mejor version
”Yesterday I was working on the bug"	"Yesterday I fixed the bug"
"I did something on the API"	"I completed the API refactoring"
"I will do the task"	"I’m going to finish the task by Friday"
"There is a problem"	"We’re blocked on the API credentials"
"Waiting for a person"	"I’m waiting for Bob’s review” (especifique)

Referencia rapida: Marco semanal para reuniones diarias

Si necesita preparar reuniones diarias de toda la semana, guarde esta plantilla:

LUNES
Yesterday: (fin de semana nada / trabajo del viernes)
Today: Starting on feature X
Blockers: None

MARTES
Yesterday: Made progress on feature X (40% done)
Today: Continuing feature X, pair with Bob
Blockers: Waiting for design review

MIERCOLES
Yesterday: Feature X is 70% done
Today: Finishing feature X, writing tests
Blockers: None

JUEVES
Yesterday: Completed feature X, PR up for review
Today: Addressing feedback, investigating bug Y
Blockers: None

VIERNES
Yesterday: Fixed bug Y, merged feature X
Today: Code cleanup, prepare for next sprint
Blockers: None

Asi sabe que decir cada dia, luciendo organizado y profesional.