BCom Business Management with Project Management (NWU) Past Papers: Exam Notes & Study Guide

North-West University (NWU) candidates in BCom Business Management with Project Management often approach past papers as if they were only “questions to practise”. In reality, these papers are a structured reflection of what examiners repeatedly test: project planning and scheduling, stakeholder and risk management, procurement and contracting basics, budgeting and cost control, governance and reporting, and applied decision-making under uncertainty. This study guide distils common NWU-style past-paper patterns, explains the underlying theory you’re expected to apply, and gives you model methods to answer typical questions efficiently.

Because project management exams are strongly process-based, the same topics reappear in different forms: short definitions, calculations, “critique this plan” questions, scenario-based selections, and mini case studies requiring a justification. The notes below therefore combine (1) how to spot the question type, (2) what framework to use, and (3) the kind of output marks schemes reward—especially for project planning documents, risk registers, and budgeting logic.

Focus note for this guide: It is aligned to the NWU Project Management programmes & notes context and targets the kind of content that appears when you practise BCom Business Management with Project Management (NWU) past papers.

NWU BCom Business Management with Project Management: How Past Papers Test You (and How to Answer)

NWU past papers in this field typically test both knowledge and application. Knowledge shows up as definitions (“What is a WBS?” “Explain stakeholder mapping.”). Application shows up when examiners provide a scenario—an industry setting, a project goal, constraints, and partial information—and then ask you to select tools, build a small artefact (e.g., a risk matrix or milestone plan), or calculate a performance outcome (e.g., whether a schedule is ahead/behind, what the cost impact is, or which option you should choose).

Recognising the Core Exam Patterns

Most questions fall into five repeating clusters. Past-paper practice becomes easier when you train yourself to identify which cluster you are in within the first minute.

Concept & terminology questions
- These ask for a clear definition and usually one or two implications.
- Typical outputs: 4–6 lines with key terms and a brief “why it matters”.
Process questions (what comes next?)
- Examiners may provide a mixed list of project activities and ask you to order or select the correct sequence.
- Typical outputs: ordered steps and short justifications.
Planning document questions
- You might be asked to draft or partially draft:
  - a Project Charter element,
  - a WBS fragment,
  - a risk register entry,
  - a communication plan,
  - or a milestone schedule.
- Typical outputs: structured tables/bullets that look like exam artefacts.
Quantitative/project performance questions
- These include time-cost trade-offs, budgeting, schedule logic, or simple earned-value style analysis (even when the exam does not fully label it as EV).
- Typical outputs: correct formulas, correct substitution, and a conclusion sentence.
Scenario-based decision questions
- You are given options (e.g., contract types, procurement choices, stakeholder responses) and asked which is best and why.
- Typical outputs: decision criteria + one or two arguments for/against each option.

If you can classify the question quickly, you stop wasting time “thinking broadly” and start producing what the examiner is likely to reward.

The Marking Logic: Why Structure Matters

In project management exams, marks are rarely awarded for “beautiful essays” alone. They are awarded for:

correct use of the relevant tool (e.g., WBS, risk matrix, stakeholder register),
correct reasoning linked to the scenario,
and correct calculations where required.

A practical approach:

For definitions: Term → concise meaning → relevance to the project.
For process: Action → input/outcome → relationship to next step.
For calculations: Write formula first → substitute values → compute → interpret.
For scenarios: State decision → justify using 2–3 criteria → acknowledge constraint/assumption.

Even when exam instructions don’t explicitly say “show working”, you should display enough working for method marks.

A Working Vocabulary You Should Practise

NWU-style questions often require you to use specific project management terms precisely. Your answers should reflect the following vocabulary correctly:

Project Charter: authorisation document that defines purpose, objectives, scope boundaries (high level), roles, and initial governance.
WBS (Work Breakdown Structure): hierarchical decomposition of deliverables into manageable work packages.
Milestones: significant events that indicate progress (e.g., “design approved”).
Dependencies:
- Finish-to-start (FS): next task starts after previous finishes.
- Start-to-start (SS), finish-to-finish (FF), etc., if covered in class.
Critical Path: the longest sequence of dependent activities determining shortest completion time.
Risk Register: log of risks with probability/impact, response strategy, and owner.
Stakeholder Register: list of stakeholders with influence/interest, needs, and engagement approach.
Procurement: sourcing goods/services, including terms like tender, contract, supplier evaluation.
Budget Baseline / Cost Baseline: approved cost estimate used to measure performance.
Variance: difference between planned and actual results.
Change Control: formal process to evaluate and approve/deny scope/time/cost changes.
Project Governance: oversight mechanisms (steering committee, reporting cadence, escalation).

Building the Exam “Templates” in Your Head

A common reason students lose marks is that they know the concept but fail to format the answer in the expected structure. Instead of writing full paragraphs, use repeatable templates.

Template: Risk Register Entry (What Examiners Like)

For each risk, include:

Risk description (in scenario language)
Category (schedule/cost/quality/safety/legal/stakeholder)
Probability rating (low/medium/high or numeric)
Impact rating (low/medium/high or numeric)
Overall risk rating (e.g., probability × impact)
Response:
- Mitigate (reduce probability/impact),
- Transfer (e.g., insurance/contract terms),
- Avoid (eliminate the activity),
- Accept (plan contingency if it happens)
Risk owner and trigger indicator
Contingency action

This is exactly the kind of content that repeats across NWU projects/PM notes.

Template: Stakeholder Engagement Response

Stakeholder management answers usually look best when you:

identify stakeholder,
classify them by interest and influence,
then match an engagement approach:
- Manage closely (high influence/high interest),
- Keep satisfied (high influence/low interest),
- Keep informed (low influence/high interest),
- Monitor (low influence/low interest)

You should link the approach back to the scenario: e.g., an influential regulator needs approvals and formal evidence; end-users need clarity and feedback loops.

Mini-Case Skill: Turning “Text” Into a Project Plan

Past papers often provide text like:

“The client wants the system ready by 30 April”
“A supplier has quoted 6 weeks for delivery”
“Work can begin immediately, but testing depends on data migration completion”
“Budget is capped and changes require approval”

Your job is to translate those into plan elements:

Timeline constraints: deadlines and external dates.
Dependencies: “testing depends on data migration”.
Resources: who is available and what their capacity is (if given).
Constraints: budget cap, change approval gate.
Assumptions: what you must state to make the plan workable.

The translation skill is the real difference between high and low marks.

Consistent Numerical Reasoning: The “Show Your Logic” Rule

When quantitative questions appear, examiners usually test whether you:

use the correct formula,
interpret the outcome, not just compute.

For example, if a schedule variance is negative, the conclusion should reflect “behind schedule”. If a risk score is higher, you should justify “higher priority for response”.

A good habit is to end each calculation with a one-sentence interpretation:

“Therefore, the project is behind schedule and requires corrective action such as re-sequencing tasks or adding resources.”

This turns method marks into interpretation marks.

Project Planning, Scheduling, and Risk Management: NWU Exam-Focused Notes

Project planning and risk management are usually the most heavily assessed parts of BCom project management papers. They are also the easiest topics to practise because you can create your own mini “artefacts” like WBS fragments, milestone tables, and risk registers.

Project Planning: From Purpose to Deliverables

Planning begins with the project charter and flows into deliverables and work. A typical exam chain is:

Define purpose and objectives
- Objectives should be specific and measurable where possible (time, cost, quality outcomes).
Clarify scope (high level) and boundaries
- Scope boundaries help avoid scope creep.
Identify major deliverables
- Deliverables are what the client receives.
Create WBS
- Break deliverables into manageable work packages.
Estimate activity durations
- Durations often derive from resource capacity, supplier lead times, and complexity.
Sequence activities
- Use dependencies to create logical order.
Develop schedule and milestones
- Include milestones to track progress.
Plan resources
- Identify who does what and when.
Plan risk responses and contingencies
- Include governance for risk monitoring.
Set baselines

Cost and schedule baselines guide performance measurement.

Examiners like when your answer has this flow because it demonstrates you understand how planning components connect.

