Diploma in Management (D3MNGT) – Project Management Subjects Notes (CPUT Cluster)

These Diploma in Management (D3MNGT) notes focus on Project Management subjects typically examined in the CPUT learning environment and aligned with how project management is taught across South African universities. The emphasis is on what you must know, apply, and write in exams: project life cycle, planning tools, risk and cost control, scheduling, quality, procurement, stakeholder management, and basic governance. Each section is written to support both short-answer and long-explain questions with practical examples and exam-ready frameworks.

CPUT Cluster 1: Project Management Foundations for D3MNGT (CPUT-style Exam Notes)

A strong project management foundation is essential because most later topics—scheduling, cost control, risk, quality, procurement—depend on the same core concepts. Examiners often test whether you understand projects as temporary endeavours with constraints (time, cost, scope), and whether you can logically connect the life cycle with planning and execution.

Meaning of a Project vs. Operations

A project is a temporary endeavour undertaken to create a unique result. In contrast, operations are ongoing and repetitive (e.g., daily transport services, routine customer support). The “temporary” aspect is not just the start and end dates—it is also about the changing needs, evolving risks, and the fact that resources and plans are refined as the project progresses.

Key differences examiners look for:

• Uniqueness: Projects create something different each time.
• Temporary: They have a defined beginning and end (even if the end is later than planned).
• Constraints: Projects are planned under constraints of scope, time, and cost.
• Progressive elaboration: Detailed planning improves as more information becomes available.

Example (Operations vs Project)

• Operations: A hospital’s daily supply of bandages and routine patient rounds.
• Project: Introducing a new electronic patient record system, training staff, migrating data, and ensuring compliance by a specific deadline.

The Project Life Cycle (Overview + Why It Matters)

A project life cycle describes stages from initiation to close-out. A common exam-friendly sequence is:

1. Initiation
2. Planning
3. Execution (Implementation)
4. Monitoring & Controlling
5. Closing

You should be able to describe what happens in each stage and identify typical outputs.

Initiation: Turning an idea into a project

At initiation, you clarify:

• The business need or problem
• High-level objectives
• Stakeholders
• Feasibility and risks at a high level

Outputs often include:

• Project charter / assignment document
• High-level scope
• Initial stakeholder analysis

Planning: Defining “how” and “what”

Planning is the stage where you reduce uncertainty and set baselines:

• Scope definition
• Schedule development
• Budgeting and cost estimation
• Risk management planning
• Quality planning
• Communication plan
• Procurement plan (if needed)
• Resource planning

A key exam concept is that planning produces plans and baselines:

• Scope baseline
• Schedule baseline
• Cost baseline
  These are used later for variance analysis.

Execution: Doing the work

Execution includes:

• Resource mobilization
• Implementing plans
• Managing quality
• Team coordination
• Stakeholder engagement

Execution should not be described as “doing tasks only.” It includes coordination, communication, and handling changes.

Monitoring & Controlling: Measuring performance

Monitoring & controlling runs throughout the life cycle. It answers:

• Are we on schedule?
• Are we within budget?
• Are we meeting quality requirements?
• How are risks changing?
• Are stakeholders satisfied?

Closing: Formal acceptance and lessons learned

Closing ensures:

• Deliverables are accepted
• Documentation and audits are completed
• Contract closure (where relevant)
• Lessons learned are captured

The Triple Constraint and Project Trade-offs

Most D3MNGT exam questions link the triple constraint to real decisions. The triple constraint is:

• Scope (what must be delivered)
• Time (when it must be delivered)
• Cost (how much money it can use)

If one changes, at least one of the others must change.

Example: scope increase vs time/cost

A municipality wants an additional service included in a tender:

• If scope increases and time is fixed, cost usually rises.
• If scope increases and cost is fixed, time may increase or quality may be compromised.

In answers, show that trade-offs must be managed through change control and stakeholder agreement.

Stakeholders: Who matters and why

Stakeholders are any individuals or organizations that affect or are affected by the project. In a management diploma project management context, you are expected to classify stakeholders and explain engagement strategies.

Common stakeholder categories:

• Sponsor: funds and supports the project at governance level
• Project manager: coordinates planning/execution and reporting
• Team members: execute tasks and provide technical input
• Customers/users: receive the deliverable
• Suppliers/contractors: provide goods/services
• Regulators/authorities: ensure compliance
• Community/public: affected by the project’s impacts

