Project Management Deliverables relating to Project Lifecycle

Project management deliverables are the tangible or intangible outputs—products, services, or documents—produced as a result of project activities. They are specific, measurable, and agreed upon by stakeholders to demonstrate progress toward project goals.

Overview of Project Deliverables

Deliverables are essential for breaking down project goals into manageable components, tracking progress, and ensuring stakeholder alignment.

Types of Deliverables:

  • Internal Deliverables: Created for internal use, such as team charters, project plans, and risk logs.
  • External Deliverables: Client-facing, such as a finished software product, marketing campaign, or project report.
  • Process Deliverables: Interim outputs that mark progress, such as prototypes, wireframes, or testing reports.
  • Product Deliverables: The final, completed goods or services delivered.
  • Tangible vs. Intangible: Physical/digital items (e.g., machinery) vs. conceptual outcomes (e.g., a new training program).

Textual/Documentation Deliverables Project Lifecycle

The project lifecycle defines the stages a project goes through from start to finish. Textual and documentation deliverables are key to managing and controlling these stages.

1. Initiation Phase (Initiating)

  • Goal: Define the project at a high level and obtain authorization.
  • Key Deliverables:
    • Business Case: Why the project is needed.
    • Feasibility Study: Whether the project is achievable.
    • Project Charter: A formal document outlining objectives, scope, and key stakeholders.

2. Planning Phase (Planning)

  • Goal: Develop a roadmap for project execution and define constraints.
  • Key Deliverables:
    • Project Management Plan: A comprehensive document (roadmap) detailing tasks, timelines, and resources.
    • Scope Statement/WBS: Defines boundaries and breaks down work.
    • Communication Plan: Strategy for stakeholder communication.
    • Risk Register: Identifies potential threats and mitigation strategies.

3. Execution Phase (Executing)

  • Goal: Carry out the work defined in the plan to produce deliverables.
  • Key Deliverables:
    • Interim Products/Prototypes: Tangible outputs produced.
    • Meeting Minutes/Notes: Documentation of decisions and action items.
    • Change Requests: Documents updating scope or plan.

4. Monitoring and Controlling Phase

  • Goal: Measure performance against the plan and adjust as needed.
  • Key Deliverables:
    • Status Reports: Progress updates on key performance indicators (KPIs).
    • Quality Control Reports: Results of testing and validation.
    • Updated Project Schedule: Reflects current progress.

5. Closing Phase (Closure)

  • Goal: Formally accept deliverables and close out the project.
  • Key Deliverables:
    • Final Product/Report: The completed output.
    • Project Closure Report: Confirms final deliverables and contract closure.
    • Lessons Learned Document: Records successes and areas for improvement.

Best Practices for Managing Deliverables

  • Define Early: Ensure all stakeholders agree on what “done” means at the start.
  • Use Tools: Employ PM software (e.g., Asana, Jira, Monday.com) to track deliverables.
  • Assign Owners: Each deliverable should have a single, clear owner to ensure accountability.
  • Link to KPIs: Connect deliverables to key performance indicators to measure value.

Project Management Deliverables relating to Project Lifecycle

Unknown's avatar

Author: Mark Whitfield

Welcome to my site! After graduating in Computing in 1990, I accepted a position as a programmer at a Runcorn based software house specialising in electronic banking software, namely sp/ARCHITECT-BANK on Tandem Computers (now HPE NonStop). This was before the internet became more prevalent and so the notion of enabling desktop access to company accounts for inter-account transfers and book keeping was still quite a cutting edge idea (and smartphones only ever hinted at in Space 1999). The company was called The Software Partnership (which was taken over by Deluxe Data in 1994). I spent 5 years in Runcorn developing code for SP/ARCHITECT for various banks like TSB, Bank of Scotland, Rabobank and Girofon (Denmark) to name but a few. I then moved onto a software house in Salford Quays for further bank facing projects. After a further 23 years in the IT industry and now a Senior IT Project Manager (both Agile and Waterfall delivery), I thought I would echo out my Career Profile in this corner of the internet for quick and easy access.

Leave a comment