WBS in Exams: How to Get Marks Quickly

A WBS answer is not only about listing tasks. It must show structure. Common expectations:

Deliverables at level 1 or 2.
Work packages at lower levels.
Clear verbs that describe work and nouns that describe outputs.

Practical WBS Example (How It Should Look)

Imagine a scenario: “Implement a customer relationship management system for a small retailer chain”.

A WBS might include:

1. Project Management
- 1.1 Initiation and charter
- 1.2 Planning and baselining
- 1.3 Reporting and governance
2. Requirements and Design
- 2.1 Stakeholder interviews
- 2.2 Requirements documentation
- 2.3 System configuration design
3. Implementation
- 3.1 Data migration planning
- 3.2 Data migration execution
- 3.3 User training setup
4. Testing and Acceptance
- 4.1 Test plan development
- 4.2 System testing
- 4.3 User acceptance sign-off
5. Deployment and Close-out
- 5.1 Go-live support
- 5.2 Lessons learned
- 5.3 Project closure report

In exams, you might not need the entire WBS. But you should show at least 2–3 deliverable branches and 4–8 work packages with logical sequencing.

Scheduling: Dependencies, Milestones, and Critical Path

Scheduling questions often revolve around:

identifying dependencies from narrative text,
building a simple schedule table,
determining whether the project meets a deadline,
and interpreting “critical” activities.

Dependency Extraction: A Skill Worth Practising

Text patterns:

“Testing cannot start until…” → dependency (usually FS).
“Procurement takes place after…” → sequence and likely FS.
“Training can begin once…” → again sequence, sometimes SS.
“Approvals are required before…” → gating activity.

You should convert narrative constraints into explicit statements like:

“Task B (Testing) depends on Task A (Data Migration) — Finish-to-Start.”

Milestones as Progress Indicators

Milestones are not “tasks”. They are events. They often include:

approval moments,
completion moments,
sign-off moments.

Examples:

“Requirements approved by client”
“System configuration completed”
“UAT sign-off received”
“Go-live achieved”

A strong exam answer includes:

milestone name,
the task(s) it marks completion of,
and the date/time period (if given or if you estimate).

Risk Management: From Identification to Response

Risk management in exams usually tests:

whether you can identify risks,
whether you can assess probability and impact,
whether you can select appropriate responses,
and whether you understand monitoring/ownership.

Building a Risk Matrix

When the exam uses a matrix, it often expects:

probability scale (e.g., Low=1, Medium=2, High=3),
impact scale (e.g., Low=1, Medium=2, High=3),
risk score = probability × impact.

You can then prioritise:

high scores → mitigation and monitoring,
medium scores → planned response,
low scores → accept or light monitoring.

Risk Categorisation (Exam-Friendly)

Common categories:

Schedule: delays in supplier delivery, slow approvals.
Cost: budget overruns, additional labour.
Quality: defects, failure to meet standards.
Legal/Compliance: regulatory requirements, contract breaches.
Stakeholder: resistance, unclear expectations.
Safety/Operations: unsafe working conditions, downtime.
Technical: system compatibility issues, data quality.

Worked Risk Register Mini-Set (Example)

For the earlier CRM scenario, plausible risks could include:

Risk ID	Risk description	Category	Prob (1-3)	Impact (1-3)	Score	Response	Owner
R1	Supplier delays data migration tools	Schedule	3	2	6	Mitigate: confirm lead times; backup tools	IT Procurement Lead
R2	User requirements change due to stakeholder misalignment	Stakeholder	2	3	6	Mitigate: workshops; change control gate	Project Manager
R3	Data quality issues cause test failures	Quality/Technical	2	3	6	Mitigate: data cleansing; phased testing	Data Lead
R4	UAT sign-off is delayed by client availability	Schedule	2	2	4	Accept/Mitigate: schedule sessions early; escalation	PMO Coordinator

This sort of structured output can appear in many variations across past papers.

Scenario-Based Risk Questions: “What Should You Do?”

Past papers often include a paragraph like: “A critical dependency is at risk and the probability is increasing.” Then the question asks:

What do you do?
What risk response is appropriate?

