Bachelor of Commerce (BCom) in Project Management (Regent) Study Notes

A Bachelor of Commerce (BCom) in Project Management at Regent Business School is designed to connect core commerce foundations—accounting, economics, business law, and management—with the practical discipline of planning, executing, monitoring, and closing projects. These Exam Notes / Study Notes compile the most commonly assessed themes in project management modules as a BCom student is typically expected to understand them: scope and scheduling, cost and risk, procurement, governance, stakeholder management, and project finance. The notes also support how South African distance-learning learners commonly study for Regent-style assessments by pairing definitions with exam-friendly frameworks, step-by-step procedures, and worked mini-examples.

This guide is aligned with the way students in South Africa search for and prepare for qualification modules (e.g., “project management exam notes”, “BCom project management study notes”, “mng / mng 0001 / pm exam notes” style keywords). It is written for learners using Regent Business School Project Management Qualification Notes, with an exam-focused approach: clarity first, then application.

Regent Business School: BCom Project Management Core Frameworks (Regent PM Modules)

Regent Business School’s Project Management qualification typically builds from general management principles into specialized project planning and controls. Even if your module codes differ across academic years, the learning outcomes in project management almost always map to the same “exam kernel”: the project lifecycle, the PM knowledge areas, and the tools/processes used to manage time, cost, scope, quality, risk, and stakeholders.

How Project Management Questions Are Usually Structured in Exams

South African university exams in business and management disciplines often test three layers of understanding:

1. Conceptual definitions
   • e.g., “Define scope creep.”
   • “Explain the difference between a program and a project.”
2. Process and tools
   • e.g., “Use a WBS to break down a deliverable.”
   • “Explain the critical path method (CPM).”
3. Application to scenarios
   • e.g., “A contractor is delayed due to material lead times—how do you respond using risk and schedule controls?”

Project management papers commonly mix short questions (definitions, contrasts, list formats) with long scenario questions (you must propose a plan, justify choices, and show calculations or structured reasoning). A good exam answer therefore uses a consistent structure:

• State the principle (1–2 lines)
• Apply to scenario facts (3–6 lines)
• Justify (2–4 lines)
• Close with an outcome (1–2 lines)

The Project Lifecycle (And Why It’s a High-Frequency Exam Topic)

A project lifecycle describes the progression from idea to completion. Most Regent-style project management questions expect the classic stages:

• Initiation
• Planning
• Execution
• Monitoring & Controlling
• Closing

Initiation: From Need to Project Charter

In initiation, the project manager (or project sponsor) ensures the project has a legitimate business case and is formally authorized.

Key exam terms:

• Business case: Why the project exists (value, costs, feasibility).
• Project charter: The document that authorizes the project and provides high-level objectives.
• Stakeholders: People/organizations affected by or influencing the project.

Typical exam pitfall: Students confuse initiation with planning. Initiation sets “what and why,” while planning decides “how.”

Planning: The “Blueprint” Phase

Planning translates objectives into detailed management plans:

• Scope management plan
• Schedule plan
• Cost management plan
• Quality management plan
• Risk management plan
• Communication plan
• Procurement plan
• Stakeholder engagement plan

The exam frequently asks you to outline these plans and link each to an objective.

Execution: Delivering the Work

Execution involves:

• Coordinating people and resources
• Implementing the planned activities
• Managing team performance

In scenario questions, execution is where you mention:

• Resource deployment (roles and responsibilities)
• Issue resolution (operational problems)
• Quality assurance (process compliance and deliverable inspection)

Monitoring & Controlling: “Variance Management”

Monitoring & controlling ensures performance matches the baseline. You measure actual results and take corrective/preventive actions.

Exam keywords:

• Baseline: Approved plan used as reference (scope baseline, schedule baseline, cost baseline).
• Variance: Difference between planned vs actual.
• Corrective action: Change to bring performance back on track.
• Preventive action: Address root causes to avoid future variance.

Closing: Formal Acceptance and Lessons Learned

Closing includes:

• Acceptance of deliverables
• Administrative closure
• Documentation and lessons learned

A common exam prompt: “Explain how lessons learned improve future projects.”

Project Governance and Roles (Sponsor, PM, Team, Steering Committee)

Many learners treat project governance as “management structure,” but exams reward deeper definitions.

Typical Roles

• Project sponsor: Supports and funds the project; removes obstacles.
• Project manager: Plans, coordinates, monitors, and reports; accountable for performance.
• Steering committee / executive committee: Provides strategic direction and resolves escalations.
• Project team: Performs the work.
• Functional managers: Provide resources and ensure alignment to functional goals.

Governance Mechanisms

Exams may ask for governance mechanisms such as:

• Stage gates (approval checkpoints)
• Change control board (CCB)
• Status reporting cadence
• Escalation procedures
• Benefits review (especially in commerce/business contexts)

Work Breakdown Structure (WBS): How to Score Marks

The WBS is one of the most exam-friendly tools because it is straightforward to demonstrate logically.

WBS Definition

A Work Breakdown Structure is a hierarchical decomposition of the total project scope into smaller components (work packages).

How to Construct a WBS in Exams

A step-by-step approach:

1. Start with the final deliverable(s)
2. Break deliverables into major components
3. Continue decomposing into manageable work packages
4. Ensure work packages are measurable
5. Assign ownership and link to schedule and cost

Work package criteria (common exam expectation):

• Clear deliverable
• Defined scope boundaries
• Estimated duration and cost
• Owner assigned

Mini-Scenario Example (Exam-Style)

Suppose the deliverable is: “Implement an Enterprise Resource Planning (ERP) system.”
A decomposed WBS might include:

• ERP Project Management
  • Project planning and governance
  • Requirements gathering coordination
• ERP Configuration
  • Business process mapping
  • System configuration
• Data Migration
  • Data cleansing
  • Data import and validation
• Testing
  • Unit testing
  • User acceptance testing
• Training and Change Management
  • Training sessions
  • Go-live support

Even if your module uses different terminology, the WBS logic stays consistent.

Scheduling Basics: CPM, Gantt, and Milestones

South African exams frequently test:

• Difference between Gantt charts and CPM
• Ability to read a simple schedule logic
• Critical path reasoning in scenario questions

Gantt Charts

A Gantt chart visualizes tasks and durations over time. It’s great for:

• Communication
• Timeline snapshots
• Tracking progress at task level

But Gantt charts alone may not identify critical dependencies. That’s where CPM helps.

Critical Path Method (CPM)

CPM identifies the longest sequence of dependent activities that determines project duration.

Key terms:

• Forward pass: earliest start/finish times
• Backward pass: latest start/finish times
• Float/Slack: how much a task can slip before it affects the finish date

In exams, you may be asked to:

• Identify critical activities
• Explain what happens if a critical task is delayed

Milestones

Milestones are significant events or checkpoints, often used for reporting and governance.

In a procurement-heavy project, milestone examples include:

• Contract awarded
• Equipment delivered
• Installation complete
• System go-live

Cost Management: Estimating, Budgeting, and Control

Cost questions commonly test:

• cost estimate types
• budgeting logic
• earned value concepts (if covered in your course)
• how to respond to cost overruns

Cost Estimate Types (Conceptual)

• Order of magnitude: very rough early estimate
• Budgetary: more detailed, used for planning
• Definitive: detailed estimate closer to execution

Budgeting vs Estimating

• Estimating: predicting costs
• Budgeting: allocating the estimate into a baseline distribution

Exam-Ready Control Concepts

If actual costs exceed baseline:

• Assess whether scope changed (scope creep)
• Evaluate schedule impact (delay costs)
• Investigate procurement variations (supplier pricing)
• Use corrective actions (optimize resources, re-baseline with approval)

Stakeholder Management: From Identification to Engagement

Stakeholder management is frequently tested through case scenarios involving:

• conflicting interests
• resistance to change
• communication failures

Stakeholder Identification

Common categories:

• Internal (project team, department heads)
• External (suppliers, regulators, community)

