PGM4817 The Project Manager & Project Team — UNISA-Style Exam Notes (CEMS)

PGM4817 focuses on the practical and interpersonal side of project delivery: how the project manager leads planning, coordination, decision-making, and governance, and how a project team is organised, motivated, and supported to achieve project objectives. Unlike purely technical modules, this course emphasises human systems—roles, communication, leadership, team dynamics, conflict, performance, and accountability. These exam notes are written in a UNISA-friendly style, aligning with common themes found in College of Economic and Management Sciences (CEMS) project management courses.

1) The Role of the Project Manager in Project Governance (PGM4817 Core Leadership)

A project manager is not simply an administrator; they are the person accountable for ensuring that the project is initiated properly, planned realistically, executed with control, monitored continuously, and closed formally. In PGM4817, the emphasis is on leadership through governance, where the project manager manages both (1) project work and (2) stakeholder relationships that enable the work.

1.1 Project governance and why the project manager matters

Project governance refers to the structures, rules, decision rights, reporting lines, and oversight mechanisms that ensure the project stays aligned to organisational strategy and remains controlled. In an exam context, governance is often asked as “what ensures the project is still on track and why decisions are justified.”

Typical governance components include:

• Project charter / mandate: authorises the project and defines purpose, scope boundaries, and high-level objectives.
• Business case: explains the rationale, benefits, cost drivers, and the expected return.
• Project life cycle: defines stages and decision gates (e.g., approve concept, approve plan, approve changes).
• Reporting and performance monitoring: how progress is tracked, escalated, and acted on.
• Change control: who can approve changes and under which conditions.
• Risk and issue management: how risks are identified, assessed, responded to, and monitored.
• Quality management: how deliverables meet agreed quality criteria.

The project manager is central because they translate governance into day-to-day behaviour: they set expectations, keep documentation current, run meetings effectively, and ensure that the team follows agreed controls.

Example scenario (university-style)

Imagine a South African municipality launches a project to upgrade street lighting in five wards. A project manager is appointed, but stakeholders disagree on the budget, prioritisation, and timelines. Strong governance means the project manager:

1. Ensures a business case is documented (why the project is worth doing),
2. Uses a stage-gate approach (e.g., design approval before procurement),
3. Implements change control for scope/budget/timing disputes,
4. Reports performance using agreed indicators to municipal committees.

Without this, the project may drift into “constant rework,” cost overruns, and delayed approvals.

1.2 The project manager’s key responsibilities: controlling without micromanaging

A frequent exam theme is the tension between control and empowerment. The project manager must exercise control over outcomes, while empowering the team to deliver efficiently.

Core responsibilities typically include:

• Initiation
  • Confirm project mandate and stakeholder list
  • Ensure readiness: resources, initial feasibility, and roles
• Planning
  • Develop the project management plan (scope, schedule, cost, quality, communication, risk)
  • Create work breakdown structures and define deliverables
  • Set baselines for performance measurement
• Execution (leading the work)
  • Coordinate tasks across functions
  • Manage procurement support if needed
  • Facilitate decisions and remove blockers
• Monitoring & controlling
  • Track KPIs and milestones
  • Identify variances and corrective actions
  • Manage risks and issues actively
• Communication and stakeholder management
  • Provide regular updates
  • Translate technical progress into stakeholder-friendly reporting
• Closing
  • Ensure acceptance, handover, documentation
  • Capture lessons learned and formalise closure

In a project environment, the project manager often faces pressure: “Get it done quickly.” But in governance terms, urgency must still respect approval processes, quality checks, and controlled changes.

1.3 Leadership styles and their fit with project team maturity

An exam question may ask how different leadership styles are used based on team capability and project context. A useful model is the idea that leadership should match the maturity and competence of the team.

Common styles and project implications:

• Directive / autocratic
  • Useful when quick decisions are needed and the team lacks clarity or experience.
  • Risk: demotivates capable team members; may hide problems.
• Coaching
  • Useful when team members are capable but need guidance on expectations, roles, or standards.
  • Risk: can slow decisions if overused.
• Supportive / participative
  • Useful when team members have competence and need involvement to commit to plans.
  • Risk: decision-making may become slow if consensus is demanded for every matter.
• Delegating
  • Useful when team members are highly capable and trust is high.
  • Risk: if accountability is unclear, quality and outcomes degrade.

Practical application

