These exam notes are written for the BCom Business Management (Project Management elective) track associated with University of Johannesburg (UJ) – College of Business & Economics. They blend core project-management theory with the way exam questions are typically framed in South African BCom courses (similar patterns to modules such as MNG/PMB project management–style electives at SA universities). The notes focus on exam-ready concepts: project initiation, planning, scheduling, risk and cost control, stakeholder management, procurement, governance, and common appraisal/monitoring techniques.

1) Project Management Foundations for BCom Business Management (UJ Project Management Elective)

1.1 What “Project” means in a business management context

In BCom Business Management project management electives, you’re usually expected to distinguish sharply between everyday operations and projects.

Operations (ongoing work):

• Repeats regularly (e.g., monthly reporting, routine maintenance).
• Stable objectives and continuing processes.
• Usually measured by efficiency, service levels, and quality.

Projects (temporary work):

• Have a defined start and end.
• Aim to create a unique deliverable (product, service, result).
• Have constraints: scope, time, cost, and quality.
• Bring uncertainty and require formal planning and coordination.

Exam angle: “Define a project” plus “explain why projects need management.” Typical answer points:

1. Projects are time-bound.
2. They involve multiple activities and resources.
3. They face uncertainty (unknowns/risk).
4. They require coordination of stakeholders and decisions.
5. They require governance to ensure accountability.

1.2 The project lifecycle (phase model) and why it matters

A lifecycle is the structure used to manage a project from idea to closure. Common phase models include initiation → planning → execution → monitoring & control → closure. Many lecturers compress this, but exams still test these ideas.

Why phases matter:

• Each phase has different decision needs:
  • Initiation: “Should we do it?”
  • Planning: “How exactly will we do it?”
  • Execution: “Do the work as planned.”
  • Monitoring & control: “Are we on track?”
  • Closure: “Did we deliver and learn?”
• Resources and approvals increase with risk reduction and maturity.

Typical lifecycle signals you must mention in exams:

• Business case and authorization early.
• Detailed plans after requirements and scope definition.
• Change control when execution begins and uncertainties are lower but changes still occur.
• Performance reporting during execution.
• Handover and lessons learned at closure.

1.3 Project governance and the “who decides” structure

In project management exams, governance is often treated as “the framework for decision-making, accountability, and oversight.”

Common governance roles (write as bullets in exams):

• Project Sponsor / Steering Committee: provides strategic direction, approves major changes, secures resources.
• Project Manager: owns delivery performance (time, cost, scope, quality), manages the team, coordinates stakeholders.
• Functional Managers: provide resources (people) and manage their home-team responsibilities.
• Project Team: executes tasks.
• PMO (Project Management Office), where applicable: sets standards/templates, supports reporting.
• Stakeholders: anyone affected or influencing the project.

Key governance concepts:

• Authorization to start (based on feasibility/business case).
• Stage-gate approvals (common in SA organizations).
• Change control board or formal approval process for scope/time/cost changes.
• Escalation path when issues exceed the PM’s authority.

Counterpoint often tested:

• If governance is weak, scope creep and poor approvals happen—delivery fails even if “work execution” is strong.

1.4 The Project Management Knowledge Areas (exam-friendly mapping)

Even when lecturers don’t call them by the exact PMBOK names, exams often test knowledge areas that resemble them:

1. Integration management: manage project coordination across processes.
2. Scope management: define, plan, validate, control scope.
3. Schedule (time) management: create and control the schedule.
4. Cost management: budget, estimate, and control costs.
5. Quality management: plan quality standards, assurance, and control.
6. Resource management: plan and manage human/material resources.
7. Communications management: plan information flows and reporting.
8. Risk management: identify, analyze, respond, monitor risks.
9. Procurement management: buy or contract goods/services.
10. Stakeholder management: identify stakeholders and manage engagement.

How to score marks:

• Use definition + “how you would apply it” to a business scenario.
• Don’t list only terms; apply them to context (e.g., a construction project, ERP implementation, or business process change).

2) Project Initiation, Planning, and Scope/Time Control (UJ-Style Exam Focus)

