> For the complete documentation index, see [llms.txt](https://docs.codeforgod.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codeforgod.org/panduan-pre-hack-dan-hack/waktu-scrum.md).

# Waktu Scrum

Waktu Scrum adalah pertemuan di antara anggota Tim Proyek yang dipimpin oleh PIC, yang dilakukan secara singkat (15 menit atau kurang) untuk saling tukar info antar anggota Tim Proyek untuk menjawab 3 pertanyaan: 1) Apa yang sudah dikerjakan jam-jam sebelum? 2) Apa yang akan dikerjakan jam selanjutnya ini? dan 3) Adakah halangan/rintangan yang menghambat mengerjakan tugas?

### Tujuan scrum adalah untuk:

1. Menyinkronkan pekerjaan seluruh tim.
2. Mengidentifikasi dan menyingkirkan halangan/rintangan dalam proses pengerjaan.
3. Mengadaptasikan rencana tugas dan daftar tugas yang belum dikerjakan.
4. Memantau proses dengan meninjau dan memperbarui to do list yang sudah dikerjakan.
5. Meningkatkan partisipasi dan kolaborasi antar tim.
6. Lakukan Waktu Scrum secara rutin (4-6 kali sehari) agar progres bisa dipantau lebih baik.
7. PIC proyek dan timnya akan melakukan "check status" dengan panitia setiap 3 jam (mulai Sabtu, pkl 9.00 pagi).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.codeforgod.org/panduan-pre-hack-dan-hack/waktu-scrum.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.