Project Strategy and Governance (Wits Module) Study Notes

Project Strategy and Governance is a core module in many Wits University short courses and specialised offerings under the broader Project Management area, especially in programmes aligned to strategic planning, governance oversight, risk and compliance, and performance management. In practice, governance determines how decisions are made and by whom, while strategy determines where the project aims to go and why. Strong governance translates strategic intent into enforceable plans, measurable outcomes, and transparent accountability—reducing the likelihood of scope drift, stakeholder conflict, and unmanaged risk.

These study notes are written for exam preparation: they explain concepts clearly, present common assessment angles (e.g., “compare”, “discuss”, “apply to a scenario”), and include structured examples you can adapt to your own answers. The focus is on Wits-style project management thinking: integrated governance, disciplined decision-making, and performance-driven control.

Section 1: Foundations of Project Strategy & Governance in Wits Project Management Contexts

Project strategy and governance are not separate “topics” in real projects. Strategy without governance often becomes wishful thinking; governance without strategy can become bureaucracy. In the Wits Module context (commonly embedded in short courses and specialised project management learning), exam questions frequently test whether you can connect these two: how strategic choices lead to governance structures and controls.

Why Strategy Matters for Projects

A project is typically bounded by time, cost, scope, and quality. However, a project is also bounded by strategic purpose: what value it creates, which organisational objectives it supports, and which benefits stakeholders expect. Strategy answers questions such as:

1. What outcome are we pursuing?
   Example: improve service delivery, reduce operational costs, modernise systems, or develop new capability.

2. How does the project’s approach support that outcome?
   Example: adopt agile delivery for rapid feedback; use stage-gate for compliance-heavy deliverables; implement change management early if adoption is a known barrier.

3. What assumptions underpin success?
   Example: vendor capability, regulatory timelines, user readiness, and availability of skilled staff.

4. Which trade-offs are acceptable?
   Example: cost vs. speed; functionality vs. security; breadth of scope vs. time to value.

A strong strategic framing helps prevent common failure modes:

• Scope creep (“we thought of another feature”)
• Benefit neglect (delivering outputs, not outcomes)
• Misaligned priorities (project metrics do not reflect business value)
• Uncontrolled stakeholder expectations

Why Governance Matters for Projects

Governance is about rules, roles, procedures, and oversight. It provides the decision rights and accountability needed when projects involve uncertainty, competing interests, and resource constraints. Typical governance questions include:

• Who approves the project charter?
• Who can approve scope changes?
• What happens when risk materialises?
• How are disputes escalated and resolved?
• How is performance reported to senior leadership?
• When do we pause, revise, or terminate the project?

In exams, governance is often assessed via the candidate’s ability to describe:

• structures (steering committees, project boards, governance forums)
• processes (stage approvals, change control, risk escalation)
• documents (charters, business cases, benefit management plans, reporting templates)
• principles (transparency, accountability, fairness, responsiveness)

The Strategy–Governance Link: A Practical Model

A useful way to connect strategy and governance is to treat governance as the mechanism that makes strategy executable.

• Strategy defines “what success looks like” (outcomes, benefits, value, strategic alignment)
• Governance defines “how decisions get made and controlled” (approval gates, decision forums, authority levels, compliance requirements)
• Project execution defines “how work gets done” (planning, delivery method, coordination)
• Monitoring and control defines “how we learn and correct” (performance reporting, risk reviews, corrective actions)

Common Exam Phrase to Use

If you’re answering “discuss” questions, a strong exam-friendly framing is:

Governance ensures strategic intent is translated into enforceable controls, measurable performance, and accountable decision-making.

This shows you understand the direction of influence—not just definitions.

Wits-Style Governance Themes Examiners Often Look For

Although question formats vary, typical themes include:

1. Strategic alignment

   • How the business case ties to organisational objectives
   • Ensuring the project’s benefits are real and owned by business units

2. Decision rights and escalation

   • Clear escalation pathways for risks, issues, and change approvals
   • Authority boundaries (what the project manager can decide vs. what needs steering approval)

3. Evidence-based oversight

   • Governance based on data and documented assumptions
   • Not on opinions or political preferences

