PadhaikoAll subjects

Project Integration Management

ICT Project Management (ENCT 412)

Open in the Padhaiko app

5.1 Develop project charter

Definition

Project Charter

Develop Project Charter is the Initiating process of creating a formal document that officially authorizes the existence of a project and grants the Project Manager authority to apply organizational resources to project activities.

Crucially, the Project Charter is issued and signed by a Project Sponsor or initiator external to the project team—not by the Project Manager alone.

Inputs, Tools & Techniques, and Key Contents

Essential Elements of an ICT Project Charter
Charter SectionWhat It Defines (ICT Example)
Project Purpose & Business CaseWhy the project is undertaken (e.g., reduce hospital patient check-in time by via a digital portal)
Measurable Objectives & Success CriteriaSMART targets (budget , go-live in months, uptime)
High-Level Requirements & Scope BoundariesCore features included and explicit exclusions (e.g., Phase 1 web + Android only; iOS deferred)
Summary Milestone Schedule & BudgetKey phase-gate dates and pre-approved funding ceiling
High-Level Risks & AssumptionsMajor uncertainties (e.g., third-party payment gateway API readiness)
Assigned PM & Authority LevelNames the Project Manager and specifies authority over staffing, procurement, and budget
Sponsor Approval Sign-OffFormal signature authorizing project launch and resource expenditure

5.2 Develop project management plan

Definition

Project Management Plan

Develop Project Management Plan is the Planning process of defining, preparing, and coordinating all subsidiary plans and integrating them into a single comprehensive master document—the Project Management Plan (PMP).

The PMP defines how the project is executed, monitored and controlled, and closed.

Core Components of the Project Management Plan

  1. Subsidiary Management Plans: Scope, Requirements, Schedule, Cost, Quality, Resource, Communications, Risk, Procurement, and Stakeholder engagement plans.
  2. Performance Measurement Baselines (PMB):
    • Scope Baseline: Project Scope Statement + WBS + WBS Dictionary.
    • Schedule Baseline: Approved version of the project schedule model.
    • Cost Baseline: Approved time-phased budget (excluding management reserves).
  3. Governance & Tailoring Plans:
    • Change Management Plan: Defines how formal change requests are submitted, evaluated, and approved.
    • Configuration Management Plan: Controls versioning of code, hardware specs, and baseline documents.
    • Life Cycle & Development Approach: Specifies Waterfall, Iterative, Agile, or Hybrid delivery rules.
AspectProject CharterProject Management Plan
Process GroupInitiatingPlanning
Primary Author / SignerWritten/signed by Project SponsorCreated by Project Manager & Team, approved by key stakeholders
Level of DetailHigh-level vision, objectives, summary budget/milestonesDetailed baselines, WBS, schedules, subsidiary plans, control rules
PurposeAuthorizes project & PM authorityGuides execution, monitoring, control, and closure
Change FrequencyRarely changed once approvedProgressively elaborated and updated via Integrated Change Control

5.3 Direct and manage project execution

Definition

Direct and Manage Project Execution

Direct and Manage Project Execution (also called Direct and Manage Project Work) is the Executing process of leading and performing the work defined in the Project Management Plan and implementing approved changes to achieve project objectives.

Major Activities Performed During Execution


5.4 Monitor and control project work

Definition

Monitor and Control Project Work

Monitor and Control Project Work is the continuous process of tracking, reviewing, and reporting overall project progress to meet the performance objectives defined in the Project Management Plan.

Key Functions

  1. Comparing Actuals Against Baselines: Transforming raw Work Performance Data (from Executing) into analyzed Work Performance Information (schedule variance, cost variance, defect trends) and formatted Work Performance Reports (status dashboards, EVM summaries).
  2. Forecasting: Projecting future completion dates (Estimate at Completion, ) and remaining resource needs based on current trends.
  3. Initiating Change Requests: Whenever variance exceeds tolerance thresholds or preventive action is needed, submitting formal Change Requests into Integrated Change Control.

5.5 Integrated change control

Because scope, schedule, cost, quality, and risk are tightly coupled, changing one area without checking the others causes silent baseline failure.

Definition

Perform Integrated Change Control

Perform Integrated Change Control is the Monitoring & Controlling process of reviewing all change requests, approving changes, and managing changes to deliverables, OPAs, project documents, and the Project Management Plan—and communicating those decisions.