Stakeholder Analysis Tools

• Power/interest grid
• Influence mapping
• Issue log

Engagement Strategy Examples

• High power, high interest: manage closely, involve in decisions
• High power, low interest: keep satisfied, concise communication
• Low power, high interest: keep informed, involve in feedback
• Low power, low interest: monitor with minimal effort

In exam answers, always link stakeholder engagement actions to risk reduction.

Risk, Procurement, and Quality in Regent-Style Commerce Project Management

Project management in a commerce qualification doesn’t treat risk as a “technical side topic.” Exams typically expect you to connect risk to cost, schedule, quality, and business value—and to show practical responses.

Risk Management: Register, Assessment, and Response

What Is Project Risk?

A project risk is an uncertain event or condition that, if it occurs, affects project objectives (scope, schedule, cost, quality, or benefits).

Risk Management Process (Exam Structure)

1. Identify risks
2. Perform qualitative analysis
3. Perform quantitative analysis (if required)
4. Plan risk responses
5. Implement responses
6. Monitor risks

In scenario questions, you normally don’t need advanced statistics unless the paper asks for it. But you must show logical reasoning and credible actions.

Identifying Risks: Common Sources

High-frequency risk categories in business/ERP/construction/IT projects:

• Technical risks: system integration complexity, performance requirements
• Schedule risks: dependency delays, resource availability
• Cost risks: price increases, currency fluctuations, labor rates
• Procurement risks: supplier delays, contract disputes
• Compliance risks: regulatory requirements, audit findings
• People risks: resistance to change, skill gaps
• Vendor risks: SLA noncompliance

Exam tip: If your scenario includes a specific constraint (e.g., “materials have a 6-week lead time”), treat it as a schedule risk and also as a procurement risk.

Qualitative Risk Analysis: Likelihood × Impact

Qualitative analysis ranks risks using scales such as:

• Likelihood: Low / Medium / High
• Impact: Low / Medium / High

Often exams ask you to create a risk matrix and identify:

• High priority risks requiring active management
• Low priority risks suitable for monitoring

Example Risk Matrix Logic (No complicated math required)

• High likelihood + high impact → top priority
• Low likelihood + low impact → monitor

Then ask: “What response strategy would you choose?”

Risk Response Strategies: Avoid, Mitigate, Transfer, Accept

A strong exam answer includes:

• the correct strategy selection
• a brief justification
• the action detail (who does what)

Avoid

Change the plan to eliminate risk cause.

• Example: choose an alternative technology with fewer integration dependencies.

Mitigate

Reduce likelihood and/or impact.

• Example: hold additional vendor testing, create buffer time, increase training sessions.

Transfer

Shift impact to a third party.

• Example: use warranties, performance bonds, insurance, fixed-price contracts (where appropriate).

Accept

Acknowledge risk and prepare contingency.

• Example: build contingency reserve time/cost; no plan changes unless triggered.

Worked Mini-Scenario: Schedule Delay Risk

Scenario: A project depends on a supplier delivering equipment. Supplier lead time is uncertain; current estimate is 5–7 weeks. The baseline schedule allocates 6 weeks.

Risk identification:

• If delivery arrives at 7 weeks, delivery milestone slips by 1 week.

Risk response:

• Mitigate: place order earlier, negotiate expedited shipping options, ensure interim storage/installation readiness.
• Transfer: include penalties in procurement contract (where feasible) or warranty terms.
• Accept: if acceleration is too expensive, set contingency schedule buffer and document trigger conditions.

An exam might ask you to “recommend response strategies.” Your answer should show a balanced approach—cost trade-offs are expected in commerce contexts.

Procurement Management: Contracts, SLA, and Buyer-Supplier Governance

Procurement questions often test your ability to:

• describe contract types
• explain procurement planning stages
• link procurement decisions to risk and cost control

Procurement Planning

Procurement planning identifies:

• what to buy
• when to buy
• how to buy
• contract strategy

Exams may ask: “Explain why procurement planning should start early.”
Answer logic:

• supplier lead times
• contract negotiation time
• quality verification planning

Contract Types (Conceptual, Exam-Common)

Common contract types:

• Fixed-price: contractor bears cost risk; good for stable scope.
• Cost-reimbursable: buyer bears more cost risk; good for uncertain scope.
• Time and materials: flexible for evolving work; must control rates and usage.

In exam scenarios, choose based on uncertainty:

• If scope is stable: fixed-price can be safer for budget control.
• If scope is uncertain: cost-reimbursable or T&M may reduce contractor resistance.

Service Level Agreements (SLA)

If your procurement relates to services (e.g., IT support), an SLA defines:

• service performance levels
• response and resolution times
• reporting requirements
• remedies for nonperformance

In exams, SLAs relate strongly to quality and risk mitigation.

Procurement Stages (What to Write for Full Marks)

A logical sequence:

1. Request for proposal/quotation (RFP/RFQ)
2. Bid evaluation
3. Supplier selection
4. Contract negotiation
5. Contract award
6. Supplier performance monitoring
7. Contract closure

Scenario questions often require you to justify evaluation criteria. Common criteria include:

• total cost of ownership
• past performance
• delivery capability
• compliance with requirements
• risk posture (financial stability, capacity)

Quality Management: Quality Planning and Control

Quality questions may appear as:

• definitions (quality assurance vs quality control)
• process planning
• methods for inspections/testing
• continuous improvement and corrective actions

Quality Assurance vs Quality Control

• Quality assurance (QA): process-focused—ensures the team is doing the right things correctly.
• Quality control (QC): product/deliverable-focused—checks whether output meets requirements.

In exams, if asked “what’s the difference,” you should include these definitions and provide a short example.

Quality Planning: Requirements and Acceptance Criteria

Quality planning includes:

• quality standards and benchmarks
• acceptance criteria
• inspection/testing methods
• documentation requirements

In a commerce context (e.g., ERP system), quality might include:

• accurate data migration
• correct process configuration
• user acceptance test (UAT) pass rates
• transaction integrity

Root Cause and Corrective/Preventive Action

Exams love frameworks that show logical improvement:

• Identify defect or deviation
• Determine root cause
• Apply corrective action
• Prevent recurrence with preventive action

If your course uses structured methods, you can reference:

• 5 Whys
• Fishbone (Ishikawa) in qualitative analysis
• Pareto principle (focus on most frequent causes)

You should not overcomplicate—just show sound reasoning.

Finance, Business Case, and Economics of Project Management (BCom Lens)

Because the qualification is a Bachelor of Commerce, exams often assess how well you understand the economic justification for projects and the financial logic behind cost, benefits, and investment decisions. Instead of treating project management as “only schedules and templates,” commerce modules test business outcomes.

The Business Case: Why Financial Thinking Matters

A project business case explains:

• costs (initial and ongoing)
• benefits (quantified and qualitative)
• risks and uncertainties
• feasibility and alternatives
• expected value over time

A frequent exam requirement is to describe what happens if benefits do not materialize:

• revisit assumptions
• change scope or strategy
• implement benefits tracking and monitoring

Benefit Types: Tangible vs Intangible

Tangible Benefits

Examples:

• cost reduction (fewer operational hours)
• increased revenue (new product launch)
• reduced downtime (improved availability)

Intangible Benefits

Examples:

• customer satisfaction
• compliance readiness
• improved decision-making quality

Exams may ask how intangible benefits can still be managed:

• convert to proxy metrics (surveys, SLA compliance)
• track leading indicators
• align benefits to strategic objectives

Discounting and Time Value of Money (If Covered)

Many commerce-based projects include investment evaluation.

Typical methods:

• NPV (Net Present Value)
• IRR (Internal Rate of Return)
• Payback period

Even if your Regent module doesn’t require full calculations, you should explain:

• why future benefits are less valuable than immediate cash flows
• how discount rates affect decision outcomes

Cash Flow Basics for Project Evaluation

A simple project evaluation logic:

