Phase

Description

Project Initiation & Project Planning

The Project Initiation Phase involves collating and analysing information about the project from a range of stakeholders to define the scope of the project & to brief the Project Manager who will be responsible for completing the project. Some Project Planning tasks may begin in this phase including preliminary planning re resouce allocation, budgets and scheduling however project planning is not completed until after the System Definition Phase is complete. 
Typically Project Initiation occupies approx 5 percent of the overall project budget.

Project Initiation Workflow Diagram 
Activities & Templates

System Definition

The System Definition Phase covers the development of the detailed business requirements and high-level technical design requirements for the project. On some projects there may be the need to develop prototypes and/or mockups in order to finalise the system definition. Project Planning is completed at the end of this Phase as it should now be clear exactly what is to be delivered by the project. The System Defition Phase therefore, consists of the following sub-phases;

1. Project Planning

1. Development of Requiremnents Model including Creative Design and User Interface Design

1. Prototyping/mockups (optional)

Workflow Diagram
Activities & Templates

Development & Testing

The Development & Testing Phase is where the major system development and system testing activities are undertaken. The Development & Testing phase is split into two sub-phases;

1. The Component Development Stage - covers the actual development activities (ie coding & design integration) as well as Component Testing which involves testing the idividual components or modules within the application is isolation rather than as a complete system. At the completion of this sub-phase the application is deployed to the staging environment for System Testing.

1. System Test Stage - focuses on testing the application from a system level on the staging environment using Test Cases which are derived from the business use cases in the Requirements Model.

Workflow Diagram 
Activities & Templates

System Acceptance

The System Acceptance Phase is where the completed application and any supporting materials required to put the system into production are tested by the client before the application is deployed to the live environment. The purpose of this phase is to ensure that what has been developed complies with the Requirements Model and that the application works 'as specified'. 
Typically the Acceptance Phase occupies 5-10 per cent of the overall project budget. 

Workflow Diagram 
Activities & Templates

Deployment & Review

The Deployment and Review Phase defines the processes that complete the installation of the website/application once it has passed the System Acceptance Phase. Deployment is a broad term that covers a series of activities that may start as early as 75 percent of the way through the System Definition Phase (ie Deployment Planning). This phase also involves a Post Project Review whereby the Project Manager and the project team in general review the project's successes and failures and feed the need for any corrective action back into the Project Management Methodology. 
Typically the Deployment & Review Phase occupies 5-10 per cent of the overall project budget. 

Workflow Diagram 
Activities & Templates

Change Management

The Change Management Process covers the documentation, analysis, implementation and tracking of changes to requirements that arise during the lifecycle of the project. The Change Management Process can be relevant during all phases of a project. 

Workflow Diagram 
Activities & Templates

Project Monitoring & Control

The PMC process covers the ongoing monitoring of project parameters throughout the life of the project and the analysis and reporting of project data/results in a timely and useful manner. The PMC process runs throughout the whole project.

 
Workflow Diagram 
Activities & Templates