Power/Interest Matrix (Exam-ready)

A typical approach:

• High power, high interest → manage closely
• High power, low interest → keep satisfied
• Low power, high interest → keep informed
• Low power, low interest → monitor with minimal effort

Example in a retail store refurbishment

• Sponsor (store owner): high power/high interest
• Employees: medium power/high interest
• Local council: high power/low interest (compliance inspections)
• Nearby customers: low power/high interest (affected by access and noise)

Project Governance and Decision-Making

Governance is the framework that controls how decisions are made, how risks are escalated, and how the project remains aligned to organizational goals. In exam answers, governance is often implied through:

• reporting structures,
• steering committees,
• approval processes,
• stage gates or milestones,
• documented sign-offs.

For D3MNGT, it is useful to connect governance with:

• authority to approve changes,
• how progress is reported,
• how issues are resolved.

Common Project Management Processes (High-level list)

You do not need to memorize every standard term, but you must show exam knowledge of the broad process areas:

• Project integration management: integrating all plans and managing changes
• Scope management: defining and controlling what is included/excluded
• Schedule management: planning and controlling timeline
• Cost management: budgeting and controlling expenditure
• Quality management: ensuring deliverables meet requirements
• Resource management: acquiring and developing team resources
• Communications management: distributing information effectively
• Risk management: identifying, analysing, responding, monitoring risks
• Procurement management: acquiring resources from external providers
• Stakeholder management: engaging people appropriately

Exam Writing Strategy for Foundations Questions

When asked “Explain project management” or “Differentiate project vs operations,” use this exam structure:

1. Define clearly
2. Give at least one real-life example
3. Explain why it matters
4. Use key terms (life cycle, constraints, stakeholders, baselines, trade-offs)

If you also connect to management decisions (budget approvals, stakeholder conflict, trade-offs), your answer appears deeper and more relevant.

CPUT Cluster 2: Scope, WBS, Scheduling, and Budgeting for D3MNGT

Most project management exam papers in a management diploma level test whether you can produce logical planning outputs and interpret them. This section focuses on scope management, Work Breakdown Structure (WBS), scheduling, and cost estimation/budgeting—the planning backbone of any project.

Scope Management: Define, Break Down, Control

Scope refers to the boundaries of the project: what work must be completed to produce the required deliverables. Scope management ensures the project does not “drift” beyond what was agreed.

Scope planning

You plan how scope will be defined and verified. Outputs:

• Scope statement
• assumptions and constraints
• stakeholder input

Scope definition

You detail the deliverables and acceptance criteria. You should show:

• what will be delivered,
• key requirements,
• exclusions (important for preventing scope creep).

Create WBS from the scope

You transform the scope statement into manageable components.

Scope verification & control

• Verification: formal acceptance of completed deliverables
• Control: manage changes to scope using change control procedures

Work Breakdown Structure (WBS): The Exam Core Tool

A WBS decomposes the total scope into smaller components. The goal is not just structure—it enables:

• easier cost and schedule estimation,
• assigning responsibilities,
• monitoring progress.

WBS Rules of Thumb (use in answers)

• Use deliverable-based decomposition where possible
• Ensure components are mutually exclusive (no overlap)
• Ensure coverage: WBS parts add up to the full scope
• Define each work package with enough clarity for estimating

Example: WBS for a “Customer Feedback System” project

Deliverable: A system for collecting and analysing customer feedback.

Possible WBS at a simple level:

1. Project Management
   • 1.1 Project initiation and charter
   • 1.2 Reporting and stakeholder communication
2. System Requirements
   • 2.1 Gather requirements
   • 2.2 Document requirements
3. Design
   • 3.1 User interface design
   • 3.2 Data model design
4. Development
   • 4.1 Build data collection form
   • 4.2 Build database and analytics
   • 4.3 Integration with website
5. Testing
   • 5.1 Functional testing
   • 5.2 User acceptance testing
6. Training & Rollout
   • 6.1 Training staff
   • 6.2 Rollout and monitoring
7. Closure
   • 7.1 Final documentation
   • 7.2 Lessons learned

In exam answers, if a question asks you to “construct a WBS,” you must show logical decomposition and numbering.

Scope Creep: Causes and Prevention

Scope creep is uncontrolled expansion of scope without adjusting cost or time baselines.