4. Risk and compliance integration

   • Governance structures reflect regulatory or contractual constraints
   • Stage-gates and approvals reflect compliance requirements

5. Accountability and transparency

   • Reporting is consistent, timely, and uses agreed metrics
   • Minutes, approvals, and decisions are traceable

A Short Scenario to Practise Connecting Strategy and Governance

Imagine a university unit launching a project to implement a student information system. Strategy decisions include:

• Outcome: improve student services and reduce processing time
• Approach: phased rollouts to reduce disruption

Governance decisions must follow:

• A steering committee approves stage plans and benefits targets
• A change control board approves feature changes affecting scope, compliance, or timelines
• A risk owner escalates security risks immediately
• Reporting includes both delivery metrics (milestones) and outcomes (processing time reduction)

If governance is missing—e.g., no stage approvals or change control—the system risks:

• delayed compliance approvals
• uncontrolled feature expansion
• benefit shortfalls because users were never trained or adoption was not measured

This kind of scenario connection is frequently rewarded in exams because it shows concept application, not only memorisation.

Section 2: Project Governance Structures, Roles, and Decision-Making Mechanisms

Governance works through structures and roles. Examiners often test whether you can (a) name typical governance bodies, (b) describe their responsibilities, and (c) explain decision-making mechanisms like stage-gates, change control, and escalation. In a Wits-focused project management environment, clarity on roles is especially important because Wits courses often emphasise professional practice standards and structured reporting.

Core Governance Roles (Who Does What?)

A typical governance model includes roles such as:

• Project Sponsor / Executive Owner

  • Owns the business case and benefits
  • Secures resources and resolves high-level issues
  • Approves major scope or strategic changes

• Project Manager

  • Manages day-to-day delivery
  • Builds plans and reports performance
  • Implements approved controls (risk management, issue management, change control processes)

• Steering Committee / Project Board

  • Provides oversight and strategic direction
  • Ensures alignment with organisational priorities
  • Approves key stages, monitors performance, and escalates decisions

• Technical or Domain Experts

  • Provide specialist guidance (e.g., architecture, compliance, security)
  • Validate technical feasibility and quality standards

• Business Owner(s) / Benefit Owner(s)

  • Owns operational outcomes (adoption, process improvement, service quality)
  • Confirms benefits realisation assumptions
  • Ensures business readiness (training, processes, governance integration)

• Procurement and Contracting Stakeholders

  • Ensure procurement compliance and contract governance
  • Oversee vendor performance and contractual change impacts

• Risk and Compliance Functions

  • Support risk identification, assessment, mitigation planning
  • Ensure regulatory and audit requirements are met

In exams, you may be asked: “Explain responsibilities of the project sponsor, project manager, and steering committee.” A high-scoring answer clearly distinguishes authority level and accountability.

Governance Structures: Steering Committees and Stage-Gates

Governance structures vary by organisation, but two common patterns are:

1. Steering committee / project board oversight

   • Regular meetings (e.g., monthly, bi-monthly, quarterly)
   • Key decisions are documented and communicated
   • Provides strategic guidance and resolves deadlocks

2. Stage-gate governance

   • Work is divided into stages (e.g., concept, design, procurement, implementation)
   • Entry and exit criteria exist for each stage
   • Approval is required to move to the next stage

Stage-Gate: Granular Components You Can Mention in Exams

A typical stage-gate model includes:

• Stage objectives
• Deliverables
• Stage exit criteria
• Review process
• Decision outcome categories, such as:
  • Approve to proceed
  • Approve with conditions
  • Hold (request more information)
  • Reject / re-plan
  • Terminate (if business case deteriorates)

This detail matters because governance isn’t just “a committee meets”; it is a structured method for decision-quality improvement under uncertainty.

Change Control: Governance of Scope, Cost, Time, and Quality

Change control is a classic governance process. It ensures that changes are assessed systematically rather than informally. A well-structured change control process typically includes:

1. Change request submission

   • Who requests the change (project team, stakeholder, regulator)
   • Description of the requested change
   • Rationale

