CDP H2 2026 Roadmap
Delivery / Program Management — team-level rollup across the team's initiatives.
Rolling roadmap — updated as initiative timelines are confirmed.
Portfolio
| Initiative | Target quarter | Health | DRI | Implementors | QA | Timeline |
|---|---|---|---|---|---|---|
| Mention User in CDP Notes | 2026-Q3 | At Risk | Zhelia Alifa | Berlianto, Jovi, Alfi | Hendry (primary), Izzul (backup) | timeline |
| Customer Segmentation | 2026-Q3 | At Risk | Zhelia Alifa | Julio Jeffer, Azani, DATA Team (ext) | Hendry (primary), Izzul (backup) | timeline |
| Team Owner Field & Team Permission | 2026-Q3 | At Risk | Zhelia Alifa | Ghozi, Azani, Alfi | Hendry (primary), Izzul (backup) | timeline |
| Legacy Migration: CRM Notes → CDP | 2026-Q3 | At Risk | Zhelia Alifa | Berlianto, DATA Team (ext) | Hendry (primary), Izzul (backup) | timeline |
| Legacy Migration: CRM Activity Logs → CDP | 2026-Q3 | At Risk | Zhelia Alifa | Jeffer, DATA Team (ext), TBD (FE) | Hendry (primary), Izzul (backup) | timeline |
| Export Customer Data with Layout | 2026-Q3 | Backlog | Zhelia Alifa | Ghozi, Jovi, Alfi | Hendry (primary), Izzul (backup) | timeline |
| Create Ticket & Auto-Associate from CDP (Cross-Platform) | 2026-Q3 | At Risk | Zhelia Alifa | Jovi, Alfi, TBD (BE, conditional) | Hendry (primary), Izzul (backup) | timeline |
| Customer Event-Based Engine (CEBE) | 2026-Q3 | Backlog | Zhelia Alifa | Julio Jeffer (BE), DATA Team (ext), TBD (Infra) | Hendry (primary), Izzul (backup) | timeline |
| Multi-BSUIDs (CDP × CRM) | 2026-Q2 | — | TBD | TBD (Backend) | Hendry (primary), Izzul (backup) | — |
Multi-BSUIDs (CDP × CRM) is listed for completeness but its
target_quarter: 2026-Q2is now past and it has nodelivery/timeline.md— DRI/PM to decide whether it shipped, slipped to Q3, or closed, then set its health, DRI and timeline (or drop the row if closed). It is intentionally left ranked last (P9) on the Priority table below pending that decision.
Priority
| Priority | Initiative | Depends on | Note |
|---|---|---|---|
| P1 | Mention User in CDP Notes | — | Notes feature readiness — commitment 2026-07-14 (revenue) |
| P2 | Customer Segmentation | — | Commitment 2026-07-21 (revenue) — scoped in initiative folder; FE/QA sized (4.5), BE effort still TBD |
| P3 | Team Owner Field & Team Permission | — | Commitment 2026-08-18 (revenue) |
| P4 | Legacy Migration: CRM Notes → CDP | P1 — Mention User in CDP Notes | Commitment 2026-08-04 (revenue) — blocked until P1 ships |
| P5 | Legacy Migration: CRM Activity Logs → CDP | — | Commitment 2026-08-04 (revenue) |
| P6 | Export Customer Data with Layout | — | |
| P7 | Create Ticket & Auto-Associate from CDP (Cross-Platform) | — | |
| P8 | Customer Event-Based Engine (CEBE) | — | |
| P9 | Multi-BSUIDs (CDP × CRM) | — | ⚠️ Past-quarter (2026-Q2), no timeline — pending shipped/slipped/closed decision; drop or re-rank once decided |
Sequencing policy
Planning rule for 2026-Q3 delivery:
- Sequence development and delivery by priority order, hard commitment dates, and dependencies. A lower-priority initiative may move earlier only when a hard date or dependency requires it, or when doing so does not delay higher-priority / deadline-bound work.
- When an engineer is assigned to multiple initiatives, their work queue follows the same rule: priority + hard date + dependency order first.
- Engineers should not be idle. If their current top-priority work is blocked or waiting on another role, they should pull the next eligible initiative that does not delay rule 1.
- CDP QA defaults to Hendry. Izzul is a backup only when Hendry's timeline clashes or the team needs extra QA support; do not pre-allocate Izzul to CDP unless that clash exists.
Implications from the current staffing:
- Mention User in CDP Notes (P1) gets first claim on Berlianto, Jovi, and QA capacity.
- Legacy Migration: CRM Notes → CDP (P4) cannot start until P1 ships, regardless of its 2026-08-04 revenue commitment.
- Export Customer Data with Layout (P6) may start only where it uses idle capacity without delaying P1-P5 or hard-deadline work. Ghozi's Export backend work must yield to Team Owner Field & Team Permission (P3) once P3 effort is confirmed; Jovi can pull Export work after P1 frontend work is no longer the bottleneck.
- Customer Segmentation (P2), Team Owner Field & Team Permission (P3), and both migrations (P4/P5) still need effort inputs before the policy can produce dated portfolio forecasts.
- QA capacity is assigned to Hendry first; Izzul remains an escalation/backup lane because his capacity is distributed across multiple teams.
- Azani (FE) queue order did not match priority + hard-date sequencing — flagged and reordered
in the render, still needs real-world confirmation. Azani is on both Customer Segmentation
(P2, 3 FE days, commitment 2026-07-21) and Team Owner Field & Team Permission (P3, 10 FE days,
commitment 2026-08-18).
readiness.htmlhad Team Owner FE first (~Jul 1–14) with Segmentation FE queued after it, with no dependency or capacity reason found for that order (Azani is atload 0.25, well under capacity). The render (2026-07-01 correction) now draws Segmentation FE first (~Jul 1–5) and Team Owner FE second (~Jul 6–19), matching rule 2 — but this is the policy-correct order, not a confirmed fact about Azani's actual queue; someone still needs to check with Azani/DRI that this is (or becomes) the real sequence. It also has one cascading effect: Team Owner FE finishing ~5 days later than before may push back Alfi's Team Owner Mobile start, currently modeled~Jul 15on the assumption FE finishedJul 14(Mobile chunk 10 depends on FE chunks 8-9 per the timeline critical path) — worth re-checking given Alfi is already the most over-committed resource on the team (see Mobile over-commitment risk below). See Program-level risks below.
Portfolio progress & forecast
| Initiative | % done | Effort (total man-days) | p85 forecast | Confidence |
|---|---|---|---|---|
| Mention User in CDP Notes | 0% | 34 | 2026-08-19 | medium |
| Customer Segmentation | 0% | TBD (BE 4, FE 3, QA 1.5 = 8.5; Data/Design pending) | — | medium |
| Team Owner Field & Team Permission | 0% | TBD (BE 10, FE 10, Mobile 10 = 30; Design/QA pending) | — | medium |
| Legacy Migration: CRM Notes → CDP | 0% | — | — | — |
| Legacy Migration: CRM Activity Logs → CDP | 0% | TBD (BE 17, FE 1, QA 6.5 = 24.5 CDP-side; DATA Team pending) | withheld — CRM Stage-0 DSN/query-plan gate | medium |
| Export Customer Data with Layout | 0% | 32.5 | 2026-09-19 | medium |
| Create Ticket & Auto-Associate from CDP (Cross-Platform) | 0% | TBD (FE 3, Mobile 10, QA 1.5 = 14.5 known; BE/Design pending) | — | medium |
| Customer Event-Based Engine (CEBE) | 0% | TBD (BE 15 = 15 known so far; Data/Infra pending) | — | — |
Effort for Mention User in CDP Notes is BE/QA from its RFC task-breakdown artifact
(generated: 2026-06-24), a now-confirmed Mobile estimate from Alfi (10 man-days = 2
man-weeks) that overrides the earlier verify-only 0, and FE now confirmed by Jovi at 9.5
man-days (was 6, the task-breakdown estimate) — total 34 (was 30.5). The mobile ticket is 12
SP including a +2 SP bugfix placeholder carried from this quarter's note-cdp init that is likely
not picked up this quarter (testing slips to next Q); that placeholder is excluded from the firm
10-day capture. The +3.5 FE days push the forecast to p50 2026-08-10 / p85 2026-08-19 (was
08-05/08-14), widening the already-flagged miss against the 2026-07-14 commitment to ~4 weeks —
now tracked as a Program-level risk below. For Export Customer Data with Layout the backend
(15 man-days) is confirmed by Ghozi (3 man-weeks, incl. 1 man-week buffer), overriding the
task-breakdown BE figure; FE is now confirmed by Jovi at 7.5 (matching the 2026-06-30 v2.6
breakdown sync; QA 3.5→5 remains breakdown-sourced) and Mobile is confirmed by Alfi at 5 man-days
(1 man-week) — total 32.5 (was 27); p85 forecast pushed ~1 week to 2026-09-19 (was 09-11) on
the added FE scope. For Team Owner Field & Team Permission the backend (10 man-days =
2 man-weeks, incl. 1 man-week buffer) is confirmed by Ghozi, and Frontend (Azani, 10 man-days = 2
man-weeks) and Mobile (Alfi, 10 man-days = 2 man-weeks) are now confirmed; its Design/QA man-days
are still pending, so its total stays TBD (BE 10 + FE 10 + Mobile 10 = 30 so far). Legacy
Migration: CRM Activity Logs → CDP now has a full breakdown-sourced estimate (BE 17 / FE 1 / QA
6.5 = 24.5, updated 2026-07-01 with 2 new chunks) — its BE 17 is now Jeffer-confirmed same-day,
resolving the earlier P2→P5 sequencing risk (Customer Segmentation's BE is also now sized, at just 4
days, so it clears well ahead of P5 in Jeffer's queue). Its forecast stays withheld for a
different reason: the CRM-owned Stage-0 DSN-access/query-plan go/no-go (external dependency) is
still outstanding against the 2026-08-04 commitment (see Program-level risks). Create Ticket & Auto-Associate's
web track has a partial breakdown (FE 3 / QA 1.5 = 4.5, confirmed by Jovi) but only Task 1 (FE 1.5
/ QA 0.5 = 2.0) is unblocked today — Tasks 2-3 wait on CRM's 2026-07-04 decisions. Mobile is now
confirmed by Alfi at 10 man-days (12 SP ≈ 2 man-weeks) — known total is now FE 3 + Mobile 10 + QA
1.5 = 14.5; BE (conditional, OQ-6) and Design stay TBD, so the initiative total stays TBD. This
Mobile confirmation is also what tips Alfi's cross-initiative load decisively over capacity — see
Capacity summary and Program-level risks below. Customer Segmentation now has FE and QA sized
from its FE task-breakdown (Tasks 2.1-2.3, generated 2026-06-30: FE 3 / QA 1.5), and BE is
Jeffer-confirmed at 4 (0 — Basic Attributes done in Q2 — + 4 buffer bugfixing) — 8.5 known so
far; Data/Design remain unscoped, so effort_total_days and the forecast stay TBD. Customer
Event-Based Engine (CEBE) gets its first sizing: BE is Jeffer-confirmed at 15 (5 RFC &
standardized design + 5 CTWA+Broadcast segment CDP + 5 CDP customer change & segments event,
2026-07-01); Data and Infra remain unscoped and the initiative has no RFC yet, so effort_total_days
and the forecast stay TBD — see the 2026-07-01 readiness assessment (Do not commit until the RFC
lands). Remaining initiatives stay TBD until their DRIs confirm per-discipline man-days.
QA Lanes
| Initiative | Lane | Basis | As of |
|---|---|---|---|
| Mention User in CDP Notes | B | out-of-reach: Mobile; notification delivery needs manual verification | 2026-06-29 |
| Customer Segmentation | C | transition: CRUD automatable; data-ingestion checks keep a manual gate | 2026-06-29 |
| Team Owner Field & Team Permission | B | security/isolation + migration before/after crosscheck | 2026-06-29 |
| Legacy Migration: CRM Notes → CDP | B | migration: before/after data crosscheck needs manual QA | 2026-06-29 |
| Legacy Migration: CRM Activity Logs → CDP | B | migration: before/after data crosscheck needs manual QA | 2026-06-29 |
| Export Customer Data with Layout | B | out-of-reach: Mobile; email crosschecking/operations | 2026-06-29 |
| Create Ticket & Auto-Associate from CDP (Cross-Platform) | C | transition: strongest Lane-A candidate; cross-platform incl. Mobile, awaiting E2E | 2026-06-29 |
| Customer Event-Based Engine (CEBE) | B | Q3 scope is research/assessment/analysis; real-time downstream | 2026-06-29 |
| Multi-BSUIDs (CDP × CRM) | B | security/isolation: multi-org BSUID scoping | 2026-06-29 |
Lane A: 0 of 9 · Lane C: 2 of 9 · Lane B: 7 of 9 (target 20–50% in Lane A). Lane C (Customer Segmentation, Create Ticket) is the transition lane — QA initiates the full E2E suite and Eng contributes; each graduates to Lane A once the entry bar (100% E2E, spec-mapped) is met. Create Ticket is the strongest Lane-A candidate.
Note: Multi-BSUIDs (CDP × CRM) is now on the Portfolio and Priority (P9) tables above, flagged for a shipped/slipped/closed decision.
Capacity summary
See capacity.md for the full per-implementor table.
- BE/FE/QA available eng-days are set for 2026-Q3 in
capacity.md: BE Ghozi/Berlianto/Julio Jeffer each 65, FE Jovi/Azani each 65, QA Hendry 65, QA Izzul 15 backup (13 man-weeks × 5). - RFC-backed committed-days now exist for Mention User in CDP Notes (FE now Jovi-confirmed at 9.5, was 6), Export Customer Data with Layout (FE Jovi-confirmed at 7.5; QA grew to 5 with the v2.6 sync), Legacy Migration: CRM Activity Logs → CDP (new, BE 17 / FE 1 / QA 6.5), and Create Ticket's web track + Mobile (FE 3 / QA 1.5 Jovi-confirmed; Mobile 10 Alfi-confirmed); full load is still not computable until the remaining initiative estimates are confirmed.
- Mobile (Alfi) is now confirmed over-committed — no longer a "before create-ticket" caveat
(timeline-mapper 2026-07-01). With Alfi's Create-Ticket estimate now confirmed at 10 days (12
SP ≈ 2 man-weeks), his fully-known committed load is 35 days (Mention User 10, Team Owner
Field & Team Permission 10, Export Customer Data 5, Create Ticket 10) against 6 man-weeks
available (30 days × 0.8 = 24 effective) → load 1.46,
overby 11 days. Per-initiative verdict, updated: the three deadline-sequenced lanes — Mention User (P1, 07-14, 10d), Team Owner Field (P3, 08-18, 10d), Export (P6, no date, 5d) — already sum to 25 days, exceeding Alfi's 24 effective days before Create Ticket is even added. Create-Ticket from CDP (P7) Mobile has no room left in Q3: it must be deferred to next quarter, or CDP needs materially more than Alfi's current 6 man-weeks of allocated capacity (roughly 8–9 more effective days). This is escalated as a Program-level risk below. Frontend (Jovi) now carries 20 confirmed days across 3 initiatives (under, 0.38 of 52 effective days); Azani carries a confirmed 10 days on Team Owner Field & Team Permission (under, 0.19 of 52 effective days). - Customer Segmentation staffing is now mirrored from its README/timeline; Julio Jeffer and Azani are assigned (Data is owned by the external DATA Team, a cross-squad dependency — not CDP capacity). Azani's FE (3) and Hendry's QA (1.5) are sized from the FE task-breakdown (2026-06-30); Julio Jeffer's BE is now confirmed at 4 days (0 done in Q2 + 4 buffer bugfixing).
- Julio Jeffer (BE) sequencing risk resolved on capacity (Jeffer-confirmed 2026-07-01). He is
the sole named BE for Customer Segmentation (P2, hard date 2026-07-21, now sized at 4 BE
days), Legacy Migration: CRM Activity Logs → CDP (P5, hard date 2026-08-04, confirmed at 17 BE
days), and now CEBE (P8, no hard date, confirmed at 15 BE days, same day) — 36 days combined
against 52 effective days (
load 0.69). The sequencing policy puts P2 first in his queue, P5 second, and CEBE (P8) last; none displace each other at this load. Seecapacity.md## Over/under-commitmentand Program-level risks below. - Remaining initiatives stay
TBDuntil DRIs confirm per-discipline man-days.
Cross-initiative dependencies
- Legacy Migration: CRM Notes → CDP (P4) is blocked by Mention User in CDP Notes (P1) — the migration can only run after the mention feature ships so migrated historical notes render mentions consistently with notes authored post-feature. Tracked in
legacy-migration-crm-notes/README.mdfrontmatterdepends_on: [notes-mention-user].
External & cross-squad dependencies
| Initiative | Blocking dependency | Owner (squad / vendor) | Status |
|---|---|---|---|
| ⏰ Team Owner Field & Team Permission | Teams-for-user(+descendants) API to the §2.4 contract + team radio in permission UI (CHG-001) + legacy→Launchpad team-name crosswalk; must land before flag-ON GA | Launchpad (radio ownership ⚠️ Launchpad vs Admin Portal — confirm) | 🔴 in-repo chunks build now; all gate GA |
| ⏰ Team Owner Field & Team Permission | CDP Mobile module renders Team Owner field + per-note permission flags | Mobile Squad | 🔴 |
| ⏰ Legacy Migration: CRM Notes → CDP | Net-new org-scoped Person-notes extraction endpoint (does NOT exist today; Decision 10 / OQ-7) | Legacy CRM Squad | 🔴 hard prerequisite for any run |
| ⏰ Legacy Migration: CRM Notes → CDP | Per-CID coverage ≥99% (OQ-2); bulk-throughput load test (OQ-7); bluemonday/Infosec (OQ-10); CRM bucket access + PII residency (OQ-9); per-caller audit (OQ-11); CSM per-CID consent | Data Eng / Infosec / CDP Infra / Legacy CRM / Platform / CSM | 🟡 |
| ⏰ Legacy Migration: CRM Activity Logs → CDP | Read-only Postgres DSN scoped to audits+users (Gate A/OQ-1) + EXPLAIN-ANALYZE query plan & index (Gate B/OQ-2) — Stage-0 no-go until both pass | CRM Squad + Platform / CRM DBA | 🔴 |
| ⏰ Legacy Migration: CRM Activity Logs → CDP | USMAN deactivated-user behavior (OQ-9); Figma badge/status frames (OQ-10); Deal join-model class names + won/done/resolved id-sets (OQ-12) | Platform/USMAN / Design / CRM | 🟡 |
| Export Customer Data with Layout | No CDP "Customer Data" quota type + no s2s export-history register path today (OQ-17); gates EXP-S08 only (a Should-Have) — core pipeline unblocked | Billing/IAG + Chat/Omnichannel | 🔴 |
| Export Customer Data with Layout | Notification ingest channel REST vs Kafka (OQ-10); OSS quota headroom (OQ-4); optional mobile tap-through routing (OQ-12) | One Notification / Alibaba OSS / Mobile | 🟡 |
| ⏰ Mention User in CDP Notes | Web Figma frames for the mention typeahead picker + chip (OQ-14) — only build blocker; gates web composer/chip (§4.D chunk 7) | Design System | 🔴 |
| ⏰ Mention User in CDP Notes | Infosec approval of bluemonday allow-list + lock-screen PII egress (OQ-19/REV-14); notification category choice — reuse mention(2) vs CDP-specific (OQ-1) | Infosec / Notification Platform | 🟡 |
| Multi-BSUIDs (CDP × CRM) | crm_phones.bsuid column + immutability guard (TF-3154) + CRM-first deploy order (TF-3154 → TF-3156 → TF-3155 → flag) | CRM (⚠️ TF is CDP's Jira project but RFC names CRM as owner — confirm) | 🔴 |
No timeline yet: Multi-BSUIDs (CDP × CRM) has no
delivery/timeline.md. It is now on the Portfolio table above but still off the Priority table (itstarget_quarter: 2026-Q2is now past) — scaffold a timeline + decide whether it shipped, slipped to Q3, or closed.
Program-level risks
- Mention User in CDP Notes (P1) is at risk against its own 2026-07-14 revenue commitment: its derived forecast (p50 2026-08-10 / p85 2026-08-19, timeline-mapper 2026-07-01, after Jovi's FE confirmation added +3.5 days) lands ~4 weeks after the commitment date. No dependency is blocking it — the gap is pure BE→FE→QA critical-path length against a tight window. This has not previously been called out as a Program-level risk despite the forecast already missing the date; flagging it now since it also directly drives P4's dependency risk below.
- Mobile (Alfi) is over-committed across 4 initiatives by 11 days (
load 1.46) — newly confirmed (timeline-mapper 2026-07-01) once Create-Ticket's Mobile estimate (10 days, 12 SP ≈ 2 man-weeks) landed. Mention User (P1), Team Owner Field & Team Permission (P3), and Export Customer Data (P6) already consume 25 of Alfi's 24 effective days on their own; Create Ticket (P7) Mobile has no room left under the priority + hard-date sequencing policy. Decision needed: defer Create-Ticket Mobile to next quarter, or secure Alfi materially more than his current 6 man-weeks (30 days) of CDP-allocated capacity. Seecapacity.md## Over/under-commitmentfor the full breakdown. - Team Owner Field & Team Permission (P3) is at risk against the 2026-08-18 revenue commitment:
in-repo BE/FE/Mobile chunks are buildable now, but flag-ON GA is gated on Launchpad shipping
the teams-for-user endpoint + Team Only radio, which is not yet committed. Latest status:
2026-06-30. - Legacy Migration: CRM Notes → CDP (P4) is at risk against the 2026-08-04 revenue commitment:
doubly blocked by the P1 Mention User dependency and a net-new org-scoped extraction endpoint
the Legacy CRM Squad has not yet built. The date is unachievable by the P1 dependency alone,
and the gap just widened (timeline-mapper 2026-07-01): P1's forecast finish is now p50
2026-08-10 / p85 2026-08-19 (was 08-05/08-14, before Jovi's +3.5 FE-day confirmation), which lands
further past P4's 08-04 date, so even with a ready endpoint and zero build time P4 cannot meet
08-04 while it waits on P1 — move P4's date or cut P1 to ship its mention schema sooner. Latest
status:
2026-06-30. - Legacy Migration: CRM Activity Logs → CDP (P5) is at risk against the 2026-08-04 revenue
commitment, now on a single front: the migration run is gated on CRM-owned read-only DSN
access + a passing extraction query plan (Stage-0 go/no-go) not yet granted. Its build is sized
at 17 BE days, Jeffer-confirmed 2026-07-01 — and the Jeffer/P2-sequencing risk flagged
earlier that same day is now resolved: Customer Segmentation's BE is also Jeffer-confirmed (4
days), so his combined P2+P5 load (21 days) clears well inside his 52 effective days and P2's
small remaining scope doesn't crowd out P5. The Stage-0 CRM dependency is the sole remaining
blocker against 08-04. Latest status:
2026-07-01. - Customer Segmentation (P2) is at risk against the 2026-07-21 revenue commitment: Basic
Attributes is in progress; its FE task-breakdown is now reconciled into the README (FE 3 / QA
1.5 = 4.5, generated 2026-06-30), and its BE is now Jeffer-confirmed at 4 days (0 — Basic
Attributes build done in Q2 — + 4 buffer bugfixing for remaining hardening); Data/Design remain
unscoped, so
effort_total_daysand the forecast stayTBD. The BE confirmation also resolves the P5 sequencing risk (see above). New (2026-07-01): Azani's FE queue order was backwards in the render, now corrected to policy — but not yet confirmed as the real queue. Azani is booked on both Segmentation FE (P2, 3 days) and Team Owner Field & Team Permission FE (P3, 10 days);readiness.htmlhad Team Owner FE running first with Segmentation FE queued after it, with no dependency forcing that order — left that way, Segmentation's FE work would have started after 2026-07-14 with only ~1 week of runway to the 07-21 commitment (plus Hendry's 1.5 QA days still to run after). The render now draws Segmentation FE first (~Jul 1–5) and Team Owner FE second (~Jul 6–19). This still needs a DRI call to confirm Azani's actual queue matches — and reordering surfaces one knock-on effect: Team Owner FE finishing ~5 days later than the old slot may push Alfi's Team Owner Mobile start (modeled~Jul 15, assumes FE doneJul 14) later, which matters because Alfi is already the team's most over-committed resource (see Mobile over-commitment risk below). Latest status:2026-07-01. - Create Ticket & Auto-Associate from CDP (P7) is at risk on two fronts now: (1) the web
track — CRM embed reuse, Qontak One auth, and CDP embed-source allow-list decisions are due by
2026-07-04; a web RFC + task breakdown exists — Task 1 (gate + shell, 2.0d) is unblocked and can
start immediately behind an OFF flag, Tasks 2-3 (2.5d) remain blocked on the 07-04 CRM decisions
(R1 review: 8.0/10, HOLD partial-proceed); (2) Mobile is no longer merely unblocked — its
effort is now confirmed at 10 days (Alfi, 12 SP ≈ 2 man-weeks, timeline-mapper 2026-07-01), and
that is exactly what tips Alfi over capacity by 11 days across his 4 initiatives (see the
dedicated Mobile-overcommitment risk above). Latest status:
2026-07-01.