2.1 Project initiation: business case, feasibility, and objectives

A strong exam answer must explain why initiation is more than “choosing a project.”

Business case (typical components):

• Problem/opportunity statement.
• Options considered (do nothing vs do minimum vs full solution).
• Costs, benefits, and financial justification.
• Risk and feasibility considerations.
• Strategic alignment to organizational goals.

SMART objectives (must be mentioned):

• Specific (clear deliverable)
• Measurable (performance metrics)
• Achievable
• Relevant
• Time-bound (deadline or milestone date)

Common exam question pattern:

• “A company wants to implement a new system. Explain how you would initiate the project.”
  A top response includes:

1. Identify business need and stakeholders.
2. Gather baseline data (current performance).
3. Draft business case and cost-benefit justification.
4. Define scope boundaries at high level.
5. Identify high-level risks.
6. Obtain formal authorization.

2.2 Stakeholder identification and engagement

Stakeholder management is central in BCom projects because business delivery always involves people and interests.

Steps to identify stakeholders:

1. List groups/individuals affected by the project.
2. Determine their influence and interest.
3. Assess their likely stance: supportive, neutral, resistant.
4. Determine engagement needs and communication method.

Stakeholder mapping example (exam-friendly):

• High power / high interest: Steering committee, sponsor → engage closely.
• High power / low interest: procurement head → keep informed.
• Low power / high interest: end users → involve and educate.
• Low power / low interest: peripheral stakeholders → minimal updates.

Engagement tactics you can mention:

• Workshops to co-create requirements.
• Steering committee reports.
• Training for end users.
• Consultation sessions for affected departments.
• Change communication for staff.

Counter-argument: If stakeholder engagement is treated as a “later task,” requirements will be wrong, adoption fails, and schedule delays occur due to rework.

2.3 Scope management: requirements, WBS, and control of scope creep

Scope is often tested heavily because it connects to schedule and cost outcomes.

Scope management includes:

• Collect requirements.
• Define scope.
• Create Work Breakdown Structure (WBS).
• Validate scope (acceptance of deliverables).
• Control scope (manage changes).

Define scope (exam style):

• Include deliverables and boundaries.
• Exclude non-in-scope items.
• Provide acceptance criteria.

2.4 Work Breakdown Structure (WBS): building blocks for planning

A WBS breaks the project into smaller deliverables and work packages.

How to present WBS in an exam:

• Use a hierarchical numbering structure.
• Work packages should be:
  • Clearly defined.
  • Small enough to assign responsibility.
  • Measurable (completion criteria).
  • Enough detail for scheduling and estimating.

Illustrative WBS mini-example (generic, adaptable):
Project: “Implement customer order system”

• 1.0 Project Management
  • 1.1 Kick-off and reporting
  • 1.2 Procurement & contracting support
• 2.0 Requirements & Design
  • 2.1 Requirements workshops
  • 2.2 Process mapping and solution design
• 3.0 Development & Configuration
  • 3.1 System configuration
  • 3.2 Integration setup
• 4.0 Testing & Training
  • 4.1 Test planning
  • 4.2 User training
• 5.0 Deployment
  • 5.1 Go-live support
  • 5.2 Post-implementation review

Why WBS matters for marks:

• It creates the basis for time estimates, resource assignment, and cost estimation.
• It also supports risk identification by work package.

2.5 Scheduling and time management: activities, dependencies, and critical path

Exams often ask you to “explain how you would develop a schedule” or “what is the critical path.”

Key scheduling concepts:

• Activities: tasks in the schedule.
• Dependencies: relationships between tasks:
  • Finish-to-Start (FS) most common.
  • Start-to-Start (SS), Finish-to-Finish (FF), etc.
• Milestones: key dates marking completion of major work.
• Critical path: the longest duration path that determines project completion time.

Example of critical path reasoning (simple, consistent)

Consider these activities (with durations):

• A: Requirements (3 weeks)
• B: Design (2 weeks) depends on A
• C: Procurement (4 weeks) depends on A
• D: Build (3 weeks) depends on B
• E: Integration (2 weeks) depends on C and D
• Project finishes when E finishes.