2. Impact assessment

   • Scope impact
   • Cost impact
   • Schedule impact
   • Quality impact
   • Risk impact
   • Benefits impact (sometimes overlooked; should be included)

3. Change classification

   • Major vs minor changes
   • Changes that affect compliance or contractual obligations are usually major

4. Approval authority determination

   • Project manager authority for minor changes
   • Sponsor/steering committee for major changes
   • Procurement and legal involvement for contract-related changes

5. Implementation plan and communication

   • Update baseline documents
   • Communicate to stakeholders
   • Train impacted users if needed

6. Verification and closure

   • Confirm implemented change meets acceptance criteria
   • Update lessons learned

Why Change Control Is Often Examined

Change control is frequently targeted because it tests whether you understand:

• governance reduces chaos,
• accountability is required,
• decisions must be documented,
• and baselines need protection.

A common weak answer says “use a change request form.” A stronger answer adds impact assessment, classification, approval authority, and baseline updates.

Governance of Risk: Escalation and Ownership

Risk governance integrates with organisational decision-making. Key governance concepts:

• Risk ownership: each risk has an owner responsible for mitigation progress.
• Risk appetite: how much risk the organisation is willing to accept.
• Escalation thresholds: certain risks must be escalated immediately based on severity (impact x likelihood), time sensitivity, or compliance relevance.

A Concrete Risk Escalation Example

Suppose a project has a cybersecurity requirement for the protection of student data. A risk is identified:

• likelihood: possible
• impact: high (breach leads to compliance violations and reputational damage)

If the project’s governance defines that any high-impact cybersecurity risk must be escalated within a defined period (e.g., at the next steering session or within 5 working days), the governance process is “doing work” rather than just recording risks.

In exams, you can strengthen answers by describing:

• who escalates,
• when escalation occurs,
• and what governance decisions may follow (e.g., pause procurement until security review is completed).

Governance of Benefits: Beyond Outputs

Many learners focus only on output delivery (systems built, reports produced, training sessions completed). Governance should also cover benefits realisation. This includes:

• Benefit ownership (who is accountable for the operational outcomes)
• Benefit metrics (how success is measured)
• Measurement timing (when benefits will be observed)
• Assumption tracking (what must be true for benefits to materialise)

Example: Benefits Realisation Plan for a Student System Project

Possible benefits and metrics:

• Reduced average processing time for student applications
• Improved accuracy of registrations
• Increased student satisfaction scores

Governance mechanisms:

• Benefit owner confirms measurement methodology
• Baseline processing times are captured before rollout
• Benefits are reviewed after each rollout stage
• Steering committee receives benefits status alongside schedule progress

Governance of Procurement and Contracts

Procurement often introduces governance complexity:

• contractual obligations,
• performance penalties,
• delivery acceptance criteria,
• change orders.

A governance lens asks:

• Who approves vendor variations?
• How are contractual deliverables assessed?
• How do contract milestones align with stage-gates?
• How does risk management address vendor delivery risk?

In exam answers, linking procurement governance to overall project governance shows maturity: you are not treating contracts as a separate managerial silo.

Section 3: Project Performance Management, Monitoring & Control for Strategic Delivery

Performance management is where governance becomes visible. It involves selecting metrics, reporting performance, interpreting results, and taking corrective actions. Strategy determines what metrics matter; governance determines how decisions are made based on performance data. In a Wits Project Management module context, exam questions often test your ability to differentiate output metrics vs outcome/benefit metrics, explain control cycles, and propose corrective actions under constraints.

Performance Framework: From Strategy to Metrics

A useful performance chain is:

• Strategic intent → expected outcomes/benefits
• outcomes/benefits → key performance indicators (KPIs)
• KPIs → delivery targets (milestones and quality criteria)
• delivery targets → work package plans and operational controls
• operational controls → performance reporting
• reporting → governance decisions and corrective actions

Distinguishing Key Metric Types

You can improve exam answers by using clear distinctions:

• Input metrics: money spent, resources allocated
• Output metrics: deliverables produced (e.g., modules developed, training delivered)
• Outcome metrics: change achieved (e.g., time saved, satisfaction improved)
• Benefit metrics: financial or strategic value (e.g., cost reduction, improved enrolment retention)

