Project Lifecycle

The following is an overview of the Project Management Framework and Lifecycle. For a complete and detailed view, see the full Project Management Framework. For quick tips and a condensed summary, check out the One Pager or the Quick Reference Guide. The IT Project Management Framework Lifecycle consists of multiple elements working together to ensure the consistent and successful delivery of projects. These elements are:

Project Phases

The project lifecycle is broken into defined phases, each with its own purpose, deliverables, and actions required to progress.

Action Items

The required activities that must be completed to ensure compliance and consistency for each project

Templates

Standardized documents that collect and report consistent project data, enabling effective tracking throughout the lifecycle. All templates are available on the IT PMO Website within the Templates section.

Roles and Responsibilities

Understanding each role and its responsibilities throughout the project lifecycle ensures clear ownership, smoother collaboration, and successful delivery. 

 

Project Phases

 

The IT Project Management Framework Lifecycle consists of four phases. Intake is separate and distinct from the formal lifecycle but is a critical first step in how all project requests are captured and reviewed. Each phase builds on the work completed in the prior phase, providing a structured and consistent approach to moving projects forward successfully. 

A diagram of a project lifecycle timeline with "Intake Phase 0" highlighted in dark blue. This highlighted phase begins after the initial "Project Intake Form Requested" step and proceeds along a timeline arrow to a yellow diamond marker labeled "Gate 1".

Intake is separate and distinct from the IT Project Management Framework Lifecycle. Any UD employee is eligible to submit a project request. The PMO Team, in collaboration with the requesting functional office, coordinates the intake process. Submitting a Project Intake Request does not imply acceptance – the process is designed to promote equity and transparency by applying consistent selection criteria to all submissions. Once reviewed, the request is presented to the Governance Committee at Gate 1.

A diagram of a project lifecycle timeline with "Initiation Phase 1" highlighted in dark blue. This highlighted phase is situated along the timeline arrow between two yellow diamond markers labeled "Gate 1" and "Gate 2".

The Initiation Phase begins after Gate 1 approval. During this phase the project is more fully defined so it may be properly resourced and planned. The Project Manager coordinates engagement with the requester, sponsor, and stakeholders and completes the Project Charter, which is presented for approval at Gate 2.

A diagram of a project lifecycle timeline with "Planning Phase 2" highlighted in dark blue. This highlighted phase is situated along the timeline arrow between two yellow diamond markers labeled "Gate 2" and "Gate 3".

The Planning Phase builds on Initiation and is one of the most critical phases of the lifecycle. A well-developed plan helps ensure the project is completed on time and on budget. The phase concludes with a sponsor-approved Project Planning Document presented at Gate 3.

A diagram of a project lifecycle timeline with "Delivery Phase 3" highlighted in dark blue. This highlighted phase spans along the timeline arrow starting from a yellow diamond marker labeled "Gate 3", crossing an intermediate marker labeled "Gate 3+", and ending at "Gate 4".

Delivery consists of two concurrent sub-phases: Execution (doing the work) and Monitoring and Control (tracking progress, managing risks, and reporting status). The Project Manager executes the project and notifies the Governance Committee of any scope or schedule changes via Gate 3+.

A diagram of a project lifecycle timeline with "Closeout Phase 4" highlighted in dark blue. This highlighted phase represents the final stage on the timeline arrow, beginning immediately after a yellow diamond marker labeled "Gate 4".

During Closeout the project team documents lessons learned, archives project documentation, and transitions delivers to operations. The project is formally closed at Gate 4 following sign-off from the Governance Committee. 

Roles & Responsibilities

Although the Project Manager is most often associated with project work, many roles contribute throughout the lifecycle. The most common roles are as follows. Each role's level of involvement will vary based on the project's size, complexity, and phase. 

  • Senior leader (Director or VP level) who champions the initiative

  • Ensures alignment with university strategic goals 

  • Secures funding, resolves major escalations, and approves key milestones

  • Business leader (Director+) who makes the case for the project

  • Defines project goals, provides oversight, and approves deliverables 

  • Provides formal sign-off on the project's final deliverables

  • Coordinates the project on behalf of their functional area

  • Secures necessary resources and serves as an escalation path for the Project Sponsor 

  • May be shared across departments for cross-functional projects

  • Leads the project through the full PM Lifecycle

  • Creates and coordinates approval for PM deliverables 

  • Manages status reporting and ensures the schedule is followed

  • Cross-functional leadership group that provides governance and decision support

  • Advisory in nature; provides recommendations to the Project Sponsor and university leadership 

  • Typically engaged for high-impact or complex projects

  • Define business requirements, validate solutions, and ensure alignment with business processes and operational needs

  • Coordinate stakeholder and end user participation 

  • Support user acceptance testing, change management, and adoption

  • Define the technical approach, architecture, and implementation strategy

  • Ensure solutions align with UDIT standards, security requirements, and infrastructure 

  • Oversee technical teams and manage technical risks and dependencies

  • IT-facing business partner who aligns business needs with IT priorities

  • Supports project prioritization and ensures ongoing communication between IT and departments 

  • Persons or organizations impacted by or involved in the project

  • Provide input, participate in testing and feedback, and are directly affected by project outcomes 

  • Must be identified by the Project Sponsor and Project Manager at the outset of the project

  • Engaged as needed to provide specialized expertise, tools, or implementation support

  • Brought in with sponsor approval to supplement the project team 

  • Specialists retained for their deep knowledge in a specific system, application, or functional area

  • Can be internal or external; consult on project tasks and designs throughout the lifecycle 

  • Examples include Data Analysts, IT Security, IT Compliance, and Technical Experts