Compute earliest times:

• A finishes at week 3.
• B starts week 3 → finishes week 5.
• C starts week 3 → finishes week 7.
• D starts after B → week 5 to week 8.
• E depends on both C (ready week 7) and D (ready week 8) → starts week 8, finishes week 10.

Project duration = 10 weeks.

• Path 1: A(3) + C(4) + E(2) but E must wait for D → not enough alone.
• Path 2: A(3) + B(2) + D(3) + E(2) = 10 weeks (critical).

Exam tip: A good answer explicitly states “critical path activities” and why float is zero (or minimal).

2.6 Resource planning and cost estimation link to scheduling

Time and cost are not separate in exams; you must show integration.

Resource planning basics:

• Identify required skills.
• Estimate resource availability and constraints.
• Assign resources to work packages.
• Consider constraints like hiring lead times.

Cost estimation types (common):

• Top-down estimates (rough, early stage).
• Bottom-up estimates (sum of work packages; more accurate).
• Analogous estimating (based on similar past projects).
• Parametric estimating (using rates and parameters).

Consistency requirement for exams: If you state that cost is computed per work package, then your later answers about budget/cost control should reflect that approach.

2.7 Baseline, monitoring, and control: what you measure

An exam typically expects you to mention the idea of a baseline: the approved plan used as reference.

Baseline components:

• Schedule baseline (planned start/finish dates).
• Cost baseline (planned budgets per time period).
• Scope baseline (what is included and accepted criteria).

Monitoring & control focuses on:

• Performance measurement.
• Variance analysis (what differs from plan).
• Corrective actions.
• Change requests (scope/time/cost adjustments).

3) Cost Management, Earned Value, Budgeting, and Performance Measurement

3.1 Cost management: estimates, budgets, and control

Cost management ensures the project is completed within approved budgets while meeting scope and quality requirements.

Core processes:

1. Plan cost management (how you will estimate, budget, measure).
2. Estimate costs (resources, quantities, rates).
3. Determine budget (time-phased budgets).
4. Control costs (track actual costs vs planned values).

Cost breakdown structures (CBS)
Similar to WBS, a CBS breaks project costs into categories to help control spending.

Example cost categories:

• Labour
• Materials
• Equipment rental
• Travel and accommodation
• Professional services
• Contingency

3.2 Contingency vs management reserve (important distinction)

A frequent exam point: different types of funds for uncertainty.

• Contingency reserve: for known-unknown risks (identified risks likely to occur). Tied to specific risk events.
• Management reserve: for unknown-unknowns (unknown uncertainties). Not allocated to specific work packages at the time.

How to score: Explain when each is used and who approves drawdown.

3.3 Cash flow and time-phased budgeting

Budgeting is often time-phased. Examiners like scenarios with monthly spend patterns.

Time-phased budget idea:

• Even if total project budget is fixed, spending occurs over time.
• Poor forecasting causes cash flow problems even if final total cost remains okay.

Exam-ready example structure:

• Month 1: planning and early labour (lower spend)
• Month 2–3: procurement and major labour (higher spend)
• Later months: testing, training, deployment (moderate spend)

3.4 Earned Value Management (EVM): what it is and how to compute

EVM integrates scope, schedule, and cost into performance metrics.

Core EVM terms:

• Planned Value (PV): budgeted cost of work planned by a certain date.
• Earned Value (EV): budgeted cost of work actually performed by that date.
• Actual Cost (AC): actual cost spent for the work performed by that date.

From these you compute:

• Cost Variance (CV) = EV − AC
• Schedule Variance (SV) = EV − PV
• Cost Performance Index (CPI) = EV / AC
• Schedule Performance Index (SPI) = EV / PV

Interpretation:

• CV > 0 → under budget (good)
• CV < 0 → over budget (bad)
• SV > 0 → ahead of schedule
• SV < 0 → behind schedule
• CPI > 1 → cost-efficient
• CPI < 1 → cost-inefficient

EVM numerical example (consistent and reusable)

Suppose by end of Month 2:

• PV = R 400,000 (planned)
• EV = R 350,000 (earned for actual work)
• AC = R 420,000 (actual spent)

