Developmental OODA LOOP 5: Deliver

This final developmental stage will ideally have the smallest number of developmental tasks as your capability transitions into operational use and tasks shift towards Operation and Maintenance (O&M) funds. Any developmental work remaining here should be to support evaluating the metrics of capability performance and optimization or troubleshooting. Further work from hereon should focus on iteration for future deployments and overall sustainment/ modernization/ disposal functions. Ideally, by this phase, the product is ready to be moved into the manager’s organizational product line portfolio and can be supported by the capability community without supporting funds from other agencies or partners supporting R&D. The steps for this loop are:

1. Identify performance parameters, consistency, reliability concerns, and troubleshooting issues any early adopters are experiencing. As these details are identified, it may or may not be possible to fully address them within the scope and require workarounds until an upgrade or modernization effort is initiated.

2. Orient users with stakeholders as these topics are tackled with the users who may not be fully aware of decisions made during early procurement steps and compromises that were necessary to stay within constraints.

3. Work with your stakeholders to decide on what current acquisition mechanisms or contract mods may enable work to support this period. Ideally, the procurement contract in place has sufficient scope to cover these remaining needs but occasionally things fall out of scope. Depending on the scale of procurement, it may be worth considering investing IRAD if data rights conflicts won't be an issue.

4. Act on the plan to resolve any technical issues, secure supply chains, and maintain any support and disposal functions required.

By following these basic steps, developers should be able to deliver their capability and establish an enduring relationship with the user to continue support.