Lessons Learned Applying the Mission Diagnostic
March 2008 • Technical Note
Audrey J. Dorofee, Lisa Marino, Christopher J. Alberts
This technical note describes the adaptation of the Mission Diagnostic (MD) necessary for a customer and the lessons we learned from its use.
Software Engineering Institute
CMU/SEI Report Number
DOI (Digital Object Identifier):10.1184/R1/6575096.v1
The Mission Success in Complex Environments (MSCE) research team along with Acquisition Support Program (ASP) staff applied the Mission Diagnostic (MD) to a project for the development and broad deployment of a software Application. The purpose of this MD engagement was to conduct a rapid evaluation of the Application project's potential for success during its alpha phase deployment, knowing additional deployments were to quickly follow. Software development and deployment was a new domain for applying the MD, and this particular project included additional constraints. Therefore, we modified the basic MD in several ways. We developed a new set of MD drivers for use with software development and deployment projects, used teleconferencing to collect data from project personnel, and included outcome-based scenarios to assess a variety of mission outcomes. From this experience, we have also derived the basis for a new success-driven framework with an integrated risk perspective. This technical note describes the adaptation of the MD necessary for this customer and the lessons we learned from its use.