MODULE 1

Q1. What are the three basic goals of a project and how do project managers achieve them in conditions of uncertainty?
Project management revolves around three fundamental goals, collectively known as the Triple Constraints
of Project Management or the Project Management Triangle. These three constraints—Cost, Scope, and
Time—are interconnected, meaning that any change in one directly affects the others. Managing these
constraints effectively is crucial for project success.

Triple Constraints of Project Management

1. Cost (Budget Constraint)
o Represents the financial resources allocated to the project.
o Includes direct costs (e.g., labor, materials) and indirect costs (e.g., overhead expenses).
o A well-defined budget ensures the project remains financially viable.
2. Scope (Work Constraint)
o Defines the activities, deliverables, and objectives required to complete the project.
o Includes project requirements, milestones, and end-user expectations.
o Scope creep (uncontrolled expansion of project scope) can lead to budget overruns and
schedule delays.
3. Time (Schedule Constraint)
o Refers to the project’s duration and deadlines for each phase.
o Includes task dependencies, resource availability, and project milestones.
o Delays in one task can affect the entire project timeline.
Impact of Changes in One Constraint on Others
 If cost is reduced, either the scope must be decreased or the timeline extended.
 If scope increases, either cost must increase or time must be extended.
 If time is shortened, either cost increases (e.g., hiring more resources) or scope decreases.

Uncertainty in project management arises due to changing requirements, unforeseen risks, resource
constraints, and external factors. Project managers use the following strategies to achieve the three goals
despite uncertainties:
1. Cost Management
 Budget Planning – Estimating both fixed and variable costs, including labor, equipment, and
contingency reserves.
 Cost Control Techniques – Using Earned Value Management (EVM) to track budget deviations.
 Stakeholder Communication – Keeping clients and sponsors informed to manage expectations.
2. Scope Management
 Scope Definition and Planning – Creating a Scope Management Plan to define deliverables and
prevent scope creep.
 Change Control Mechanisms – Implementing formal change requests to assess the impact of
modifications.
 Task Management Tools – Using tools like Work Breakdown Structure (WBS) to track activities
effectively.
3. Time Management
 Project Scheduling – Using Gantt charts, Critical Path Method (CPM), and resource leveling to
allocate tasks.
 Monitoring Progress – Comparing actual progress against the baseline schedule and making
necessary adjustments.
 Risk Mitigation – Identifying potential bottlenecks and planning alternative approaches (e.g., fast-
tracking or crashing).
Achieving the Goals in Conditions of Uncertainty
 Risk Management
1. Identify & Analyze Risks
o Create a Risk Register listing threats and opportunities.
o Qualitative (probability/impact) and quantitative (expected monetary value) analyses.
2. Plan Responses
o Avoid, Mitigate, Transfer, Accept strategies.
o Allocate contingency reserves for known-unknowns and management reserves for
unknown-unknowns.
3. Monitor & Control
o Regular risk reviews; update the register; trigger response plans as needed.
 Scope Control
1. WBS & Scope Baseline
o Break project into work packages; define acceptance criteria.
2. Requirements Traceability Matrix
o Links each requirement to deliverables, ensuring nothing is lost or added inadvertently.
3. Formal Change Control
o All changes submitted via Change Requests, evaluated by a Change Control Board (CCB)
for impact on time/cost.
 Time Management
1. Schedule Modelling
o Critical Path Method (CPM) identifies the longest sequence of dependent tasks.
o PERT uses three-point estimates (optimistic, most likely, pessimistic) to handle
uncertainty in activity durations.
2. Compression Techniques
o Crashing: Add resources to critical activities (↑ cost).
o Fast-tracking: Perform sequential tasks in parallel (↑ risk).
3. Progress Monitoring
o Compare actual versus planned milestones; forecast Estimate at Completion (EAC) and
To-Complete Performance Index (TCPI).
 Cost Management
1. Earned Value Management (EVM)
o Track PV (Planned Value), EV (Earned Value), AC (Actual Cost).
o Calculate Cost Variance (CV = EV–AC) and Cost Performance Index (CPI = EV/AC).
2. Forecasting & Control
o Use EVM metrics to forecast EAC and drive corrective actions.
o Maintain contingency reserves and update based on risk realisations.
 Adaptive Delivery & Stakeholder Engagement
