--- description: Risk Register creation โ€” identifikasi, scoring, dan mitigasi risiko proyek dengan probability ร— impact matrix --- # /risk_register - Risk Planning Workflow **Sumber:** TOPIC_004 > 05_project_blueprint.md (ยง5.7 Risk Assessment) --- ## ๐Ÿ“‹ Kapan Menggunakan Workflow Ini - Bagian dari **Project Charter** creation - Saat **planning phase** sebelum development - Untuk **proactive risk management** - Saat muncul **new risks** selama proyek --- ## ๐ŸŽฏ Risk Categories ``` +-----------------------------------------------------------------+ | PROJECT RISK CATEGORIES | +-----------------------------------------------------------------| | | | TECHNICAL RISKS | | โ€ข New/unfamiliar technology | | โ€ข Integration complexity | | โ€ข Performance issues | | โ€ข Security vulnerabilities | | | | RESOURCE RISKS | | โ€ข Key team member availability | | โ€ข Skill gaps | | โ€ข Contractor/vendor reliability | | | | SCHEDULE RISKS | | โ€ข Unrealistic deadlines | | โ€ข Dependencies on external parties | | โ€ข Scope creep | | | | BUDGET RISKS | | โ€ข Underestimated costs | | โ€ข Currency fluctuation | | โ€ข Unexpected expenses | | | | EXTERNAL RISKS | | โ€ข Regulatory changes | | โ€ข Market changes | | โ€ข Third-party service outages | | | +-----------------------------------------------------------------+ ``` --- ## ๐Ÿ› ๏ธ STEP-BY-STEP WORKFLOW ### STEP 1: Brainstorm Risks (15 min) **Per category, list potential risks:** **Technical:** - R1: \_\_\_ - R2: \_\_\_ **Resource:** - R3: \_\_\_ - R4: \_\_\_ **Schedule:** - R5: \_\_\_ **Budget:** - R6: \_\_\_ **External:** - R7: \_\_\_ --- ### STEP 2: Score Each Risk (10 min) **Scoring Matrix:** | | Low Impact (1) | Medium Impact (2) | High Impact (3) | | -------------------------- | -------------- | ----------------- | --------------- | | **High Probability (3)** | 3 | 6 | 9 (Critical) | | **Medium Probability (2)** | 2 | 4 | 6 | | **Low Probability (1)** | 1 | 2 | 3 | **Score = Probability ร— Impact** | Score | Priority | | ----- | ------------------------------ | | 7-9 | ๐Ÿ”ด Critical โ€” Immediate action | | 4-6 | ๐ŸŸก Medium โ€” Plan mitigation | | 1-3 | ๐ŸŸข Low โ€” Monitor | --- ### STEP 3: Define Mitigation (15 min) **For each risk, define:** - **Mitigation Strategy** โ€” How to reduce probability or impact - **Owner** โ€” Who is responsible for monitoring - **Trigger** โ€” What indicates this risk is materializing --- ### STEP 4: Assign Owners (5 min) **Each risk needs:** - [ ] Clear owner assigned - [ ] Owner aware of responsibility - [ ] Review schedule defined --- ## ๐Ÿ“‹ RISK REGISTER TEMPLATE ```markdown ## PROJECT RISK REGISTER ### Project: \***\*\_\_\*\*** ### Date: \***\*\_\_\*\*** | ID | Risk Description | Category | Probability | Impact | Score | Mitigation Strategy | Owner | Status | | --- | ----------------------------- | --------- | ----------- | ------ | ----- | -------------------------------- | -------- | ------ | | R1 | New technology learning curve | Technical | M | M | 4 | Training, POC first | Dev Lead | Open | | R2 | Key developer leaves | Resource | L | H | 3 | Documentation, knowledge sharing | PM | Open | | R3 | Third-party API changes | External | M | H | 6 | API versioning, fallback plan | Dev Lead | Open | | R4 | | | | | | | | | | R5 | | | | | | | | | **Scoring:** - Probability: H=3, M=2, L=1 - Impact: H=3, M=2, L=1 - Score: Probability ร— Impact (1-9) - Priority: 7-9 Critical, 4-6 Medium, 1-3 Low **Status:** Open | Mitigated | Closed | Materialized ``` --- ## ๐Ÿ’ก Common Software Project Risks | Risk | Category | Typical Mitigation | | ----------------- | --------- | --------------------------------------- | | Scope creep | Schedule | Clear scope document, change process | | Key person leaves | Resource | Documentation, pair programming | | Technology issues | Technical | POC, training, expert consultation | | Budget overrun | Budget | Buffer, regular tracking, early warning | | Vendor failure | External | Backup vendors, SLA contracts | | Security breach | Technical | Security audit, penetration testing | | Integration fails | Technical | Early integration testing, mocks | --- ## ๐Ÿ“ Output File **Setelah workflow selesai, AI WAJIB generate file markdown:** **Path:** `AI-Agent/Output/Planning/[ProjectName]/12_risk_register.md` **Template Output:** ```markdown # [Project Name] - Risk Register **Date:** [YYYY-MM-DD] **Version:** 1.0 **Status:** [Active / Final] --- ## Risk Summary | Priority | Count | | ----------------- | ----- | | ๐Ÿ”ด Critical (7-9) | X | | ๐ŸŸก Medium (4-6) | X | | ๐ŸŸข Low (1-3) | X | | **Total Risks** | **X** | --- ## Risk Register | ID | Risk Description | Category | Prob | Impact | Score | Mitigation | Owner | Status | | --- | ---------------- | --------- | ----- | ------ | ----- | ---------- | ------ | ------ | | R1 | [Description] | Technical | H/M/L | H/M/L | X | [Strategy] | [Name] | Open | | R2 | [Description] | Resource | H/M/L | H/M/L | X | [Strategy] | [Name] | Open | | R3 | [Description] | Schedule | H/M/L | H/M/L | X | [Strategy] | [Name] | Open | | R4 | [Description] | Budget | H/M/L | H/M/L | X | [Strategy] | [Name] | Open | | R5 | [Description] | External | H/M/L | H/M/L | X | [Strategy] | [Name] | Open | --- ## Scoring Guide **Probability:** H=3, M=2, L=1 **Impact:** H=3, M=2, L=1 **Score:** Probability ร— Impact (1-9) | Score | Priority | Action | | ----- | ----------- | ------------------------- | | 7-9 | ๐Ÿ”ด Critical | Immediate action required | | 4-6 | ๐ŸŸก Medium | Plan mitigation | | 1-3 | ๐ŸŸข Low | Monitor | --- ## Top 3 Critical Risks ### R[X]: [Risk Title] - **Score:** X (H ร— H) - **Trigger:** [What indicates this is happening] - **Mitigation:** [Strategy] - **Owner:** [Name] - **Review Date:** [Date] ### R[X]: [Risk Title] - **Score:** X - **Trigger:** [What indicates this is happening] - **Mitigation:** [Strategy] - **Owner:** [Name] ### R[X]: [Risk Title] - **Score:** X - **Trigger:** [What indicates this is happening] - **Mitigation:** [Strategy] - **Owner:** [Name] --- ## Risk Review Schedule Struktur Folder Agent-0 menggunakan struktur folder terorganisir untuk menyimpan semua artefak dan log. Agent-0/ +-- Topic/ # Topik diskusi & eksplorasi | +-- index.md +-- Plan/ # Rencana implementasi | +-- index.md +-- Find/ # Temuan & isu | +-- index.md +-- Knowledge/ # Domain knowledge | +-- index.md | +-- {domain}/ +-- Research/ # Hasil riset mendalam | +-- index.md +-- Log/ +-- aktivitas.md # Log aktivitas harian +-- failures.md # Log kegagalan +-- user_behaviour.md # Preferensi user .agent/ +-- STANDARDS.md # Aturan operasional (wajib baca) +-- workflows/ # 9+ workflow files +-- templates/ # Template artefak scripts/ # Python automation (opsional) +-- analyze_workspace.py +-- auto_index_updater.py +-- document_health_analyzer.py +-- failure_analyzer.py Artefak Agent-0 mengelola beberapa jenis artefak dengan konvensi penamaan yang konsisten. ๐Ÿ’ฌ Topic Topik diskusi, eksplorasi ide, atau riset. Bisa berbentuk simple (1 file) atau expanded (multi-file). TOPIC_NNN_slug.md ๐Ÿ—๏ธ Plan Rencana implementasi dengan task list, timeline, dan kriteria penyelesaian. PLAN_NNN_slug.md ๐Ÿ” Finding Temuan, bug, atau isu yang perlu ditangani. Bisa terhubung ke Topic atau Plan. FIND_NNN_slug.md ๐Ÿ“š Knowledge Fakta, referensi, dan data yang bisa di-retrieve. Diorganisir per domain. K_NNN_slug.md Workflow Workflow adalah prosedur terstruktur yang dipanggil dengan slash command. COMMAND DESKRIPSI /wake_up Ritual awal sesi โ€” load context & briefing /create_topic Buat topik diskusi baru /create_plan Buat rencana implementasi /create_finding Dokumentasikan temuan/isu /deep_research Riset mendalam dengan web search /self_audit Cek kesehatan workspace /log_failure Catat kegagalan untuk pembelajaran /discussion_cycle Diskusi topik terstruktur /create_knowledge Buat entry knowledge base Python Automation - Weekly: Monitor Critical risks - Bi-weekly: Review all open risks - Monthly: Full risk reassessment --- ## Status Legend - **Open** โ€” Risk identified, being monitored - **Mitigated** โ€” Mitigation in place - **Closed** โ€” No longer a risk - **Materialized** โ€” Risk occurred --- ## Next Steps ๐Ÿ”„ **Continue to Final Step:** - [ ] Proceed to `/compile_blueprint` โ€” Compile semua output -> 1 master document โœ… **After Blueprint Complete:** - [ ] Begin project execution - [ ] Schedule first sprint/iteration - [ ] Set up development environment - [ ] Monitor risks weekly ``` --- ## ๐Ÿ“š Referensi - PMBOK, Risk Management Body of Knowledge - TOPIC_004/05_project_blueprint.md (Lines 550-606)