Suppose a project team is newly formed for a software implementation. Early tasks may require directive leadership (defining standards, workflows, and responsibilities). As the team becomes familiar with the system and processes, leadership can shift towards participative/coaching to improve commitment and idea-sharing.

1.4 Competencies expected of a PGM4817 project manager

In many South African exam settings, “competencies” are interpreted broadly: not only technical knowledge, but soft skills and ethical decision-making.

A well-rounded project manager should demonstrate:

• Planning competency: build realistic baselines and manage scope.
• Communication competency: tailor messages for different audiences (executives vs team vs clients).
• Negotiation competency: resolve conflicts between stakeholders.
• Risk competency: proactively manage uncertainties.
• Leadership competency: motivate and guide the team.
• Integrity and ethics: ensure transparency in reporting, procurement, and decisions.
• Coaching and development: grow team capability through learning and feedback.

Ethics matters because project managers may face incentives to “hide bad news.” Strong governance requires accurate reporting and early escalation rather than late failure.

1.5 The “triangle” of project constraints and decision-making

A standard project management concept is the triple constraint: scope, time, cost (sometimes quality is included as a fourth element). The project manager must decide how changes affect the constraint triangle.

How to answer exam questions:

• Identify what constraint is threatened (e.g., delay threatens time; increased requirements threaten scope).
• Explain trade-offs:
  • Reduce scope to protect time and cost.
  • Increase resources/cost to protect time and maintain scope.
  • Extend schedule to protect cost and maintain scope.
• Emphasise change control:
  • Changes must be documented.
  • Stakeholders must agree on approved trade-offs.
  • The baseline should be updated only with approval.

A project manager who adjusts without governance creates “silent baseline drift,” which makes performance tracking meaningless.

2) Building, Structuring, and Managing the Project Team (UNISA-Style Team Practice)

In PGM4817, the project team is treated as a system. Teams do not automatically succeed because they exist; they succeed because roles are clear, communication works, conflict is managed constructively, and performance is supported.

2.1 Project team roles: who does what?

A common exam requirement is to distinguish roles, responsibilities, and authority. In team contexts, confusion arises when people do tasks but do not own decisions.

Key roles often include:

• Project Manager: accountable for overall success; coordinates plan execution; manages governance and reporting.
• Project Sponsor: provides strategic direction, resources, and removes high-level blockers; champions the project.
• Functional Managers: own technical resources; allocate personnel and ensure alignment with departmental priorities.
• Team Members / Specialists: execute tasks; produce deliverables; follow standards and provide input on risks/issues.
• Project Coordinator / Scheduler (where applicable): manages schedules, meeting cadence, and reporting accuracy.
• Quality Manager / Quality Assurance: ensures processes meet required quality criteria.
• Procurement Specialist: supports sourcing, contracting, supplier relationship management.
• Risk/Issue Owner: responsible for specific risk response actions.

Roles vs responsibilities

• Role: the title/responsibility category (e.g., “risk owner”).
• Responsibility: specific activities (e.g., “update risk register weekly and propose response actions”).
• Authority: decision rights (e.g., “can approve design changes up to R50 000 without sponsor approval”).

For exams, a strong answer clarifies these elements because it shows governance maturity and prevents “accountability gaps.”

2.2 Team formation: selecting and onboarding for early performance

Team formation involves more than assigning people. It includes ensuring the team has:

• Required competencies
• Adequate capacity (time availability)
• Clear reporting lines
• Access to information and tools
• A working agreement on how the team collaborates

Onboarding steps that exam markers often reward include:

1. Clarify project purpose and success criteria
2. Define roles and expectations
3. Introduce the project management plan basics (scope boundaries, reporting cadence)
4. Train on standards and tools
5. Establish communication norms
6. Conduct early risk review (team experiences and assumptions)
7. Set short-term milestones to build momentum

2.3 Team structures: functional, matrix, and projectised forms

Team structure affects authority, coordination effort, and conflict patterns.

Functional structure

• Team members primarily belong to functional departments.
• Project manager often has limited authority.
• Good for stable organisations; less ideal when project needs cross-functional speed.

Matrix structure

• Team members report to both functional and project structures.
• Can be weak when priorities conflict, strong when coordination is well managed.
• Many South African organisations operate in matrix environments (e.g., engineering teams within a department supporting multiple initiatives).

Projectised structure

