Project Phases Overview


A project should always be driven by the identification of a clear business need. During this Identification Phase, the need is clearly articulated and an assessment of feasibility and options is made. After the need is fully thought through and there is agreement that further effort should be put forward, project initiation can commence. Please refer to the Ideation section of this website.



During the Initiation Phase, an initial definition of the project’s high-level objectives, scope, resource needs, responsibilities, and timeframe are leveraged from the Project Proposal Summary (PPS) that the Business Analysis team will provide. The project manager (PM) is assigned and the PM and owner/technical lead will work closely with the sponsor to complete and gain approval on the project charter. This phase concludes when a kick-off meeting is held and the sponsor will officially charge the team.



During the Planning Phase, the Business Analysis team will work closely with all project roles to flesh out and document technical and functional requirements. On the heels of this activity, the project panager will work closely with the owner/technical lead and all team members to develop the project schedule, identify and document risks and issues, as well as resources needed. ServiceNow will be the repository for these important project items that will be tracked and updated throughout the project.



During the Execution Phase, the project team completes the tasks established in the Planning Phase and develops the project deliverable(s). Simultaneously, the project manager and owner/technical lead collaboratively monitor and control the project. The project manager focuses on ensuring the team has the resources they need, tracks task completion and project progress, and keeps stakeholders updated. This phase concludes with the project deliverable(s) achieved and accepted by the stakeholders on the project, which signals that the business need was successfully met.



During the project’s Closeout Phase, the project team assesses lessons learned during the project to improve performance on the next project. Likewise, any open items left to be completed after the project ends are evaluated and either begun as new projects, deferred, or made as enhancements to the production system. Finally, all artifacts produced during the project are archived for access by other project teams to use as applicable. This phase concludes when the Business Analysis team provides an outbrief to the working groups and IT governance steering committee.