Our ISO 9001:2000 Project Life Cycle
Processes meant to ensure Quality
The Project Life Cycle
 
This diagram documents the formal project life cycle that is applied for all projects. For smaller projects, some of the stages may be skipped, however that fact is always documented to meet the needs of the quality system.
 
STAGE 1 - TM and You - The Planning Stage
 
In this stage we plan and prepare formal documents that will aid, control and manage the coding, testing and deployment of the system. This stage generally includes the prototyping of the system as well. At the end of this stage there are exact specifications and guidelines for the development team.
 
STAGE 2 - TM and the Developer - The Implementation Stage
 
The first two milestones of the second stage may overlap with the end of the first stage, allowing for coding to begin immediately. Implementation is governed by the plans made in the first stage, especially the test cases and acceptance criteria.
 
STAGE 3 - Closing the Project - The Closing & Archiving Stage
 
It is important to wrap things up in a formal manner. All code, documentation, test results and acceptance tests must be archived to aid in maintenance and future upgrades. This is an absolute must to protect and safeguard the customer's investment in the project.
 
STAGE 4 - Maintenance and Upgrades - Future Stages
 
Once the project has been signed off, there will be ongoing maintenance and upgrades. Non-trivial projects generally plan for such future stages. Smaller projects may not have formal planning, but most software applications do need maintenance and upgrades once they have been in use for some time. The above diagram shows maintenance steps, if involved.
 
Change Orders
 
All above stages may involve changes in the requirements which may affect various documents, including the contract. Regardless of which stage, each Change Order is handled as a separate process to ensure that documentation remains up to date.
 

Tahir Mufti, IT Outsourcing Consultant ©2006-2010

www.mufti.net