Common causes:

• unclear requirements at initiation
• stakeholder changes not managed formally
• lack of acceptance criteria
• weak change control
• informal requests treated as “small extras”

Prevention strategies:

• clear scope statement and exclusions
• WBS and deliverable acceptance criteria
• change control process (requests, impact analysis, approvals)
• regular scope verification meetings

Example (scope creep)

A project to deliver a “small office renovation” begins as:

• paint and flooring replacement
  Later, clients request:
• additional partitions
• new ceiling lights
  Without revised budget/time, the project overruns.

In exam answers, emphasize baseline and change control.

Scheduling: From Activities to Timelines

A schedule is not just dates—it is the planned sequence and duration of work.

Steps to create a basic schedule

1. Identify activities (from WBS work packages)
2. Estimate duration
3. Determine dependencies (predecessor/successor relationships)
4. Build network logic
5. Calculate start and finish dates (forward pass)
6. Calculate latest dates (backward pass)
7. Identify critical path (for advanced questions)
8. Finalize schedule baseline and monitor variance

Dependencies and Why They Matter

Dependencies show logical relationships:

• Finish-to-Start (FS): Activity B cannot start until A finishes (most common)
• Start-to-Start (SS): B can start when A starts
• Finish-to-Finish (FF): B finishes when A finishes
• Start-to-Finish (SF): rare and usually not used

In exam questions, they may provide dependency statements and ask for scheduling implications.

Example dependencies

• “Testing starts after development completes” → FS dependency
• “Training starts when materials are ready” → could be FS depending on whether training needs completion or partial readiness

Critical Path Method (CPM) / Basic Scheduling Logic

If your exam includes CPM basics, you should know:

• The critical path is the longest path in the network that determines project duration.
• Activities on the critical path have zero float (or minimal float); delays directly delay the project completion.

Even without detailed float calculations, you should understand the concept:

• if you delay a non-critical activity, the project may still meet deadline due to slack.
• if you delay critical activities, deadline moves.

Gantt Charts: Common and Understandable

A Gantt chart is a visual timeline showing start/finish dates of activities. It is popular for management reporting because:

• easy communication
• helps track progress
• shows overlaps and delays

A Gantt chart typically includes:

• activity names
• start date
• finish date
• duration
• progress percentage (if updated)

In exam settings, you may be asked to “draw a Gantt chart” or “explain how you would use it.”

Cost Estimation and Budgeting: What to Include

Cost management includes:

• estimate costs
• determine budget (cost baseline)
• control costs

Cost estimation methods (exam-level)

• Analogous estimating: using similar past projects
• Parametric estimating: using statistical relationships (e.g., cost per square metre)
• Bottom-up estimating: sum of detailed work package estimates (most accurate)

For D3MNGT, you can score well by:

• naming the methods,
• giving a brief advantage/disadvantage,
• describing when each method is used.

Example: parametric estimate for construction-like work

If a refurbishment costs R3,500 per square metre, and the area is 80 m², estimated cost:

• 80 × 3,500 = R280,000

If you use this figure anywhere later, keep it consistent.

Budgeting with a Worked Example (Consistent Numbers)

Let’s build a compact budgeting example that can also support exam numeric questions.

Assume a project “School Career Day Platform” requires three cost categories:

Cost Category	Estimated Amount (R)
Labour (design + build + setup)	120,000
Software/Tools (licenses + hosting setup)	45,000
Contingency/Uncertainty allowance	15,000
Total Project Budget	180,000

Total budget: R180,000.

Interpreting contingency

Contingency is not profit; it is an allowance for known unknowns. In exam answers:

• explain that contingency is part of the baseline unless removed via change control,
• show it helps absorb small overruns without immediate escalation.

Cost Baseline and Variance Thinking

A cost baseline is the agreed expected cost schedule over time. When costs occur, you compare actuals to expected values.

For theory questions, you should state:

• if actual costs > planned costs, variance exists,
• corrective actions depend on severity and cause:
  • efficiency improvement,
  • re-planning,
  • change requests,
  • renegotiation with vendors.

CPUT Cluster 3: Risk, Quality, Communication, and Change Control (Real Exam Applications)

Many D3MNGT project management exam questions reward students for connecting theory to managerial decisions. This section develops risk management, quality management, communication, and change control. The goal is to help you write structured answers with practical impacts.

