Chatbot (BOT Squad) — Capacity Plan 2026-Q3
Delivery / Program Management — squad capacity & load for the quarter.
Capacity
Committed days roll up from each initiative's per-discipline effort (effort_<discipline>_days on
the initiative README) assigned to the named implementor. Load = Committed ÷ (Available × Focus)
→ over (>1.0) · at (≈1.0) · under (<1.0). Focus defaults to 0.8. Available eng-days uses the
standard quarter assumption (13 wks × 5 days = 65 eng-days) — the same convention as the other BOT
squads' capacity plans — until an implementor's actual availability (leave, partial allocation,
other-team split) is confirmed otherwise.
Implementors are recorded on five BOT initiative READMEs (implementors: frontmatter): Autonomous AI
Agent, AI Agent Impact Report, AI Agent Testing, AI Agent Knowledge, and Native Integration. Native
Integration's assignment is the Google Calendar Sprint 1 slice only and is unestimated — shown TBD
in allocations and excluded from the numeric columns below.
effort_* man-days are DRI-confirmed (task-breakdown-derived, no formal implementor sign-off) on four
initiatives: AI Agent Knowledge 13, AI Agent Testing 37.5, AI Agent Impact Report 33.5, and Autonomous
AI Agent 24.5 (Phase 2 only — Phase 1 shipped unsized, Phase 3/4 have no PRD). Per-discipline
splits are canonical on each initiative README; the per-person allocation is the table below.
Chatbot only has two QA people, so product initiatives and the existing Engineering Initiatives bucket default QA to Tito Amanda as primary, Izzul as backup unless a documented clash requires otherwise. Code Readiness is the explicit exception: it is open-contributor and records QA Scope and ownership only on stories where QA actually participates.
QA BAU (automation + deployment support): standing workstream under BOT-4609, not an initiative, not sized — see qa-bau.md.
| Implementor | Available eng-days | Focus factor | Committed days | Allocation (by initiative) | Load |
|---|---|---|---|---|---|
| farras.herdicho (BE) | 65 | 0.8 | 24.5 + TBD | autonomous-ai-agent (BE 8), ai-agent-testing (BE 16.5), code-readiness-q3-2026 (BE, CR-S05 / BOT-4655, BOT-4656) TBD | 0.47 under + TBD |
| samudra.linggar (FE) | 65 | 0.8 | 13.5 + TBD | autonomous-ai-agent (FE 12), ai-agent-knowledge (FE 1.5), ai-agent-testing (FE) TBD, engineering-q3-2026 (FE) TBD (Story A3), code-readiness-q3-2026 (FE, CR-S01 and CR-S04) TBD | 0.26 under + TBD |
| baghiz.firdausa (FE) | 65 | 0.8 | 28.5 + TBD | ai-agent-impact-report (FE 15.5), ai-agent-testing (FE 13), native-integration / Google Calendar (FE TBD), engineering-q3-2026 (FE) TBD (Story A3), code-readiness-q3-2026 (FE, CR-S02 and CR-S04) TBD, qontak-action (FE) TBD | 0.55 under + TBD |
| eko.aprianto (BE) | 65 | 0.8 | 8 + TBD | ai-agent-knowledge (BE 8), qontak-action (BE) TBD, ai-agent-testing (BE) TBD, engineering-q3-2026 (BE) TBD (Stories A5, A6) | 0.15 under + TBD |
| agus.suparman (BE) | 65 | 0.8 | 10 + TBD | ai-agent-impact-report (BE 10), native-integration / Google Calendar (BE TBD), engineering-q3-2026 (BE) TBD, qontak-action (BE) TBD | 0.19 under + TBD |
| tito.amanda (QA) | 65 | 0.8 | 24 + TBD | autonomous-ai-agent (QA 4.5), ai-agent-knowledge (QA 3.5), ai-agent-impact-report (QA 8), ai-agent-testing (QA 8), native-integration / Google Calendar (QA TBD), engineering-q3-2026 (QA) TBD | 0.46 under + TBD |
| izzul (QA, backup) | 65 | 0.8 | 0 | ai-agent-knowledge, ai-agent-impact-report, ai-agent-testing, engineering-q3-2026 (QA) TBD | 0.00 under |
Over/under-commitment
- No one is over capacity on estimated work. Baghiz is the binding constraint at 0.55× (28.5 / 52), Farras next at 0.47×, Tito the busiest QA lane at 0.46×; everyone else ≤0.26×.
- The unsized Google Calendar slice caps the conclusion. Its
TBDload must be confirmed before any of the above is treated as final headroom. - Five of eight active/draft initiatives are unstaffed, so the squad can pull backlog-tier work once the external blockers on the staffed ones clear.
Notes
- Quarter window: 2026-Q3 (Jul–Sep), 65 eng-days assumed per implementor (13 wks × 5 days), 0.8 focus → 52 effective days. Eight active/draft BOT initiatives share the squad; four are now sized and staffed (above), five remain unstaffed/unsized backlog-tier work.
- Code Readiness contributions are unsized and appear as
TBD; its open-contributor policy adds a capacity allocation only when a person is named on a tracker story. - Branch Bot Response — Customer/Contact Field carries no allocation row: shipped 2026-Q2, recorded retroactively 2026-07-27, out of this plan's Q3 scope. See retroactive record.