Standard Change Control Workflow

  1. Log Change Request: Every requested change (scope addition, schedule slip, defect fix, preventive action) is documented in a Change Log—never implemented informally.
  2. Impact Analysis: The PM and technical leads evaluate how the change affects Scope, Schedule, Cost, Quality, Resources, and Risk.
  3. Review & Decision (CCB): Minor changes within PM tolerance may be decided by the PM; baseline-altering changes go to the Change Control Board (CCB) or Sponsor for approval, deferral, or rejection.
  4. Update Baselines & Communicate: Approved changes update the PMP baselines and configuration records, and are communicated to the team for execution.

Configuration Management Activities


5.6 Close project or phase

Definition

Close Project or Phase

Close Project or Phase is the final Closing process of finalizing all activities for the project, phase, or contract—verifying that exit criteria are met, transferring the product to operations, archiving organizational knowledge, and releasing project resources.

Key Closure Checklist

  1. Confirm Final Acceptance: Verify all deliverables passed Scope Verification and Quality Control, and obtain formal written Client / Sponsor Sign-Off.
  2. Close Contracts & Procurements: Settle final vendor invoices, confirm warranty/SLA terms, and archive contract closure notices.
  3. Transition to Operations: Hand over source code, runbooks, credentials, monitoring dashboards, and user training manuals to the IT operations/support team.
  4. Capture Lessons Learned: Document what worked, what failed, estimation accuracy, and risk responses into Organizational Process Assets (OPAs).
  5. Release Team & Archive Records: Complete performance feedback, release staff to new assignments, and close financial cost centers.

Worked Out Examples

Example 5.1

5.1

Project Charter Financial Justification (NPV, ROI, and Payback Period): Before signing the Project Charter for an automated cloud billing platform, the Project Sponsor requires a financial check at a discount rate of per year. The project demands an upfront investment of at and generates net cash inflows of in Year 1, in Year 2, and in Year 3.

  1. Calculate the Net Present Value ().
  2. Compute the discounted Return on Investment ().
  3. Compute the undiscounted Payback Period and recommend whether the Sponsor should sign the charter.

Discounting each year's cash inflow at :

Total Present Value of inflows:

Subtracting the initial investment :

Computing discounted ROI and undiscounted Payback Period:

For undiscounted Payback Period:

  • End of Year 1 cumulative inflow (remaining ).
  • End of Year 2 cumulative inflow (remaining ).
  • Fraction of Year 3 needed .

Because and , the project is financially viable and the Sponsor should authorize the Project Charter.

Answer:
  1. ().
  2. Discounted .
  3. Payback Period . The Sponsor should approve and sign the Project Charter.
Example 5.2

5.2

Integrated Change Control Impact Analysis: Midway through an e-commerce portal project (baseline budget , baseline schedule , PM single-change approval limit or ), the marketing head asks a developer directly to add a custom AI product-recommendation widget. The developer estimates it will take engineers for at per engineer-day, plus in third-party API credits, and will push the critical-path launch date back by .

  1. Compute the total cost impact and percentage budget increase of this change.
  2. Outline the exact Integrated Change Control steps the team must follow, and state who holds authority to approve or reject this request.

Quantifying cost and schedule impact:

Schedule impact on the critical path.

Integrated Change Control workflow and approval authority:

  1. Do Not Code Informally: The developer must reject the informal verbal request and direct it through the PM.
  2. Log & Analyze: The PM logs a formal Change Request in the Change Log and documents the () cost impact, launch delay, and API dependency risk.
  3. Escalate to CCB: Because both the cost impact () and schedule impact () exceed the PM's delegated threshold, the request must be submitted to the Change Control Board (CCB) / Project Sponsor for decision.
  4. Baseline Update (if approved): Update Scope, Schedule, and Cost baselines and version-control the updated PMP before assigning work.
Answer:
  1. Change cost (new budget , ), plus schedule delay.
  2. The developer must not start informally; the PM logs the request, performs impact analysis, and escalates to the CCB / Sponsor (since and ).

Exercises

Practice Exercises — Project Integration Management

Question 1

What is a Project Charter, who issues it, and why is it essential before project planning or execution begins? List five key items included in an ICT Project Charter.

