What Is The Agreement Between The Mda And Pm That Will Be Used For Tracking And Reporting

Milestone B is usually the formal launch of an acquisition program with the approval of the MDA for the Basic Acquisition Program (APB). The BPA is the agreement between the MDA and the program manager and its or their order supply chain, which is used for monitoring and reporting over the life of the program or desa term program. The PBO will include accessibility caps for production and maintenance costs. Affordability caps are defined as fixed cost requirements for CPPs. The BPA`s cost, timing and performance lines should be at a high program level to allow flexibility to move requirements within and beyond versions. Statutory authority to make commitments leading to immediate or future expenditures for the MDAP at Stage B, the MDA must certify in writing to Congress that the program is affordable and that the Director of Cost Assessment and Program (DCAPE) agrees with reasonable costs and timeline forecasts to execute development and production plans. For each increment of an MDAP or BUT program and each sub-program of an MDAP, a separate APB is required. Increments can be used to plan simultaneous or sequential efforts to provide capacity faster and in tune with the technological maturity of each increment. (If an MDAP requires the provision of two or more categories of final items that differ considerably in terms of form and function, sub-programs may be implemented.) With regard to the milestone, the MDA concludes, if not already completed: contractual report that provides to PMs: Defines the part of the program produced by a specific contractor and forms the basis for the collection of data relating to the costs and dates of the contract. The Milestone-B decision authorizes the entry of the program into the EMD phase and the awarding of contracts for EMD activities. Based on precedents for an agile approach to streamlining documentation, as defined in previous milestone decisions, there should be few additional requirements for this review of the decision.

Agile program managers should be in constant contact with key stakeholders regarding program changes during the intermediate phase between decision points. More frequent ongoing reviews and ongoing coordination with stakeholders create the conditions for effective review of decisions.