PJM01B1 – Project Management Semester Exam Papers & Notes

Project Management semester exams often test not only your knowledge of processes and terminology, but also your ability to apply project management frameworks to realistic scenarios. This study guide focuses on PJM01B1 (Project Management) semester exam papers & notes in the style commonly aligned with University of Johannesburg (UJ) College of Business & Economics assessment patterns—structured answers, correct use of tools, and clear linkage between planning, execution, monitoring & controlling, and closing. You’ll find exam-oriented explanations, worked mini-cases, likely question formats, and revision checklists designed to help you score consistently.

Section 1: PJM01B1 Exam Paper Format, Marking Priorities & How to Answer Like a Top Student

Understanding what PJM01B1 exams usually assess

Most semester examinations in Project Management courses evaluate four broad competencies:

Conceptual mastery
You should know definitions and distinctions (e.g., project vs programme, stakeholder vs shareholder, baseline vs target, risk vs issue, schedule vs timeline, cost estimate vs budget).
Process sequencing and logic
Many questions require you to show the flow of activities. For example, you typically move from:
- initiating → planning → executing → monitoring & controlling → closing
  or from:
- requirements/stakeholder analysis → scope definition → WBS → schedule/networking → resource estimation → budgeting → risk planning → monitoring controls.
Application using project tools
Expect questions that ask you to use at least one tool from each of these categories:
- scope tools: WBS, product breakdown, requirements traceability (light form)
- schedule tools: Gantt charts, critical path concepts, dependency logic, milestones
- cost tools: estimates, contingency vs reserve, cost baseline
- quality and risk tools: quality plan, risk register basics, probability/impact
- stakeholder tools: influence/interest, RACI, communication plan
- procurement/contracting (where included): roles, procurement steps, selection criteria
Communication and structure under exam constraints
Even if your calculations are right, you can lose marks for weak structure. Examiners prefer:
- headings that map to the question subparts,
- bullet points for lists,
- short paragraphs with direct “because” reasoning,
- correct terminology.

Common question styles in PJM01B1 papers

While individual papers differ, project management semester exams often include a blend of:

Short answer / definitions
Example prompt types:
- “Define a project charter. State two benefits.”
- “Differentiate risk and issue.”
- “What is a baseline?”
Scenario-based structured questions
Example prompt:

“A contractor is delaying a construction project. Identify 3 likely schedule causes, propose monitoring methods, and explain corrective actions.”
Tool-based questions
Example prompt:
- “Construct or interpret a simple WBS level.”
- “Explain critical path and its relevance to project control.”
- “Build a risk response table with probability/impact and owners.”
Calculation-based questions (sometimes present)
Many PJM01B1 versions include calculations such as:
- estimating durations,
- identifying critical path from a small network,
- simple cost comparison (planned vs actual),
- budgeting totals from given cost lines.

Even where calculations appear, the course often rewards interpretation as much as arithmetic: you may be asked to explain what your calculation means for decision-making.

How marking schemes usually reward your answer

To score well, align your response to typical marking keys:

Marks for definition keywords
Use standard terms: “baseline,” “scope,” “WBS,” “stakeholder,” “risk register,” “RACI,” “change control,” “variance.”
Marks for correct sequencing or logical ordering
If asked “what should happen next,” you must show the flow.
Marks for justification
Statements like “This reduces risk” must connect to a specific mechanism (e.g., “because it transfers risk through contract terms” or “because it adds buffer time after identifying critical tasks”).
Marks for completeness
If the question asks for 4 items, don’t give 3. If asked for “advantages and disadvantages,” give at least one of each.

Exam technique: turning a vague prompt into a high-scoring structured answer

A reliable method for PJM01B1 is CLAIM → WHY → HOW → EXAMPLE:

CLAIM: Write the main point directly (e.g., “The WBS decomposes project work into manageable components.”)
WHY: Provide the reasoning (e.g., “This enables accurate estimation and tracking.”)
HOW: Mention the steps or tool mechanics (e.g., “Start from deliverables, then break down into work packages.”)
EXAMPLE: Apply it to the scenario (e.g., “For a campus renovation project, deliverables include classrooms, wiring, and signage.”)

Typical “trap” questions (and how to avoid losing marks)

Confusing planning vs executing
- Planning: define how you will do it
- Executing: perform the work
  If the scenario says “the team started late,” the examiner may want monitoring/control, but you must still reference correct planning controls.
Mixing risk and issue
- Risk: uncertain future event
- Issue: happened already
  In answers, explicitly separate them.
Saying “we will manage stakeholders” without specifics
Examiners expect tools like communication plan or RACI or stakeholder mapping.
Only giving theory
Always connect to project decisions: cost, schedule, scope, quality, risk responses.

A UJ-aligned answer style: crisp formatting

Because you’re studying within the University of Johannesburg (UJ) College of Business & Economics ecosystem, align your exam writing to what many South African lecturers reward:

Use bullet points for lists.
Use mini-headings that mirror sub-questions:
- Scope
- Schedule
- Cost
- Risk
- Stakeholders
When a question includes “explain,” include short reasoning rather than only definitions.

Mini-example: answering “baseline” (short answer)

Baseline definition (CLAIM):
A baseline is an approved plan used as a reference point for measuring performance.

WHY (justification):
Without baselines, you cannot calculate variances (schedule variance, cost variance) or control changes.

HOW (tool mechanics):
Baselines are created during planning and updated only through formal change control.

EXAMPLE:
If a project baseline says finishing Phase 2 by week 10, and actual completion is week 12, you identify a schedule variance of +2 weeks and decide whether corrective action is needed.

Section 2: Core Project Management Knowledge for PJM01B1—Scope, Time (Schedule), Cost, Quality & Integration

Integration management: the “connective tissue” topic that examiners love

In many project management curricula, Integration Management is tested because it shows whether you understand how everything connects. Core integration outputs commonly include:

Project charter (authority to start)
Project management plan (how you’ll execute/control)
Direct and manage project work
Monitor and control
Perform integrated change control
Close project

Project charter vs project management plan

A typical exam question:

“Differentiate the project charter from the project management plan.”

Project charter focuses on:

purpose and high-level description,
high-level objectives,
summary milestones,
assigned project manager authority,
stakeholders overview,
approval to start.

Project management plan focuses on:

how you will plan/execute/control the project,
subsidiary plans: scope, schedule, cost, quality, communications, risk, procurement (depending on syllabus depth).

In answers, always mention “authority to start” for charter and “how you’ll manage” for the management plan.

Scope management: WBS, requirements, and change control

Work Breakdown Structure (WBS): what you must show in answers

A WBS is a hierarchical breakdown of project work into deliverables and work packages. It is essential for:

accurate estimation of time and cost,
assigning responsibilities,
monitoring progress at manageable levels,
preventing scope creep.

A WBS should generally be:

deliverable-based,
measurable where possible,
detailed enough for work packages.

Example: WBS for a “Smart Classroom Setup” mini-project

Suppose a university department wants a smart classroom upgrade. A possible WBS structure (simplified for exam style):

Project Management
1.1 Project initiation
1.2 Reporting and governance
1.3 Risk reviews
Classroom Infrastructure
2.1 Electrical wiring improvements
2.2 Network installation
2.3 Cable management
Technology Installation
3.1 Interactive display installation
3.2 Audio system setup
3.3 Device configuration
Training & Handover
4.1 Trainer preparation
4.2 Staff training sessions
4.3 User manuals and sign-off

Where marks typically come from:
Examiners want you to show that you can break deliverables down and that you understand why this matters for tracking.

Scope baseline and change control

Exam questions may include:

“Explain scope baseline.”
“Why do we need change control?”

Scope baseline often includes:

scope statement,
WBS,
WBS dictionary.