1. Estimate initial investment costs
2. Estimate annual benefit inflows (or cost savings)
3. Estimate ongoing costs
4. Apply discount rate
5. Calculate NPV/IRR or justify based on payback

Exam scenario example (conceptual):
If two projects have similar total benefits but one returns benefits earlier, it typically scores better under discounting principles.

Budgeting and Cost Control: Reserves and Contingency

A commerce-friendly explanation distinguishes:

• contingency reserve: for known unknowns (identified risks)
• management reserve: for unknown unknowns

Exams often ask: “What is the purpose of contingency reserve?”
A strong answer:

• to fund risk response actions without disrupting baseline approvals
• to reduce schedule/cost shocks from expected uncertainties

Financing and Procurement Link

Finance and procurement connect via:

• payment terms
• milestone-based billing
• retention clauses (construction/service quality assurance)
• supplier financing costs

If a scenario indicates late payments, you should identify procurement and relationship risk.

Earned Value Management (EVM): If Present in Your Module

Some project management curricula include earned value concepts as part of monitoring and controlling.

Core terms:

• PV (Planned Value): what budget planned to achieve by a date
• EV (Earned Value): what budget actually earned based on completed work
• AC (Actual Cost): what it actually cost

Key performance indicators:

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

If your exam requires calculations, you must be consistent with units (e.g., Rand values vs percentage complete).

Worked example (simple, exam-friendly):
Assume by day 30:

• PV = R300,000 (planned)
• EV = R240,000 (earned)
• AC = R270,000 (actual)

Then:

• CV = EV − AC = 240,000 − 270,000 = −R30,000 (over budget)
• SV = EV − PV = 240,000 − 300,000 = −R60,000 (behind schedule)
• CPI = 240,000 / 270,000 = 0.89
• SPI = 240,000 / 300,000 = 0.80

In an exam response, interpret:

• CV negative → cost efficiency is poor
• SV negative → schedule progress is behind

And propose actions:

• cost corrective actions (replan, optimize resources)
• schedule corrective actions (fast tracking, adjust dependencies)

Project Cost Breakdown and Cost Drivers

Exams sometimes ask about what drives cost in projects.

Common cost drivers:

• labor rates and availability
• procurement pricing
• rework due to poor scope definition
• delays due to dependency management
• change requests and scope creep
• quality failures and defect remediation

A commerce-minded approach emphasizes:

• reducing rework saves money
• scope changes should pass through formal change control
• early planning reduces expensive late corrections

Communication, Change Control, and Exam-Ready Project Management Implementation

Beyond technical project planning, exams frequently evaluate whether you can manage human and governance dynamics: communication, change control, issue escalation, and close-out documentation.

Communication Management: Stakeholder Updates That Earn Marks

Communication management covers:

• who needs information
• what information is needed
• when communication occurs
• how it is delivered
• why it matters (decision/action)

Core Communication Tools

• Project status reports
• Steering committee dashboards
• Risk registers
• Issue logs
• Meeting minutes and action registers
• Dashboards and KPI trackers

A Good Exam Answer Includes “Cadence”

Exams like cadence because it shows process maturity:

• Weekly team stand-up (operational)
• Fortnightly project status (stakeholders)
• Monthly steering committee (governance and decisions)

Meeting Structure (Exam-Style Bullet Answer)

A high-scoring structure for project meetings:

1. Agenda
2. Review prior actions
3. Progress update
4. Key risks and issues
5. Schedule and budget variance
6. Decisions required
7. Action items assigned with owners and due dates

If you include “decisions required,” you show governance thinking.

Issue Management vs Risk Management (Common Confusion)

• Risk: uncertain future event/condition.
• Issue: occurred event already affecting the project.

If an exam asks to “differentiate risk and issue,” write:

• risk is proactive planning; issue requires immediate action.
• risk uses contingency planning; issue uses corrective action and escalation.

Change Control: Preventing Scope Creep and Stabilizing Delivery

Change control is central to keeping projects aligned to objectives.

The Change Control Process (General Steps)

