Daily e Reunioes 1:1

As Tres Partes da Daily (Standup)

A daily e o ritmo diario da maioria das equipes remotas. O formato padrao e Yesterday/Today/Blockers, 1~2 minutos por pessoa.

Yesterday (O que fiz ontem)

Framework basico:

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

Exemplos:

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

Nao diga:

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

Today (O que vou fazer hoje)

Framework:

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

Exemplos:

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

Palavras-chave:

I’m going to / I’ll — Planos futuros
then — Em seguida
by EOD / by this afternoon — Estimativa de tempo
assuming no blockers — Condicao (se nao houver problemas)

Blockers (Algo esta nos impedindo?)

Mencione apenas o que realmente esta bloqueando voce. Problemas pequenos nao sao blockers.

Sinais de Blocker:

Voce nao consegue continuar trabalhando (esperando alguem ou uma decisao)
Precisa de ajuda para resolver um problema tecnico
O processo esta travado (por exemplo, deploy falhou)

Exemplos:

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

Nao e Blocker:

"I'm not sure about the design decision for X"  (isso e uma questao, nao um blocker)
"The timezone handling is complex"  (dificil nao e o mesmo que travado)

Cenarios de Reuniao 1:1

1:1 e uma discussao privada com seu gerente (ou colega). Geralmente usada para reportar progresso, discutir dificuldades, buscar feedback e solicitar recursos.

Cenario 1: Reportar progresso

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.

Expressoes-chave:

I wanted to give you an update on… — Iniciar o relatorio
We’re X% complete — Percentual de progresso
on track to… — No caminho para concluir no prazo
ahead of schedule — Adiantado

Cenario 2: Apresentar uma dificuldade

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?

Expressoes-chave:

I wanted to discuss… — Iniciar tema delicado educadamente
We realized… — Nova informacao surgiu
I’m worried about… — Expressar preocupacao
Have we considered… — Sugerir solucao

Cenario 3: Solicitar recursos ou ajuda

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?

Cenario 4: Dar feedback (quando voce e senior)

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.

Modo Express em Reunioes

Voce tem uma ideia e quer expressar em ingles, mas nao tem certeza da formulacao. Use o Modo Express para obter tres opcoes rapidamente:

Exemplo: Voce quer dizer “Essa tarefa foi mal estimada”

Input: "Essa tarefa foi mal estimada, muito mais dificil do que a gente pensou"

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."
  Dica: Use "underestimate" em vez de "didn't estimate well" -- mais profissional

Expressoes de Tempo e Progresso

Estimativa de conclusao

Expressao	Significado
by EOD (end of day)	Ate o final do dia
by Friday	Ate sexta
by next Tuesday	Ate terca que vem
in 2 weeks	Em duas semanas
mid-April	Meados de abril
on track to…	No caminho para…
ahead of schedule	Adiantado
at risk of slipping	Com risco de atraso

Percentual de progresso

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

Erros Comuns na Daily

Interferencia comum de falantes de portugues

Erro	Versao melhor
”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” (seja especifico)

Referencia Rapida: Framework de Daily para a Semana

SEGUNDA
Yesterday: (fim de semana / trabalho de sexta)
Today: Starting on feature X
Blockers: None

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

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

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

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

Assim voce sabe o que dizer todo dia, parecendo organizado e profissional.