REQ-FUN-111

Per-activity forecasted finish date from EV and SPI

ID
REQ-FUN-111
Category
Functional Requirements
Status
approved
Priority
P1
Created
2026-05-11T18:34:00.000Z
Approved
2026-05-11T18:37:00.000Z
Updated
2026-05-11T18:37:00.000Z

What

For each in-progress activity, system SHALL compute a forecasted finish date as forecast_finish = actual_start + (estimated_duration / max(activity_SPI, 0.1)), where activity_SPI is derived from percent_complete vs planned percent_complete at current_date.

Why

established project management guidelines Control Schedule outputs schedule forecasts; activity-level forecasts support proactive corrective action.

How

Computed at read-time from current activity + baseline rows; surfaced in the activity detail JSON and Gantt UI. Floor on SPI prevents division by zero. Reported alongside actual_finish (null if not yet finished) so the UI can compare.

Done when

Activity at 50% complete that should be at 75% per planned schedule produces a forecast_finish shifted later by a measurable amount; null when actual_start is null.

Out of scope

Three-point estimate refinement of remaining duration.

established project management guidelines Mapping

Primary Knowledge Area
Schedule Management
Secondary KAs
Cost Management
Primary Process Group
Monitoring & Controlling
established project management guidelines Deliverable
Status Report

Schedule forecasting at activity level - direct established project management guidelines Control Schedule output.