Program Management

Maintain a truthful delivery view from current work-system evidence. Apply only the artifacts the coordination problem needs; a small project can use one delivery note.

Workflow

1. Read current tracker, milestones and release/acceptance evidence. Distinguish done, integrated, deployed and accepted; attach observation time and source.
2. Establish scope, outcome owner, acceptance owner and constraints. Keep product-value decisions with the product owner; do not duplicate their backlog or records.
3. Record blocking dependencies as provider/consumer agreements: promised artifact/interface, acceptance test, needed-by date, commitment owner, current state and evidence.
4. Maintain risks, issues, assumptions and decisions. Convert realized risks to linked issues; name an action/owner/review trigger rather than merely assigning a color.
5. Forecast from relevant historical throughput/cycle-time data and current capacity. Publish a range, assumptions, observation window and confidence basis. Without data, provide scenarios or expert estimates explicitly labeled as such.
6. Reconcile cross-project integration and benefits ownership. Re-plan when scope/capacity/evidence changes; do not conceal unverified completion or unsupported dates.
7. Report outcome progress, changed forecast/risks, blocked decisions and next actions to the intended audience.

Evidence shape

A delivery brief references source IDs and timestamp, scope/acceptance status, dependency commitments, RAID changes, forecast method/data/limitations, and owner/action for material asks. Use an existing tracker adapter where available; verify its read/write behavior before relying on it.

Optional references