• Team members are dedicated primarily to the project.
• Project manager has stronger authority and faster coordination.
• Often more expensive but can deliver speed and cohesion.

Example: matrix conflict

If a member is assigned half-time to the project and half-time to departmental work, conflict arises about deadlines. In that case, the project manager must negotiate with functional managers, using:

• agreed capacity schedules,
• escalation mechanisms,
• clear priority rules tied to sponsor decisions.

2.4 Team development: from forming to performing

A well-known model is team development through stages (commonly forming, storming, norming, performing). In exam answers, you should:

• describe behavioural indicators at each stage,
• connect those indicators to what the project manager should do.

Forming

• People are polite; roles are unclear; focus on understanding.
• Project manager actions:
  • Provide structure and clarity.
  • Explain success criteria and communication plans.

Storming

• Conflicts emerge: disagreements on scope, responsibilities, or methods.
• Project manager actions:
  • Facilitate conflict resolution.
  • Clarify decision rights.
  • Use structured meetings with agendas and documented outputs.

Norming

• Agreement forms around processes and collaboration norms.
• Project manager actions:
  • Strengthen accountability.
  • Encourage ownership and peer support.

Performing

• Team works efficiently; issues are handled proactively.
• Project manager actions:
  • Focus on continuous improvement and risk monitoring.
  • Recognise achievements and support learning.

This model is valuable because it legitimises conflict as a normal step—exam markers like this because it shows mature team thinking.

2.5 Motivation and engagement: building commitment to project outcomes

Project teams are motivated by more than money. Motivation can be strengthened by:

• Meaning and purpose: show how deliverables create value.
• Autonomy with accountability: empower team choices while holding ownership for outcomes.
• Competence growth: provide coaching, learning, and clear standards.
• Recognition: acknowledge progress publicly and fairly.
• Fairness: ensure decisions (e.g., task assignments, workload) are transparent.
• Psychological safety: encourage people to raise risks early.

Practical example: risk reporting culture

A team may avoid reporting a risk because they fear blame. The project manager should:

• separate fault-finding from risk reporting,
• reward early identification,
• use “lessons, not punishment” during risk review sessions.

2.6 Managing performance: roles, feedback, and corrective action

In PGM4817, performance management should align with project deliverables and baseline expectations.

Exam-ready components:

• Set measurable deliverables: define quality standards and completion criteria.
• Use performance tracking: progress reports, milestone completion, defect metrics (for technical projects).
• Provide regular feedback: not only when problems occur.
• Use corrective actions:
  • re-plan tasks,
  • re-allocate resources (if possible),
  • implement process changes,
  • escalate when issues exceed team control.

A strong answer includes that performance management is not purely “disciplinary.” It is an operational improvement cycle.

2.7 Conflict management: constructive resolution within project teams

Conflict is inevitable. The aim is not to eliminate it, but to manage it to prevent escalation into relationship breakdown.

Common conflict types:

• Task conflict: disagreements about methods, scope, technical standards.
• Relationship conflict: personal tensions and reduced trust.
• Resource conflict: competition for time, budget, or equipment.

The project manager should use:

• Clarification of decision rights and scope boundaries.
• Evidence-based discussion: use data (schedule impact, cost estimates).
• Mediation and negotiation when parties disagree.
• Consensus where appropriate, but not for every decision.
• Escalation to sponsor/steering committee when required.

Example: task conflict on design approach

Two engineers disagree about a design approach:

• Option A: uses proven internal components (less risk, slower).
• Option B: uses new supplier components (faster, higher risk).

A strong exam answer would state that the project manager should request:

• risk assessment for Option B (supplier reliability, lead times),
• cost comparisons,
• timeline impacts,
• quality implications.

Then decisions can be justified and documented via change control or technical governance.

3) Communication, Stakeholder Engagement, and Team Collaboration Mechanisms

The effectiveness of a project manager is strongly linked to communication quality. PGM4817 typically expects students to show how communication planning supports coordination, reduces misunderstandings, and enables decision-making.

3.1 Communication planning: what, who, when, and how?

A communication plan should specify:

• What information is communicated (status, risks, decisions, changes)
• To whom it is communicated (team, sponsor, executives, client, suppliers)
• When it is communicated (cadence: weekly, monthly, milestone-based)
• How it is communicated (reports, meetings, dashboards, emails)
• Format and level of detail (technical vs executive summaries)

In exams, communication plans are often asked as “components” and “purposes.” The purposes include:

• enabling timely decisions,
• ensuring accountability,
• maintaining stakeholder trust,
• documenting agreed changes,
• reducing rework caused by misunderstandings.

3.2 Communication channels and their appropriate use

Different channels serve different functions:

• Meetings: best for discussion, alignment, and decision-making. Must be structured with agendas and minutes.
• Written reports: best for recordkeeping, accountability, and formal updates.
• Dashboards/KPIs: best for ongoing visibility and trend tracking.
• Emails: best for quick updates, but risky if used for complex decisions without documentation.
• Workshops: best for problem-solving and requirements alignment.

Exam tip: always connect channel to purpose

If a question asks “which communication method would you use,” the high-mark answer explains why, linked to the decision or information nature.

3.3 Stakeholder mapping and engagement strategies

Stakeholders include any person or organisation affected by the project or able to influence it. A stakeholder mapping approach typically considers:

• Power/Influence (can block or enable decisions)
• Interest (how engaged they want to be)
• Attitudes (supportive, neutral, resistant)

Engagement strategies often include:

• Manage closely: high power, high interest (sponsor, steering committee)
• Keep satisfied: high power, lower interest (executives who need reassurance)
• Keep informed: lower power, high interest (end-user groups)
• Monitor: low power, low interest

In a South African public sector context, stakeholders might include:

• municipal officials,
• ward councillors,
• community representatives,
• contractors and suppliers.

3.4 Team collaboration mechanisms: meetings, reporting, and decision records

A project team needs collaboration rhythms. Typical mechanisms include:

• Kick-off meeting: purpose, roles, success criteria, initial risks.
• Daily/brief stand-ups (for agile or operational projects): quickly identify blockers.
• Weekly team meetings: progress, schedule updates, issue tracking.
• Risk reviews: evaluate new risks and monitor existing ones.
• Change control meetings: evaluate impact of proposed changes.
• Quality reviews: ensure deliverables meet standards.

A key exam concept is that decisions should be recorded. Decision records prevent “memory drift.” They also help with audits and project closure.

3.5 Running productive project meetings (exam-favoured practical skill)

Good meeting design includes:

1. Agenda preparation
2. Pre-read documents
3. Clear objectives (update only vs decision required)
4. Timeboxing
5. Role clarity (chair, note-taker, decision owner)
6. Minutes and action items
7. Follow-up and accountability

Common meeting failures:

• no agenda, unclear purpose,
• too many topics without prioritisation,
• decisions made informally without record,
• action items without owners or deadlines.

A project manager should treat meetings as governance tools, not social gatherings.

3.6 Conflict communication: de-escalation and professional dialogue

Conflict communication requires specific behaviours:

• Use factual evidence: “The schedule variance is 10 days due to procurement lead time.”
• Separate people from issues: don’t blame; discuss system/process.
• Confirm understanding: summarise the other party’s position.
• Seek options: “What are the alternatives and impacts?”
• Agree on next steps: document decision and follow-up actions.

If conflict is left unmanaged, it becomes relationship conflict and reduces team effectiveness. A mature project manager aims for early intervention.

3.7 Communication under uncertainty: risk and issue escalation

The project manager must communicate risks and issues in a timely manner. “Timely” is not about fear; it is about giving stakeholders enough time to respond.

A risk escalation mechanism should specify:

• risk threshold definitions (e.g., probability x impact)
• escalation timeframes (e.g., within 24 hours for severe risks)
• required information for escalation (impact, proposed response, dependencies)

For issues (things already happening), escalation must be faster because the project is already impacted.

4) Project Control Systems: Time, Cost, Quality, Risk, and Change Management for Teams

Project control is the bridge between planning and reality. PGM4817 expects that control is not merely measuring variances, but initiating corrective actions and keeping governance intact.

4.1 Control as a cycle: plan → measure → compare → act → learn

A robust control system follows:

1. Plan: define baselines for scope, schedule, cost, quality.
2. Measure: track progress and performance regularly.
3. Compare: assess variances against baselines.
4. Act: implement corrective actions and manage changes.
5. Learn: capture lessons and improve processes.

Exams often ask students to describe “how control helps ensure successful project delivery.” Use the cycle to show structured thinking.

4.2 Time and schedule control: preventing slippage

Schedule control includes:

• milestone tracking,
• critical path monitoring (where relevant),
• identifying schedule variance causes (e.g., dependency delays),
• applying corrective actions (re-sequencing tasks, resource reallocation).

A project manager must also manage the psychological effects of time variance:

• avoid surprise escalations,
• maintain team morale via realistic corrective strategies.

Example: schedule variance from supplier lead times

If a supplier’s lead time increases unexpectedly, the schedule slips. The project manager should:

• update the schedule with the new dependency timeline,
• assess downstream impacts (testing, installation, acceptance),
• communicate changes with evidence,
• propose mitigation (expedite shipping, alternative supplier, phased delivery).

4.3 Cost control: budgeting, forecasting, and earned thinking

Cost control typically involves:

• establishing a budget baseline,
• tracking actual spending,
• forecasting end costs,
• explaining cost variance causes.

Even if the course does not focus heavily on advanced Earned Value Management mathematics, exam answers should demonstrate cost thinking:

• distinguish between planned spending and actual spending,
• explain why variances occur,
• forecast the likely cost at completion.

4.4 Quality management: standards, verification, and acceptance

Quality is often misunderstood as “gold-plating.” Instead, in project terms, quality means meeting agreed requirements and fitness for purpose.

Quality control involves:

• quality planning (define quality requirements),
• quality assurance (processes to prevent defects),
• quality control (testing/inspection to confirm compliance),
• acceptance criteria (what counts as “done” and who signs off).

Team performance depends on quality roles:

• If a team member produces deliverables without quality checks, defects appear late and are expensive to fix.
• Quality reviews should happen at planned intervals.

4.5 Risk management: from identification to response and monitoring

Risk management is central to project control because uncertainty is continuous.

A risk management process typically includes:

1. Identify risks
   • brainstorm with the team,
   • review historical data,
   • analyse assumptions.
2. Analyse risks
   • estimate probability,
   • estimate impact,
   • determine risk priority.
3. Plan responses
   • avoid, mitigate, transfer, accept (depending on feasibility).
4. Implement responses
   • assign owners and deadlines.
5. Monitor and review
   • track new risks and changes in risk status.

In exam answers, emphasise that risk management is not a one-time task. It must be revisited as the project evolves.

4.6 Risk register and risk ownership: practical control

A risk register typically includes:

• description of risk,
• category (technical, schedule, cost, stakeholder, compliance),
• probability and impact estimates,
• risk level/priority,
• planned response,
• risk owner,
• status and triggers.

Ownership matters: if no one owns a risk response, the risk remains “on paper.” The project manager ensures every important risk has:

• an owner,
• an action plan,
• monitoring triggers.

Example: compliance risk in procurement

A procurement risk might be:

• Supplier does not meet compliance requirements.
  Response:
• prequalification checks,
• contract clauses,
• document verification.

The project manager should assign a procurement specialist or quality lead as risk owner.

4.7 Issue management: differences between risks and issues

An exam question may directly ask: “What is the difference between a risk and an issue?”

• Risk: potential problem that may occur in the future.
• Issue: a problem that has already occurred and is affecting the project now.

Issue management includes:

• logging issues,
• analysing impact on time/cost/scope/quality,
• assigning an owner,
• implementing corrective action,
• escalating if the issue exceeds team control.

4.8 Change management: controlling scope/time/cost impacts

Change is inevitable. Good change management means:

• changes are evaluated,
• impacts are assessed,
• decisions are documented,
• baselines are updated only with approval.

A typical change control flow:

1. Receive change request (what is changing?)
2. Record and categorise change (scope, schedule, cost, quality)
3. Assess impact (time, cost, quality, risk)
4. Recommend options (approve, reject, modify, defer)
5. Obtain approvals (from sponsor/steering committee depending on authority)
6. Implement approved change
7. Update baselines and communicate widely

Example: scope creep from stakeholder “small additions”

A stakeholder requests “small additions” (extra features) repeatedly. Individually, each request seems minor. Collectively, they:

• extend development time,
• increase costs,
• increase testing and defects,
• delay acceptance.

Change management is how the project manager prevents uncontrolled scope growth.

4.9 Integrating control with team leadership

A control system only works if the team trusts it. The project manager should:

• make performance criteria clear,
• treat measurement as improvement, not punishment,
• use variances to ask “what can we learn and adjust?”

If the project manager uses control only to blame, team members will hide problems, undermining governance. If control is used constructively, teams become proactive and resilient.

