Zum Inhalt springen

Standup und 1:1-Gespraeche

Das Standup ist der taegliche Rhythmus der meisten Remote-Teams. Das Standardformat ist Yesterday/Today/Blockers, jede Person 1-2 Minuten.

Grundgeruest:

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

Beispiele:

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

Vermeiden Sie:

❌ "Yesterday I did some work on the bug" (zu vage)
❌ "I was working on stuff" (voellig nutzlos)

Geruest:

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

Beispiele:

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

Schluesselwoerter:

  • I’m going to / I’ll — Zukunftsplaene
  • then — anschliessend
  • by EOD / by this afternoon — Zeitschaetzung
  • assuming no blockers — Bedingung

Nennen Sie nur Dinge, die Sie wirklich blockieren. Kleinere Probleme sind keine Blocker.

Beispiele:

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

Schluesselausdruecke:

  • I wanted to give you an update on… — Bericht beginnen
  • We’re X% complete — Fortschrittsprozent
  • on track to… — Im Zeitplan
  • ahead of schedule — Vor dem Zeitplan
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?

Schluesselausdruecke:

  • I wanted to discuss… — Hoeflicher Einstieg in sensible Themen
  • We realized… — Neue Information aufgetaucht
  • I’m worried about… — Besorgnis ausdruecken
  • Have we considered… — Loesung vorschlagen
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?
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.

Sie haben eine Idee und moechten sie auf Englisch ausdruecken, sind aber unsicher bei der Formulierung. Nutzen Sie den Express-Modus fuer drei Optionen:

Beispiel: “Diese Aufgabe wurde falsch geschaetzt”

Abschnitt betitelt „Beispiel: “Diese Aufgabe wurde falsch geschaetzt”“
Basic: "The task is harder than we estimated"
Intermediate: "This task is more complex than we initially thought"
Native: "We underestimated the scope. The API integration turned out to be
trickier than we expected."
AusdruckBedeutung
by EOD (end of day)Bis Feierabend
by FridayBis Freitag
in 2 weeksInnerhalb von zwei Wochen
on track to…Im Zeitplan fuer…
ahead of scheduleVor dem Zeitplan
at risk of slippingVerzoegerungsgefahr
We're 20% done
roughly halfway through
almost finished
just getting started
nearly there
FehlerBessere 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”
MONTAG
Yesterday: (Wochenende / Freitagsarbeit)
Today: Starting on feature X
Blockers: None
DIENSTAG
Yesterday: Made progress on feature X (40% done)
Today: Continuing feature X, pair with Bob
Blockers: Waiting for design review
MITTWOCH
Yesterday: Feature X is 70% done
Today: Finishing feature X, writing tests
Blockers: None
DONNERSTAG
Yesterday: Completed feature X, PR up for review
Today: Addressing feedback, investigating bug Y
Blockers: None
FREITAG
Yesterday: Fixed bug Y, merged feature X
Today: Code cleanup, prepare for next sprint
Blockers: None

So wissen Sie jeden Tag, was Sie sagen muessen, und wirken organisiert und professionell.