Change control ensures:

formal review of changes,
impact assessment (time, cost, quality, risk),
approval/rejection decisions,
updated baselines.

Counter-argument you can use (for higher-level marks)

If you only say “change control controls scope creep,” you may lose marks for depth. Add:

Change control can also be beneficial when changes are necessary due to new stakeholder needs, but it must be controlled so that benefits outweigh costs.

Time (Schedule) management: sequencing, milestones, and critical path concepts

Scheduling fundamentals

In exams, time management questions often require:

identifying dependencies (Finish-to-Start, etc. where included),
building a basic timeline,
using milestones as control points.

Even if your paper doesn’t ask you to draw a full network, you should be fluent in interpreting schedule logic.

Critical path concept: how to explain it clearly

A critical path is the longest sequence of dependent activities that determines the project’s minimum completion time. Activities on the critical path typically have:

zero float (no slack), so any delay affects the end date.

High-scoring explanation structure:

Define critical path.
Explain float/slack in simple terms.
Link to control: focus monitoring and mitigation on critical activities.

Worked mini-case: identifying the project duration from an activity list

Consider this simplified activity set (assume all start from time 0):

Activity	Predecessor(s)	Duration (days)
A	none	4
B	A	3
C	A	2
D	B	5
E	C, D	2

To compute total project duration:

Path 1: A → B → D → E
Duration = 4 + 3 + 5 + 2 = 14 days
Path 2: A → C → E
Duration = 4 + 2 + 2 = 8 days, but note E cannot start until D completes (because E depends on both C and D).

Therefore, the controlling path is A → B → D → E, and project duration = 14 days.

Why this matters in exams:
If asked “what happens if activity B is delayed by 2 days?” the answer should show that the critical path shifts and the project completion increases by roughly 2 days (assuming no alternate constraints).

Cost management: estimates, budgets, and cost baseline

Key distinctions

Cost estimate: prediction of cost for activities/work packages.
Budget: time-phased allocation of cost for planned work over time.
Cost baseline: approved cost plan used to measure performance.

Earned value concepts (if included)

Some project management syllabi introduce Earned Value Management (EVM) lightly. If your PJM01B1 includes it, be ready to explain:

Planned Value (PV): budgeted cost for work scheduled
Earned Value (EV): budgeted cost for work performed
Actual Cost (AC): actual spending

Even if you aren’t asked to compute EVM fully, conceptual understanding can earn marks.

Worked EVM-style mini-case (interpretation emphasis)

Assume:

PV = R100,000 (planned by end of week)
EV = R80,000 (work performed is worth 80% of planned)
AC = R90,000 (actual spent)

Interpretation:

Schedule performance is behind plan (EV < PV).
Cost performance is better than expected for the work performed (EV > AC is not true here; actually EV (80k) < AC (90k), so cost performance is worse: you spent more than the value of work performed).
Provide the variance explanation:
- Schedule variance (SV) = EV − PV = 80k − 100k = −20k
- Cost variance (CV) = EV − AC = 80k − 90k = −10k

If asked what corrective actions to take:

accelerate critical tasks (if schedule is critical),
review vendor invoices and productivity,
update risk responses or re-baseline with change control (only if approved).

Quality management: planning, assurance, and control

Quality questions often include:

quality planning (what standards and metrics apply),
quality assurance (process-focused),
quality control (product-focused inspection/testing).

Example: quality plan for a software module delivery

Even for non-construction projects, quality management stays consistent:

Standard: coding standard compliance and defect rate targets.
Quality assurance: peer reviews, code scanning, testing procedures.
Quality control: run unit tests, acceptance tests, and defect triage.
Metrics:
- defects per module,
- pass rate in acceptance testing,
- time to fix critical defects.

Why quality is part of project management “integration”

Quality management affects scope (what “done” means), schedule (testing time), and cost (rework). In exam answers, explicitly connect quality to trade-offs.