5) Performance, Accountability, Ethics, and Learning: Leading the Team to Sustainable Project Success

Successful project management in PGM4817 includes performance outcomes but also sustainable practices: ethics, accountability, lessons learned, and continuous improvement. This section consolidates “human governance” into actions that students can apply in exam scenarios.

5.1 Accountability frameworks: ownership, reporting, and authority alignment

Accountability is about ensuring that:

• people who are responsible for outcomes are identifiable,
• reporting lines reflect responsibility,
• decision rights match authority.

A governance-friendly way to express accountability is:

• define deliverables (what must be produced),
• define ownership (who is responsible),
• define sign-off (who approves acceptance),
• define escalation thresholds (when issues are too significant to resolve locally).

A common exam scenario involves misaligned accountability:

• a team member completes tasks but quality approval is delayed,
• the project manager assumes functional approval will happen automatically,
• stakeholders blame each other for delays.

A high-mark answer identifies the root cause as an accountability/design problem and proposes:

• clear sign-off procedures,
• acceptance criteria,
• meeting cadence for approvals.

5.2 Sponsor and steering committee engagement: keeping alignment

While the project manager drives delivery, sponsors and steering committees keep strategic alignment.

A sponsor typically:

• provides direction and benefits justification,
• ensures resources,
• removes high-level barriers,
• supports the project manager in decision-making.

A steering committee typically:

• reviews progress and performance,
• approves major changes,
• ensures governance compliance.

In exam questions, the project manager should communicate clearly with these structures. Poor alignment leads to:

• misdirected work,
• late discoveries,
• high change churn.

5.3 Ethical project management: transparency, fairness, and responsible decisions

Ethics in project management may be tested as short answers or applied scenarios. Ethical concerns include:

• Accurate reporting: no misrepresentation of progress.
• Conflict of interest management: procurement decisions must be fair.
• Respect for stakeholders: community and clients must not be manipulated.
• Data integrity: cost and schedule records must be credible.
• Human-centred treatment of team members: fairness in workload, safety, and respect.

Example: “optimistic reporting”

A team reports “green” status to satisfy leadership even though delivery is behind. When the truth is revealed later:

• stakeholders lose trust,
• corrective actions become more expensive,
• team morale collapses.

Ethical governance demands early escalation and honest performance data.

5.4 Performance indicators for team and project success

Performance indicators should be:

• measurable,
• relevant to deliverables and outcomes,
• aligned to baselines.

Typical project indicators include:

• Schedule performance: milestone completion, variance days.
• Cost performance: budget vs actual, forecast at completion.
• Quality performance: defect counts, acceptance pass rates.
• Risk performance: risk register updates, triggered responses.
• Stakeholder satisfaction: feedback, escalation frequency.

For teams, additional indicators include:

• deliverable completion within agreed standards,
• responsiveness (time to address issues),
• collaboration effectiveness (measured via feedback and meeting outcomes).

5.5 Coaching, mentoring, and team development over a project life cycle

Team needs change as the project progresses. The project manager should adapt support based on competence and pressure.

Practical coaching actions:

• conduct skills gap reviews,
• pair less experienced members with specialists,
• run short learning sessions after lessons learned,
• ensure documentation habits so knowledge is not “in people’s heads.”

A sustainable project manager avoids burnout by:

• monitoring workload distribution,
• rotating tasks when appropriate,
• planning realistic sprint/iteration timelines where relevant.

5.6 Lessons learned and continuous improvement: turning experience into better delivery

Lessons learned should not be a generic conclusion; it must be actionable.

A lessons learned process may include:

• capture lessons during major milestones,
• validate lessons with evidence,
• assign improvement actions to owners,
• integrate improvements into future planning,
• document what changed and why.

Exam markers prefer if you show:

• examples of what can be captured (process failures, communication breakdowns, decision mistakes),
• examples of what should change next time (new approval cadence, updated templates, earlier stakeholder involvement).

5.7 Post-project evaluation: closing governance and stakeholder handover

Project closure is not merely administrative. It ensures:

• deliverables are formally accepted,
• documentation is complete,
• contracts are closed,
• benefits realisation plans are understood,
• stakeholders are thanked and informed.

Key closure activities:

• Formal acceptance against criteria.
• Handover of deliverables to operations or clients.
• Final performance reporting:
  • what was achieved vs planned,
  • reasons for variances,
  • cost and schedule outcomes,
  • quality outcomes.