A project that reports “on-time delivery” but achieves weak outcomes is still failing strategically.

Baselines and Control: Cost, Schedule, Scope, Quality

Governance requires baselines:

• Cost baseline
• Schedule baseline
• Scope baseline
• Quality baseline (standards and acceptance criteria)

Monitoring involves measuring actual performance against baselines. Control involves:

• corrective actions when variance occurs,
• preventive actions when trends show risk of future variance,
• re-planning when changes are approved.

Common Control Cycle for Exams

A structured answer often includes:

1. Measure actual performance
2. Compare against baselines
3. Analyse variance (why it happened)
4. Assess impact on forecast and risk posture
5. Decide response options
6. Implement corrective/preventive actions
7. Update plans and communicate via governance channels

Forecasting and Trend Analysis

Governance is forward-looking. A project’s current status is not enough; decision-makers need forecasts like:

• expected completion date,
• expected final cost,
• probability of meeting acceptance criteria,
• likely benefits realisation timeline.

Trend analysis often matters more than single-period measurements. Examples:

• If schedule variance is worsening for three consecutive reporting cycles, the risk of missing the target increases.
• If defects are increasing despite testing, quality risks escalate.

Quality Management as Governance Performance

Quality should not be treated as an “execution topic” only. Governance uses quality information to make decisions such as:

• whether to accept deliverables,
• whether to conduct rework,
• whether to adjust stage exit criteria.

Quality governance may include:

• adherence to standards,
• audit compliance checks,
• acceptance tests,
• performance testing,
• defect metrics (severity and frequency),
• independent verification and validation (IV&V) where appropriate.

In exams, try to explain:

• how quality measures feed steering decisions,
• and how “quality failure” can lead to stage-gate holds or changes.

Reporting: What Governance Needs to See

Reporting is a mechanism for transparency and accountability. Effective governance reporting typically includes:

• Executive summary (status, key decisions required)
• Progress against milestones
• Budget and cost status
• Scope status
• Quality status
• Risk register summary (top risks, mitigation status, changes)
• Issues log (what needs decisions or escalations)
• Change requests status
• Benefits status (if benefit reviews are established)

A Practical Reporting Template You Can Adapt

A high-scoring exam answer might present a table-like structure in words:

• Status: On track / At risk / Off track
• Key accomplishments since last report
• Key variances and causes
• Forecast for end date and total cost
• Decisions required from sponsor/steering committee
• Top risks and mitigation progress
• Top issues requiring escalation
• Next reporting and decision schedule

Even if your exam does not require a template, describing the content indicates governance maturity.

Decision-Making Based on Performance: Options and Trade-offs

When performance deviates from plan, governance must choose among response options:

• Corrective actions (fix current variance)
• Preventive actions (reduce recurrence)
• Re-baselining (only with approvals—requires governance)
• Scope adjustment (de-scope features or reorder priorities)
• Schedule compression (if feasible—often increases risk)
• Resource reallocation (increase capacity where constraints are identified)
• Termination (if business case fails)

A strong exam answer explains that decisions depend on:

• impact on benefits,
• cost of recovery,
• risk posture,
• sponsor acceptance,
• and governance authority.

Example: Schedule Slippage with High Compliance Risk

If a project is late due to compliance review delays, governance might decide:

• hold stage exit approval until compliance sign-off is obtained,
• allocate additional compliance resources,
• or adjust rollout sequence while keeping compliance milestones intact.

This shows governance understands “late is not always failure,” but “late + noncompliance” is critical.

Lessons Learned and Continuous Improvement

Governance should support learning. Continuous improvement includes:

• capturing lessons learned per stage,
• updating procedures and templates,
• reviewing root causes for major variances,
• ensuring corrective actions become standard practice.

In exams, mention how lessons learned feed back into governance processes, such as:

• updating risk escalation thresholds,
• improving change control effectiveness,
• refining stage exit criteria based on past failures.

Section 4: Strategic Planning Tools, Business Case Thinking, and Benefits Realisation Governance