Your response should reference:

update the risk assessment (probability/impact),
activate contingency (if pre-planned),
escalate based on governance,
and adjust the schedule only through change control.

This connects risk management to schedule governance—exactly what examiners look for.

Counter-Argument Skill: Risk Responses Have Trade-offs

High-mark answers also acknowledge trade-offs:

Mitigation costs time/money but reduces uncertainty.
Transfer shifts impact but can increase price.
Avoidance may reduce value if it removes essential work.
Acceptance relies on contingency and requires monitoring.

Even if the exam only asks “choose best response”, showing you understand trade-offs helps justify the selection.

Budgeting, Cost Control, Procurement, and Project Governance (NWU Past-Paper Style)

Cost management and governance are often assessed in a business management degree with project management specialisation: you’re expected to connect operational decisions to financial impact and organisational oversight. Many students know the “what”, but lose marks on the “how you control”.

Budgeting Basics: Baseline, Estimates, and Cost Components

Budgeting in project management includes:

identifying cost categories,
estimating costs using available information,
allocating budgets by work package,
and setting a baseline for performance measurement.

Cost categories commonly examined:

Labour: salaries/wages and labour hours.
Materials: software licences, hardware, consumables.
Equipment: leasing, rentals.
Travel and accommodation.
Professional services: consultants, legal, engineering.
Contingency reserve: to handle identified risks.
Indirect costs: overhead allocation.

A budget baseline is typically the approved cost plan against which actual spending is compared.

Cost Control: Variance, Forecasting, and Corrective Actions

In exam questions, you might be given planned and actual numbers or partial performance results.

Core logic:

Determine variance:
- Cost variance = Actual cost − Planned cost (or a variant depending on the question).
Interpret variance:
- Positive variance may indicate overspend.
- Negative variance may indicate underspend.
Forecast impact:
- If you overspend early, estimate whether you will exceed the budget.
Decide corrective actions:
- re-plan labour effort,
- negotiate scope changes,
- adjust procurement schedule,
- or escalate to governance.

Example of an Interpretation-Rich Answer

If actual costs are R50,000 while planned costs for the same period were R40,000:

Variance = R10,000 overspend.
Conclusion: “Project is over budget for the period; corrective action is required, such as reviewing resource utilisation and re-checking estimates for remaining work packages.”

Examiners reward interpretation because it shows you understand that budgets are control tools.

Mini Budget Scenario (Exam Calculations)

Suppose an exam provides:

Planned cost baseline for phase 1: R200,000
Actual cost incurred by end of phase 1: R215,000
Remaining planned cost for phase 2: R180,000
Assume no change to remaining work scope and you forecast total = actual phase 1 + remaining planned phase 2

Then:

Cost overspend in phase 1 = R215,000 − R200,000 = R15,000
Forecast total project cost = R215,000 + R180,000 = R395,000
Planned total baseline (phase 1 + phase 2) = R200,000 + R180,000 = R380,000
Forecast variance = R395,000 − R380,000 = R15,000 overspend

A complete answer must include:

the arithmetic,
and the conclusion about budget risk.

Contingency and Change Control: Preventing Scope Creep

Many past papers include a storyline where “additional requirements” appear. You must show you understand:

differences between contingency and budget reallocation,
and the change approval process.

Contingency vs Change Cost

Contingency reserve: for known risks and uncertainty already anticipated in planning.
Change cost: for scope/time requests outside baseline requirements.

An exam answer:

identifies which bucket the cost belongs to,
justifies using contingency only for defined risk outcomes,
and recommends formal change control if scope changes.

Procurement and Contracting Basics (Applied)

Procurement questions often ask:

what to do when you need goods/services,
how to manage supplier selection,
or what contract types are suitable for different risks.

Common contract concepts:

Fixed-price / lump sum: clearer cost but requires stable scope; risk shifts to contractor.
Time and materials: flexible if scope uncertain; may be riskier for cost control.
Cost-reimbursable: contractor reimbursed for eligible costs; needs strong oversight.

In scenario questions, the correct choice depends on:

clarity of requirements,
risk of change,
need for speed,
and governance strength.