Compute:

• CV = EV − AC = 350,000 − 420,000 = −R 70,000 (over budget)
• SV = EV − PV = 350,000 − 400,000 = −R 50,000 (behind schedule)
• CPI = EV / AC = 350,000 / 420,000 = 0.833
• SPI = EV / PV = 350,000 / 400,000 = 0.875

Exam response should include what you do next:

• Investigate why costs are higher (scope changes, inefficiency, resource issues).
• Investigate why schedule slips (dependency delays, missing inputs).
• Propose corrective actions: re-plan schedule, adjust resource allocation, request scope clarification, update risk responses.

3.5 Forecasting with EVM: Estimate at Completion (EAC)

EAC estimates total project cost at completion. Many exam questions ask for “EAC based on current performance.”

A common simplified formula:

• EAC = BAC / CPI
  Where BAC is Budget at Completion.

Example continued

Assume BAC = R 2,000,000 and CPI = 0.833.

• EAC ≈ 2,000,000 / 0.833 ≈ R 2,400,000

Then:

• Variance at completion: EAC − BAC = 2,400,000 − 2,000,000 = R 400,000 expected overrun.

Important: If an exam provides different assumptions or includes schedule effects separately, use the formula they expect. But for typical BCom exam computations, CPI-based forecasting is common.

3.6 Cost control techniques beyond EVM

Examiners also reward qualitative techniques.

Examples:

• Vendor performance reviews (procurement cost creep).
• Approval thresholds and change control.
• Value engineering (improving value without lowering quality).
• Regular progress measurement by work package.

Counter-argument: EVM is not a substitute for governance—if baseline is wrong or scope not validated, EVM can mislead.

4) Risk Management, Quality, Procurement, and Stakeholder Communication

4.1 Risk management process: from identification to monitoring

Risk management is heavily examined because it predicts failure modes and supports preventive action.

Standard risk lifecycle:

1. Identify risks (threats and opportunities).
2. Analyze risks (likelihood and impact).
3. Prioritize (risk matrix).
4. Plan responses (avoid, mitigate, transfer, accept; for opportunities: exploit, enhance, share, accept).
5. Monitor and control (track triggers, reassess risks).

4.2 Risk identification methods (what students should list)

In exams, you may be asked to “explain how you identify risks.” Good answers mention at least a few methods:

• Brainstorming with project team and stakeholders
• Lessons learned from previous projects
• Checklists (template-based)
• SWOT analysis (strengths/weaknesses/opportunities/threats)
• Industry benchmarking
• Interviews and expert judgement
• Site/technical assessments (if relevant)

4.3 Risk matrix: creating a prioritised list

A typical matrix:

• Likelihood: Low / Medium / High
• Impact: Low / Medium / High
• Produce overall risk level.

But exam graders like you to add:

• What exactly constitutes “impact” (cost overrun, schedule delay, quality failure, safety issues, reputational damage).
• What triggers tell you the risk is becoming real.

Example risk register entry (show format)

A risk register row should include:

• Risk description
• Category (schedule/cost/scope/technical/regulatory)
• Likelihood
• Impact
• Score (optional)
• Owner
• Response strategy
• Contingency actions / trigger

Example: “Delays in material delivery”

• Likelihood: Medium
• Impact: High
• Response: Mitigate by dual sourcing; create procurement buffer
• Trigger: Supplier misses milestone date by 1 week
• Owner: Procurement Manager

4.4 Quantitative risk analysis vs qualitative

Students sometimes confuse them; clarify in exam answers.

• Qualitative risk analysis: ranking based on judgement (likelihood/impact matrix).
• Quantitative risk analysis: numerical methods such as expected monetary value, probability distributions, Monte Carlo simulation.

BCom exam typical: qualitative is sufficient for most questions; quantitative may appear in calculation sections with probabilities.

4.5 Risk response planning: avoid vs mitigate vs transfer vs accept

To score well, you need to explain each option and when it is appropriate.