Strategy and governance become concrete through planning tools: business case creation, benefits mapping, stakeholder analysis, and strategic alignment methods. This section focuses on “thinking tools” and how governance should operationalise them. Examiners often set scenarios where you must evaluate whether the business case is still valid, identify benefits owners, or justify strategic choices.

The Business Case: Governance’s Strategic Anchor

The business case is the justification for the project. Governance uses it to answer:

• Why this project?
• What value does it create?
• What are the costs, risks, and alternatives?
• Under what assumptions will value be achieved?
• What triggers justify stopping or modifying the project?

Business Case Components (Exam-Friendly)

A typical business case includes:

• Problem statement and opportunity
• Strategic alignment to organisational priorities
• Current-state analysis (baseline)
• Proposed solution options and why one is selected
• Cost estimates (CAPEX/OPEX where relevant)
• Benefits estimates (quantified and qualitative)
• Risks and mitigations
• Assumptions and dependencies
• Funding plan
• Delivery and governance approach

In exam answers, avoid treating the business case as a “document only.” Explain it as a decision tool that governance uses over time.

Benefit Management: From Planning to Tracking

Benefits realisation is a governance responsibility supported by performance management. Benefits planning includes:

• identify benefits categories,
• define benefit owners,
• specify measurement approach,
• establish baseline and target values,
• define review timeline.

Benefits may be:

• Financial (cost savings, revenue increases)
• Operational (cycle time reduction, improved reliability)
• Customer or stakeholder (satisfaction, service quality)
• Strategic (capability development, compliance readiness)

Example Benefit Measurement Logic

If a project aims to reduce processing time:

1. Baseline processing time is measured before implementation.
2. Targets are set for post-implementation periods.
3. Measurement occurs after stable operation begins (not immediately at rollout).
4. Governance reviews whether the benefit is achieved and if not, why.

Common governance failure: measuring benefits too early or using flawed baselines.

Stakeholder Analysis and Strategic Alignment

Projects fail often because of stakeholder misalignment. Governance requires stakeholder engagement strategies that support strategic delivery.

Stakeholder Mapping Components

A comprehensive stakeholder analysis includes:

• stakeholder identification,
• interest and influence assessment,
• likely concerns,
• engagement strategy,
• communication needs,
• decision participation requirements.

In governance contexts, stakeholders influence decisions on:

• acceptance criteria,
• change approval,
• compliance expectations,
• operational readiness and adoption.

Strategic Options and Decision Justification

Strategy questions may ask you to discuss alternative approaches and evaluate which is best under given constraints. Examples of strategic options:

• phased delivery vs full deployment
• agile vs predictive planning
• build vs buy (vendor selection)
• outsourcing vs internal development

Governance supports decisions by ensuring:

• options are evaluated consistently,
• costs and risks are compared transparently,
• stakeholders with decision rights are involved.

In a scenario, a high-scoring answer might show:

• why one option is chosen (value, risk, schedule),
• how governance ensures it remains valid if conditions change.

Governance for Assumptions and Dependencies

A business case includes assumptions and dependencies. Governance should track them because assumptions can fail.

Example assumptions:

• users will adopt the new system
• regulatory sign-off will be granted on time
• key staff are available

Dependencies:

• vendor availability
• network infrastructure readiness
• data migration support

Governance mechanism:

• assumptions register linked to risk register
• periodic review in steering meetings
• trigger conditions that require re-approval

Benefits Realisation Review Governance: Practical Staging

Many projects have a benefits review schedule aligned to delivery stages. A practical approach is:

• interim benefits reviews after each major milestone,
• post-implementation benefits validation,
• and final review after stabilisation.

This ensures governance does not treat benefits as a “future promise” without oversight.

Example Timeline (Conceptual)

• Stage 1: discovery and planning → benefits baseline confirmed
• Stage 2: build and testing → early readiness progress
• Stage 3: rollout → operational metrics begin tracking
• Stage 4: stabilisation → benefits targets measured and reported

Even when dates are not specified in the question, demonstrating awareness of staged benefits governance can improve scoring.

Strategic Governance: Managing Strategic Risks

Strategic risks are those that threaten the project’s ability to deliver intended value. Governance must:

• define strategic risk categories,
• link strategic risks to benefits and assumptions,
• escalate quickly when risks change.

Strategic risk examples:

• competitive changes reduce the project’s value
• organisational strategy pivots
• regulatory environment changes
• technology becomes obsolete before implementation

A mature exam answer connects these risks to governance decisions:

• re-evaluate business case,
• adjust scope or approach,
• or terminate if value is no longer achievable.

Counter-Argument to Consider: “Too Much Governance Slows Delivery”

Exams sometimes reward balanced discussion. One counter-argument to strong governance is that it may slow delivery through approvals and documentation. A strong response explains:

• governance can be streamlined with risk-based decision-making,
• minor changes can be handled at project level with clear authority,
• stage-gates can be shortened if criteria are met,
• governance should be evidence-based to avoid unnecessary delays.

The key is to argue governance is proportionate—not excessive.

Example: Applying Business Case Thinking to a Governance Decision

Scenario:
A project has delivered 90% of planned outputs but benefits are delayed because adoption hasn’t occurred due to insufficient change management.

Governance response may include:

• revisit benefits assumptions (user adoption dependency),
• allocate additional resources to training and process redesign,
• adjust rollout and comms schedule,
• and update benefit measurement plan.

This demonstrates that governance cares not only about delivery progress, but also about value creation.

Section 5: Exam-Ready Practice Frameworks, Governance in Real-World Scenarios, and Risk-Controlled Strategy Execution

The final section consolidates everything into exam-ready frameworks and scenario responses. This is where you practise how to structure answers: define the concept, apply to a scenario, and justify governance mechanisms. Since Wits module exams often use applied questions, this section provides “answer skeletons” you can reuse for different topics.

How to Structure “Discuss” and “Explain” Answers for Wits-Style Questions

A reliable structure:

1. Define the concept (1–2 sentences)
2. Explain why it matters (link to project outcomes)
3. Break down components (roles, processes, documents, metrics)
4. Apply to a scenario (what happens in the given case)
5. Conclude with a governance implication (decision, oversight, accountability)

Using this structure consistently improves clarity and marks.

Answer Skeleton: “Describe the project governance model and decision rights”

Use this template:

• Identify key governance bodies (e.g., sponsor, steering committee, project manager)
• Clarify decision rights:
  • what the project manager can approve,
  • what requires steering/sponsor approval,
  • what must be escalated
• Describe governance processes:
  • stage-gates,
  • change control,
  • risk escalation,
  • reporting cadence
• Explain accountability:
  • who owns business case and benefits,
  • who owns delivery,
  • who verifies compliance/quality

Mini Example You Can Adapt

If asked about decision rights, you can write:

• “Minor scope changes that do not affect compliance are approved by the project manager through a change control workflow.”
• “Major changes that affect benefits, cost baseline, or contractual obligations require steering committee approval.”
• “High-impact compliance risks are escalated immediately to sponsor and compliance functions.”

This shows precision and governance logic.

Scenario Workshop 1: Budget Overrun with Unchanged Milestones

Scenario: The project is meeting all milestone dates, but costs are exceeding the cost baseline due to increased vendor expenses and rework.

Governance questions you should address:

• Is the business case still valid? (benefits vs costs)
• What approvals are required for additional spending?
• Are changes recorded under change control?
• Are risks updated (vendor delivery risk, rework risk)?
• What corrective actions are available?

Exam-ready answer approach:

1. Explain that governance uses cost baseline and change control to control spending.
2. Emphasise that meeting milestones is not enough if quality or cost variance undermines benefits.
3. Propose corrective actions:
   • audit cost drivers,
   • implement rework root cause analysis,
   • renegotiate vendor terms if contract permits,
   • and escalate to sponsor if it impacts the business case.

This answer demonstrates performance management and governance integration.

Scenario Workshop 2: Stage-Gate Failure Due to Quality Non-Compliance

Scenario: At a stage exit review, acceptance criteria are not met due to security vulnerabilities. The team requests approval to proceed to the next stage anyway.

Key governance points:

• stage exit criteria exist for a reason,
• governance should not “override” compliance without documented risk acceptance,
• quality non-compliance can increase strategic risk and undermine trust.

