Tasleemat Forms Guide

Project Artifact: Change Request

Document Reference: PMO-05.03

This document provides a comprehensive, professional reference to understand the purpose and effective usage of the Change Request in alignment with the Tasleemat framework.

1. What?

A standardized form capturing full justification and impact analysis for proposed modifications.

2. Why?

Ensures changes are rigorously evaluated before approval to protect project scope, budget, and timeline.

3. When?

Submitted whenever a baseline adjustment or scope modification is identified during execution.

4. Who?

Submitted by any stakeholder or team member, evaluated by the Project Manager, and approved by CCB.

Tailoring Tips

Include precise schedule and cost impact estimates before submitting to CCB.
Attach updated architectural or technical specs to support evaluation.

Alignment & Dependencies

1. Pre-requisites & Inputs (Upstream Dependencies)

Mandatory:
- Project Management Plan (PMO-04.01.01)
- Approved Baselines: Scope (PMO-04.02.05), Schedule (PMO-04.03.08), Cost (PMO-04.04.04)
Optional / Contextual:
- Risk Register (PMO-04.08.02)
- Stakeholder Engagement Plan (PMO-04.10.01)

2. Downstream Dependents

Mandatory:
- Project Status Report (PMO-06.01)
- Change Log (PMO-05.04)
- Lessons Learned Summary (PMO-07.01)
Optional / Contextual:
- Variance Analysis (PMO-06.04)
- Decision Log (PMO-05.02)

5. How?

To accurately and professionally complete the Change Request, the responsible party must populate the following critical sections based on the project context (ensure parameters.md is referenced for global project variables):

Requestor Name and Position: The name and organizational role or position of the person submitting the change request.
Change Category: The specific project dimension affected (e.g., Scope, Schedule, Cost, Quality, Resource).
Change Type: Indicates whether the change is mandatory (legal/compliance) or discretionary.
Description of Change: Comprehensive narrative detailing the requested modification or enhancement.
Justification for Proposed Change: The business driver, operational trigger, or rationale justifying the change.
Implications of Not Making the Change: Risks, costs, operational penalties, or missed opportunities if the change is rejected.
Impacts of Change: Detailed assessment of impacts across scope, schedule, budget, risks, and contracts.
Comments: Additional context, dependencies, or evaluation notes.

6. Reference Example

A fully completed, gold-standard reference example illustrating this artifact in practice is available:

📖 Completed Example: 05_03_Change_Request_Example.md