Standup dan Komunikasi 1:1
Tiga Bagian Standup
Section titled “Tiga Bagian Standup”Standup adalah ritme harian sebagian besar tim remote. Format standarnya adalah Yesterday/Today/Blockers, masing-masing orang 1~2 menit.
Yesterday (Apa yang saya lakukan kemarin)
Section titled “Yesterday (Apa yang saya lakukan kemarin)”Kerangka paling sederhana:
Yesterday, I [action] [what] and [result/impact].Contoh:
✅ "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."Jangan katakan:
❌ "Yesterday I did some work on the bug" (terlalu samar)❌ "I was working on stuff" (sama sekali tidak berguna)Today (Apa yang akan saya lakukan hari ini)
Section titled “Today (Apa yang akan saya lakukan hari ini)”Kerangka:
Today I'm going to [action] [what], and I'll [next step if needed].Contoh:
✅ "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."Kata kunci:
- I’m going to / I’ll — Rencana masa depan
- then — Selanjutnya
- by EOD / by this afternoon — Estimasi waktu
- assuming no blockers — Kondisi (jika tidak ada masalah)
Blockers (Apa yang menghalangi kita)
Section titled “Blockers (Apa yang menghalangi kita)”Sebutkan hanya hal yang benar-benar menghalangi Anda. Masalah kecil bukan blocker.
Contoh:
✅ "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?"Skenario Rapat Satu-Satu (1:1)
Section titled “Skenario Rapat Satu-Satu (1:1)”1:1 adalah diskusi pribadi Anda dengan manajer (atau rekan kerja). Biasanya digunakan untuk melaporkan progres, membahas kesulitan, meminta umpan balik, meminta sumber daya.
Skenario 1: Melaporkan Progres
Section titled “Skenario 1: Melaporkan Progres”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 stillworking on edge cases and error handling. I'm on track to finishby next Friday.Ekspresi kunci:
- I wanted to give you an update on… — Memulai laporan
- We’re X% complete — Persentase progres
- on track to… — Sesuai jadwal
- ahead of schedule — Lebih cepat dari jadwal
Skenario 2: Mengungkapkan Kesulitan
Section titled “Skenario 2: Mengungkapkan Kesulitan”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?Ekspresi kunci:
- I wanted to discuss… — Memulai topik sensitif dengan sopan
- We realized… — Informasi baru muncul
- I’m worried about… — Mengekspresikan kekhawatiran
- Have we considered… — Menyarankan solusi
Skenario 3: Meminta Sumber Daya atau Bantuan
Section titled “Skenario 3: Meminta Sumber Daya atau Bantuan”I need your help on something. The API integration is proving morecomplex than expected. Could we bring in Alice, who has experiencewith this library? Or would I have more time if we pushed backthe deadline by two weeks?Skenario 4: Memberikan Umpan Balik
Section titled “Skenario 4: Memberikan Umpan Balik”I wanted to share some feedback on the last standup. I noticedthe discussion on technical details went pretty long. Maybe wecould move those to a separate meeting, and keep standup focusedon blockers and progress? Just a thought.Ekspresi Waktu dan Progres
Section titled “Ekspresi Waktu dan Progres”Estimasi Waktu Penyelesaian
Section titled “Estimasi Waktu Penyelesaian”| Ekspresi | Artinya |
|---|---|
| by EOD (end of day) | Sebelum pulang hari ini |
| by Friday | Hari Jumat ini |
| by next Tuesday | Selasa depan |
| in 2 weeks | Dalam dua minggu |
| on track to… | Sesuai jadwal |
| ahead of schedule | Lebih cepat dari jadwal |
| at risk of slipping | Kemungkinan terlambat |
Persentase Progres
Section titled “Persentase Progres”We're 20% done40% completeroughly halfway throughalmost finishedjust getting startednearly thereKesalahan Umum Standup
Section titled “Kesalahan Umum Standup”Interferensi Umum Penutur Non-Inggris
Section titled “Interferensi Umum Penutur Non-Inggris”| Salah | Versi Lebih Baik |
|---|---|
| ”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” (spesifik) |
Referensi Cepat: Kerangka Standup Satu Minggu
Section titled “Referensi Cepat: Kerangka Standup Satu Minggu”MONDAYYesterday: (weekend nothing / Friday work)Today: Starting on feature XBlockers: None
TUESDAYYesterday: Made progress on feature X (40% done)Today: Continuing feature X, pair with BobBlockers: Waiting for design review
WEDNESDAYYesterday: Feature X is 70% doneToday: Finishing feature X, writing testsBlockers: None
THURSDAYYesterday: Completed feature X, PR up for reviewToday: Addressing feedback, investigating bug YBlockers: None
FRIDAYYesterday: Fixed bug Y, merged feature XToday: Code cleanup, prepare for next sprintBlockers: NoneDengan ini Anda tahu apa yang harus dikatakan setiap hari, terlihat terorganisir dan profesional.