Risk Management: Identify, Analyse, Respond, Monitor

A risk is an uncertain event or condition that, if it occurs, has an effect on objectives (time, cost, scope, quality, safety).

Risk identification methods

Common approaches:

• brainstorming with team and stakeholders
• expert judgement
• checklists from past projects
• SWOT analysis (strengths/weaknesses/opportunities/threats)
• reviewing historical incidents
• assumption and constraint reviews

Risk analysis: qualitative and quantitative

• Qualitative risk analysis: rank risks by likelihood and impact (often using a matrix)
• Quantitative risk analysis: assign numbers (probabilities, expected monetary values, etc.)

At diploma level, qualitative is often sufficient, but you must still show logic in your ranking.

Risk Matrix (Exam-friendly explanation)

A risk matrix typically uses:

• Likelihood (e.g., Low, Medium, High)
• Impact (e.g., Low, Medium, High)

Then classify:

• high likelihood/high impact → top priority
• low/low → monitor

Example risk matrix scenario

For a “Municipal Water Billing System” upgrade:

1. Data migration errors
   • Likelihood: Medium
   • Impact: High
   • Priority: high
2. Staff training delay
   • Likelihood: Low-Medium
   • Impact: Medium
   • Priority: medium
3. Supplier late delivery of hardware
   • Likelihood: Medium
   • Impact: High
   • Priority: high

Risk Responses: Avoid, Mitigate, Transfer, Accept

You must know response strategies and when to use them.

Avoid

Change plans to eliminate the risk.

• Example: choose a vendor with proven migration experience rather than an untested supplier.

Mitigate

Reduce likelihood or impact.

• Example: run test migrations in a sandbox environment.

Transfer

Move risk to another party (insurance, contractual terms).

• Example: include delivery penalties in vendor contract.

Accept

Accept the risk and prepare contingency if it happens.

• Example: if a non-critical report fails, there is a fallback manual process.

Trigger-based contingency: writing like a manager

In exams, it helps to mention triggers. A trigger is an event/condition that signals the risk is materializing.

Example:

• Risk: “Supplier hardware delayed.”
• Trigger: “Hardware not received by week 2 of setup phase.”
• Response: “Switch to alternative vendor stock for testing and adjust installation schedule.”

This shows maturity and makes your answer more than generic definitions.

Quality Management: Meeting Requirements, Not Just “Doing Work”

Quality management ensures deliverables meet specified requirements. In many exam questions, quality is not defined as “polishing”; it includes:

• meeting technical specifications,
• meeting user expectations,
• compliance with standards,
• defect prevention and correction.

Quality planning

Quality planning answers:

• What quality standards apply?
• What checks are needed?
• Who is responsible for inspection/approval?

Quality assurance vs quality control

• Quality assurance: process-focused; prevent problems (audits, compliance checks)
• Quality control: product-focused; detect defects (testing, inspections)

Example: software project

• QA: define coding standards and review processes; run periodic audits.
• QC: perform functional testing and user acceptance testing.

Quality Metrics and Acceptance Criteria

Acceptance criteria define what “done” means for a deliverable. Exam questions may ask you to “define acceptance criteria” or “explain how to verify.”

For example, for a training module:

• Completion rate for trainees: at least 95%
• Post-test average score: at least 75%
• Training feedback rating: minimum 4/5

If you use metrics in answers, ensure they are consistent within the answer.

Managing Defects: Root Cause Thinking

Examiners often want you to show that defects aren’t just fixed—they are analysed to prevent recurrence.

Simple root-cause logic:

• Identify the defect
• Determine where in the process it was introduced
• Analyse causes (people, process, tools, environment)
• Apply corrective actions (fix) and preventive actions (improvement)

Communication Management: Plans, Channels, and Reporting

Project communication ensures information flows between stakeholders appropriately. Communication failure often causes:

• misunderstanding of scope,
• delayed decisions,
• unresolved issues escalating.

Communication planning

You decide:

• what information to share,
• with whom,
• how often,
• through which channel,
• who is responsible.

Communication channels

• meetings (status meetings, steering committee)
• emails and reports
• dashboards
• minutes and action logs
• presentations
• documented change requests

Status Reporting: A Practical Structure

A well-structured status report commonly includes:

• project progress vs plan
• schedule performance (what finished, what is next)
• cost status
• risks and issues summary
• decisions needed / action items