Integrated change control: the exam-ready logic chain

When asked: “Explain integrated change control and steps,” use this structure:

Identify change request
From team, client, regulator, risk event, stakeholder feedback.
Review impact
Scope, schedule, cost, quality, risk, procurement impacts.
Evaluate alternatives
Options to accept, modify, delay, or reject change.
Decide through approval authority
Depends on governance structure—steering committee, client, PMO.
Update baselines
Only after approval, update project management plan and relevant baselines.
Communicate changes
Ensure stakeholders understand implications and new expectations.
Track results
Monitor whether the change delivered expected benefits.

A strong answer always includes: “impact assessment” and “update baselines through change control.”

Section 3: Tools & Techniques You Must Master—Stakeholder Management, Risk Management, Procurement, and Communication

Stakeholder management: mapping influence/interest and using RACI

Stakeholder management is commonly examined because projects succeed or fail based on relationships and expectations.

Stakeholder identification and analysis

A high-scoring answer includes:

how stakeholders are identified (direct, indirect, power-interest),
classification by influence and interest,
analysis of needs and expectations.

Stakeholder mapping (influence/interest matrix)

Examiners like you to describe typical quadrants:

High influence / high interest: manage closely (frequent engagement)
High influence / low interest: keep satisfied (minimal effort, ensure no surprises)
Low influence / high interest: keep informed (share updates)
Low influence / low interest: monitor (watch for changes)

RACI: who does what

RACI stands for:

Responsible: does the work
Accountable: final answer/approval
Consulted: gives input
Informed: notified

A scenario-based exam question might ask you to assign RACI roles for tasks like:

requirements gathering,
tendering,
implementation approvals,
training.

Example: RACI for “System Cutover” task

Task: Switch from old system to new system.

PM:
- Responsible (project coordination) or Accountable (often Accountable)
Technical Lead:
- Responsible (technical execution)
Procurement Officer:
- Consulted (vendors and licenses)
Finance Manager:
- Consulted/Approved (budget and invoices)
Business Owner/Client Representative:
- Accountable (acceptance and sign-off)
End Users:
- Informed (training schedule and downtime windows)

In answers, the goal is consistency and clear role reasoning.

Communication management: designing a communication plan

Communication is frequently assessed through scenario questions like:

“The project is facing misunderstandings with the client.”
“Stakeholders complain they weren’t informed.”

A communication plan typically contains:

stakeholder,
information needs,
format (meeting, report, email),
frequency,
owner (who sends),
channel,
escalation path.

Example communication plan (exam-friendly table)

Stakeholder	Need	Format	Frequency	Owner	Channel
Sponsor	performance & governance	Steering report	fortnightly	PM	Email + meeting
Client/Customer rep	progress and approvals	Weekly update	weekly	PM	Email
Technical team	tasks and blockers	Stand-up meeting notes	3x weekly	Tech Lead	Teams/Room
End users	training and downtime	Training schedule	as-needed	Training Coordinator	Email

Even if your exam doesn’t require a table, structuring in this way demonstrates completeness.

Risk management: register, response strategies, and risk ownership

Core definitions

Risk: uncertain event that, if it occurs, affects objectives.
Issue: problem that has happened.
Probability/impact: measure of likelihood and consequence.
Risk appetite/tolerance: how much risk you’re willing to accept (if covered in syllabus).

Risk identification methods

Typical methods:

brainstorming (with experienced team members),
lessons learned from past projects,
checklists,
expert interviews,
analysis of constraints and assumptions.

In answers, show that you know risk identification is iterative.

Risk register: what must be included

A basic risk register often includes:

risk description,
category (technical, schedule, cost, stakeholder, procurement, etc.),
probability,
impact (usually rated),
overall priority (often probability × impact),
risk owner,
response strategy,
triggers,
contingency actions.

Risk response strategies: avoid, mitigate, transfer, accept

Exams commonly test you to give the best match:

Avoid: eliminate the cause
Example: change design approach.
Mitigate: reduce probability and/or impact
Example: add testing, increase monitoring.
Transfer: shift impact to a third party
Example: insurance, fixed-price contract (careful: transfer is not free).
Accept: no action now; plan contingency
Example: monitor and have backup plan if occurs.

Example: risk response for procurement delays

Risk: “Vendor delivery delay due to supply chain disruptions.”

Probability: Medium
Impact: High (schedule slip)
Owner: Procurement Officer
Response:
- Mitigate: dual-source where possible, early ordering, vendor performance tracking.
- Contingency: plan temporary workaround or adjust schedule with change control.

In exam answers, mention a trigger (e.g., “delivery date moved by more than 5 working days”).

Worked scenario: building a simple risk matrix and choosing responses

Assume the following risks (ratings 1–5):

Risk	Probability	Impact	Priority
R1: Key staff availability reduced	4	4	16
R2: Client requirement changes late	3	5	15
R3: Technology compatibility issues	2	4	8
R4: Supplier cost increases	3	3	9

Priority = Probability × Impact.

Highest priority: R1 (16) and R2 (15)

Response choice:

For R1, likely mitigate (backup staffing plan, schedule staffing changes earlier).
For R2, mitigate and avoid through early requirements and change control; treat as both stakeholder and scope risk.
For R3, mitigate with prototypes, technical reviews.
For R4, transfer via contract terms or mitigate by supplier diversification; consider contingency reserve.

This shows you can move from analysis to action—what examiners often grade most.

Procurement and contracting basics (when included)

Procurement questions may ask you to:

describe procurement planning steps,
explain procurement documentation,
understand contract types (high-level),
explain vendor selection criteria.

Common procurement steps

Determine what to buy/contract.
Prepare procurement plan and specifications.
Invite bids/tenders (as applicable).
Evaluate proposals using agreed criteria.
Select vendor and negotiate contract terms.
Contract administration and performance monitoring.
Closure and lessons learned.

Contract terms and risk allocation

Examiners like the idea that contracts:

set performance requirements,
define delivery timelines,
specify penalties/bonuses,
determine warranties and acceptance criteria,
govern change orders and dispute resolution.

Even in simplified exam contexts, demonstrate that procurement affects schedule, cost, and risk.

Lessons learned & closing: linking learning to future risk reduction

Closing is sometimes treated as “administrative,” but project management exams often test whether you understand its value:

formal acceptance,
documentation updates,
final reports,
release of resources,
lessons learned and recommendations.

Tie lessons learned to risk management:

if previous projects had staffing delays, you update hiring plans and risk triggers.

Section 4: Semester-Exam Style Practice—Likely Questions, Worked Answers, and Mini-Case Papers

How to use these practice papers strategically

This section provides exam-like prompts and model answer frameworks. The aim is not to memorize sentences but to internalize:

how to structure answers,
which tools to apply,
what marks typically come from.

You’ll see question types matching:

definitions,
scenario solutions,
WBS/schedule/cost/risk/stakeholder tasks,
short calculations where relevant.

Practice Paper 1 (Structured Scenario): “Campus Renovation Delays”

Question 1: Identify problems and classify them (risk vs issue)

A university renovation started late. Students report that some classrooms are still closed. The client also says requirements were unclear.

Model answer framework:

Issues (already happening)
- Renovation started late (schedule issue).
- Classrooms still closed (delivery/acceptance issue).
Risks (future/uncertain)
- Requirements unclear (could lead to more scope changes and rework).
- Supplier delays due to procurement lead times.
Stakeholder impacts
- Students and lecturers affected by closures.
- Client may increase scrutiny and request acceleration.

Why it scores:
You separate issue from risk and connect to impacts.

Question 2: Provide 3 schedule monitoring methods

Expected items:

milestone tracking (e.g., completion of wiring, painting, signage),
progress reporting (weekly actual vs planned),
variance analysis (schedule variance),
critical path monitoring (if a critical path exists).

Sample structured response:

Track milestone completion percentages weekly.
Compare actual progress vs schedule baseline and calculate variances.
Monitor critical path activities and risks affecting them.

Question 3: Recommend corrective actions

Corrective actions for delay typically include:

re-sequencing tasks (fast-tracking where appropriate),
resource leveling or adding manpower (subject to budget),
change request review if scope changes occurred,
revise schedule with change control (only if agreed),
improve procurement follow-up for critical items.

Counterpoint to earn extra depth:
Corrective action isn’t always “work faster.” Fast-tracking can increase rework and risk. Therefore, propose analysis before acceleration.

Practice Paper 2: “Small IT Implementation—Budget Overrun and Stakeholder Pressure”

Question 1: Explain cost baseline and variance (short calculation)

Assume:

Budgeted cost for scheduled work (PV) = R200,000
Earned value (EV) = R170,000
Actual cost (AC) = R210,000

Compute:

Schedule variance (SV) = EV − PV = 170,000 − 200,000 = −R30,000
Cost variance (CV) = EV − AC = 170,000 − 210,000 = −R40,000

Interpretation:

behind schedule and over budget for the work performed.
corrective action must target both productivity and schedule.

Marks strategy:
Show both calculations and interpretation; don’t stop at numbers.

Question 2: Propose stakeholder engagement steps

Stakeholder pressure is often a result of misaligned expectations. Provide actions:

Update communication plan and increase reporting frequency for key stakeholders.
Conduct a requirements validation session to confirm scope.
Use change control for new requests.
Use RACI to clarify accountability for approvals.

Practice Paper 3: “Procurement Tender—Risk of Non-Performance”

Question 1: Create a mini risk register entry for vendor non-performance

Risk: vendor fails to meet delivery performance.

Include:

probability: medium
impact: high
owner: procurement officer or project manager
response: mitigate/transfer/accept

Example entry:

Probability: 3/5
Impact: 5/5
Priority: 15
Response:
- Mitigate: include performance KPIs, enforce milestones, require proof of capacity.
- Transfer: incorporate penalties/bonuses and warranties in contract.
- Contingency: identify alternative supplier or schedule workaround.

Question 2: Explain how contract terms can reduce schedule risk

Answer should mention:

clear acceptance criteria,
delivery dates,
penalties for delays,
change order process,
dispute resolution mechanism,
warranty and maintenance responsibilities.

Practice Paper 4: WBS and Schedule Logic (Pure Tool Questions)

Question 1: Build a WBS for “Event Management Project”

Scenario: A department plans an academic conference with venue, speakers, registration system, and marketing.

A WBS can look like:

Project Management
Venue and Logistics
Speakers and Programme
Registration and Ticketing
Marketing and Communications
Event Delivery (day-of operations)
Closure and Post-event Reporting

Then break down one deliverable to work packages:

Venue and Logistics:
- 2.1 Secure venue booking
- 2.2 Catering arrangements
- 2.3 Audio-visual equipment
- 2.4 Staffing and signage

Exam scoring tip:
Always show you know how to go from deliverables to work packages.

Question 2: Milestones and control

Provide 5 milestones:

venue confirmed,
keynote speakers confirmed,
registration system tested,
final programme published,
event concluded and reports submitted.

Connect milestones to control:

milestone completion indicates progress and triggers decision points.

Section 5: Comprehensive Revision Notes—Checklists, Formula Mind-Maps, Common Marking Rubrics, and Final Exam Readiness

The PJM01B1 “must-know” checklist (printable style)

Use this as your last-week revision scaffold. If you can explain every item below clearly, you’re prepared for most paper structures.

Core frameworks

