Overview
Introduction to the concept of project life cycle phases used by Project Managers and teams to effectively structure projects and set them up for success. A project phase is a collection logically related project activities that culminates in one, or more, deliverables.
There are many different names for project phases, often relating to various industry specific phrasing; however, some common names for these phases are:
Feasibility
The project feasibility phase begins with identifying the Business Case, determine the validity and benefits, and if the organization has the capability to deliver the intended outcome. The outcome of this phase is a project charter, and a GO/NO-GO decision regarding if the project should move forward to the project design phase.
Design
The project design phase develops the road map (i.e. project plan) used throughout the life of the project. Resources are identified and assigned to the project. Key stakeholders are identified, and interviews may be conducted as appropriate. The project plan defines the project scope, overall objectives, deliverables, schedule, and milestones. Furthermore it contains a communication plan, as well as a risk management plan. The outcome of this phase is an appropriately scaled project plan.
Build
This phase incorporates the primary execution phase of the project where the team works towards meeting project objectives and producing deliverables in association with identified quality assurance activities. Status is reported to key stakeholders. Any changes to the approved project baseline will go through a change management process. The Project Manager will monitor performance of the project and make adjustments to ensure the objectives are met.
Test
This phase is associated with the final quality review and inspection of the project deliverables before transition, go-live, or customer acceptance.
Deploy
This phase is where the project deliverables are put into production use, and activities associated with transition to operation sustainment, and organizational change management.
Close
The team is assembled to discuss and capture things that went well and things that didn’t. A closeout document is created, all project documents are archived, and contracts are closed.
Need additional help or have issues
For support, requests may be submitted anytime using the appropriate Enterprise Service Management form. Requests generate a Ticket which will be worked in order received and urgency by IT Employees with the knowledge and permissions to assist with the request.
For immediate assistance please review the Contact Us page for the appropriate support group.