In exam answers, you can present an “ideal” status report template and describe why each part matters.

Change Control: The Heart of Integration Management

Change control manages modifications to scope, schedule, cost, quality, or other project baselines. This is essential to prevent unmanaged changes (scope creep) and to keep governance aligned.

Change request process (exam model)

1. A change is identified (request or issue)
2. Document the change request (description + rationale)
3. Assess impact:
   • time impact,
   • cost impact,
   • scope impact,
   • quality impact,
   • risk impact.
4. Decision:
   • approve,
   • reject,
   • defer,
   • request more info.
5. Implement approved change
6. Update baselines and communicate decisions
7. Monitor outcomes

Example: change request

A project budget is R180,000 (as earlier). A new requirement adds:

• additional testing effort costing R12,000
  Impact:
• cost increases by R12,000 (and baseline must update)
• schedule might require additional two days if labour is limited

In an exam answer, show that:

• the PM does not approve unilaterally if governance rules require sponsor/steering approval,
• the PM updates documentation and stakeholders.

Dealing with Conflict: Stakeholder Management Link

Changes often trigger stakeholder conflict:

• users want more features
• sponsor wants deadline and budget adherence
• team wants workable scope

A good exam response ties change control to stakeholder engagement:

• explain the trade-off,
• present impacts clearly,
• document decisions,
• maintain transparency.

CPUT Cluster 4: Procurement, Contracts, Resource Management, and Stakeholder Engagement

Project management in the diploma level context often includes procurement and resource planning because many projects depend on external parties (suppliers, contractors) and internal capacity (people with skills). This section supports exam answers by connecting procurement processes with governance and project risk.

Procurement Management: Make-or-Buy Decisions

Procurement refers to obtaining products, services, or results from outside the project organization.

Make-or-buy logic

You decide whether to:

• produce internally,
• outsource.

Criteria include:

• cost comparison (including overhead)
• availability of skilled labour
• speed requirements
• quality requirements
• risk and accountability

Example

A company can build a reporting dashboard:

• internally if the team has BI skills,
• or buy a commercial BI tool if time is critical.

Procurement Planning: What to Buy and How

Procurement planning includes:

• deciding procurement type (purchase, contract, framework)
• defining requirements and specifications
• identifying vendors/contracting strategy
• establishing evaluation criteria

Important exam idea: procurement must be consistent with scope requirements. Poor procurement planning leads to mismatched deliverables.

Types of Contracts (Exam-ready comparison)

Common contract types:

• Fixed-price (lump sum): vendor delivers at a set price; risk is mostly with vendor
• Time-and-materials: costs depend on time and materials; risk is higher for buyer
• Cost-plus: reimburses allowable costs plus fee; risk highest for buyer and requires tight governance
• Unit price: price per unit; used where quantities can vary

In exam questions, you may be asked to choose a contract type based on uncertainty.

Example selection reasoning

If scope is very well defined and risk is low, fixed-price can be appropriate.
If requirements are uncertain, time-and-materials or cost-plus with strict monitoring might be used.

Contractor Selection: Evaluation Methods

Vendor evaluation often uses:

• price,
• technical capability,
• past performance,
• delivery timelines,
• quality assurance systems,
• compliance and certifications.

A simple approach examiners like:

• define weighted scoring for criteria
• evaluate proposals
• document decisions

Procurement Risk and Contractual Controls

Procurement introduces risks:

• late delivery,
• quality failure,
• vendor non-compliance,
• cost overruns.

Controls include:

• clear specifications,
• acceptance testing,
• service-level agreements (SLAs),
• penalties for non-performance,
• warranties and guarantees,
• escalation procedures.

Example: acceptance testing clause

In a software service contract:

• vendor must deliver a working prototype
• acceptance test must pass defined test cases
• acceptance triggers payment release

This prevents “deliver and dispute” problems.

Resource Management: People, Roles, and Capacity

Resource management ensures the project has the people and skills to execute work.

Resource planning components

• Identify required roles (e.g., developer, analyst, project assistant)
• Estimate availability and capacity
• Plan acquisition if resources are external
• Build a resource calendar (where applicable)

Team Development and Motivation (Exam-level)

Project teams need coordination and motivation. Common elements:

• clear roles and responsibilities
• communication routines
• training and support
• recognition and feedback
• conflict management

