Program Acquisition Strategy Formulation
Definition: The Acquisition Strategy is a comprehensive, integrated plan developed as part of acquisition planning activities. It describes the business, technical, and support strategies to manage program risks and meet program objectives. The strategy guides acquisition program execution across the entire program (or system) life cycle. It defines the relationship between the acquisition phases and work efforts, and key program events such as decision points, reviews, contract awards, test activities, production lot/delivery quantities, and operational deployment objectives. The strategy evolves over time and should continuously reflect the current status and desired end point of the program .
Keywords: acquisition, acquisition strategy, agile acquisition, "big bang" acquisition, contracting, evolutionary acquisition, information technology, software engineering, spirals, systems engineering
Developing and executing an effective acquisition strategy requires "systems thinking" to ensure the various elements of the strategy are integrated, and interdependencies are understood and accounted for during execution of the strategy. The acquisition strategy is dynamic in that it must reflect changes that occur often during execution. Cost, schedule, and system performance (or capability) trade-offs may also be required, and program managers will need the insight to make informed decisions based on understanding the risks involved in achieving desired outcomes. Therefore, systems engineering plays a key role in both planning and executing this strategy.
How agencies acquire the products and services they need to perform their operations (or execute their mission) varies depending on the criticality or urgency of the product or service to the agency's mission. Another factor is whether the acquisition entails investments or allocation of relatively large amounts of agency resources. Acquisition planning for major, complex efforts requires greater detail and formality, and a greater, earlier need for systems engineering. Acquisition management at this level often requires balancing the equities of multiple stakeholders by establishing and executing a governance process that strikes a balance between the desire for consensus and the agility needed to make trade-offs among cost, schedule, and the capabilities delivered to address changing needs and priorities. Because of the challenges inherent in such an acquisition environment—political, organizational/operational, economic, and technical—the FAR requires program managers to develop and document an acquisition strategy to articulate the business and technical management concepts for achieving program objectives within imposed resource constraints. MITRE systems engineers are often called upon to help develop and execute this strategy.
MITRE SE Roles & Expectations: MITRE systems engineers (SEs) are expected to help our clients/customers craft realistic, robust, and executable acquisition strategies. This means helping articulate what the government needs, translating those needs into mission/outcome-oriented procurement/solicitation requirements, and adequately identifying the issues, risks, and opportunities that shape and influence the soundness of the acquisition strategy. MITRE systems engineers help agencies achieve what the Federal Acquisition Regulation (FAR) characterizes as "mission-oriented solicitations ."
Best Practices and Lessons Learned
Acquisition Strategy: Answering the Question "How to Acquire?"
Focus on Total Strategy: Avoid the temptation to only focus on the contracting aspects of an acquisition strategy. In many agencies, the term "acquisition strategy" typically refers to the contracting aspects of an acquisition effort. This view tends to ignore other factors that influence a successful outcome, including technical, cost or schedule, which often have interdependencies that must be considered to determine how to acquire needed capabilities. The overall strategy for doing so will be shaped and influenced by a variety of factors that must be considered individually and collectively in planning and executing the acquisition effort.
Write It Down: The FAR requires program managers to develop an acquisition strategy tailored to the particulars of their program. It further defines acquisition strategy as "the program manager's overall plan for satisfying the mission need in the most effective, economical, and timely manner ." An acquisition strategy is not required (or warranted) for all acquisition efforts. However, most (if not all) acquisition efforts for which MITRE provides systems engineering support require acquisition planning and a written plan (acquisition plan) documenting the ground rules, assumptions, and other factors that will guide the acquisition effort. For major system acquisition programs, a written (i.e., documented) acquisition strategy may be used to satisfy FAR requirements for an acquisition plan .
Apply Early Systems Engineering: In essence, the FAR requires federal agencies to have increasingly greater detail and formality in the planning process for acquisitions that are more complex and costly. These major or large-scale federal acquisition efforts also have a greater need for application of sound systems engineering principles and practices, both within the government and among the suppliers (industrial base) of the products and services. A well-known axiom of program/project management is that most programs fail at the beginning . In part this can be attributed to inadequate systems engineering, which when done effectively articulates what the government needs, translates those needs into procurement/solicitation requirements, and identifies issues, risks, and opportunities that shape and influence the soundness of the acquisition strategy.
An Acquisition Strategy Is Not a Single Entity: It typically includes several component parts (or strategy elements) that collectively combine to form the overall strategy (or approach) for acquiring via contract(s) the products/supplies or services needed to fulfill an agency's needs. These elements tend to differ depending on the nature of the acquisition effort, whether or not the effort is formally managed as a "program," and the acquisition policies, procedures and governance policies and regulations of the agency being supported. However, a common element of most acquisition (program) strategies includes structuring the program in terms of how and when needed capabilities will be developed, tested, and delivered to the end user. In general, there are two basic approaches: delivering the capability all at once, in a single step (sometimes referred to as "grand design" or "big bang") to fulfill a well-defined, unchanging need; or delivering capability incrementally in a series of steps (or spirals) to accommodate changes and updates to needs based on feedback from incremental delivery of capability. This latter approach is often referred to as evolutionary or agile acquisition (actual definitions may vary). For more details on each of these strategies, see the Agile Acquisition Strategy, Evolutionary Acquisition, and "Big Bang" Acquisition articles within this topic of the Systems Engineering Guide.
Picking the Appropriate Strategy: Selecting which capability delivery approach to use depends on several factors, including what is being acquired, the level of maturity of the enabling technology, the rate at which technology changes, and the stability of the requirements or evolving nature of the need that the acquisition effort is addressing. For most information technology acquisition efforts, experience has shown that an evolutionary/ incremental/agile approach is preferred to accommodate and plan for change inherent in software-intensive systems. However, incorporating an evolutionary or agile approach to delivery of capability is no guarantee that an acquisition strategy is sound. Other factors also determine the effectiveness of a given strategy . These include aspects such as whether the strategy is based on an authoritative assessment of the risk involved in achieving the objectives of the acquisition effort; a realistic test and verification strategy and meaningful event or knowledge-driven milestone reviews to assess progress toward achieving acquisition objectives; and realistic cost, schedule and performance (delivered capability) baselines.
References & Resources
- Defense Acquisition Guide Book.
- Federal Acquisition Regulation, Subpart 34.005-2
- Federal Acquisition Regulation, Part 34
- Federal Acquisition Regulation, Subpart 34.004
- S. Meier, Best project management and systems engineering practices for large-scale federal acquisition programs, Acquisition Community Connection Practice Center, DAU.
Additional References & Resources
"Government Acquisition Support," MITRE Systems Engineering Competency Model
Not all references and resources are publicly available. Some require corporate or individual subscriptions. Others are not in the public domain.
References and resources marked with this icon are located within MITRE for MITRE employees only.
For more information on the Systems Engineering Guide, or to suggest an article, please Contact Us.