• Avoid: change plan to eliminate risk (e.g., redesign to remove uncertain dependency).
• Mitigate: reduce likelihood/impact (e.g., supplier evaluation, additional testing).
• Transfer: shift impact to third party (e.g., insurance, contract clauses).
• Accept: no action beyond monitoring (for low-risk or unavoidable risks).

Opportunities management:

• Exploit: ensure opportunity happens (e.g., secure early purchase discount).
• Enhance: increase probability/impact (more marketing to accelerate uptake).
• Share: partner with other firm to share benefit and risk.
• Accept: take benefit if it occurs (monitoring and readiness).

4.6 Quality management: standards, assurance, and control

Quality management ensures deliverables meet requirements. Often exams expect three layers:

• Quality planning (standards, acceptance criteria)
• Quality assurance (processes to ensure quality)
• Quality control (inspections/tests to verify deliverables)

Quality standards examples:

• Specifications in contracts (technical requirements).
• Service-level targets.
• Testing protocols.
• Compliance standards and regulatory requirements.

4.7 Quality metrics and acceptance criteria

To prevent disputes during validation:

• Define what “done” means.
• Provide objective acceptance criteria:
  • measurable performance indicators
  • documentation requirements
  • sign-off procedures by stakeholders

Example acceptance criteria (format):

• “System meets 95% of user acceptance test cases by defect severity.”
• “Training session attendance ≥ 90% of required users.”
• “Documentation delivered within 5 working days of final testing.”

4.8 Procurement management: contracting decisions and controls

Procurement is a major exam topic in project management electives.

Procurement planning:

• What to buy vs do in-house.
• Define specifications and scope for suppliers.
• Decide procurement approach:
  • competitive bidding
  • negotiated contracts
  • framework agreements
• Plan contract type based on risk:
  • fixed-price (lower buyer risk but requires detailed scope)
  • cost-plus (higher buyer cost but suits uncertain scopes)
  • time and materials (common when scope uncertain, but requires careful monitoring)

4.9 Procurement risks: managing supplier performance and contract management

Key procurement risks:

• Vendor delays
• Quality noncompliance
• Price escalation
• Scope ambiguity leading to disputes

Controls you should mention:

• Clear contract deliverables and acceptance criteria.
• Service Level Agreements (SLAs) where relevant.
• Regular performance reviews.
• Change control within contract boundaries.
• Penalty/bonus clauses where appropriate.

4.10 Communications management: planning and reporting rhythm

Communications is not just “sending emails.” Exams expect structured communication planning.

Communications plan components:

• Stakeholders list
• Information needs (what they need)
• Format (reports, meetings, dashboards)
• Frequency (weekly status, monthly steering committee)
• Owner (who sends)
• Method (meeting, email, system dashboard)

Common communication channels:

• Weekly project status meetings.
• Monthly steering committee reports.
• Risk review sessions.
• Issue logs and escalation.

What to include in status reports (marks booster):

• Progress vs schedule baseline
• Budget status and variance (possibly EV metrics)
• Top risks and changes
• Decisions needed from sponsor
• Issues and corrective actions
• Next steps and milestones

5) Project Implementation, Monitoring & Control, Change Management, and Project Closure (Exam-Ready Syntheses)

5.1 Execution and resource coordination: turning plans into delivery

Execution is where the project actually produces deliverables.

Execution responsibilities of a project manager:

• Assign tasks and ensure resources are working on approved scope.
• Coordinate team activities across functions.
• Manage stakeholder expectations during delivery.
• Ensure quality procedures are followed.
• Track progress and report performance.

Exam scenario reminder: If asked “what would you do during execution,” do not talk only about “working.” Talk about control loops: progress measurement, issue handling, and escalation.

5.2 Monitoring & control: integrated performance tracking

Monitoring & control is not separate from execution—it's ongoing.

Integrated controls often include:

• Scope verification (confirm deliverables meet requirements)
• Schedule tracking (actual progress vs baseline)
• Cost tracking (actual costs and commitments)
• Quality checks (tests/inspections)
• Risk monitoring (watch triggers and update risk register)
• Stakeholder monitoring (engagement and acceptance)

Issue management vs risk management (frequent distinction):

