liveBook · Manning

Project life cycle

As explained in Think Like a Software Engineering Manager

A project life cycle is the sequence of phases through which a project progresses from initiation through completion and delivery.

A project life cycle is the sequence of five phases that moves a project from discovery to delivery and reflection. It gives engineering managers, product managers, and technical program managers a shared structure for planning, coordinating work, adapting to change, and tracking progress. section 10.0 section 10.3

Use the phases to organize the project’s major responsibilities:

  • Project discovery defines the product road map and aligns the technical road map with strategic goals. section 10.3
  • Preplanning establishes the foundation by assessing priority, defining scope, and identifying key stakeholders. section 10.3
  • Planning and project kickoff turn the initial wish list into a detailed plan covering budget, resources, team building, communication, training, and tracking. section 10.3
  • Execution delivers the work through implementation, testing, defect triage, technical decisions, partner management, check-ins, feedback loops, and risk management. section 10.3
  • Postexecution recognizes contributors, evaluates success metrics, addresses maintenance and technical debt, and uses a retrospective to improve future work. section 10.3

A coordinated team effort

Treat the project like a sports team preparing for a game: clarify roles, train and plan together, track timing and milestones, then adapt when circumstances change. The project plan, risk list, dependencies, sprint ceremonies, and leadership visibility help the team coordinate toward shared objectives. section 10.0

Figure 10.1 The five phases of a project life cycle
figure

Use the five-phase figure as a quick visual map of the project’s progression from discovery through postexecution. section 10.1

How Think Like a Software Engineering Manager covers it

How deep it goes
Maps five phases and phase-specific responsibilities, while stopping short of detailed tool instructions or implementation mechanics.
Examples
Uses a sports-team analogy and examples involving road maps, sprint ceremonies, milestones, testing, defect triage, and technical debt.
What it assumes
Assumes basic familiarity with projects and team roles while defining the phases and responsibilities from the ground up.
What you can do after
Apply it to organize project plans, coordinate stakeholders, monitor risks and milestones, and guide retrospective improvement.
How it connects
Connects project planning with road maps, stakeholder management, risk management, resource allocation, project portfolio management, and retrospectives.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.