Project vs programme vs portfolio
Project life cycle (conceptualizing typical phases)
Initiation outputs: charter, early stakeholder identification
Planning outputs: management plan, scope baseline, schedule baseline, cost baseline
Execution outputs: deliverables produced, work performed
Monitoring & controlling: performance measurement, variance analysis, corrective actions
Closing outputs: acceptance, lessons learned, final reports

Scope toolkit

WBS definition
Work packages
Scope baseline components
Scope creep
Change control rationale

Time toolkit

Milestones
Dependencies
Critical path concept
Float/slack explanation
Schedule variance interpretation

Cost toolkit

Estimate vs budget vs baseline
Contingency vs management reserve (if covered—be clear which one is for known vs unknown risk in your syllabus)
Cost variance meaning
Budget updates via approved change control

Quality toolkit

Quality planning
Quality assurance
Quality control
Standards and metrics
Rework as both quality and cost issue

Stakeholder toolkit

Influence/interest mapping
RACI
Communication plan
Managing expectations
Escalation path

Risk toolkit

Risk register basics
Probability and impact
Risk responses: avoid, mitigate, transfer, accept
Triggers
Risk ownership

Procurement toolkit

Procurement plan basics
Vendor selection criteria concept
Contract administration concept
Performance monitoring

Mind-map summary (text version): how concepts connect in exam answers

A frequent reason students lose marks is answering in “silos.” High scores come from connecting the dots.

Use this chain:

Scope (what is to be delivered)
↓
WBS (how deliverables are decomposed)
↓
Schedule (how work is sequenced and timed)
↓
Budget (how costs are estimated and allocated over time)
↓
Quality (standards and “definition of done”)
↓
Risk (uncertainties that threaten scope/schedule/cost/quality)
↓
Stakeholders & communications (who must know what and when)
↓
Monitoring & controlling (variance, corrective actions, decision-making)
↓
Change control & integration (approved updates to baselines and plans)
↓
Closing & lessons learned (capture and reuse learning)

Write your exam answers in this logic. Even if the question only mentions “schedule,” include brief scope/cost/quality ties where relevant.

Common marking rubrics: what examiners want to see on the page

Even without seeing a specific rubric, many South African university exams follow patterns:

For definitions (usually 2–5 marks)

1 mark: correct definition
1 mark: key distinguishing feature
1 mark: example or application
optional: brief impact (“why it matters”)

For scenario questions (usually 10–25 marks)

30–40%: correct identification of issues/problems
30–40%: tool-based solutions (WBS/risk register/RACI/schedule controls)
20–30%: justification, trade-offs, and impact on objectives
bonus: completeness, crisp structure, and correct terminology

For calculations (varies)

50%: correct arithmetic
50%: interpretation and recommendation based on results

Short “exam-ready” answer templates you can reuse (without memorization)

Template A: answering “Explain and justify”

Definition: …
Key components: …
Why it matters: …
In practice (example): …

Template B: answering “Propose actions”

Immediate action: …
Corrective action: …
Preventive action: …
Monitoring: …
Governance: change control / approvals as relevant

Template C: answering “Risk response”

Risk statement: …
Probability and impact: …
Owner: …
Response strategy: avoid/mitigate/transfer/accept
Trigger: …
Contingency plan: …

Built-for-exam worked mini-cases (with full reasoning)

To strengthen your application, here are two integrated cases combining multiple topics, which reflect how exams often test higher marks.

Mini-case 1: Delayed project due to unclear scope and vendor issues

Scenario:
A project to install lab equipment is behind schedule by 3 weeks. The sponsor complains about missed milestones. The procurement records show a vendor delivery delay and the team realized the requirements changed after initial design.

Answer approach:

Classify problems
- Schedule delay = issue (already happened).
- Vendor delivery delay = risk that materialized into issue.
- Requirement changes after design = risk that has created scope rework (issue).
Diagnose likely root causes
- Scope clarity gaps → rework and rescheduling.
- Procurement planning gaps → late supplier delivery.
- Stakeholder engagement gaps → approvals and requirement validation delayed.
Monitoring & controlling actions
- Update schedule baseline only via change control.
- Track milestones and show current progress vs planned.
- Add weekly stakeholder reporting focusing on milestone recovery plan.
Corrective actions
- Re-baseline schedule with approved change (if sponsor accepts updated completion).
- Accelerate non-dependent tasks (where safe) and adjust sequence.
- Implement stricter vendor milestone tracking and penalties if contract allows.
Preventive actions
- Strengthen requirements validation earlier (to reduce future scope change).
- Update risk register with vendor lead-time and requirement-change risks and set triggers.

This answer typically scores because it ties scope, schedule, procurement, stakeholder communication, and risk into one coherent response.

Mini-case 2: Quality failures increasing cost and affecting schedule

Scenario:
A project deliverable fails acceptance tests twice. The team says it is “a quality problem,” but actual costs are increasing and timeline is slipping.

Answer approach:

Explain quality failure as both a quality and schedule risk outcome:
- rework causes delays,
- rework consumes budget → cost variance.
Recommend quality controls:
- implement testing strategy before acceptance,
- introduce peer reviews,
- define acceptance criteria and ensure alignment with stakeholders.
Use cost and schedule controls:
- track rework effort and update estimates,
- manage corrective actions through integrated change control if scope/standards change.
Stakeholder communication:
- provide transparent reports on defect causes,
- request timely decision on whether to change approach or accept added testing time.

High marks come from clearly linking quality to scope, time, and cost—rather than treating it as isolated.

Final exam readiness plan (last 7 days)

A practical revision plan helps translate notes into exam performance. Use this:

Day 1–2: Tool mastery
- WBS, milestones, critical path concept (explain + mini-calc)
- risk register structure + risk responses
- stakeholder mapping + RACI + communication plan
Day 3–4: Scenario drilling
- Do at least 2–3 scenario questions focusing on structured explanations.
- For each: identify issues vs risks, then propose corrective actions.
Day 5: Mixed paper simulation
- Timed answers (even if unofficial).
- Practice crisp formatting and complete lists.
Day 6: Weak areas review
- Revisit definitions that you frequently confuse (risk vs issue, baseline vs target, charter vs plan).
- Fix explanation gaps: add “why it matters” and “how you monitor.”
Day 7: Final consolidation
- Read checklists.
- Prepare a “one-page” concept map (scope → schedule → cost → quality → risk → stakeholders → control).

How to perform during the exam: small actions with big scoring effects

Read the entire question first, including marks allocation.
Underline keywords: “justify,” “recommend,” “explain,” “compare,” “construct.”
Use the mark structure: if it says “state four,” give four.
If you’re calculating, show steps and then interpret results.
If you’re unsure, still provide the best structured answer based on correct framework logic.
Avoid filler: use project management terminology and direct reasoning.

Putting it all together: a model high-mark mini-answer (definition + application)

If asked: “Define integrated change control and explain why it matters,” a top-level answer would include:

Definition: integrated change control is the process of reviewing, approving, and managing changes across the entire project.
Why it matters: it prevents uncontrolled scope creep, ensures schedule and cost impacts are understood, protects quality objectives, and maintains baseline integrity.
How it works: change requests are evaluated, impacts are assessed, decisions are made by the appropriate authority, baselines are updated only when approved, and stakeholders are informed.
Example: when a client adds extra equipment, you assess impact on cost and timeline, decide whether to accept or reject via approvals, then update schedule and cost baselines accordingly.

Closing note: what consistently distinguishes A-level answers

In PJM01B1 semester exams, the strongest differentiator is not memorization—it’s structured application. Students who score highest:

use correct terminology,
provide complete lists that match question instructions,
connect tools to project objectives,
include justification and trade-offs,
and communicate clearly under time pressure.

With the frameworks, practice prompts, and checklists above, you can approach most PJM01B1 question styles with confidence and produce exam-ready, mark-aligned responses.