• Risk exists before it happens; you prepare responses.
• Issue is an event already occurring; you resolve it with corrective actions.

A top exam answer will explicitly mention:

• When a risk becomes an issue, update the register.
• Ensure actions are assigned owners with deadlines.

5.3 Change management: scope change, time change, and cost impacts

Change management is central in business projects where requirements evolve.

Change control process typical steps:

1. Identify change and document it (change request).
2. Evaluate impact: scope, schedule, cost, quality, risk.
3. Decide approval/rejection based on governance.
4. Update baselines if approved.
5. Communicate changes to all stakeholders.
6. Track execution of change actions.

What examiners look for:

• A structured approach rather than “request approval.”
• Mention of impact analysis (not just yes/no).

Example: change request evaluation

Suppose during system implementation:

• New requirement: additional reporting module.
• Impact:
  • Scope expands: new deliverable
  • Schedule: +2 weeks due to additional development and testing
  • Cost: extra R 150,000 for development and testing labour

Your response should show:

• Updated WBS and schedule activities.
• Updated budget and maybe baseline.
• Updated risks (e.g., testing resource constraints).
• Stakeholder communication plan (train users on new module).

5.4 Performance measurement dashboards: linking metrics to decisions

Beyond calculations, exam questions sometimes ask what metrics drive decisions.

Common project decision metrics:

• Progress % complete (but must be reliable via acceptance criteria).
• CPI/SPI from EVM for cost and schedule efficiency.
• Number and severity of defects (quality).
• Risk exposure changes (risk).
• Procurement performance (supplier OTIF—on time in full, if used).

Important exam nuance: Using “% complete” without a reliable method leads to inaccurate EV (earned value). Strong exam answers mention that EV requires objective measures like milestones or work package acceptance.

5.5 Corrective action planning and preventive actions

Corrective actions respond to actual variance.
Preventive actions prevent recurrence or reduce likelihood of future issues.

Corrective action example:

• If procurement delays cause schedule slip:
  • expedite shipping (if possible)
  • switch supplier for remaining items
  • re-sequence tasks where dependencies allow

Preventive action example:

• If delays resulted from weak supplier assessment:
  • enhance vendor evaluation criteria
  • require detailed delivery schedules
  • include penalty clauses for late delivery

5.6 Lessons learned and closure: acceptance, handover, and evaluation

Closure ensures the project ends properly and knowledge is captured.

Closure activities:

• Formal acceptance of deliverables.
• Handover to operations (or business unit).
• Release resources and final accounting.
• Final performance reporting: compare planned vs actual.
• Document lessons learned: what worked, what failed, improvement recommendations.
• Archive project records.

Why closure is tested:

• Projects often “stop” operationally but not administratively.
• Without formal closure, benefits don’t get realized because ownership and operational processes are unclear.

5.7 A full exam-style integrated scenario (end-to-end)

To synthesize concepts, consider the following scenario used for exam practice.

Scenario: “Introduce a customer order management system” (COS)

A retail business wants to implement a system to reduce order processing time and improve order accuracy. The project runs for a planned baseline of 10 weeks (time plan built using critical path logic similar to the earlier example).

Assume by end of Week 6:

• PV (planned value) = R 900,000
• EV (earned value) = R 800,000
• AC (actual cost) = R 950,000

Compute:

• CV = EV − AC = 800,000 − 950,000 = −R 150,000 (over budget)
• SV = EV − PV = 800,000 − 900,000 = −R 100,000 (behind schedule)
• CPI = EV/AC = 800,000/950,000 ≈ 0.842
• SPI = EV/PV = 800,000/900,000 ≈ 0.889

Interpretation for exam:

• Cost efficiency is poor (CPI < 1), so spending is higher than value earned.
• Schedule efficiency is also poor (SPI < 1), so work accomplished lags behind plan.

What should the project manager do next?

1. Diagnose root causes:
   • Are costs high due to rework from unclear requirements?
   • Are delays caused by supplier integration dependencies or insufficient test environments?
2. Check whether scope is stable:
   • If new reporting requirements were introduced without approvals, that could inflate costs and reduce earned value.