Example Decision Logic

If scope is stable and requirements are well-defined:

fixed-price contracts may be suitable because supplier knows deliverables.

If requirements are uncertain and likely to evolve:

time and materials can manage uncertainty, but you need:
- cost caps,
- approval thresholds,
- and tight reporting.

Governance: Steering Committees, Reporting, and Escalation

Governance is the exam topic that links project management to organisational decision-making.

Typically expected governance elements:

reporting cadence (weekly status, monthly management reports),
escalation triggers (e.g., cost variance threshold),
documentation (charter, plans, risk register),
approvals (change requests),
and roles (PM, sponsor, steering committee).

A common exam scenario:

“Cost variance exceeds threshold; what happens next?”
Your answer should include:

report to appropriate level (PM → steering committee),
provide options and impact,
request approval for corrective actions,
update baselines if change is approved.

Communication Planning: Reporting with Purpose

Communication questions may ask:

who needs what information,
how often,
and in what format.

A strong answer includes:

stakeholder type (sponsor, supplier, team, client users),
information needs (status, risk updates, financials),
frequency,
channel (meetings, reports, dashboards),
and escalation route.

In project management exams, communication is not just “send updates”; it is a control mechanism ensuring stakeholders stay informed and decisions are made promptly.

Stakeholders, Communication, Quality, and Integration: Putting It All Together for NWU Exams

Many past papers test integration: how multiple project management areas connect. Students often treat WBS, risk register, and budgets separately. Examiners want you to show that decisions in one area affect others.

Stakeholder Management: Beyond “Identify Stakeholders”

Stakeholder management in exams tends to include:

identification,
analysis (influence/interest),
engagement strategy,
and conflict handling.

Stakeholders might include:

project sponsor,
client representatives,
end-users,
internal departments,
contractors/suppliers,
regulatory bodies,
unions or community groups (in certain public/industrial scenarios),
finance and procurement teams.

Stakeholder Register Entry Elements

An exam-friendly stakeholder register entry typically contains:

Name/role (e.g., “Client IT Manager”)
Interest level (high/medium/low)
Influence level (high/medium/low)
Key concerns/expectations
Engagement approach
Communication cadence
Owner (who manages them)

This structure prevents vague answers.

Handling Stakeholder Conflicts: Decision Criteria

Past papers sometimes include a stakeholder conflict like:

“The finance department wants cost limits; the operations team wants additional features.”
In your answer:
state the conflict,
evaluate using criteria:
- budget baseline constraints,
- scope acceptance criteria,
- risk exposure,
- schedule impact,
- value to the project objectives.

Then apply governance:

escalate if approvals are required,
log the change request,
and update baseline only if approved.

This shows you understand project governance and change control as decision architecture.

Quality Management: Meeting Standards in a Project Environment

Quality questions may test:

what quality means,
quality planning,
and quality assurance/control activities.

Quality management does not mean perfection; it means meeting defined requirements.

Common quality elements:

acceptance criteria for deliverables,
QA/QC distinction:
- Quality Assurance: process-focused (ensure the process produces quality),
- Quality Control: product-focused (test/inspect deliverables),
quality checklists,
inspection and testing,
documentation of defects and corrective actions.

Example: Translating Quality into Exam Artefacts

If the scenario is a software rollout:

QA might include standard coding practices, review processes, and configuration management.
QC might include:
- testing scripts,
- performance checks,
- defect logs,
- user acceptance criteria.

For exam answers, it helps to list:

the standard/requirement,
the method of verification,
the evidence you will produce (test report, sign-off).

Project Integration: The Glue Between Plans

Integration shows up when questions ask:

“How do you manage changes?”
“How do you ensure the schedule and budget remain aligned?”
“How do you update plans when risks materialise?”

Integration logic:

A change in schedule affects labour costs and supplier payments.
A risk trigger might require contingency use or rescheduling.
Stakeholder decisions require documentation and baseline updates.

In a high-mark answer, you explicitly connect:

risk response → schedule adjustment (if needed),
schedule adjustment → cost forecast update,
quality outcomes → acceptance decisions.