1. Iterative Approaches (Agile/Scrum)
o Break work into short sprints with fixed scope, time and cost for each sprint.
o Regular reviews and backlog reprioritization accommodate changing requirements.
2. Communication Plan
o Define stakeholder information needs, formats, frequency (e.g., weekly status reports,
demos).
o Early warning systems for issues, with clear escalation paths.
By integrating these strategies, project managers ensure that cost, scope, and time remain balanced,
delivering successful outcomes even under uncertain conditions.
Q2. Why project manager’s role is more of a facilitator rather than a supervisor?
A project manager (PM) plays a crucial role in ensuring a project’s success. While traditional supervisors
focus on controlling tasks and enforcing discipline, a project manager acts as a facilitator, enabling the team
to collaborate effectively, solve problems, and achieve project goals efficiently. This shift in role is essential,
especially in dynamic, cross-functional project environments.

Difference Between a Facilitator and a Supervisor

Aspect Supervisor Facilitator
Focus Direct control over employees Encourages collaboration
Authority Command-based leadership Influence-based leadership
Decision-Making Top-down approach Encourages team input
Team Engagement Employees follow orders Teams participate actively
Problem-Solving Gives solutions Guides teams to find solutions
A facilitator enables the team by providing the necessary tools, resources, and support to remove obstacles
rather than just giving direct orders.

Why a Project Manager Acts as a Facilitator

A. Encouraging Team Collaboration
 A project manager coordinates efforts among team members from different departments.
 Encourages open communication through meetings, brainstorming, and discussions.
 Uses team-building techniques to create a positive working environment.
B. Managing Stakeholder Expectations
 Acts as a bridge between executives, clients, and team members.
 Facilitates stakeholder meetings to align project goals and priorities.
 Ensures transparent communication about project progress and risks.
C. Problem-Solving and Decision-Making
 Encourages the team to propose solutions rather than just follow orders.
 Uses facilitation techniques like focus groups, SWOT analysis, and expert consultations.
 Helps teams resolve conflicts through negotiation and consensus-building.
D. Flexibility and Adaptability
 Unlike supervisors who enforce rigid rules, a facilitator adapts to changes in project scope, budget,
and timeline.
 Uses Agile, Scrum, or other iterative methodologies to handle uncertainties.
 Helps team members adjust to changing requirements and external factors.
E. Motivating and Empowering the Team
 Provides a supportive environment rather than just assigning tasks.
 Recognizes individual contributions to boost morale and productivity.
 Delegates responsibilities while ensuring team members have autonomy to make decisions.

Impact of a Facilitator Approach on Project Success

 Higher Team Efficiency: When team members are empowered, they take ownership of their tasks.
 Better Innovation & Problem-Solving: Teams can suggest creative solutions instead of just following
directives.
 Stronger Stakeholder Engagement: Encourages active participation from clients, executives, and
end-users.
 Lower Risk of Project Failure: By addressing issues early and keeping communication open, risks are
identified and mitigated quickly.
Q3. What is the project life cycle? How is the cost of change, risk, and influence of stakeholders affected
by Project time during the life cycle of the project? (Repeat x2)
The Project Life Cycle (PLC) is a structured sequence of phases that a project goes through from initiation to
closure. It provides a framework for managing tasks, resources, and risks throughout the project.

A typical project life cycle consists of the following phases:

 Initiation – Defining the project’s objectives and feasibility.
 Planning – Developing a roadmap, timelines, and resource allocation.
 Execution – Implementing project tasks and deliverables.
 Monitoring & Controlling – Tracking performance and making adjustments.
 Closure – Completing the project and assessing results.

Each phase has different levels of cost, risk, and stakeholder influence, which change as the project
progresses.
Phases of the Project Life Cycle
1. Initiation Phase
o Definition: The project’s purpose, feasibility, and high-level requirements are determined.
o Key Activities:
 Defining the business case and project objectives.
 Identifying stakeholders.
 Conducting a feasibility study.
 Developing a Project Charter.
o Impact on Cost, Risk & Stakeholders:
 Cost of Change – Low, as no major investments are made yet.
 Risk Level – High, as uncertainties are maximum due to lack of clarity.
 Stakeholder Influence – Maximum, as key decisions are made in this phase.

2. Planning Phase
o Definition: The project roadmap, including scope, schedule, and budget, is finalized.
o Key Activities:
 Developing the Work Breakdown Structure (WBS).
 Creating the Project Schedule.
 Budget estimation and resource planning.
 Identifying risks and preparing mitigation plans.