1. Change request submitted
2. Impact assessment (scope, schedule, cost, quality, risk)
3. Review by CCB / stakeholders
4. Decision: approve/reject/approve with conditions
5. Update baselines if approved
6. Communicate change and implement

Impact Assessment: What to Mention

Exams reward listing impacts:

• schedule (duration, critical path changes)
• cost (labor/material increases, contingency usage)
• quality (new requirements, testing implications)
• risk (new vulnerabilities or reduced uncertainties)
• stakeholder impacts (training, acceptance)

Scope Definition: Requirements and Deliverables

A major source of poor projects is weak scope definition.

Core scope-related terms:

• Requirements: what the deliverable must do.
• Deliverables: tangible outputs produced.
• Acceptance criteria: how you know deliverables are complete/acceptable.

A strong exam strategy: Always link scope definition to acceptance and quality.

Closing and Lessons Learned: The “Final Marks” Section

Closing is not simply “finish paperwork.” Exams expect closure includes:

• Verify deliverables meet acceptance criteria
• Obtain formal sign-off
• Release resources
• Archive project documentation
• Conduct lessons learned session
• Update organizational process assets for future use

Lessons Learned Categories

• process improvements
• risk response improvements
• stakeholder engagement improvements
• technical estimation and planning improvements

A high-scoring answer includes “how lessons learned will be used next time,” not only that it is documented.

How to Answer Common Regent/SA Project Management Exam Questions (Template Library)

This section compiles exam-ready templates that you can adapt to scenarios.

Template 1: “Explain and Apply” (Used in 10–15 mark questions)

1. Define the concept.
2. Describe the process steps.
3. Apply to the given scenario using 2–4 facts.
4. Recommend actions with justification.
5. Conclude with expected outcomes.

Template 2: “Identify Risks” (If asked for risk identification)

1. List at least 5 risks (more if mark allocation is high).
2. For each risk provide:
   • cause (why it could happen)
   • event/condition (what could occur)
   • potential impact (cost/time/quality)
   • risk response (avoid/mitigate/transfer/accept)

Template 3: “Build a WBS”

1. Identify top-level deliverable(s).
2. Break down into major components.
3. Break down into work packages.
4. Ensure work packages are measurable.
5. Link work packages to scheduling and ownership.

Template 4: “Change Control Scenario”

1. State the need for change control.
2. Identify the change request.
3. Perform impact assessment categories:
   • scope, schedule, cost, quality, risk, stakeholder
4. Recommend decision and next steps.
5. Explain baseline update and communication plan.

Worked Example: Integrating Scope, Schedule, Risk, and Quality

Use this integrated mini-case because many exams ask multi-layered questions.

Scenario: A company is launching a new customer billing system. The project includes software configuration, data migration, testing, and staff training. The company reports that customer data quality is “uncertain,” and the vendor has a limited schedule window for testing. Additionally, stakeholders request adding a new reporting dashboard late in the project.

Scope

• Define deliverables: configuration, data migration, testing, training, go-live.
• Add reporting dashboard only through change control if it is part of scope.

Schedule

• Identify critical tasks: testing and vendor testing window.
• Use milestones: data migration completed, UAT completed, go-live sign-off.

Risk

• Data quality risk → mitigate with data cleansing and validation.
• Vendor testing window risk → mitigate by reserving vendor resources early.
• Late dashboard request risk → manage with change control and impact assessment.

Quality

• Acceptance criteria for data migration accuracy.
• UAT pass criteria for user sign-off.
• Monitoring for defect levels and remediation cycles.

Change Control

• Treat the late dashboard request as a change request.
• Assess impacts:
  • schedule slip (testing time)
  • cost impact (additional configuration and testing)
  • risk impact (more complexity)
• Decide approve/reject/conditional approval with stakeholder alignment.

This integrated narrative is exactly what long scenario questions reward.

South Africa-Focused Study Strategy: How to Prepare Efficiently for Regent PM Assessments

Because many South African distance-learning students manage limited time, a high-performing strategy is to study with active recall and structured writing. Project management topics are formula-like in that answers must include definitions + steps + application. A practical routine:

1. Create a personal glossary of project management terms:
   • WBS, baseline, variance, risk register, stakeholder matrix, acceptance criteria
2. Practice scenario answers:
   • choose one scenario type per day (risk identification, change control, schedule explanation, procurement justification)
3. Memorize templates:
   • use the “define → process → apply → justify → outcome” structure
4. Do at least one calculation set (if applicable):
   • CPM float and critical path reasoning
   • basic EVM interpretation (CV, SV, CPI, SPI)

Regent Business School Qualification Notes: Module-Consolidated Exam Checklist (BCom Project Management)

This final cluster functions as a consolidated checklist to ensure coverage across the most commonly examined components in a Regent-style Project Management BCom qualification. Instead of repeating earlier content, the checklist compresses it into an “exam readiness” form that you can review quickly before tests and assignments.

Core Concepts Checklist (Must Know)

You should confidently explain or apply:

• Project lifecycle: initiation → planning → execution → monitoring & controlling → closing
• Project governance:
  • sponsor role
  • steering committee decisions
  • CCB (change control)
• WBS:
  • definition
  • steps to build it
  • purpose (scope clarity and planning)
• Scheduling tools:
  • Gantt charts for visualization
  • CPM for critical path and float
  • milestones for reporting
• Cost management:
  • estimating vs budgeting
  • cost control using variance thinking
  • contingency reserve vs management reserve
• Risk management:
  • risk register usage
  • qualitative likelihood/impact
  • response strategies (avoid/mitigate/transfer/accept)
• Procurement:
  • procurement planning stages
  • contract types selection logic
  • SLAs and supplier monitoring
• Quality:
  • QA vs QC
  • acceptance criteria and testing logic
  • corrective and preventive actions
• Communication and stakeholder management:
  • engagement strategies by power/interest
  • communication cadence
• Change control:
  • impact assessment categories
  • baseline update and communication plan
• Closing:
  • acceptance sign-off
  • lessons learned and organizational improvement

Scenario Answer Checklist (If You Have 15–25 Marks)

When writing a long scenario answer, ensure you include:

1. Relevant definitions (only what you need)
2. At least one process (risk management steps, change control steps, WBS steps)
3. At least two tools (e.g., risk matrix + change impact; WBS + milestone schedule)
4. Clear actions and justification
5. A measurable outcome (reduced uncertainty, improved schedule adherence, deliverable acceptance)

“What Examiners Look For” (Writing Quality Indicators)

A well-structured answer should show:

• Logical sequence (process order is correct)
• Coverage (all key areas mentioned for the question type)
• Scenario specificity (you reference details from the prompt)
• Decision justification (you explain why you recommend an action)
• Terminology accuracy (no mixing risk vs issue, QA vs QC, baseline vs plan)

Quick Revision Examples (Recall Prompts)

Use these prompts to rehearse:

• “Describe the difference between risk and an issue and give one action for each.”
• “Explain how WBS supports scope control and scheduling.”
• “A supplier misses a delivery date—what risks and procurement actions apply?”
• “A late requirement is requested—how do you manage it using change control?”
• “If schedule variance is negative, what performance indicators suggest the underlying cause?”
• “When would you choose fixed-price vs cost-reimbursable contracts?”
• “Explain contingency reserve and how it differs from management reserve.”
• “How does stakeholder power/interest affect your engagement plan?”

Final Exam Readiness Summary

A BCom in Project Management from Regent Business School rewards students who can combine commerce thinking (business case, cost logic, value delivery) with project control discipline (planning, governance, monitoring, and change control). To perform well, master the lifecycle, tools (WBS, CPM, milestones), governance and communications, and show practical risk and quality responses in scenarios. When writing answers, keep them structured: define → apply process → use tools → justify decisions → state outcomes—that pattern mirrors what examiners are trained to reward.

By consistently practicing scenario-based answers using the templates and checklists above, you build not only knowledge but also the exam technique required to convert understanding into marks.