Skip to main content

Delivery Timeline

Two PRDs under one anchor: Basic Attributes (foundation, in progress under Jira epic TF-2544) and Use-Case Activities (cross-module associations, draft).

MilestoneTrackEffortConfidenceProgressTarget DateStatus
Anchor + 2 child PRDs documentedboth0/02026-06-26Done
Jira epic TF-2544 activebasic-attributesHighJira active2026-06-27In Progress
Basic Attributes — backend RFC/design locatedbasic-attributesMediumJira active2026-05-19External RFC exists
Basic Attributes — buildbasic-attributesTBDJira active / TBD days2026-Q3In Progress
Use-Case Activities — RFCuse-case0/0TBDPending
Use-Case Activities — builduse-case0/02026-Q3Planned
Internal Alpha → Open Beta → GAboth0/02026-Q3Planned

Jira Evidence

  • Jira epic TF-2544 is In Progress.
  • Child work under the epic includes completed design/planning and backend foundation tasks, active backend membership/recalculation tasks, and remaining frontend/QA/final-verification tasks. Examples checked on 2026-06-27: Done TF-3107, TF-3108, TF-3109, TF-3202-TF-3205; active TF-3206-TF-3211, TF-3222, TF-3226; remaining TF-3216, TF-3217, TF-3246, TF-3258, TF-3260, TF-3261.
  • Rovo search found the external Confluence RFC DRAFT RFC — Customer Segmentation based on Basic Attributes (Backend) submitted 2026-05-19 and related to TF-2544; it is not mirrored in this repo's rfcs/ folder.
  • Jira proves Basic Attributes work is in progress, but delivery burnup still cannot be derived until effort_<discipline>_days and effort_total_days are confirmed.

Staffing

DisciplineImplementor
BackendJulio Jeffer
FrontendAzani
DataDATA Team (external squad)
QAHendry (primary), Izzul (backup)