CDP — 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. Committed-days are TBD
until each initiative's DRI confirms its man-days. RFC task breakdowns currently provide concrete
BE/FE/QA estimates for notes-mention-user; export-customer-data and
team-owner-field-and-team-permission now carry Ghozi-confirmed BE man-days (15 and 10
respectively). Mobile (Alfi) man-days are now estimated for notes-mention-user (10),
team-owner-field-and-team-permission (10), and export-customer-data (5), and Frontend (Azani)
for team-owner-field-and-team-permission (10); other initiatives remain TBD. Customer
Segmentation's FE (3) and QA (1.5) are sized from its FE task-breakdown, and its BE is now
Jeffer-confirmed at 4 (0 Basic Attributes done in Q2 + 4 buffer bugfixing); Data/Design remain
pending. 2026-07-01 refresh (timeline-mapper): export-customer-data's FE/QA breakdown grew with the
v2.6 sync (FE 3.5→7.5, QA 3.5→5); legacy-migration-crm-activity-logs now has a full breakdown-sourced
estimate (BE 17 — Jeffer-confirmed same-day — / FE 1 / QA 6.5; DATA Team days still TBD); and
create-ticket-from-cdp's web track now has a partial breakdown (FE 3 / QA 1.5 — only 2.0 of that
is unblocked today, the rest gated on CRM's 2026-07-04 decisions; BE/Design still TBD); and
customer-segmentation now has an FE task-breakdown-sourced estimate (FE 3 / QA 1.5) — its BE
task breakdown still carries no man-day sizing.
Same-day human confirmation (2026-07-01): Jovi confirmed FE at 7.5 (export-customer-data,
matches breakdown) and 3 (create-ticket-from-cdp web, matches breakdown), and 9.5 for
notes-mention-user (was 6 — a real increase, not just a confirmation). Alfi confirmed Mobile at
10 days (12 SP ≈ 2 man-weeks) for create-ticket-from-cdp — this was the last unknown mobile
figure in his queue and tips him decisively over capacity (see below).
Available eng-days convert the 2026-Q3 capacity input at 1 man-week = 5 eng-days. 2026-Q3 spans
13 calendar weeks, so a full-time engineer has 13 man-weeks available: BE
Ghozi/Berlianto/Julio Jeffer each 13 man-weeks (65 days), FE Jovi/Azani each 13 man-weeks
(65 days), QA Hendry 13 man-weeks (65 days), QA Izzul 3 man-weeks (15 days — a
cross-team partial allocation, not a function of quarter length), and Mobile Alfi 6 man-weeks
(30 days — a cross-team partial allocation for CDP). Focus 0.8 → 52 effective days/quarter
for a full-time engineer (Alfi's 30 days × 0.8 = 24 effective days).
For CDP, QA assignment defaults to Hendry. Izzul's capacity is distributed across multiple teams,
so Izzul is held as backup only when Hendry's timeline clashes or CDP needs extra QA support.
Scheduling follows the roadmap's 2026-Q3 sequencing policy: priority order + hard commitment dates + dependencies determine each engineer's queue, and an engineer pulls the next eligible initiative when their higher-priority work is blocked or waiting on another role. This keeps engineers productive without letting lower-priority work delay higher-priority or deadline-bound work.
| Implementor | Available eng-days | Focus factor | Committed days | Allocation (by initiative) | Load |
|---|---|---|---|---|---|
| Ghozi (BE) | 65 | 0.8 | 25 | export-customer-data (15), team-owner-field-and-team-permission (10) | under (0.48) |
| Jovi (FE) | 65 | 0.8 | 20 | export-customer-data (7.5), notes-mention-user (9.5), create-ticket-from-cdp (3) | under (0.38) |
| Alfi (Mobile) | 30 | 0.8 | 35 | notes-mention-user (10), team-owner-field-and-team-permission (10), export-customer-data (5), create-ticket-from-cdp (10) | over (1.46, 11 days over) |
| Azani (FE) | 65 | 0.8 | 13 | team-owner-field-and-team-permission (10), customer-segmentation (3) | under (0.25) |
| Berlianto (BE) | 65 | 0.8 | 10 + TBD | notes-mention-user (10), legacy-migration-crm-notes (TBD) | TBD |
| Julio Jeffer (BE) | 65 | 0.8 | 36 | legacy-migration-crm-activity-logs (17), customer-segmentation (4), customer-event-based-engine-cebe (15) | under (0.69) |
| Hendry (QA) | 65 | 0.8 | 19 + TBD | notes-mention-user (4.5), export-customer-data (5), legacy-migration-crm-activity-logs (6.5), create-ticket-from-cdp (1.5), customer-segmentation (1.5), remaining initiatives (TBD) | under (0.37 known) |
| Izzul (QA backup) | 15 | 0.8 | 0 unless needed | backup for CDP timeline clashes / extra QA support | under (backup lane) |
| DATA Team (Data — external squad) | — | — | — | customer-segmentation, legacy-migration-crm-notes, legacy-migration-crm-activity-logs, CEBE (cross-squad dependency, not CDP capacity) | cross-squad |
| TBD (Infra) | — | — | — | CEBE | — |
| TBD (BE, conditional) | — | — | — | create-ticket-from-cdp (OQ-6) | — |
| TBD (FE, minor) | — | — | 1 | legacy-migration-crm-activity-logs (1, CALM-S05) | — |
| TBD (BE) | — | — | — | multi-bsuids-cdp-x-crm | — |
Over/under-commitment
- BE/FE/QA available-days are now set from 2026-Q3 man-week capacity. Full load is still not computable for most people because most initiative committed-days remain pending DRI estimates.
- Known committed-days so far: Jovi has 20 FE days (
0.38load against 52 effective days — export-customer-data 7.5 + notes-mention-user 9.5 + create-ticket-from-cdp 3, all now confirmed by Jovi), Berlianto has 10 BE days, Ghozi has 25 BE days (0.48load against 52 effective days — export-customer-data 15 + team-owner-field-and-team-permission 10, both confirmed), Azani has 13 FE days (0.25load — team-owner-field-and-team-permission 10 + customer-segmentation 3, the latter now breakdown-sourced), Julio Jeffer has 36 BE days (0.69load against 52 effective days — legacy-migration-crm-activity-logs 17 + customer-segmentation 4 + customer-event-based-engine-cebe 15, all Jeffer-confirmed), and Hendry has 19 QA days (0.37load against 52 effective days — notes-mention-user 4.5 + export-customer-data 5 + legacy-migration-crm-activity-logs 6.5 + create-ticket-from-cdp 1.5 + customer-segmentation 1.5). Izzul remains backup capacity for timeline clashes. - Julio Jeffer (BE) sequencing risk resolved on capacity (Jeffer-confirmed 2026-07-01). Customer
Segmentation (P2, hard date 2026-07-21) BE is now sized at 4 days (0 — Basic Attributes
build done in Q2 — + 4 buffer bugfixing), and Legacy Migration Activity Logs (P5, hard date
2026-08-04) BE is confirmed at 17 days. Combined 21 days against his 52 effective days
(
load 0.40) — no numeric overload, and P2's small remaining scope clears well ahead of P5 under the sequencing policy. P5's forecast staysTBDfor a different reason now: it is gated on the CRM-owned Stage-0 DSN-access/query-plan go/no-go (external dependency), not on Jeffer's queue. - CEBE (P8) backend now sized — Jeffer-confirmed 2026-07-01 (Slack, 15 days: 5 RFC & standardized
design + 5 CTWA+Broadcast segment CDP + 5 CDP customer change & segments event). Added to his
queue behind P2/P5, this brings his combined load to 36 days / 52 effective (
load 0.69) — still comfortably under capacity, and CEBE is P8 so it doesn't contend with any higher-priority claim on his time. This is only the CDP-owned backend slice: CEBE's Data (Central DB schema, retriever/metrics, backfill) and Infra (streaming/queue, monitoring) tracks remain unsized and Infra has no named owner — and the initiative has no RFC yet, so it is not planning-ready regardless of this capacity fit (seecustomer-event-based-engine-cebe/README.mdand the 2026-07-01 readiness assessment). - Mobile (Alfi) is confirmed over-committed — no longer speculative (timeline-mapper 2026-07-01).
Available 30 days (6 man-weeks, a cross-team partial CDP allocation) × 0.8 = 24 effective days,
against 35 now-fully-known committed days (notes-mention-user 10 + team-owner-field-and-team-permission
10 + export-customer-data 5 + create-ticket-from-cdp 10, Alfi-confirmed 2026-07-01) → load 1.46,
overby 11 days. The notes-mention-user mobile figure already excludes a +2 SP bugfix placeholder likely not picked up this quarter (testing slips to next Q); the create-ticket figure has no such exclusion (12 SP ≈ 2 man-weeks, taken at face value). Per-initiative verdict (timeline-mapper 2026-07-01, updated): the three deadline-sequenced lanes — notes-mention-user (P1, 07-14, 10d), team-owner-field-and-team-permission (P3, 08-18, 10d), export-customer-data (P6, no date, 5d) — already sum to 25 days, i.e. alone they exceed Alfi's 24 effective days (load 1.04) before Create-Ticket is even added. Create-Ticket-from-CDP (P7) Mobile (10d, P7 — CDP's lowest-priority Mobile assignment) has no room left in Q3 under the priority + hard-date + dependency sequencing policy: it must be deferred to next quarter, or Alfi needs materially more than his current 6 man-weeks (30 days) of CDP-allocated capacity — closing the 11-day gap needs roughly 8–9 more effective days, i.e. ~10–11 more raw days of CDP allocation. This is no longer a "tips him past 1.0" caveat — it is an 11-day, ~46%-over-capacity shortfall. - Several roles are still unassigned (marked
TBD (Role)across initiative READMEs and timeline staffing tables). - Data is a separate external squad (DATA Team), not CDP capacity. The Data tracks for Customer Segmentation, both Legacy Migrations, and CEBE depend on the DATA Team cross-squad; that row is listed for allocation visibility only and carries no CDP available/committed/load figures.
Notes
- Quarter window: 2026-Q3 (Jul–Sep). Keep available-days synced from staffing inputs and
committed-days synced from each initiative README as remaining CDP initiatives record
DRI-confirmed
effort_*.