3. Reassess risks:
   • Supplier delivery risk may have escalated to an issue.
4. Propose corrective actions:
   • re-sequence tasks (fast-track integration where possible)
   • add temporary testing resources (if budget permits)
   • request decisions from sponsor via change control
5. Update forecasts:
   • If BAC is known (example would be required in the exam), forecast EAC using CPI.

Exam scoring logic:

• A good answer demonstrates you can compute CV/SV/CPI/SPI and then interpret them in business terms (why it happened + what actions follow).

5.8 Procurement and supplier management in the scenario (linking multiple knowledge areas)

The system implementation requires external integration support. If procurement is weak, quality issues and schedule overruns become likely.

Exam-ready actions:

• Confirm contract deliverables with acceptance criteria.
• Monitor supplier progress against milestones.
• Use change control when interfaces change.
• Ensure quality assurance includes both internal testing and supplier compliance tests.

Link to stakeholder management:

• End users are stakeholders.
• If users are not trained early, adoption delays cause “delivery acceptance” to be delayed.

5.9 Quality control checkpoints during implementation

In the scenario:

• Requirements are validated via workshops and sign-offs.
• Testing includes unit tests, integration tests, and user acceptance tests.

Exam answer points:

• Provide objective acceptance criteria for each testing stage.
• Use defect severity to guide corrective actions.
• Record testing outcomes to support scope validation.

5.10 Final deliverables and closure in the scenario

Closure must ensure:

• Stakeholders sign-off that deliverables meet scope requirements.
• Operations receive documentation and training materials.
• The business case benefits are tracked post-implementation (even if outside formal project boundaries, mention transition to operations).

Lessons learned examples:

• Requirements workshops earlier than planned reduces rework.
• Test environment readiness is a critical dependency.
• Clear supplier interface specifications prevent late integration changes.

Appendix: Quick Exam Templates and How to Structure Answers (UJ BCom Style)

A) “Define and explain” templates

When asked to define a concept (project, risk, EVM, WBS), use this structure:

1. Definition (1–2 lines)
2. Purpose (why it matters)
3. Key components/steps (3–6 bullets)
4. Application in a project (1 scenario sentence)

B) Risk register template

Include these fields:

• Risk description
• Category
• Likelihood
• Impact
• Score/priority
• Risk owner
• Response strategy (avoid/mitigate/transfer/accept)
• Trigger
• Contingency plan

C) Change request template

Include:

• Request summary and reason
• Impact analysis (scope, schedule, cost, quality)
• Risks created/affected
• Recommended decision (approve/reject/hold)
• Approver (steering committee/sponsor)
• Updated baselines and communication plan

D) Short EVM calculation checklist

Given PV, EV, AC:

1. Compute CV = EV − AC
2. Compute SV = EV − PV
3. Compute CPI = EV/AC
4. Compute SPI = EV/PV
5. Interpret results
6. Recommend corrective actions and (if BAC given) EAC

E) University alignment note (UJ focus)

This document is tailored to the University of Johannesburg (UJ) – College of Business & Economics context for BCom Business Management (Project Management elective) style assessments: structured definitions, practical application, calculations (especially EVM), and project control processes (scope/time/cost/risk/quality) tied to stakeholder decisions and governance. The emphasis on templates and scenario-based reasoning matches common SA exam marking practices in business management project modules.

Summary cheat-sheet (final revision)

• Initiation: business case, feasibility, objectives, authorization.
• Planning: scope (WBS), schedule (dependencies/critical path), costs, quality standards, communications plan.
• Execution & control: integrate tracking of scope/schedule/cost/quality; manage issues vs risks.
• EVM: PV, EV, AC → CV/SV/CPI/SPI → interpret + forecast.
• Risk: register + matrix + responses + monitoring triggers.
• Quality: plan/assure/control + acceptance criteria.
• Procurement: contracting approach + acceptance + supplier monitoring.
• Change & closure: structured change control; acceptance, handover, lessons learned.

If you want, I can also generate: (1) a set of exam-style questions with model answers aligned to these sections, and (2) a 10–15 calculation practice pack for EVM and variance interpretation using consistent numbers.