The current issue of National Defense has a reader comment on a previous article about the software development issues of Joint Strike Fighter.
Dr. Polk mentions in his reader response that Scrum is a way to improve software development.
The defense and space programs we work make use of many of the Scrum process elements:
- Incremental development cycles - Rolling Waves with increments within the Rolling Wave
- Bounded scope within the increment and Rolling Wave.
- Work Packages for 100% complete deliverables
- Predefined outcomes using Integrated Master Plan Accomplishment Criteria (AC) that state what "done" looks like at the end of the Work Package.
- Measures of Physical Percent Complete in terms of Technical Performance Measures, Measures of Effectiveness, Measures of Performance, and Key Performance Parameters.
All of these have the "smell" of Scrum. Within a Validate Earned Value Management System, and DCMA surveillance, and DoD 5000.02 acquisition guidance.
The Core Connections with Scrum
- Define outcomes before starting work
- Never measure progress by effort - only by preplanned outcomes
- Execute in fixed increments of time, with defined outcomes
- Produce 100% working product - even if that product is only incrementally functional - at the end of each cycle.
The Core Disconnects
Most (or maybe even the vast majority) of Scrum projects that claim connections with Earned Value systems have disconnects:- Agile system try to make connections with Earned Value. But our Earned Value and the management systems are validated. No "making it up," no skipping steps, no "confusion" allowed.
- Agile claims to reduce risk, but DID 81650 mandates programmatic risk be embedded in the Integrated Master Schedule (IMS). This risk is "bought down," as the program proceeds from left to right. Specific units of measures of risk reduction are part of the Performance Measurement Baseline.
- Agile claims to handle emergent requirements, as does the Rolling Wave and Increment processes. Formal change control is required to support these changes, since scope control is mandated in a government procurement domain.