Practical “End-to-End” Mini-Scenario (Exam-Style)

Consider a project: “Roll out a workplace training programme using an e-learning platform.”

Key elements you might expect in questions:

WBS deliverables:
- requirements,
- platform configuration,
- content upload,
- pilot testing,
- training sessions,
- evaluation and close-out.
Schedule constraints:
- vendor lead time for platform customisation,
- deadline for completing pilot before next quarter starts.
Risks:
- content quality issues,
- user resistance,
- vendor delay,
- technical compatibility.
Budget controls:
- cost baseline includes vendor fees and internal labour,
- contingency reserved for content rework risks.
Governance:
- weekly project team meeting,
- monthly steering committee,
- escalation if schedule slips beyond a defined threshold.
Quality:
- acceptance criteria such as “pilot completion report signed off”.

An exam prompt might ask you to:

identify dependencies,
propose risk responses,
produce a small risk register table,
and propose a communication plan.

Integration is assessed by whether your answers are consistent across these items.

Practise Like It’s a Past Paper: Exam Strategy, Typical Question Walkthroughs, and Revision Drills for NWU

This section focuses on the practical side: how to practise using past papers effectively, how to manage time, and how to answer walkthrough-style questions in a way that aligns with marking patterns.

Time Management: A Simple Repeatable Routine

A practical routine for past-paper practice:

Read the entire question (30–60 seconds)
Identify the requirement words:
- “Explain”, “Define”, “Discuss”, “Justify”, “Calculate”, “Prepare”, “Design”, “Recommend”
List the expected artefact:
- definition lines,
- risk register table,
- schedule/milestone list,
- stakeholder mapping,
- budget variance calculation.
Draft a structured answer quickly (don’t perfect sentences too early)
Do calculations carefully and include a short interpretation.
Check for scenario alignment:
- ensure the selected option fits the described constraints.

For time management:

If a question is worth 10–15 marks, plan about 10–12 minutes (depending on the exam total).
For structured tables, allocate time to format cleanly—illegible tables often cost marks.

Typical Walkthrough 1: “Prepare a Risk Register” Scenario

You might get a prompt like:

“The project involves installing equipment at multiple sites. There is limited access time and supplier lead times are uncertain.”

A high-mark answer should:

Provide 4–6 risks with different categories (schedule, safety, quality, procurement, stakeholder).
Assign probability and impact ratings consistently.
Provide responses that are realistic and not generic.

A good response set includes:

a mitigation for supplier delay,
a mitigation for site access constraints,
a safety risk response (permit-to-work, training, PPE),
a quality risk (testing/inspection before sign-off),
a stakeholder risk (site managers informed schedule early),
and at least one contingency approach (e.g., backup suppliers or overtime approval path).

Typical Walkthrough 2: “Milestones and Dependencies” From Narrative

If the question includes text like:

“Design approval is required before implementation starts”
“Testing cannot begin until installation is complete”
“Client training will occur after successful testing”

Then:

Extract dependencies:
- Implementation starts after Design approval (FS dependency).
- Testing after Installation complete (FS).
- Training after Testing sign-off (could be FS).
Create milestones:
- Design approved,
- Installation complete,
- Testing complete and UAT sign-off,
- Training completed.

Finally, conclude whether the schedule meets a deadline (if provided). If not, mention corrective actions like:

fast-tracking non-dependent tasks,
adding resources to critical activities (if allowed),
or revising milestones through change control.

Typical Walkthrough 3: Budget Variance Interpretation

Suppose the question provides:

“Planned cost for period: R120,000”
“Actual cost: R135,000”
“Remaining planned cost: R200,000”
“Forecast assume remaining costs unchanged”

Then compute:

Variance in period: R15,000 overspend.
Forecast total = R135,000 + R200,000 = R335,000.
Planned total baseline = R120,000 + R200,000 = R320,000.
Forecast variance = R15,000 overspend.

Then interpret:

“Project is trending over budget; propose corrective actions such as re-estimating remaining work, reviewing procurement, or submitting a change request if scope adjustments are necessary.”