• Archive records (contracts, plans, approvals, change logs).
• Lessons learned meeting and documentation.
• Resource release (team members return to functional roles with closure clarity).

A well-managed closure reduces organisational friction after the project ends.

5.8 Applied case study synthesis: managing a multi-stakeholder delivery with team dynamics

To integrate the themes of PGM4817, consider a combined scenario suitable for exam application:

Scenario

A national education programme introduces a digital learning platform pilot in multiple provinces. A project manager leads a cross-functional project team:

• technical development team,
• content development team,
• procurement and vendor support team,
• stakeholder engagement team (schools and district offices).

The sponsor wants a pilot launch by a fixed date due to political and media attention. Early on, risk signals appear:

• supplier components have uncertain lead times,
• content review timelines vary between schools,
• data privacy requirements require additional compliance checks.

What the project manager should do (linking multiple exam topics)

1. Governance and charter: confirm scope boundaries and success criteria (what qualifies as pilot “ready”).
2. Team structure: ensure clear role allocation across teams (who owns content review, who owns technical integration).
3. Communication plan: establish a cadence for stakeholder updates and a separate technical reporting rhythm for internal risks.
4. Risk management:
   • log supplier lead time risk,
   • log compliance risk,
   • log content review variability risk,
   • assign owners and define triggers.
5. Control systems:
   • monitor schedule milestones,
   • forecast cost impact from added compliance work,
   • run quality gates before acceptance.
6. Change control:
   • prevent scope creep (extra features requested by schools without approval),
   • assess impacts and get sponsor decisions.
7. Conflict management:
   • facilitate task conflict between technical and content teams about integration priorities,
   • reduce relationship conflict by using structured meetings and decision records.
8. Ethics and transparency:
   • report accurate status even when the pilot schedule is under pressure.
9. Learning and closure:
   • capture lessons on compliance readiness and school onboarding,
   • adjust future rollout plans.

This scenario is valuable because it requires students to demonstrate that leadership, team management, communication, and control are not separate topics—they are interconnected in delivery.

5.9 Common exam pitfalls and how to avoid them

To score well in PGM4817-style questions, students should avoid these pitfalls:

• Only listing definitions without applying them to a project scenario.
• Ignoring governance (e.g., saying “just ask the supplier” instead of explaining change control, approvals, and accountability).
• Confusing risks with issues, or treating risks as if they are already happening.
• Explaining team conflict as purely negative, instead of showing constructive conflict and how to manage it.
• Reducing communication to “regular meetings” without stating who receives what information, when, and why.
• Assuming authority is automatic, without discussing role alignment and decision rights.

High-mark responses show clear logic:

• identify the problem,
• choose an approach linked to course concepts,
• justify the approach,
• state what documentation/controls ensure the decision is credible.

Quick Reference: High-Yield Terms and Exam-Ready Links

Key terms to remember

• Project governance: structures and decision rights ensuring alignment and control.
• Sponsor: provides strategic direction and resources; removes high-level blockers.
• Steering committee: oversight and major approvals.
• Change control: evaluate, approve, implement, update baselines.
• Risk vs issue:
  • risk = potential future event,
  • issue = already affecting the project.
• Quality management: quality planning, assurance, control, acceptance criteria.
• Communication plan: what/who/when/how and format detail.
• Accountability: clear ownership, reporting, authority, escalation thresholds.
• Lessons learned: actionable improvements tied to owners and evidence.

A simple exam-writing structure for scenario questions

1. State the problem (schedule, scope, team conflict, stakeholder misalignment, governance gap).
2. Identify relevant concepts from PGM4817 (team roles, communication plan, risk response, change control).
3. Propose actions step-by-step with governance and accountability.
4. Justify why your actions reduce risk and protect outcomes.
5. Mention documentation/recording (minutes, decision logs, updated registers, approvals).
6. Conclude with expected effect (better control, improved trust, reduced rework).

Summary

PGM4817 examines the project manager and project team as the human engine behind project delivery. Strong governance ensures alignment, transparency, and controlled decision-making; effective team management ensures roles, motivation, conflict resolution, and performance measurement. Communication systems and control cycles translate planning into real execution, while ethical leadership and lessons learned create sustainable improvement beyond the project end. Mastery of these concepts—applied to realistic scenarios—is essential for high marks in UNISA CEMS-style project management examinations.