I. Objective(s): Address SE shortfalls in projects characterized as quick response, network-enabled, or emergent. The objectives were to: Phase 1 - (a) identify MPTs considered viable in the sponsor’s environment, and (b) identify gaps where no useful/viable MPTs could be identified. Phase 2 – (c) gather additional information on MPTs associated with the environment identified in Phase 1 and develop a taxonomy of MPTs identified; (d) investigate use of micro-process modeling techniques to support the definition and evaluation of MPTs; and (e) provide implementation guidance on the three MPTs recommended in Phase 1.

II. Approach: Literature and industry surveys were used to gather data on current SE practice in similar environments. Consolidation and analysis of data produced a set of common themes across interview responses, a list of candidate MPTs that were recommended by organizations with environments similar to the Sponsor’s, and a framework for showing the relationships among challenges, themes and MPTs.

III. Project Deliverables: Final Technical Report

IV. Significant Research Findings & Products: The research established four key challenges:

• Requirements – Changing requirements priorities and/or emerging requirements

• Stakeholders – Obtaining useful stakeholder input and addressing conflicting stakeholder requirements

• Sustainment – Conflicts between developing new capabilities and supporting a currently deployed system

• Integration – Integrating independently evolving components into a larger interoperable system

Three MPTs were recommended as most likely to increase effectiveness in Sponsor’s environment: Scrum, rapid prototyping, and continuous integration. Gaps were identified through industry survey responses and by comparing useful, viable MPTs to the four challenge areas. Primary gaps identified through the survey were decision management and stakeholder requirements definition. The challenge area where the MPT gap was largest was Sustainment.

The team developed the “bridge diagram” to help strategize solutions and assess current practices. The diagram links 3 kinds of information: a theme from survey responses, specific theme elements, and MPTs that have proven effective in achieving those elements. Scrum was described in a formal process modeling tool (Little JIL from UMass). Single point of failure and finite state verification analyses were performed. Implementation guidance was developed for 3 MPTs based on the bridge diagram. There simply were not good tools for rapid/agile SE in use. Tools that have been applied were drawn mainly from agile software development and had resulted in mixed success.