Classes / Shared specialties / Command Department
Command Track: Contracts, Money, Hiring and Planning · Rank 5 coursework · Module 1 of 3 · about 40 min
Running a program: schedule, budget and risk
We use NASA program and project life-cycle governance as an example of phases and evidence-based decision points, not a universal rule for every employer. The linked NPR 7120.5F page directs readers to interim NID 7120.148 for the most recent requirements. Any real project needs its currently applicable directive, tailoring and designated authorities.
Earned value management ties schedule and money together. Planned value is the budgeted cost of the work you meant to finish by now. Earned value is the budgeted cost of the work you actually finished. Actual cost is what you spent. Cost performance index (CPI) is earned value divided by actual cost, and schedule performance index (SPI) is earned value divided by planned value. Under 1.0 means over budget or behind.
Risk management is a habit, not a form. List what could go wrong, rate each risk by likelihood and consequence, assign an owner and a plan, and review the list on a schedule. The NASA Systems Engineering Handbook walks through how technical risk, requirements and reviews fit together.
We report measured status, assumptions and recovery proposals separately. An unfavorable ratio needs its cause investigated rather than invented from the number alone. A proposed recovery is not evidence that the vendor, resources or critical-path dependencies have actually changed.
We distinguish measured earned-value status from a guaranteed forecast. Planned value is budgeted work scheduled; earned value is budgeted work actually accomplished; actual cost is spending for that work. They must use the same status date and compatible scope. CPI compares earned value with actual cost, while SPI compares earned value with planned value. A favorable one cannot establish the other.
Worked example, fictional status with all values in the same budget units: planned value is ten, earned value eight and actual cost twelve. SPI is 0.8 and CPI is about 0.67. The model shows less budgeted work accomplished than planned and more cost per earned unit, not an exact calendar delay or a guaranteed final overrun. Critical-path dependencies and remaining-work assumptions still matter.
A gate is an evidence-based decision, not simply a date reached. A risk owner and mitigation plan do not prove the action was implemented or effective. Changes in requirements, vendor timing or test results can alter both the risk picture and the schedule logic, so a historical pass needs its scope retained.
Practice, on paper: we calculate new matched-date ratios and connect an invented risk to a dependency, decision need and follow-up evidence. Our self-check separates current measurement, assumption and forecast. We approve no project gate, spend no budget and change no real schedule.
Sources
- NASA NPR 7120.5: Space Flight Program and Project Management
- NASA Systems Engineering Handbook
- NASA: Earned value management tutorial
- NASA: Performance management reference card, formulas
Module quiz
10 questions, 8 correct to pass. You'll see what you missed and why, and you can retake it.