Examiners reward that final “what now”.

Typical Walkthrough 4: Stakeholder Engagement Strategy

If the scenario says:

“The regulator must approve compliance documentation”
“End-users have limited time to attend meetings”
“The project sponsor wants weekly progress updates”

Then propose:

Regulator:
- high influence; likely moderate/high interest; manage closely with formal evidence and submission milestones.
End-users:
- high interest but may have lower influence; keep informed with concise training sessions and feedback windows.
Sponsor:
- high influence/high interest; manage closely with weekly updates and escalation of risks.

You can represent it as:

a mini stakeholder mapping explanation,
and then a brief communication plan.

Revision Drills: High-Impact Practice Sets

To prepare efficiently for NWU project management exams, practise in drills that mirror exam output.

Drill A: “Define and Connect” (Concept Drill)

Pick 10 topics and practise a 4-line answer each:

WBS
Milestones
Risk matrix
Change control
Project charter
Stakeholder register
Procurement contract type
Cost baseline
Earned value-style variance logic (if covered)
Governance and escalation

Rule: each definition must include one connection phrase:

“This affects…”
“This is used to…”
“This ensures…”

Drill B: “Build Artefacts” (Output Drill)

From a scenario, produce:

a WBS snippet (5–8 work packages),
a dependencies list (at least 3 dependencies),
a risk register (at least 4 risks),
a milestone table (at least 4 milestones),
and a brief communication plan (3 stakeholder groups).

Artefacts improve marks because they are easy to evaluate.

Drill C: “Scenario Decision” (Justification Drill)

Write short arguments:

If requirements are stable → which contract type suits and why?
If scope is changing → how do you manage change requests?
If a critical risk triggers → what response and escalation?

Keep justifications linked to:

constraints,
impacts on schedule/cost/quality,
governance requirements.

Final Consolidation: A Complete “Exam-Ready” Checklist for NWU BCom Business Management with Project Management

This checklist acts like your last-mile revision tool. If you can use it after you write your answers, you will correct common errors that cost marks.

Before the Exam (Preparation Checklist)

Practise at least 3–5 past papers under timed conditions.
Create your own templates:
- risk register table,
- stakeholder mapping explanation,
- WBS structure,
- milestone list format,
- and budget variance interpretation method.
Memorise key definitions, but practise them in context:
- the “why it matters” sentence is essential.

During the Exam (Answer Checklist)

Did you identify the question type (definition, process, artefact, calculation, scenario)?
Did you use scenario language (names of stakeholders/activities from the prompt)?
For tables:
- Are categories consistent?
- Do your risk scores follow the same method?
For calculations:
- Did you use correct arithmetic?
- Did you interpret the result in a conclusion sentence?
For scenario decisions:
- Did you justify using criteria?
- Did you mention governance/change control where scope/time is affected?

Common Mistakes to Avoid (Based on Past-Paper Marking Patterns)

Writing general project management theory without linking to the specific scenario.
Creating a WBS that lists tasks without deliverable structure.
Offering risk responses that are not realistic (e.g., “avoid all risks”).
Ignoring dependencies when the question clearly implies “cannot start until”.
Calculating numbers but not interpreting what they mean for schedule/cost.
Proposing scope changes without referencing change control or approvals.

The Highest-Mark Approach: Consistency Across Artefacts

Your final answers should be mutually consistent:

If you claim a milestone depends on an approval, your WBS and risk register should reflect that same dependency.
If your risk register says “supplier delay is possible,” your schedule should contain a supplier-related activity whose duration can be affected.
If your budget question forecasts overspend, your corrective actions should be plausible and governance-aligned.

Consistency is not a technicality—it is evidence that you understand the project as an integrated system.

Last Note on How to Use This Guide With Past Papers

When you do past papers, treat each question as if you must extract:

the tool required (WBS, risk register, governance, budgeting logic),
the scenario constraint (deadline, budget cap, dependency, approval gate),
the output format required (table, sequence, short justification),
and the final decision or interpretation.

That is the method that turns “practising past papers” into repeatable exam performance for the BCom Business Management with Project Management (NWU) track.