Skip to main content

Customer Segmentation — Status 2026-06-26

Delivery / Program Management — periodic status report. health: carries the delivery-health status (backlog / on-track / at-risk / off-track / paused / completed); the doc-lifecycle status: stays in the linter enum (active).

Summary

At risk but active: Jira confirms Basic Attributes work is underway under epic TF-2544, and the roadmap records a 2026-07-21 revenue commitment. The remaining delivery risk is measurement: the Q3 delivery layer still has TBD effort and forecast fields, so repo burnup cannot yet prove whether the commitment is executable.

Highlights

  • Initiative folder, anchor PRD, child PRDs, and delivery timeline are now represented in the Q3 roadmap rollup.
  • Staffing confirmed for Backend (Julio Jeffer), Frontend (Azani), Data (DATA Team — external squad), and QA (Hendry primary, Izzul backup), then mirrored into the initiative README/timeline/roadmap.
  • Jira epic TF-2544 is In Progress; child work shows completed design/planning/backend foundation work and active backend membership/ recalculation work as of 2026-06-27.
  • Rovo found an external Basic Attributes backend RFC submitted 2026-05-19 and related to TF-2544.

Lowlights & blockers

  • Effort man-days pending — owner: DRI; ask: confirm effort_<discipline>_days so total, forecast, and capacity load can be computed. Jira status cannot be converted into man-day burnup without that denominator.
  • The external Basic Attributes RFC is not mirrored into this repo's rfcs/ folder; RFC for Use-Case Activities is still pending.

Risk & dependency changes

  • Revenue commitment added to the README (commitment_date: 2026-07-21) to match the roadmap priority note; no forecast exists yet to prove the date is executable.

Metrics

Baseline reading (t0) — the dated sequence of these reports is the burnup trend.

  • Jira work-status: TF-2544 is In Progress; done, active, and remaining child work exists under the epic.
  • Progress: 0 / TBD man-days (0%) in repo burnup only — total pending DRI man-days.
  • Throughput this period: 0 (baseline).
  • Forecast: TBD (derived once effort is finalized).

Next period

  • DRI confirms per-discipline man-days and the TPM derives the Q3 forecast against capacity.