Create and obtain agreement on the Product Description

Create and obtain agreement on the Project Charter

Project Approved for Planning by Sponsors

Develop the Scope Statement

Devekop the WBS

Develop the Project Schedule

Determine the Project Feasibility and Recommendation

Organize Project & Staff Acquisition

You should add or remove these as appropriate for your project, an example of an add would be Budget/cost Plan or Training Plan

Describe the Risk Management Plan

Describe the Change Management Plan

Describe the Project standards, Approval process, Document Controls

Describe the Communication Plan

Describe the Time Tracking Plan

Describe the Issue & Decision Management Plan

Assemble the Integrated Project Plan

Integrated Plan & Schedule Approved by Sponsors

Feasibility Study – Note: Requirements definition is an extension of the process started in the Feasibility Study. Please see the Feasibility Lifecycle model to determine if all or some of the steps are necessary.

Define in detail the procedures, high-level data requirements, existing reports and documents, roles and responsibilities, and organization of the user areas to be impacted by the product.

Describe in detail the business procedures and their data requirements.

Describe existing computer systems and their data.

Ensure that all required data elements have been identified in the data analysis.

Ensure that the sources and destinations of the data are known.

Identify and prioritize candidates for procedural change and automation.

Ensure that all entities of consequence to the application area have been identified.

Identify and define the data elements to be used, changed, or created (attributes analysis).

Determine the source of data elements in the business process.

Identify the business functions and/or existing computer systems that use each data element.

Identify the functions to be included in the new system and their data requirements.

Ensure that all operational and delivery requirements (e.g., response times, product delivery deadlines, maximum number of users, volume restrictions, frequency of use, expected product life span, other expectations, etc.) are known.

Documentation of the requirements that can be validated by users, sponsors, IT management, and developers.

Ensure that users, sponsors and IT management authorize continued work on the project.

Identify the criteria (specific product, vendor, or service characteristics, such as price, number and type of features, stability, etc.) upon which selection will be made.

Weight each criterion with respect to relative importance.

State the requirements and request proposals from prospective vendors (either for information only or for the purpose of making a vendor selection).

Provide guidelines for vendors that will enable them to. present proposals that are useful to decision makers.

Establish schedules for receipt of proposals.

Set bidders' meetings.

Identify prospective vendors.

Send out RFP's.

Obtain proposals.

Meet with vendors.

Interview and/or visit current clients of prospective vendors.

Evaluate each proposal with respect to pre-established selection criteria.

Identify modification requirements for each product.

Conduct benchmark tests.

Select vendor(s) and product(s).

Define the terms and conditions of acquisition, delivery and support, including acceptance criteria and methods.

Obtain management and sponsor approval.

Ensure that previous estimates and schedules are refined to reflect actual costs and delivery arrangements.

Identify any scope changes that have been made as a result of the selection process and contract negotiations.

Approve the selection(s), contract terms, costs, and schedules.

Specify overall implementation plan approach, i.e big bang, pilot, rolling.

Identify the functions that must be added to the selected product.

Identify programming changes that must be made to the selected product.

Identify non-programming installation requirements (tailoring via parameters and tables).

Define impact/interface requirements on other systems and obtain agreements regarding development and/or modification efforts.

Determine the impact of processing and storage volumes on the hardware (data storage, processor capacity) and on communications resources.

Set delivery schedule(s) with vendor(s).

Set site preparation schedules.

Set telecommunications line and service installation schedules.

Set installation schedules.

Describe the operations and support functions (LAN manager, back-up and recovery, technical support, etc.) that will be required.

Identify staff and organizational responsibilities.

Identify conversion requirements.

Determine the way the conversion will be performed (what programs, what controls, etc.).

Schedule the conversion effort.

Ensure that the test plans for all levels of testing are available to validate the new system and all systems being affected by it.

Develop recovery plan if acceptance criteria cannot be met or there is a need to go back.

Identify required user, support staff, and/or operator documentation and training, based on a review of delivered documentation.

Ensure that all required implementation activities have been identified and scheduled. Ensure that there is a defined installation process, indicating who is responsible for what.

Ensure that the project plan is accurate, given the information determined during this phase.

Specify when the system will be introduced into the production environment and when the user will be expected to begin testing and actual use.

Take delivery of the hardware and software and install for testing.

Exercise the product's components to validate that they perform according to acceptance criteria.

Exercise the integrated product.

Identify deficiencies.

Correct deficiencies.

Accept or reject the components and product (the contract should allow for return of the product if it does not pass the tests).

Identify program structures and modules.

Provide a detailed specification for programming.

Determine the exact location for the changes to be made.

Implement the changes identified.

Construct or generate new programs.

Ensure that changed and new components perform according to specifications.

Develop new materials or make changes to existing documentation and training materials.

Ensure that all users, operators, and support staff are able to use the changed system.

Ensure that the changed system(s) operate according to specifications using the plan developed.

Ensure that the changed system performs as expected under volume and exception conditions.

System testing can be broken down into levels of testing to include volume test, usability test, etc.

Provide the user and/or sponsor with proof that the changed system works according to expectations.

Ensure that the production environment (including users, operations, personnel, and support staff) is prepared for the start of production.

Install required new hardware, system software, and communications systems.

Make data set (files, data bases, tables) ready for the start of production.

Ensure that the changed software operates without disrupting the production environment.

Complete system installation

Put the changed software into production use.

Evaluate the performance of the changed system in terms of resource use, usability, and the degree to which it met user expectations.

Evaluate the user environment to determine if expected benefits were achieved.

These task are the ongoing management of the facilitating plans, if you added budget/cost planning in the plan section, then you should add budget management here

Risk Management - ongoing

Change Management - ongoing

Project Document Review and Organization - ongoign

Communication Management - Ongoing

Contract/Procurement Management - ongoing

Quality Assurance Management - ongoing

Time Tracking - ongoing

Issue and Decision Management - ongoing

Prepare, Conduct, and Present a project evaluation

Coordinate maintenance Turn-over

Project Complete and Maintenance Ready

Unassigned