Acquisition Strategy Statement IT Acquisition Template 10

Acquisition Strategy Statement IT Acquisition Template 10

The purpose of the Acquisition Strategy Statement is to serve as the roadmap for guiding project activities from project initiation to project completion, operations, and ultimately disposal. It must be approved by senior management before it is distributed. It then becomes a “living document” in the sense that it is updated as decisions are made and new information becomes available. It helps members of the Integrated Project Team stay focused on the priorities and directions and it helps all stakeholders understand the nature, purpose, and strategy of the acquisition and implementation approach. The nature and contents of an acquisition strategy statement tend to vary with the organization and type of acquisition. However, in all cases the statement is expected to include the essential elements of the acquisition strategy. Among the most common essential elements are those provided in Template 10, below. In using the template, keep in mind that your product must communicate with a wide range of people, from team members to senior management and users. Clear writing that quickly gets to the point is essential. Your Acquisition Strategy Statement should include all of the main headings and subheadings shown in the template. This enables an individual to find specific information quickly, without having to scan the entire document. This product is an important representation of your team and the quality of its work. If it is not prepared well, it will reflect negatively on the team and on the proposed project. If it is prepared exceptionally well, the team will be held in high regard and the project will likely gain or retain above average support from executives and other stakeholders. It is important, therefore, to make the statement attractive, informative, and easy to read. Here is the template:

Acquisition Strategy Statement Name of IT Services Acquisition Project: ____________________________________________________ Submitted by: _____________________________________________ Date Submitted: ___/___/______ 1. Proposal Summary. [Under this heading, briefly summarize the entire proposal, including costs, benefits, risks, and schedule. Provide a high-level description of the proposed IT services/products acquisition project, why it is needed, and how the proposed IT services and system implementation will meet that need. Briefly indicate who and/or what will benefit, when the costs and benefits will occur, and how risk will be managed.]

2. System Life Cycle (SLC). [Under this heading, describe or otherwise present the proposed project’s system life cycle (SLC). Do not confuse this with the system development life cycle (SDLC). The SLC, which has roots in systems engineering, covers the system from initiation to disposal. At minimum, the SLC includes these phases: planning, acquisition, implementation, operations, and disposal. Depicting the SLC is usually best accomplished using a graphic with a timeline. It is sometimes (not always) advantageous for the graphic to go a little deeper into the principal phases and show key activities, reviews, and milestones that may be of special interest to executive reviewers. An example could be an acquisition project involving outsourcing and executives might want to know when the outsourcing agreement is scheduled to be signed.] 3. Basic Acquisition Approach. [Under this heading, provide a summary statement of your basic acquisition approach and then use the subheadings below to give details of the activities. In this summary statement, identify the IT services and products (if included) to be acquired and describe at a high-level the approach that will be used to identify qualified sources of the desired IT services. If the contractor to be selected is to recommend, install, develop, or otherwise provide services related to a product, this aspect needs to be addressed in the acquisition approach. After writing the summary statement, describe the actions that were or are to be followed in each of the below areas identified by subheadings. Include the subheadings in your document.] Market Research. [Briefly described the market research planned and any results to date.] Use of Competition. [Describe how competition will be built into the acquisition process to help obtain the best price and/or best value and not exclude potentially qualified IT services contractors.] Potential Sources. [Identify the potential contractors qualified to provide the services required.] Contract Type. [Identify the type of contract planned to be awarded and give the reason for its selection.] Contract Incentives and Penalties. [Describe any incentives and penalties that you plan to build into the contract with the IT services contractor.] Risk Assessment. [Identify important risks, including risks associated with the contract type selected, and how those risks will be managed.]


Comments are closed.