At D3MNGT level, you should link motivation to outcomes:

• better engagement leads to fewer mistakes
• clear responsibility reduces delays

RACI Matrix (Often Used in Management Exams)

A RACI matrix assigns:

• Responsible: does the work
• Accountable: final answer/approval
• Consulted: provides input
• Informed: receives updates

Example for project deliverables

• Project Manager:
  • Responsible for integration and reporting
  • Accountable for baseline approvals
• Technical Lead:
  • Responsible for development quality
  • Accountable for technical correctness
• Sponsor:
  • Accountable for funding and major decisions
  • Informed for routine progress

Writing RACI in an exam answer signals structured planning.

Stakeholder Engagement Planning

Stakeholder engagement ensures that the right stakeholders participate at the right level and at the right time.

Engagement strategies

• manage expectations through communication
• involve users in testing and acceptance
• hold steering committees for major decisions
• manage resistance through transparency

Example: community stakeholder engagement

For a road improvement project:

• local community may care about access and noise
• municipality may care about compliance and cost
• contractors care about schedule feasibility

An effective PM adjusts communication:

• weekly access updates to community
• monthly compliance and budget reports to municipality

Ethical Considerations in Procurement and Project Decisions

Even though not always asked directly, ethical judgement is embedded in:

• vendor selection fairness
• avoiding conflicts of interest
• accurate reporting of progress and risks
• handling procurement documents responsibly

In exam essays, mentioning ethics helps show maturity and alignment with governance.

CPUT Cluster 5: Project Monitoring, Performance Measurement, Closing, and Integrated Project Answers

This final cluster brings together execution monitoring, basic performance measurement, governance reporting, and project closure. Many exam questions ask you to “describe what happens next” or “how would you respond to a deviation,” which requires integration of all previous topics.

Monitoring and Controlling: What “Control” Actually Means

Monitoring & controlling compares actual performance against baselines.

Key performance areas

• Schedule performance: Are we on time?
• Cost performance: Are we on budget?
• Scope performance: Are deliverables meeting requirements?
• Quality performance: Are defects within acceptable limits?
• Risk status: Are risks increasing or changing?
• Stakeholder satisfaction: Are decisions and communication working?

Variance Analysis: Simple Interpretation for Exams

Variance is difference between planned and actual.

Example: cost variance

If planned labour cost is R120,000 (from the earlier budget table) but actual labour is R128,000, cost variance is:

• 128,000 − 120,000 = R8,000 over budget

In exam answers:

• define variance,
• indicate causes (e.g., overtime, productivity issues, rework),
• propose corrective actions.

Corrective and Preventive Actions

• Corrective action: fixes the problem causing current deviation
• Preventive action: prevents potential future issues

Example scenario

Schedule behind due to vendor late delivery:

• corrective: reorder internal tasks, adjust sequence, escalate vendor
• preventive: include delivery time buffers, enforce performance terms

Basic Earned Value Concepts (If Included)

Some project management syllabi include Earned Value Management (EVM) basics. Even if not required, demonstrating familiarity can boost marks.

Core EVM elements:

• PV (Planned Value): value of planned work by a given date
• EV (Earned Value): value of completed work by that date
• AC (Actual Cost): cost spent by that date

From these:

• Schedule variance: EV − PV
• Cost variance: EV − AC

If your exam requires calculations, ensure you define each term and show arithmetic clearly.

Governance Reporting: Escalation and Decision Rights

Project governance affects:

• who receives reports,
• what triggers escalation,
• which decisions require sponsor/steering committee approval.

Escalation triggers (exam examples)

• budget variance exceeds threshold (e.g., >10%)
• critical risk materializes
• major scope change requested
• quality failure that affects acceptance

Even without specific threshold numbers in the question, explaining logic scores well.

Managing Issues: Distinguish Issues from Risks

A risk is uncertain and may happen.
An issue has already happened or is currently happening.

Exam distinction:

• If it already occurred → issue
• If it might occur → risk

Example:

• Risk: “Supplier hardware delayed.”
• Issue: “Hardware delayed and not yet delivered by week 2.”

Correct handling differs: issue requires immediate response; risk response may involve contingency planning.

Change Control and Re-baselining (Integrated Answer Example)

Suppose the project budget baseline is R180,000 and the schedule baseline is later moved due to approved scope changes. Re-baselining means updating baselines after approval.