Strong exam argument:

• “Steering approval requires evidence that risks are mitigated to an acceptable level, or else the stage should be held.”
• “If governance approves proceeding, then a risk acceptance decision must be documented with clear accountability and mitigation plan.”

This provides a balanced view: governance is firm, but it can adapt with formal decisions.

Scenario Workshop 3: Benefits Not Realised After Rollout

Scenario: A project implemented new processes and trained users, but operational performance improved only slightly compared to targets.

Governance implications:

• benefits owner accountability,
• assumption tracking,
• measurement accuracy,
• and change management effectiveness.

Exam-ready answer outline:

1. Explain difference between output delivery and benefit achievement.
2. Review benefit baseline and measurement method.
3. Identify adoption gaps: training relevance, process redesign, or user resistance.
4. Trigger governance corrective actions:
   • adjust operational rollout support,
   • refine KPI targets or measurement windows,
   • update assumptions and business case if needed.

This shows you understand benefit governance, not just project delivery.

Risk-Controlled Strategy Execution: A Maturity Model Lens

Examiners like frameworks. You can describe maturity in governance/strategy execution as progressing through:

1. Ad hoc: decisions are informal; risks recorded without escalation
2. Defined: governance roles and processes exist
3. Managed: reporting and performance management are consistent
4. Optimised: governance is proportionate, data-driven, learning-focused

In exams, you can conclude:

• high maturity enables faster decisions with fewer surprises,
• but relies on discipline in documentation, reporting, and evidence.

Common Pitfalls (And How to Avoid Them in Answers)

1. Pitfall: Only describing governance structures without processes

   • Fix: include stage-gates, change control, risk escalation, and reporting.

2. Pitfall: Only discussing project management tools (e.g., plans)

   • Fix: show governance oversight, approval gates, decision rights, and accountability.

3. Pitfall: Confusing outputs with benefits

   • Fix: explicitly separate deliverables from measurable outcomes and benefits.

4. Pitfall: No scenario application

   • Fix: map each governance mechanism to the problem in the scenario.

5. Pitfall: Overly generic statements

   • Fix: add concrete examples: “who approves,” “what triggers escalation,” “what is reported.”

Exam-Ready Terminology Checklist

You can use these terms (without overstuffing) to show conceptual command:

• Business case
• Benefits realisation
• Sponsor / project board / steering committee
• Stage-gate
• Change control
• Risk escalation
• Decision rights
• Baselines (cost, schedule, scope, quality)
• Performance reporting
• Assumptions and dependencies
• Risk appetite
• Quality acceptance criteria
• Root cause analysis
• Corrective and preventive actions
• Lessons learned

Including a few of these in relevant places improves exam credibility.

South African University-Style Framing (Wits Module Linkage)

In South Africa, students often encounter governance and strategic delivery topics in the broader project management curriculum and closely related modules across institutions. Wits-related short courses and specialisation paths within project management commonly overlap with the exam language used in modules found in university postgraduate certificates and diplomas (and in some professional bridging programmes). While each institution has its own code and rubric, the expected marks usually reward the same underlying competencies:

• explaining governance mechanisms clearly,
• applying them to plausible organisational and delivery scenarios,
• using a structured approach to risk, benefits, and performance reporting.

Final Exam Practice: A 10-Point Governance Response Plan

If you’re asked a long question in the exam, use this response plan in your mind (and write it in structured paragraphs):

1. Define governance and strategy relationship
2. Identify governance bodies/roles
3. Explain decision rights and escalation
4. Describe stage-gate logic
5. Explain change control process
6. Describe monitoring/reporting content
7. Link performance metrics to strategy and benefits
8. Explain risk ownership and escalation triggers
9. Provide corrective action options and governance approvals
10. Conclude with how governance protects strategic value

This plan helps you avoid missing major components and ensures a coherent answer.

If you want, I can also generate mock exam questions specifically aligned to the above notes (with model answers) for common Wits-style prompts such as “Discuss governance mechanisms,” “Explain stage-gate criteria,” “Apply risk escalation,” and “Evaluate benefits realisation governance.”