These exam notes are designed for learners studying the Advanced Diploma in Management Sciences (Project Management)—with a strong focus on Durban University of Technology (DUT) Project Management Study Material. The guide blends core project management theory (scope, time, cost, quality, risk, procurement, stakeholder management) with practical assessment-style application (planning documents, justifications, charts, risk registers, and monitoring reports). You will find step-by-step frameworks, worked examples, and “what markers look for” style guidance so you can translate concepts into marks.
Section 1: Project Management Foundations for Advanced Diploma (DUT Style)
Project management in an Advanced Diploma context is more than definitions: it is about using disciplined processes and evidence-based planning to reduce uncertainty and deliver value. Examiners typically reward candidates who demonstrate structured thinking, logical sequencing, and clear justification for decisions—especially where they must manage trade-offs (time vs cost, risk vs opportunity, scope vs budget).
Understanding Projects, Programs, and Portfolios (and why it matters in exams)
A project is a temporary endeavour with a defined scope and objective. A program is a set of related projects managed together to achieve a broader outcome. A portfolio is a collection of projects/programs managed to align with strategic objectives.
In exam answers, the key differentiation is not academic—it affects how you choose management methods:
- For a project, you focus on delivery: schedule, budget, scope, quality, risk, and execution control.
- For a program, you focus on benefits and coordination across multiple projects (dependency management, governance, benefits realisation).
- For a portfolio, you focus on selection and prioritisation (resource allocation, strategic alignment, and return considerations).
Common DUT assessment pattern: the question describes an initiative (e.g., construction, ICT system, training campaign). Your first paragraph should explicitly classify it: “This is a project because it is temporary and aims to produce a defined deliverable.” Then you should link it to stakeholders and governance.
Quick exam checklist: Project classification signals markers want
When you see a scenario, quickly identify:
- Start and end point (temporary).
- Deliverables (tangible outputs).
- Constraints (budget/time/resource limits).
- Unique nature (not routine operations).
- Stakeholder environment (approvals, regulators, users).
If you can do this, the rest of your planning and risk logic becomes easier to structure.
Project Life Cycle and Phases (initiation to close)
Most project management frameworks describe a life cycle with phases. A typical life cycle includes:
- Initiation
- Planning
- Execution/Implementation
- Monitoring & Controlling
- Closing
The life cycle is not identical to the schedule. The life cycle helps you understand when specific documents and controls are required:
- Initiation: business case, problem statement, high-level scope, appointment of the project manager.
- Planning: baselines (scope/time/cost), risk plan, communication plan, quality plan.
- Execution: procurement, team deployment, stakeholder engagement.
- Monitoring & Controlling: variance analysis, change control, progress reporting.
- Closing: handover, lessons learned, final acceptance, closure report.
Worked scenario: mapping a life cycle to a typical DUT-style assignment
Scenario: A municipality plans to install a small GIS mapping system for land records across three offices.
- Initiation: define objective (improve land record accuracy), identify stakeholders (municipality users, IT vendor, legal office), develop business case.
- Planning: create work breakdown structure (WBS), define acceptance criteria (data accuracy thresholds), develop risk register (data integrity risks), plan procurement approach.
- Execution: configure system, migrate data, run user training sessions.
- Monitoring & Controlling: track milestones (data migration completion), manage changes (new reporting requirement from legal office).
- Closing: validate data and sign-off, transfer system ownership, archive documentation.
In a well-scored answer, you would show this mapping explicitly, often with a small timeline diagram or list of phase activities.
Project Management Knowledge Areas (how to structure an answer)
A robust exam response often mirrors a set of knowledge areas. While different frameworks exist, the most commonly taught structure includes:
- Integration management (project charter, project management plan, directing and managing work, monitoring & controlling, change control)
- Scope management (requirements, scope definition, WBS, scope verification, scope control)
- Schedule management (activity definition, sequencing, duration estimation, schedule development, schedule control)
- Cost management (resource planning, cost estimating, budgeting, cost control)
- Quality management (quality planning, quality assurance, quality control)
- Resource management (team development, manage team, stakeholder roles)
- Communications management (communications planning, manage communications)
- Risk management (identify, analyse, plan responses, monitor)
- Procurement management (plan purchases, contract administration, close procurements)
- Stakeholder management (identify stakeholders, plan engagement, manage engagement)
Exam technique: “What are the outputs?” linking
A strong approach is to pair each knowledge area with outputs:
- If you mention risk management, you should mention the risk register and risk response plan.
- If you mention scope, you should mention requirements document, WBS, and scope baseline.
- If you mention schedule, you should mention schedule baseline and tools such as Gantt charts or network diagrams.
Markers reward this because it demonstrates you understand process outputs, not just concepts.
Project Governance and Stakeholder Environment (DUT marker-friendly points)
Advanced Diploma work expects you to discuss governance and stakeholder influence. Governance includes how decisions are made and who approves changes.
Typical governance actors:
- Project sponsor (funding and strategic support)
- Project manager (delivery leadership)
- Steering committee (high-level oversight)
- Functional managers (resource provision)
- Clients/users (acceptance)
- Suppliers/vendors (execution through contracts)
Stakeholders may have different levels of interest and power. Your answer should show awareness of engagement strategies:
- High power + high interest: manage closely, frequent communication
- High power + low interest: keep satisfied, brief updates
- Low power + high interest: inform and include
- Low power + low interest: monitor and communicate as needed
Common pitfalls and how to avoid losing marks
- Pitfall: writing about stakeholders only as a list (“clients, vendors, government”).
Fix: classify power/interest and propose engagement actions. - Pitfall: discussing risk vaguely (“there is risk of delays”).
Fix: name risks, probability/impact, and response strategy (avoid, mitigate, transfer, accept).
Integration management: the glue of the project
Integration management ensures all the other knowledge areas work together. It includes:
- Developing the project charter
- Creating the project management plan
- Managing work execution and knowledge management
- Managing change control
- Monitoring and controlling performance
In exam answers, integration often shows up as a short but decisive paragraph on change control:
- Who can request a change?
- How is it assessed?
- What tools are used (impact analysis on cost/time/scope)?
- Who approves/rejects?
Change control example (numbers for credibility)
If a request adds a new feature estimated at R 120,000 in additional cost and shifts delivery by 3 weeks, an integrated answer should show trade-off reasoning:
- Compare change cost to contingency reserve.
- Determine if schedule shift breaches contract date.
- Assess whether scope baseline needs amendment.
Even when exact amounts are not provided in the question, your structure should show how you would compute impacts and escalate approvals.
Section 2: Scope, Schedule, and Cost Planning — From WBS to Baselines
In project management exams, many candidates can “talk” about scope/time/cost, but few can build credible plans. This section teaches planning structures and provides worked examples using typical DUT-style assessment expectations.
Scope Management: requirements to WBS to baselines
Scope management aims to ensure the project includes all the work required—and only the work required—to complete the project successfully.
A practical exam answer links these steps:
- Collect requirements
- Define scope (project scope statement)
- Create WBS (work breakdown structure)
- Define and manage scope baseline
- Validate and control scope
Requirements: how to write them so they score marks
Requirements should be:
- Specific and testable
- At the correct level (not vague like “improve system”; rather “reduce data entry errors to below 2%”)
- Owned by stakeholders (who signs off?)
- Associated with acceptance criteria
Example requirement set for a school e-learning platform:
- User story: “As a lecturer, I need to upload lecture notes in PDF format.”
- Acceptance criteria: “PDF upload supports sizes up to 50MB and is accessible within 10 seconds.”
- Traceability: requirement linked to a WBS component and acceptance test.
In an exam, even if you only have to propose a few requirements, it is important to show testability and traceability.
WBS construction: the foundation for planning
A WBS decomposes project deliverables into manageable components. A good WBS typically:
- Uses a hierarchical structure
- Links to deliverables (not activities only)
- Provides work packages at the lowest manageable level
- Enables estimation, scheduling, and costing
A common mistake is to create a list of tasks that doesn’t link to deliverables. For marks, you should explicitly mention deliverables and then show decomposition.
Worked WBS example: “Community Training Workshop Series”
Project objective: deliver a training series for unemployed youth in Durban.
Deliverables (Level 2):
- Curriculum and learning materials
- Venue and logistics
- Training delivery and facilitation
- Assessment and certification
- Monitoring and reporting
Level 3 example (one deliverable):
Training delivery and facilitation
- Recruit facilitators
- Conduct sessions (Session 1–Session 5)
- Facilitate practical exercises
- Provide learner support
Work packages (Level 4 example):
- Conduct Session 1 (duration: 4 hours; cost: facilitator fees; resources: projector, printed worksheets)
Even if you don’t have to include a full diagram, demonstrating the decomposition logic helps markers.
Scope verification and scope control (where many lose marks)
Scope verification is formal acceptance of deliverables. It answers: “Has the output been accepted by the customer/client?”
Scope control is managing changes to scope. It answers: “Is the project still on track with approved scope?”
To show maturity in an exam answer, include:
- A method for review (inspection, demos, acceptance tests)
- Change request process (log, assess, approve/reject)
- Impact analysis procedure
Practical example: scope control with a change request
Scenario: During implementation of a health reporting dashboard, stakeholders request additional filters (e.g., ward-level reporting) not included in the original scope.
Scope control steps:
- Create change request record
- Assess impact:
- Cost: additional development hours + testing
- Schedule: affects release milestone date
- Quality: ensure new filters do not degrade performance
- Risk: potential data quality issues
- Decide via change control board
- Update baselines (scope baseline/time/cost) if approved
- Communicate changes
If you show that scope changes are not “free,” you get better marks.
Schedule Management: building an implementable plan
Schedule management converts scope into time-based work. A credible exam response usually covers:
- Activity definition
- Sequencing (dependencies)
- Duration estimation
- Schedule development
- Schedule control
Activity sequencing: dependencies you should mention
Common dependency types:
- Finish-to-start (FS): Task B starts after Task A finishes
- Start-to-start (SS): Task B starts when Task A starts
- Finish-to-finish (FF): Task B finishes when Task A finishes
- Start-to-finish (SF): rare and often not allowed in practice
In exam scenarios, if a client wants training delivered only after content is approved, you would indicate FS dependency.
Worked example: creating a simple schedule logic
Consider a project to build a small website for a tourism campaign.
Activities:
- Gather requirements (2 days)
- Design pages (3 days)
- Develop site (5 days)
- Content upload (2 days)
- Testing (3 days)
- Go-live approval (1 day)
Dependencies:
- 2 depends on 1 (FS)
- 3 depends on 2 (FS)
- 4 depends on 3 (FS)
- 5 depends on 4 (FS)
- 6 depends on 5 (FS)
A markers’ favourite detail: compute earliest start/finish times using the dependency logic. Even if you don’t produce a full critical path network, a simple Gantt or numbered schedule indicates planning discipline.
Cost Management: estimates to budget and baselines
Cost management ensures the project is delivered within approved budget. Steps include:
- Resource planning
- Cost estimating
- Determining budget
- Controlling costs
Using contingency properly (and consistently)
Many exam questions reward candidates who distinguish:
- Known costs (expected direct project costs)
- Contingency reserve (for identified risks that may occur)
- Management reserve (for unknown unknowns)
Even when the question does not provide these categories, you can explain them conceptually—and when numbers are provided, use them consistently.
Worked example: baseline budget calculation
Suppose a project has the following planned direct costs:
- Labour: R 400,000
- Materials/Tools: R 120,000
- Subcontractors: R 80,000
Direct project cost total = 400,000 + 120,000 + 80,000 = R 600,000.
Add contingency reserve:
- Contingency: R 60,000
Approved cost baseline = 600,000 + 60,000 = R 660,000.
Now if a stakeholder requests scope expansion costing R 30,000, your answer should explain:
- Is it within contingency?
- Does it require baseline update approval?
- Does schedule also shift?
If you show this logic, your response becomes credible.
Integrating schedule and cost: cost-time trade-offs
Real project management decisions combine time and money:
- Accelerating tasks (crashing) often costs more
- Reducing scope reduces cost but increases risk or reduces value
- Switching to alternative resources may change both schedule and cost
In exam answers, you can mention typical techniques:
- Crashing (shorten schedule at higher cost)
- Fast tracking (perform tasks in parallel where possible)
- Re-sequencing work to remove bottlenecks
But the most important is to demonstrate structured decision-making:
- Identify trade-off
- Quantify impact (even at a high level)
- Evaluate constraints (contract dates, quality requirements)
- Approve or reject via governance
Section 3: Quality, Risk, and Stakeholder Management — Turning Plans into Control
Once planning is in place, projects succeed or fail through disciplined control. This section focuses on quality assurance/quality control, risk management mechanics, and stakeholder engagement practices—three areas that frequently appear in DUT and similar South African university examinations because they test practical application.
Quality Management: plan it, assure it, and control it
Quality management is not just “checking at the end.” It is a system that ensures deliverables meet agreed requirements.
A standard approach includes:
- Quality planning: define quality standards and how you will meet them
- Quality assurance: planned audits and process improvements
- Quality control: inspection, testing, verification of deliverables
Quality planning tools
Common quality planning elements include:
- Quality standards (e.g., performance benchmarks)
- Acceptance criteria (how you know it passes)
- Quality metrics (defect rate, rework hours, response time)
- Process checklists and control points
Example: acceptance criteria in an ICT project
For an e-registration system:
- Page load time < 3 seconds for standard requests
- Database accuracy: ≥ 99.5% matching between source documents and system records
- Uptime during pilot: ≥ 98%
- Security: role-based access implemented and tested
Exams often expect you to mention such measurable criteria.
Quality assurance: audits, reviews, and documentation
Quality assurance focuses on the process, not the product. In an exam, you can propose:
- Internal audits at major milestones
- Review meetings with stakeholders
- Compliance checks (e.g., data protection, safety standards)
- Documented procedures for how deliverables are created and reviewed
A strong DUT-style answer links QA activities to reduced rework:
- If defects are prevented early, costs are lower than late-stage correction.
Quality control: inspections, testing, and defect handling
Quality control is the “find and fix” mechanism:
- Inspection reports
- Test results
- Defect logs
- Corrective action workflows
A useful exam detail: show how defects affect schedule/cost.
- If defects increase, rework extends duration and increases labour cost.
- Therefore, quality metrics become part of monitoring.
Risk Management: from identification to responses
Risk management addresses uncertainty. The most assessed elements are:
- Identify risks
- Perform qualitative and/or quantitative analysis
- Plan risk responses
- Monitor and control risks
Step 1: risk identification — structured methods
Common methods:
- Brainstorming with stakeholders
- Expert judgement
- Checklists based on past projects
- SWOT analysis (Strengths, Weaknesses, Opportunities, Threats)
- Review of assumptions and constraints
- Root cause analysis from previous failures
In exam scenarios, you should not stop at “there is a risk.” You must show at least a few credible risks with triggers.
Step 2: risk analysis — qualitative probability/impact
A typical qualitative risk assessment uses a risk matrix:
- Probability categories (Low, Medium, High)
- Impact categories (Low, Medium, High)
- Risk rating = probability × impact (often represented by a colour)
If the question provides a matrix, use it. If it doesn’t, propose one and state your scale.
Example risk register entry (format you can copy in exams)
Risk: Delays due to late procurement of components
Category: Schedule
Probability: Medium
Impact: High
Trigger: supplier misses delivery date
Mitigation: pre-order, alternate supplier identification, buffer time
Owner: Procurement officer
Contingency: allocate 1-week buffer to integration milestone
Even without exact numbers, a structured entry earns marks.
Step 3: risk response planning — avoid/mitigate/transfer/accept
Use these response strategies explicitly:
- Avoid: change plans to eliminate the risk source
- Mitigate: reduce probability and/or impact
- Transfer: shift impact to another party (insurance, contracts)
- Accept: recognise risk and manage via contingency if occurs
- Exploit/enhance (for positive risks/opportunities): increase probability/impact of beneficial events
Examiners like when you differentiate threats vs opportunities. Even if the question focuses on risk, you can mention that risk management includes both.
Worked example: risk response with decision logic
Scenario: A supplier is experiencing instability. You have:
- Option A: use supplier (low cost, medium delay risk)
- Option B: use alternate supplier (higher cost, lower delay risk)
In your risk response you would:
- Quantify delay risk severity
- Compare cost premium vs schedule protection value
- Decide based on business priorities and contractual implications
- Document decision and update procurement plan
Even if your numbers are illustrative, keep internal consistency.
Monitoring and control of risk: risk reviews and triggers
Risk is not a one-time document. Monitoring includes:
- Regular risk review meetings
- Updating probability/impact based on new information
- Trigger-based actions (when certain signals appear)
- Replanning with change control if needed
Example: trigger-based action for a project
Risk: Data migration errors
Trigger: test migration fails for more than 1% of records
Response:
- Pause migration
- Escalate to data quality team
- Increase testing cycle
- Adjust schedule baseline via approved change request if necessary
Trigger logic demonstrates operational maturity.
Section 4: Procurement, Contracts, and Integration Controls — Managing Vendors and Changes
Procurement is a major source of project risk and one of the most heavily tested practical areas in management sciences examinations. This section focuses on procurement planning, contract types, vendor selection logic, contract administration, and integrated change management.
Procurement planning: what to buy and how to manage it
Procurement planning answers:
- What work/components will be outsourced?
- How will procurement be conducted?
- What contract approach fits the risk and complexity?
A structured exam answer includes:
- Identify procurement needs from the WBS
- Decide what to procure vs what to produce internally
- Define evaluation criteria
- Estimate procurement schedule
- Define contracting approach and risk allocation
Procurement documents and workflows
Typical procurement outputs include:
- Procurement plan
- Statement of Work (SOW)
- Technical specifications
- Vendor qualification requirements
- Evaluation criteria and scoring model
- Request for Proposal (RFP), Request for Quotation (RFQ), or Invitation to Bid (ITB)
In exam responses, you do not need to draft full legal documents; however, you should describe what each document does.
Contract types: matching type to risk and certainty
Common contract types include:
- Fixed-price: vendor gets fixed amount; risk shifts to vendor for cost overruns
- Time and materials: pay for labour and materials; vendor may not bear full cost risk
- Cost-reimbursable: you reimburse allowable costs; typically requires tight oversight
- Unit price: paid per unit delivered (good when quantities can vary)
Your selection should be justified based on certainty:
- If scope is well-defined, fixed-price may be appropriate.
- If scope evolves, time and materials or cost-reimbursable with strong controls might be better.
Example: choosing a contract type for an ICT implementation
If you have stable requirements and acceptance criteria:
- Fixed-price can reduce cost uncertainty.
If requirements are still emerging and iterative development is expected:
- Time and materials may be safer, but you must control rates, approvals, and deliverables.
Vendor selection and evaluation criteria
A strong exam response includes a procurement evaluation method:
- Price evaluation
- Technical capability evaluation
- Past performance
- Delivery capacity and timeline evidence
- Risk and quality management maturity
- Compliance with required standards
Worked example: simple scoring model
Suppose evaluation criteria for a training delivery vendor:
- Technical capability: 50%
- Price: 30%
- Delivery track record: 20%
If:
- Vendor X scores Technical 80/100 → 0.5 × 80 = 40
- Vendor X price is 20% below benchmark → assume relative score 100/100 after normalization (for exam simplicity) → 0.3 × 100 = 30
- Vendor X track record 70/100 → 0.2 × 70 = 14
Total Vendor X score = 40 + 30 + 14 = 84.
Even if exam questions do not request precise scoring, explaining how you would rank vendors is often enough.
Contract administration: managing performance
Contract administration includes:
- Managing deliverable acceptance
- Monitoring contractor performance
- Handling changes in line with contractual clauses
- Processing invoices against milestones
- Managing disputes and escalation
A marker-friendly answer mentions:
- Contract change procedures
- Reporting mechanisms
- Earned value or milestone payment logic where applicable
Procurement-related risk: linking back to risk management
Procurement introduces risk:
- Vendor delay
- Quality issues
- Currency fluctuations (if contracts are in foreign currency)
- Legal/regulatory non-compliance
- Supply chain disruptions
In an exam, connect procurement to risk register entries:
- Risk: delayed delivery due to production backlog
- Response: vendor performance clauses, penalties, alternate sourcing, buffer time
Integrated Change Management: scope, schedule, cost, and procurement updates
Integration management in procurement means that when changes occur:
- You update scope baseline if needed
- You adjust schedule baseline where approved
- You revise cost baseline accordingly
- You manage supplier impacts (change orders, revised delivery dates, additional costs)
Worked scenario: change request affecting vendor deliverables
Scenario: A project requires additional reporting templates after vendor design has begun.
- Vendor impact: 2 weeks additional effort and R 50,000 additional cost.
- Internal project impact: delays system integration milestone by 1 week due to dependency.
Integrated response:
- Raise change request and log vendor impact
- Estimate total project impacts (cost + schedule + risk)
- Seek approval through change control board
- If approved, issue change order to vendor and update procurement schedule
- Communicate to all stakeholders and update baselines
This level of integration demonstrates “project management science,” not just procurement talk.
Section 5: Monitoring, Reporting, and Exam-Ready Frameworks — Tools, Case Practice, and Governance
In advanced examinations, you are usually tested on your ability to monitor project performance, report progress clearly, and demonstrate governance and lessons learned. This section provides reporting structures, performance measurement concepts, and consolidated case practice so you can transfer knowledge into high-scoring exam responses.
Project monitoring and control: what “control” really means
Monitoring and controlling includes:
- Measuring performance against baselines
- Identifying variances
- Taking corrective actions
- Updating plans as needed via change control
A strong answer uses a cycle:
- Collect data (progress, costs incurred, deliverables status)
- Compare to baseline (schedule baseline, cost baseline, scope baseline)
- Analyse variances (schedule variance, cost variance)
- Decide actions (corrective/preventive)
- Update documentation and communicate
Example: variance and corrective action logic
If a milestone is due in 2 weeks but deliverables are only 60% complete:
- Identify why (dependency? quality rework? procurement delay?)
- Evaluate options:
- recover schedule by adding resources
- reduce scope elsewhere
- renegotiate revised milestone date
- Apply governance: change approval if baseline adjustment required
Earned Value Management (EVM) concepts—exam-ready explanation
EVM is a performance measurement method that integrates scope, schedule, and cost:
- Planned Value (PV): budgeted cost for work scheduled
- Earned Value (EV): budgeted cost for work performed
- Actual Cost (AC): actual cost of work performed
From these:
- Schedule Variance (SV) = EV − PV
- Cost Variance (CV) = EV − AC
And performance indices:
- Schedule Performance Index (SPI) = EV / PV
- Cost Performance Index (CPI) = EV / AC
Worked EVM example for clarity
Assume at a reporting date:
- PV = R 200,000
- EV = R 180,000
- AC = R 210,000
Compute:
- SV = 180,000 − 200,000 = −R 20,000 (behind schedule)
- CV = 180,000 − 210,000 = −R 30,000 (over budget)
Indices:
- SPI = 180,000 / 200,000 = 0.9
- CPI = 180,000 / 210,000 ≈ 0.86
A strong exam response interprets these:
- SPI < 1 means schedule slippage.
- CPI < 1 means cost inefficiency.
Then propose corrective actions: - schedule recovery plan (fast tracking where possible)
- cost control actions (reduce rework, renegotiate vendor terms where contract allows)
Reporting formats that earn marks: status, exceptions, and dashboards
In examinations, you may be asked to “draft a progress report” or describe content for reporting. A good progress report often includes:
- Executive summary
- Progress against milestones
- Budget status (planned vs actual)
- Quality status (defects, test pass rate)
- Top risks and changes
- Decisions required from steering committee
- Next reporting period plan
Example: milestone-based status report snippet
- Milestone 1: Requirements sign-off — Completed
- Milestone 2: WBS and baseline approval — Completed
- Milestone 3: Prototype demo — In progress (70%)
- Milestone 4: User acceptance testing — Scheduled (starting 15 June 2026)
If you give dates, ensure they are consistent across the report and timeline. In exam practice, choose a clear and consistent timeline and stick to it.
Governance and decision-making: steering committee and change control board
Governance is how decisions are made when conflicts arise. A steering committee typically focuses on:
- Strategic alignment and benefits
- Major risks and escalations
- Budget approvals for changes
- Decisions on schedule baseline adjustments
A change control board (CCB) focuses on:
- Change request evaluation
- Cost/time/scope impact assessment
- Approval and documentation
Exam answer structure: “Escalation process”
When answering governance questions, show:
- Trigger for escalation (e.g., variance beyond threshold)
- Information required (impact analysis, options)
- Decision pathway (who approves)
- Implementation pathway (update baselines, communicate)
Lessons learned and closure: closing the project properly
Closing is often undervalued but is important for marks. Closure includes:
- Acceptance and sign-off (deliverables formally accepted)
- Handover to operations/support teams
- Final financial reconciliation
- Documentation archive (contracts, reports, approvals)
- Lessons learned workshop
- Team debrief and performance evaluation
A high-quality exam answer ties lessons learned to improvements:
- If risk mitigation failed, update risk approach for future projects.
- If procurement delays occurred, revise vendor qualification criteria.
Consolidated case practice: a full mini-project from planning to control
To make these notes exam-ready, here is an integrated mini-case and the types of documents/logic expected.
Case: “Riverside Library Digital Borrowing System”
A library system needs an upgrade to allow digital borrowing for members. The project must deliver a working system by 30 September 2026.
Project scope (high-level):
- Implement borrowing registration interface
- Build member account verification flow
- Integrate with barcode scans
- Provide user training and documentation
- Deliver tested and accepted system version for rollout
Constraints:
- Fixed go-live date: 30 September 2026
- Approved maximum project budget baseline: R 660,000 (includes R 60,000 contingency)
- Quality acceptance criteria:
- Borrowing transactions accuracy ≥ 99.5%
- System response time ≤ 3 seconds on typical operations
- Security roles implemented and tested
Key stakeholders:
- Library operations manager (approves acceptance)
- IT lead (technical acceptance)
- Members (end users)
- External software vendor (builds software modules)
Step 1: Scope and WBS snapshot
Deliverables:
- Requirements and process design
- System configuration and module development
- Data setup and integration
- Testing and user training
- Rollout and documentation
A WBS-derived work package example:
- Data setup and integration
- member database alignment
- barcode scan mapping
- test migration and verification
Step 2: Schedule milestones (illustrative)
- 15 August 2026: Requirements sign-off
- 31 August 2026: Prototype demo
- 15 September 2026: System module integration complete
- 25 September 2026: Testing complete
- 30 September 2026: Go-live acceptance
Dependencies:
- Testing depends on integration completion
- Integration depends on module development and data setup
Step 3: Cost baseline and contingency logic (consistent with Section 2)
Planned direct costs:
- Labour: R 400,000
- Materials/Tools: R 120,000
- Subcontractors: R 80,000
Direct total = R 600,000
Contingency = R 60,000
Approved baseline = R 660,000
Step 4: Risk register examples (minimum viable set)
- Risk: Data mapping errors during integration
- Probability: Medium
- Impact: High
- Response: Mitigate via additional test runs and verification scripts; contingency for rework
- Risk: Vendor delay in module delivery
- Probability: Low to Medium
- Impact: High
- Response: Mitigate via milestone-based delivery clauses; identify alternate support resources
- Risk: Security role misconfiguration
- Probability: Low
- Impact: Medium
- Response: Mitigate via pre-defined role templates and test automation
Step 5: Monitoring and control—what you would report at the end of August
Assume by 31 August 2026:
- PV = R 220,000 (planned value for work scheduled)
- EV = R 200,000 (work performed)
- AC = R 245,000 (actual cost)
Compute:
- SV = 200,000 − 220,000 = −R 20,000 (behind schedule)
- CV = 200,000 − 245,000 = −R 45,000 (over budget)
- SPI = 200,000 / 220,000 = 0.91
- CPI = 200,000 / 245,000 ≈ 0.82
Interpretation and corrective actions:
- Schedule issue: integration tasks starting later due to vendor module delay
- Cost issue: additional labour spent on rework caused by data mapping errors
Corrective actions: - Prioritise data mapping verification immediately
- Request vendor recovery plan and enforce milestone acceptance dates
- Use contingency reserve for proven rework, but require approvals for baseline changes if needed
Step 6: Change request handling (example linked to procurement and integration)
Change request: Add “member eligibility status filter” to borrowing screen.
Estimated impacts:
- Additional cost = R 30,000
- Schedule impact = +1 week (risk to go-live)
Integrated response:
- Log change request; assess impacts on scope, schedule, cost, quality, risk.
- Compare cost to contingency remaining:
- Baseline contingency is R 60,000.
- If used partially due to rework already (you can define an assumption if asked), ensure you compute remaining correctly.
- Decide approval via CCB:
- Approve only if schedule can be recovered via fast tracking or resource reallocation.
- Update baselines if approved; communicate to stakeholders.
Step 7: Closing and lessons learned
At go-live (30 September 2026):
- Acceptance sign-off by library operations manager and IT lead
- Handover to library operations/support
- Final project review:
- what risk triggered rework
- what improved test processes should be used next time
- vendor performance lessons for future procurement
This mini-case shows how each knowledge area connects into a complete exam answer narrative.
Exam writing patterns: how to score higher without adding irrelevant content
When exam questions ask for “discuss” or “explain,” structure your answer with:
- Definition/aim (1–2 sentences)
- Process steps or elements (numbered list)
- Outputs/documents you would use (bullet list)
- Example linked to the scenario
- Risks/trade-offs/governance (short concluding paragraph)
This approach is particularly effective for:
- Short theory questions (e.g., “Explain scope verification and control”)
- Scenario-based questions (e.g., “Design a risk response plan”)
- Planning questions (e.g., “Construct a WBS and describe how you baseline scope”)
Section 5 Addendum (University-aligned phrasing and DUT-oriented study angles)
South African management sciences assessments often reward familiar framing used across multiple university modules and national qualification structures. Even when module codes differ (e.g., DUT courses under management science/programme planning or project management streams), the assessment language commonly expects the same deliverables and control logic: project charter, project management plan, WBS, risk register, communication plan, quality plan, procurement plan, and progress reporting.
Linking your answers to widely taught course components (PM discipline vocabulary)
You can strengthen your exam phrasing by using established professional terminology consistently:
- “baseline” when you reference scope/time/cost targets
- “change request” and “change control board” when discussing modifications
- “acceptance criteria” for quality validation
- “probability/impact” and “risk matrix” for risk assessment
- “stakeholder engagement plan” and “engagement strategies” for stakeholders
DUT project management study material cluster approach (how to review effectively)
Because DUT learners often face time constraints and multiple assessment components, a practical study method is:
- Learn core definitions and process outputs (fast recall)
- Practise building one document per knowledge area:
- a WBS
- a milestone schedule
- a risk register
- a procurement approach paragraph
- a status report with governance decision request
- Practise scenario integration:
- ask yourself: “If scope changes, what happens to schedule, cost, quality, and procurement?”
This “integration mindset” is what differentiates top answers from average answers in advanced diploma-level exams.
Final exam readiness checklist (high-yield)
Before your exam, verify you can do the following under time pressure:
- Build a WBS from deliverables and describe how it drives estimation and scheduling.
- Write a risk register with probability, impact, triggers, and response strategies.
- Explain quality planning/assurance/control with measurable acceptance criteria.
- Choose a contract type and justify it using uncertainty and scope definition.
- Outline change control and baseline updating with clear governance roles.
- Interpret simple EVM metrics (PV, EV, AC) and propose corrective actions.
If you can produce these elements quickly and coherently in response to a scenario, you are positioned to perform well in Advanced Diploma in Management Sciences (Project Management) assessments—especially within the Durban University of Technology (DUT) Project Management Study Material style environment where structured, document-based thinking often earns the highest marks.