A good integrated answer covers:

1. Identify deviation (schedule/cost)
2. Determine whether due to change or performance problem
3. If due to approved change → update baselines
4. If due to performance failure → corrective actions without re-baselining (or with limited scope)

Closing Phase: What to Do at the End

Closing is frequently under-described by students, but it is often examined: “Explain project closure” or “What documents are needed.”

Closing includes:

• final deliverable acceptance
• final performance reporting
• administrative close-out
• financial close-out (including vendor contracts)
• knowledge transfer
• lessons learned documentation
• archive project documents for audit and reference

Lessons learned: how to make them useful

Lessons learned should include:

• what worked well
• what did not
• root causes
• recommendations for future projects
• actions taken (if any)

Example of a Full Integrated Exam Answer Scenario

To demonstrate integration, here is a complete scenario with consistent numbers used across this document:

Scenario

A project aims to deliver a “School Career Day Platform” with a total project budget of R180,000 and baseline schedule of 8 weeks. The budget breakdown is:

• Labour: R120,000
• Software/Tools: R45,000
• Contingency: R15,000
  Total: R180,000

At week 4, the project reports:

• development finished later than planned (schedule behind)
• additional testing is needed due to defects (quality issue)
• a vendor proposes a scope change: add an extra report dashboard (scope change request)

How a strong exam answer would handle it

1. Assess the situation
   • determine whether delays are due to performance or scope change
   • review defect causes and quality reports
2. Classify requests
   • defects and rework → issue management
   • extra dashboard → change request (scope)
3. Perform impact analysis for the change request
   • estimate additional cost for the dashboard (e.g., vendor quote)
   • estimate schedule effect (e.g., affects testing and training)
4. Use change control
   • document the request
   • present trade-offs using triple constraint
   • obtain approval from sponsor/steering committee
5. Update baselines only if approved
   • if approved and cost increases, revise cost baseline
   • if rejected, manage schedule with corrective actions
6. Implement corrective actions
   • prioritize critical path tasks
   • re-plan resource allocation to reduce delays
7. Communicate
   • status report to stakeholders
   • update risk log (new or changed risks)
8. Continue monitoring
   • track schedule and cost variance weekly/bi-weekly
9. Close properly
   • final acceptance
   • vendor contract closure
   • lessons learned

This integrated approach is exactly what examiners reward because it demonstrates management competence rather than isolated definitions.

Exam-Ready Templates and How to Score

Many students lose marks by giving definitions without applying them to a scenario. Use templates.

Template 1: “Explain and apply” structure

1. Definition (1–2 sentences)
2. Purpose (why it matters)
3. Steps or components (numbered list)
4. Example (1 example that matches your scenario)
5. Outcome (what improved—time, cost, quality, stakeholder satisfaction)

Template 2: Risk question structure

• Risk statement (event + impact)
• Likelihood and impact ranking
• response strategy (avoid/mitigate/transfer/accept)
• trigger and contingency
• owner (who manages it)

Template 3: Change control question structure

• describe request
• assess impact on scope/time/cost/quality
• decision and justification
• baseline update and communication

Summary of “High-Frequency Exam Areas” for D3MNGT Project Management

In many South African university-style exams, the highest frequency topics include:

• project life cycle and integration
• WBS and scope control
• scheduling logic (dependencies, critical path idea)
• cost estimation/budgeting and variance basics
• risk identification, analysis, and response strategies
• quality assurance vs quality control
• communication plans and status reporting
• change control process and trade-offs
• procurement/contract types and vendor management
• monitoring, escalation, corrective/preventive actions
• closing, acceptance, and lessons learned

Being consistent with definitions, using structured steps, and applying concepts to scenarios with numbers (where asked) usually gives the best results.

Final Exam Checklist (Use Before Submitting Your Answers)

• Did you define the concept (not just describe it)?
• Did you list key steps in the correct sequence?
• Did you include at least one example (preferably a realistic one)?
• Did you show the relationship between topics (e.g., scope ↔ change control; risks ↔ monitoring)?
• If numbers were given, did you compute accurately and keep figures consistent?
• Did you include governance/stakeholder perspectives where relevant?

These notes are designed to help you write complete, coherent answers for Diploma in Management (D3MNGT) – Project Management examinations within the CPUT Project Management Study Material collection, with the level of structure and practical reasoning expected at diploma level.