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 being developed.

Describe in detail 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, and expected product life span, other expectations, etc.) are known.

Ensure that the approach recommended in the Feasibility Study and reaffirmed in phase 1.0 is still valid, given the detailed understanding of requirements.

Ensure that cost benefits assumptions are still valid.

Ensure that impacts/interfaces on other projects and systems are accurately stated.

Ensure that the development platform is sufficient to support the development effort.

Revise approach and cost benefits statements as appropriate.

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

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

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

Avoid effort on projects that should be ended or redirected.

Identify the hardware upon which the new system will operate.

Identify the specific Internal Processing Facility (IPF).

Identify the system software under which the application will operate.

Identify the DBMS and/or file system that will be used in the system.

Identify portability requirements.

Choose development tools and platform.

Identify how system functions will be distributed geographically and technically (across platforms).

Determine the network(s) that will support the application.

Identify the security features of the system.

Create contingency plan and/or revise existing contingency plans.

Identify and describe the controls to be built into the system and used to ensure that data integrity is maintained.

Establish application wide standards to create a consistent user interface.

Identify the software functions that will be developed as common routines or software tools.

Identify the specific functions described in Activity 2.3 to be included in the new system.

Identify the functions to be delivered in the planned versions of the system.

Package the new system's functions into subsystems and map the flow of data between them.

Identify files and/or databases.

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

Ensure that the various aspects of the design fulfill the requirements and comply with standards.

Statement of approach

Ensure that the approach recommended in the Feasibility Study and reaffirmed in phase 2.0 is still valid, given the design results.

Ensure that cost benefits assumptions are still valid.

Ensure that impacts on other projects and systems are accurately stated.

Revise approach and cost benefits statements as appropriate.

Describe the macro/architectural design in a document.

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

Normalize the data model.

Identify the data required to support computerized functions.

Identify data segments or records based on the way data will be used in the system.

Map the logical data base design to the specific database or file management system(s) to be used.

Describe the data, as it will be stored on the physical media.

Reevaluate storage utilization and system capacity estimates previously made (Activity 3.10) based on the completed design.

Provide computer operations and hardware acquisition people with accurate information regarding requirements for operations, including conversions.

Validate the designs (logical and physical) to ensure that they adequately fulfill requirements.

Layout the format of reports.

Identify the dialogues needed to support the procedures that will be followed by system users.

Layout the format of the screens that will be required within the system.

Determine if the functional design has caused any change to the data base design and, if so, make the changes.

Layout of the forms and documents that will be required within the system.

Identify and describe the editing/validation rules for each data element and each transaction (input data flow) in the system.

Prepare descriptions of the programs (Software components) to be developed, identifying inputs, processing, performance constraints and outputs.

Determine if the macro/architectural design should be changed based on the findings of the functional design.

Identify and describe the controls to be built into the system and used to ensure that data integrity is maintained.

Ensure that the functional design covers all functions identified in the requirements.

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

Initiate the process of ordering any hardware and system software required.

Identify conversion requirements.

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

Schedule the conversion effort.

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

Identify required user, support staff and/or operator documentation and training.

Ensure that all required implementation activities have been identified and scheduled.

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.

Identify program structures and modules for the programs (software components) specified.

Ensure that program designs comply with standards and fulfill requirements as specified.

Identify opportunities for using previously developed components.

Identify components that may become reusable.

Construct or generate the programs.

Ensure that software components perform according to specifications.

Ensure that groups of components perform according to spec and interface with one another properly.

Develop new materials or make changes to existing documentation and training materials based on the specified plan.

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

Ensure that the new system operates according to specification, using the plan developed in Activity - Develop test strategy and plans.

Ensure that the 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., see guidelines on testing.

Provide the user and/or sponsor the 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 new software operates without disrupting the production environment.

Put the new system into production use.

Evaluate project performance

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