The IT Project Life Cycle: Five Process Groups and Typical Phases Explained

Every project passes through a sequence of stages from idea to completion. This sequence is the project life cycle. Understanding it gives you a map: you know where you are, what should be finished before moving on and what comes next. For IT projects, the life cycle also interacts with the software development life cycle, which we compare in SDLC Models Compared for Project Managers.

Life Cycle vs Process Groups

Two related ideas are often confused. The project life cycle is the series of phases a project goes through, and it varies by industry and organisation. The process groups are PMI’s five categories of project management activity, which occur in some form in every project and often repeat inside each phase.

The Five Process Groups

Process groupPurposeTypical IT outputs
InitiatingAuthorise the project and define it at a high levelBusiness case, project charter, stakeholder register
PlanningEstablish scope, objectives and the plan to deliver themRequirements, WBS, schedule, budget, risk register, communication plan
ExecutingDo the work defined in the planDesigned, built and tested solution, trained users
Monitoring and ControllingTrack progress and manage changesStatus reports, change log, earned value metrics, issue log
ClosingFormally finish the projectHandover documents, acceptance, lessons learned, closure report

Monitoring and controlling runs alongside all the other groups, from the first day to the last. It is not a phase that begins after execution.

A Typical IT Project Life Cycle

Different organisations name the phases differently, but a common predictive pattern looks like this:

  1. Concept or initiation: a need is identified, a business case is written and the project is approved.
  2. Planning: detailed requirements, scope, schedule, budget and risks are defined, and a baseline is agreed.
  3. Design: architecture, user interface and data models are created.
  4. Build or development: the system is configured or coded.
  5. Testing: the solution is verified against requirements and validated by users.
  6. Deployment: the solution is released into the live environment and users are trained.
  7. Closure and handover: operations take over, benefits are reviewed and lessons are captured.

Notice that planning, executing and controlling activity appear inside several of these phases. Design work involves planning the build, for example, and testing involves controlling quality.

Phase Gates

A phase gate (or stage gate) is a decision point at the end of a phase where a governing group reviews results and decides whether to proceed, change course or stop. Gates reduce the risk of pouring money into a failing project. Typical gate questions include:

  • Is the business case still valid?
  • Were the phase deliverables completed and accepted?
  • Are costs and schedule within tolerance?
  • Are the top risks understood and managed?
  • Does the team have what it needs for the next phase?

Gates work only if stopping is a genuine option. If every project always passes, the gate is a ritual and not a control.

Life Cycle Types

Predictive (plan-driven)

Scope, time and cost are defined early, and work flows through phases largely in order. It suits stable, well-understood requirements and regulated environments.

Iterative and incremental

The product is developed in repeated cycles, each adding functionality. Scope is refined between cycles.

Adaptive (Agile)

Work is done in short timeboxes with frequent feedback, and the backlog is reprioritised continuously. See Scrum Framework Explained.

Hybrid

A mix, such as upfront planning and governance with Agile delivery inside the build phase. Hybrids are very common in large IT organisations.

Cost and Risk Across the Life Cycle

Two patterns hold across most projects. First, uncertainty and the stakeholders’ ability to influence the outcome are highest at the start, and fall as work progresses. Second, the cost of making a change is low early and rises sharply later. Changing a requirement on paper costs very little; changing it after the system is live can cost many times more. This is why careful work in initiation and planning pays off in predictive projects, and why Agile approaches use frequent feedback to find problems sooner.

Worked Example: Intranet Replacement

A company replaces its intranet. During initiating, the sponsor approves a charter with a budget ceiling. During planning, the team gathers requirements from departments and builds a schedule. In executing, the vendor configures the platform while the team migrates content. Monitoring and controlling tracks content-migration progress weekly and handles requests for extra features through change control. In closing, the intranet team hands the platform to support, trains administrators and runs a lessons-learned workshop. Each process group appears in the project, even though no one labels them that way day to day.

Common Mistakes

  • Skipping initiation and planning to “get started faster”, then paying for it with rework.
  • Treating monitoring and controlling as an end-stage activity.
  • Running gates without clear criteria or genuine authority to stop.
  • Ignoring closure because the team is already moving to the next project.
Key takeaways
  • The life cycle is the sequence of phases; the five process groups are categories of activity within it.
  • Monitoring and controlling runs for the whole project.
  • Phase gates give governance a chance to continue, redirect or stop.
  • Life cycles can be predictive, iterative, adaptive or hybrid.
  • Early work is cheap to change; late change is expensive.

Related Lessons