o Impact on Cost, Risk & Stakeholders:
 Cost of Change – Increasing, as changes affect detailed plans and resources.
 Risk Level – Starts decreasing as planning provides clarity.
 Stakeholder Influence – Still high, but decisions begin solidifying.

3. Execution Phase
o Definition: The actual work of the project is carried out, and deliverables are produced.
o Key Activities:
 Allocating resources and executing tasks.
 Monitoring progress against the Project Baseline.
 Managing team communication.
 Resolving issues and risks.
o Impact on Cost, Risk & Stakeholders:
 Cost of Change – Very high, as modifications at this stage involve rework.
 Risk Level – Moderate, as most risks have been identified and planned for.
 Stakeholder Influence – Reduced, as the project is in execution mode.
4. Monitoring & Controlling Phase
o Definition: Continuous tracking and evaluation of project performance.
o Key Activities:
 Tracking KPIs (Key Performance Indicators).
 Controlling budget deviations.
 Ensuring quality control.
 Mitigating risks proactively.
o Impact on Cost, Risk & Stakeholders:
 Cost of Change – Extremely high, as changes may lead to budget overruns.
 Risk Level – Low, as continuous monitoring keeps issues in check.
 Stakeholder Influence – Minimal, as decisions are mostly finalized.

5. Closure Phase
o Definition: The project is officially completed and handed over.
o Key Activities:
 Conducting a final review.
 Delivering the final product/service.
 Performing a post-mortem analysis to document lessons learned.
o Impact on Cost, Risk & Stakeholders:
 Cost of Change – Maximum, as changes require new projects or contracts.
 Risk Level – Very low, as the project is closing.
 Stakeholder Influence – Minimum, as their role is complete.

Project Phase Cost of Change Risk Level Stakeholder

Influence
Initiation Low High Maximum
Planning Moderate Medium High
Execution High Moderate Medium
Monitoring & Controlling Very High Low Low
Closure Maximum Very Low Minimum

 Cost of Change Increases Over Time

o In the early phases, changes are cheap and easy to implement.
o In later phases, changes require rework, additional resources, and financial losses.
 Risk Level Decreases Over Time
o At the start, uncertainty is highest, and risks are poorly understood.
o As the project progresses, risks are identified, mitigated, and controlled.
 Stakeholder Influence is Maximum at the Beginning
o In the Initiation and Planning phases, stakeholders make critical decisions.
o In later phases, most decisions are already made, reducing their direct influence.
Q4. Short note: Triple constraints in Project Management

In project management, the Triple Constraints—Scope, Time, and Cost—form the foundational framework
for defining project success. Often depicted as a triangle, these three elements are interdependent: a
change in one invariably impacts the others. Effectively managing these constraints is essential to delivering
a project within agreed parameters while maintaining the desired quality.

1. Scope Constraint
 Defines what work is to be completed and what the project will deliver (e.g., features,
functionalities, services).
 Documented through the Scope Baseline, which includes the Work Breakdown Structure (WBS),
scope statement, and deliverables.
 Poor scope management leads to scope creep, which can derail timelines and budgets.
2. Time Constraint
 Represents the schedule for completing the project activities and achieving milestones.
 Involves sequencing tasks, estimating durations, and assigning resources using tools like Gantt
charts, Critical Path Method (CPM), and PERT analysis.
 Delays in one activity can create cascading delays across the entire project.
3. Cost Constraint
 Refers to the budget allocated for completing the project, including direct and indirect costs (labor,
materials, overhead, etc.).
 Tracked and managed using techniques like Earned Value Management (EVM), which evaluates
Planned Value (PV), Earned Value (EV), and Actual Cost (AC).
 Budget overruns are common when time or scope changes aren't properly controlled.

4. Interdependence of Constraints
 The Triple Constraints are not isolated—they influence one another.
o Increasing scope typically increases cost and time.
o Reducing time may increase cost (e.g., overtime) or reduce scope.
o Cutting cost might mean reducing scope or extending deadlines.
Example: In a software development project, if a client requests new features (scope increase), the timeline
may need to be extended, or additional developers may be hired (increasing cost).

5. Role in Project Success

 The Performance Measurement Baseline combines scope, time, and cost plans, forming the
reference for tracking performance.
 Effective management ensures the project is delivered on time, within budget, and to the defined
scope, while maintaining quality.
 A project is often deemed successful only if all three constraints are balanced.