Definition, issuer, and importance: A Project Charter is a formal document issued and signed by the Project Sponsor (or initiator external to the project team) that officially authorizes the project and gives the Project Manager authority to assign organizational resources. Without a charter, a project lacks formal funding, executive backing, and clear scope boundaries.

Five key contents of an ICT Project Charter:

  1. Project purpose and business case justification.
  2. Measurable project objectives and success criteria.
  3. High-level requirements, scope boundaries, and major risks.
  4. Summary milestone schedule and pre-approved budget.
  5. Assigned Project Manager, authority level, and Sponsor sign-off.
Answer:

A Project Charter is issued by the Project Sponsor to formally authorize a project and grant the PM authority over resources. It contains the business case, measurable objectives, high-level scope/risks, summary budget/milestones, and Sponsor sign-off.

Question 2

Distinguish between a Project Charter and a Project Management Plan (PMP). Explain the role of the three Performance Measurement Baselines inside the PMP.

Charter vs. PMP: The Project Charter (Initiating) is a high-level authorization document signed by the Sponsor, whereas the Project Management Plan (Planning) is a detailed master plan prepared by the PM and team specifying how the project will be executed, monitored, controlled, and closed.

Role of the three Performance Measurement Baselines:

  • Scope Baseline (Scope Statement + WBS + WBS Dictionary), Schedule Baseline, and Cost Baseline form the integrated reference standard against which actual progress is measured during Monitor and Control Project Work. Any change to these baselines requires formal Integrated Change Control.
Answer:

The Charter authorizes the project at a high level (Initiating), while the PMP integrates all subsidiary plans and the three Performance Measurement Baselines (Scope, Schedule, Cost) to guide execution and variance control.

Question 3

Explain Perform Integrated Change Control and distinguish among Corrective Action, Preventive Action, and Defect Repair. What role does the Change Control Board (CCB) play?

Integrated Change Control and CCB: Perform Integrated Change Control reviews every requested change across all baselines (Scope, Time, Cost, Quality, Risk) before approving or rejecting it, ensuring no single change silently breaks another constraint. The Change Control Board (CCB) is the formally chartered governance group responsible for reviewing, approving, deferring, or rejecting baseline-impacting change requests.

Three types of approved change actions:

  • Corrective Action: Intentional activity that realigns future project performance with the PMP (recovering from an existing variance).
  • Preventive Action: Intentional activity that lowers the probability of negative future performance variance (proactive risk reduction).
  • Defect Repair: Intentional activity to modify or fix a non-conforming product component.
Answer:

Integrated Change Control evaluates cross-constraint impacts of all change requests, with major baseline changes decided by the CCB. Corrective actions fix future alignment after a variance, preventive actions avert anticipated problems, and defect repairs fix non-conforming deliverables.

Question 4

Describe the key activities performed during Close Project or Phase. Why is formal closure still mandatory if an ICT project is cancelled midway?

Key closure activities:

  1. Obtain formal written client/sponsor acceptance of deliverables.
  2. Close all vendor contracts and settle final payments.
  3. Hand over documentation, codebases, and operational support runbooks.
  4. Capture and archive lessons learned in OPAs.
  5. Release team members and close project accounts.

Why closure applies to cancelled projects: If a project is terminated early, formal closure documents the exact completion state, settles vendor obligations cleanly, preserves reusable software/hardware assets, and records the root causes of cancellation so future projects avoid the same mistakes.

Answer:

Close Project or Phase secures formal acceptance, closes contracts, transitions deliverables, archives lessons learned, and releases resources. Even cancelled projects must go through closure to settle contracts, preserve reusable assets, and document termination reasons.

Question 5

An IT services firm evaluates a Project Charter for a campus Wi-Fi automation tool requiring an upfront cost of () with net inflows of (Year 1), (Year 2), and (Year 3) at a discount rate.

  1. Compute the and discounted .
  2. Compute the undiscounted Payback Period and state whether the project passes financial selection.

Calculating Present Values and at :

Calculating discounted and undiscounted Payback Period:

For undiscounted Payback Period:

  • Year 1 cumulative ; Year 2 cumulative .
  • Remaining in Year 3 .
  • Fraction of Year 3 .

Because , the project passes financial selection.

Answer:
  1. , .
  2. Payback Period (). Yes, the project passes financial selection ().
← Project Management Process GroupsProject Scope Management →