Boston Project Management Short Learning Programme Certificate Notes (UNISA-Style Study Guide)

Boston Project Management Short Learning Programme Certificate Notes are the kind of materials South African learners often look for when preparing for short course assessments, portfolio-based certification, and practical project management modules aligned with common university formats (e.g., UNISA project management-style outcomes, C2C/PMBOK-style process groups, and CUT/Varsity College applied project planning logic). These notes focus on the typical content you’d expect to be assessed: project scope, schedule, cost, quality, risk, procurement, stakeholder management, and monitoring & evaluation—presented in a way that matches how learners study for project management NQF-aligned short programmes.

Because many learners search using university course codes and keywords (e.g., UNISA, MNG, CNS, PMBOK, project planning, risk management), the sections below explicitly mirror that exam language and structure, while staying tightly focused on the Boston Project Management Short Learning Programme Certificate learning outcomes and assessment expectations.

1) Boston Project Management: Course Overview, Learning Outcomes, and Exam-Style Success Criteria

The Boston Project Management Short Learning Programme Certificate (often studied by learners who want a structured, practical credential) typically trains learners to perform the core disciplines of project management: defining and controlling scope, building a workable schedule, estimating and managing costs, ensuring quality, identifying and responding to risk, managing stakeholders, and reporting progress through clear monitoring and evaluation. The certificate value is usually highest when your output (assignments, workplace evidence, or case-study answers) is coherent, documented, and aligned to accepted project practices.

Why this programme is assessed the way universities assess

South African universities such as UNISA and CUT (and many other institutions) tend to assess project-related modules with a combination of:

Applied problem solving (case studies)
Structured planning outputs (WBS, Gantt charts, budgets)
Justification of decisions (why a risk strategy, why a stakeholder approach)
Control mechanisms (change control, variance analysis, quality assurance)
Terminology accuracy (scope vs requirements, risk vs issue, assumption vs constraint)

Even when Boston’s certificate isn’t a full UNISA module, the assessment logic often mirrors those academic expectations: your answers must be traceable—every plan should “connect” to the project objectives, and every control should connect to measurable outcomes.

Typical Boston “certificate-ready” outputs you should be able to produce

In most short project management certificates, assessments reward learners who can produce professional artefacts. The artefacts below are the core “expected outputs” that map strongly to exam answers and portfolio tasks.

Common required outputs

Project Charter / Project Summary
- Problem statement or need
- Objectives (SMART)
- Scope boundaries (in-scope / out-of-scope)
- High-level schedule and resources
- Assumptions and constraints
Work Breakdown Structure (WBS)
- Decomposition of deliverables into work packages
- Clear naming and logical grouping
Schedule
- Activity list
- Sequencing (dependencies)
- Durations and milestones
- A Gantt chart or equivalent schedule view
Budget
- Cost estimate by cost category or work package
- Resource costs (e.g., labour)
- Contingency and justification
Risk Register + Risk Response Plan
- Likelihood/impact scoring
- Risk owner
- Prevention/contingency/mitigation strategy
Stakeholder Register + Engagement Plan
- Power vs interest mapping
- Communication methods and frequency
Quality Plan
- Quality objectives and criteria
- Inspection/testing or assurance activities
- Quality metrics
Monitoring & Evaluation (M&E)
- KPIs aligned to objectives
- Reporting cadence
- Variance interpretation
Change Control / Governance
- How scope and schedule changes are evaluated
- Approval thresholds and documentation approach

How to score well in short-course assessments (the “exam rubric mindset”)

Even without seeing a formal marking rubric, you can study in a way that matches typical marking criteria:

Marking pattern you should target

Correct structure: headings, logical flow, and complete coverage of the question.
Correct concepts: use the right project management terms.
Consistency: your scope, schedule, and budget must align.
Evidence-based assumptions: if you assume a duration, explain why.
Professional communication: bullet points, tables, and clear wording.
Justification: “because” statements, trade-offs, risks of alternatives.

Mapping to commonly searched South African university keywords

Many learners search for study material using keywords such as “UNISA project management”, “MNG project management exam notes”, and “CNS project planning risk management study notes.” While Boston is not UNISA, you should adopt UNISA-style clarity: define concepts precisely, apply them to a scenario, and present structured deliverables.

A practical way to do this is to treat Boston assignments like mini-UNISA exam questions:

Start with a short “context” (what the project is and why it matters).
Define scope and objectives in a measurable way.
Produce the plan artefacts (WBS/schedule/budget).
Add risk and stakeholder artefacts.
Close with control and monitoring.

2) Scope, Requirements, WBS, and Scheduling: From Project Charter to Gantt Chart (UNISA-Style Applied Questions)

Scope and schedule are the backbone of most project management assessments. If scope is unclear, your schedule becomes unreliable. If schedule is unrealistic, budget and quality suffer. For a Boston project management certificate, you will typically be expected to transform a narrative scenario into structured artefacts: WBS, activity list, sequencing, durations, milestones, and then a coherent Gantt chart.

Understanding scope: deliverables vs work vs requirements

A common mistake in project management exams is confusing:

Scope (what is included in the project deliverables)
Requirements (detailed needs that deliverables must meet)
Work (activities performed to produce deliverables)

Scope answers: “What are we delivering and what are we not delivering?”
Requirements answer: “What must the deliverables do or contain?”
Work answers: “What do we do to build/produce the deliverables?”

To avoid losing marks, always produce an “in-scope / out-of-scope” list and then tie requirements back to deliverables.

Constructing a project scope statement (scenario method)

Use a scenario-to-scope checklist:

Identify deliverables from the narrative.
Determine boundaries: what is not included.
Specify acceptance criteria at a high level (to link to quality later).
State major constraints (e.g., limited budget or deadline).
List assumptions (e.g., client feedback will be provided within 5 working days).

Example deliverables logic (generic, but exam-usable):

Deliverable A: “Project initiation documents completed”
- Charter, stakeholder register, risk register initial version
Deliverable B: “Approved design and build plan”
- Requirements document, WBS, schedule baseline
Deliverable C: “Implementation and handover”
- Training materials, final documentation, sign-off

This approach makes it easier to build the WBS because each deliverable becomes a parent node.

Work Breakdown Structure (WBS): the marks are in the decomposition

A strong WBS usually demonstrates:

Completeness (covers all deliverables)
Decomposition logic (parent-to-child relationships)
Work package clarity (each work package has an identifiable output)
Manageability (not too large to control)

WBS structure you should remember

A typical WBS uses numbering like:

1.0 Project Management & Governance
2.0 Planning
3.0 Execution
4.0 Monitoring & Control
5.0 Closure

Then each of those expands into smaller work packages. For Boston certificate-level learning, you generally don’t need to use complex WBS standards, but you do need to show a coherent decomposition.

Example: Turning a case study into WBS + schedule (with consistent numbers)

To make this exam-ready, consider a concrete case scenario used throughout these notes (so the numbers stay consistent):

Case scenario: “Community Health Appointment System Setup (CHAS)”

Organisation: a community clinic in Gqeberha (Port Elizabeth)
Objective: implement an appointment scheduling system
Timeline constraint: go-live by 12 weeks
Team (assumed for planning exercises):
- 1 Project Manager (PM)
- 1 Business Analyst (BA)
- 1 Developer/Technician (Dev)
- 1 QA/Trainer (QA)
- 1 Data Capturer (DC)
Core deliverables:
1. Requirements and process mapping completed
2. System configured and integrated
3. Training delivered and handover documentation completed
4. Go-live with monitoring period plan

We’ll use this scenario to illustrate WBS and scheduling logic. Assume the assessment expects a baseline schedule around the 12-week deadline.

Step 1: Build the WBS for CHAS

A simplified WBS aligned to deliverables could look like this:

WBS (CHAS)

1.0 Project Initiation
- 1.1 Kick-off workshop
- 1.2 Project charter approval
- 1.3 Stakeholder register creation
2.0 Requirements & Planning
- 2.1 Process mapping sessions
- 2.2 Requirements sign-off
- 2.3 WBS and schedule baseline
- 2.4 Risk register initial version
3.0 System Configuration & Integration
- 3.1 Configure appointment workflow
- 3.2 Integrate data entry templates
- 3.3 Testing (functional)
4.0 Training & Handover
- 4.1 User training sessions
- 4.2 Handover documentation
- 4.3 Go-live readiness checklist
5.0 Monitoring & Closure
- 5.1 Monitor first two weeks after go-live
- 5.2 Lessons learned workshop
- 5.3 Final report and closure sign-off

This WBS is “good exam practice” because each work package is output-oriented (kick-off workshop, requirements sign-off, testing, training).

Step 2: Schedule activities with durations and dependencies

To get a credible schedule, you must set dependencies. For example:

Requirements sign-off must happen before configuration.
Testing requires configuration to be done.
Training depends on go-live readiness.

Assume working days: 5 days/week. A 12-week timeline equals 60 working days.

Now assign durations that sum to an achievable timeline when sequenced appropriately. A sample activity plan (durations in working days):

Activity plan (CHAS)

1.1 Kick-off workshop: 2 days
1.2 Project charter approval: 3 days (after kick-off)
1.3 Stakeholder register creation: 3 days (parallel to charter approval)
2.1 Process mapping sessions: 8 days
2.2 Requirements sign-off: 5 days (after process mapping)
2.3 WBS and schedule baseline: 4 days (after requirements sign-off)
2.4 Risk register initial version: 3 days (parallel to baseline)
3.1 Configure appointment workflow: 10 days (after requirements sign-off)
3.2 Integrate data entry templates: 8 days (after workflow configuration)
3.3 Testing (functional): 7 days (after integration)
4.1 User training sessions: 6 days (after testing)
4.2 Handover documentation: 4 days (after training draft materials begin)
4.3 Go-live readiness checklist: 3 days (after training + documentation started; finish before go-live)
5.1 Monitor first two weeks after go-live: 10 days (after go-live)
5.2 Lessons learned workshop: 2 days (after monitoring begins; end before closure)
5.3 Final report and closure sign-off: 3 days (after lessons learned)

You can see a schedule can fit into 12 weeks because many tasks are parallelised:

Stakeholder register creation runs while charter approval is finalised.
WBS baseline and risk register creation run in parallel after requirements sign-off.
Integration happens after workflow configuration, but testing can’t start until integration is complete.
Monitoring starts after go-live and extends the project to closure timing.

Step 3: Milestones that an examiner can identify quickly

Milestones should align to deliverables and acceptance checkpoints:

CHAS milestones

Milestone M1: Charter approved (end of Week 1)
Milestone M2: Requirements signed off (around Week 3)
Milestone M3: Testing completed (around Week 7)
Milestone M4: Training completed + readiness checklist complete (around Week 9–10)
Milestone M5: Go-live (around Week 10)
Milestone M6: Monitoring period complete and closure sign-off (around Week 12)

A 12-week timeline with go-live around Week 10 is common in small-to-medium implementation projects, because training and documentation typically follow or overlap with testing.

Scheduling fundamentals you must mention in exam answers

When explaining scheduling, include these fundamentals:

Activity sequencing
- Identify logical relationships (finish-to-start, start-to-start).
Critical path thinking
- The critical path is the chain of activities that determines project duration.
Baseline vs actual
- Baseline schedule is approved; actual performance is tracked against it.
Buffer/contingency
- A contingency slot helps absorb delays (but must be realistic).
Resource constraints
- If the Dev or QA is overloaded, durations may be optimistic; state assumptions.

Counter-argument to “just use durations”

A frequent weak answer is: “I list activities and assign durations.” Strong answers show reasoning. Example counter-argument you should be prepared to handle:

Weak: “Testing takes 7 days.”
Stronger: “Testing takes 7 days because functional test cases cover appointment workflow, data template validation, and user role permissions; 2 days are allocated for retesting issues discovered in the first testing cycle.”

Examiners tend to reward that reasoning because it demonstrates you understand why the duration exists, not just that it exists.

3) Cost, Budgeting, Risk, and Stakeholder Management: Building Control Systems That Survive “Change”

Project management certification assessments often ask for cost and risk planning, then expect evidence of governance and stakeholder engagement. This section builds the control mindset: not only “what the plan is,” but how you keep it stable when the real world introduces change.

Cost management basics: estimates, categories, and contingency

Cost management usually includes:

Cost estimation (what it will cost)
Budgeting (approved baseline)
Cost control (variance monitoring)

For Boston certificate-style work, you often need a simple but coherent budget. You don’t always need a full Earned Value Management system, but you must show how costs relate to scope and timeline.

Example: A consistent CHAS budget (used later for variance-style reasoning)

Assume the assessment requires a budget with labour, materials/tools, and contingency. For CHAS in Gqeberha, you might use the following simplified cost estimate categories:

CHAS budget (example)

Labour costs
- PM (planning + governance): R 18,000
- BA (requirements + mapping): R 14,000
- Dev/Technician (configuration + integration): R 22,000
- QA/Trainer (testing + training): R 12,000
- Data Capturer (template setup): R 6,000
- Labour subtotal: R 72,000
Tools and materials
- Training materials printing and consumables: R 3,000
- Connectivity/data costs (project period): R 2,000
- Miscellaneous software/config licences (if applicable): R 4,000
- Tools subtotal: R 9,000
Contingency
- Risk contingency reserve: R 10,000
Total project budget (baseline): R 91,000

Now check internal logic:

Labour (72,000) + Tools (9,000) + Contingency (10,000) = R 91,000
This is consistent and provides a baseline you can later use in “what if” questions.

How to justify contingency (and not lose marks)

Learners often add contingency “because emergencies happen.” That’s not enough. A better justification links contingency to identified risks.

A contingency rationale statement might say:

Contingency is set at R 10,000 because top risks include late stakeholder feedback, device/connectivity downtime, and rework from requirements changes.
This reserve will be used only after change control approval, or within pre-approved mitigation actions.

Risk management: from risk identification to response planning

Risk management is not only listing risks. A strong risk register includes:

Risk description
Causes and potential impacts
Likelihood and impact rating
Risk score (if used)
Response strategy
Risk owner
Triggers (signals that risk is occurring)
Contingency actions

Defining likelihood and impact (a scoring model)

Assume a 1–5 scale for both likelihood and impact.

Likelihood (1=rare, 5=almost certain)
Impact (1=insignificant, 5=project-threatening)

Risk score = Likelihood × Impact.

CHAS risk register (example with consistent scoring)

Below is an example risk register. The values are chosen to demonstrate a typical certificate-level structure.

CHAS risk register (sample)

Risk ID	Risk description	Likelihood (1-5)	Impact (1-5)	Score	Response strategy	Owner	Trigger
R1	Stakeholder feedback delayed on requirements	4	4	16	Mitigate: weekly review checkpoints, set feedback SLA	BA	No feedback received within 5 working days
R2	Dev/Technician unavailable due to other duties	3	5	15	Mitigate: cross-training tasks to QA/PM support, create task backup plan	PM	Missed resource booking twice
R3	Testing finds critical defects requiring rework	3	4	12	Contingency: allocate re-test buffer; triage critical vs minor	QA	Defect severity high in first testing cycle
R4	Connectivity/data entry disruptions	2	3	6	Mitigate: schedule offline data capture plan; use alternate device	DC	Connectivity unstable more than 2 days
R5	Training materials not ready by training date	3	2	6	Mitigate: draft materials early; run “train the trainer”	QA	Training deck incomplete 2 days before session

These risks show:

At least one high score risk (R1: 16, R2: 15).
A mix of mitigation and contingency.
Ownership and triggers, which are often required by examiners.

Linking risks to schedule and cost (the “control system” connection)

You should explicitly connect:

Risk responses to schedule buffers
Risk responses to cost contingency usage

Example linkage:

R1 (stakeholder feedback delayed) mitigates via weekly review checkpoints, which affects schedule by inserting a recurring checkpoint and potentially compressing approval lead time.
If delays still occur, cost contingency may cover extra BA time or additional workshop costs—subject to change control.

This is where many learners lose coherence: they list risks, but don’t show how risks change the plan. In a Boston certificate context, coherence matters.

Stakeholder management: power/interest and engagement plans

Stakeholders influence requirements, approvals, and acceptance. A stakeholder register typically includes:

Name/role (e.g., Clinic Manager, IT support, Nurses)
Influence/power level
Interest level
Engagement strategy
Communication frequency and channel
Current stance (supportive, neutral, resistant)

Example stakeholders in the CHAS scenario

Use roles tied to the project context in Gqeberha:

CHAS stakeholder set

Clinic Manager (approver and beneficiary)
Nurses (end users)
Business Analyst liaison (community operations contact)
Data Capturer (operational data entry)
Dev/Technician (system configuration)
QA/Trainer (testing and training)

Even in a certificate exercise, naming “roles” instead of specific individuals is acceptable, as long as you keep consistency.

Power/interest mapping (how to describe it in exams)

A simple approach:

High power / high interest: frequent updates, involve in decisions.
High power / low interest: manage closely, occasional updates.
Low power / high interest: keep informed, gather feedback.
Low power / low interest: monitor with minimal communication.

For CHAS:

Clinic Manager likely is High power / High interest.
Nurses likely are Low-medium power / High interest (they need the system to work but approvals may be handled by the Manager).
Dev/Technician is High interest / Medium-high power operationally.
Data Capturer is Medium interest, potentially moderate influence.

Engagement tactics that gain marks

Include concrete tactics:

weekly review checkpoint (for requirements and approvals)
training sessions scheduled in advance with sign-up lists
demonstration of “appointment workflow” to nurses
sign-off checklist for go-live readiness

Handling change: change control as a governance mechanism

Short programmes often assess your ability to respond to change. You can use a simple change control process:

Change control process (exam-friendly)

A change request is submitted (scope/schedule/cost/quality).
PM assesses impact (time, cost, risk, quality).
If approved threshold is met, Steering group/Clinic Manager signs off.
Baseline updates (schedule/budget/scope documentation).
Communication to stakeholders.
Update risk register if new risks emerge.

In CHAS, for example:

If additional features (e.g., SMS reminders) are requested after requirements sign-off, you treat them as a change request: it impacts scope and schedule and may require either timeline extension or trade-off (reducing other items).

Counter-argument: “Change is always bad”

You should be able to argue balance:

Change is not inherently bad; uncontrolled change is bad.
A controlled change process protects stakeholder trust, cost control, and delivery reliability.

In exam answers, demonstrating that balance improves marks because it shows maturity.

4) Quality Planning, M&E, and Governance: Delivering Acceptable Outcomes, Not Just Activities

Quality management and monitoring & evaluation (M&E) are where many learners underperform because they focus on planning but not on proof of achievement. Boston certificate assessments often require you to define quality criteria, show how you will check performance, and explain how you report progress and manage acceptance.

Quality management: defining “fitness for use”

Quality isn’t just “does it work.” It means:

Does the deliverable meet requirements?
Is it usable by end users?
Does it satisfy acceptance criteria?
Is it delivered within constraints (time, budget)?

For CHAS:

The system must correctly create and manage appointments.
Nurses must be able to use the workflow with minimal training.
Data entry must be accurate enough for reliable scheduling.

Quality planning artefacts you should be able to write

In certificate-style answers, you may be asked to create:

Quality objectives
Quality criteria / acceptance criteria
Quality assurance and quality control activities
Test plan or inspection checklist
A simple quality metric

Quality objectives (CHAS example)

Objective Q1: Functional workflow operates as specified in requirements.
Objective Q2: Data entry accuracy meets a defined threshold during testing.
Objective Q3: Training enables nurses to complete scheduling tasks within a set time.

Example acceptance criteria and measurable quality metrics

You need measurable criteria. For example:

During functional testing, no “critical defects” may remain open at go-live.
In a sample of 30 test bookings, at least 28/30 bookings must schedule correctly (accuracy threshold 93.3%).
- This is a concrete numeric example to show you can quantify quality.
Training assessment: at least 80% of participants complete a standard booking scenario correctly after training.

You can present those as:

Acceptance criteria (what must be true)
Evidence (how you prove it: test results, sign-off forms, observation records)

Quality assurance vs quality control (avoid mixing them)

Examiners often look for the conceptual distinction:

Quality assurance (QA): process-focused. Ensures the project’s methods prevent defects.
Quality control (QC): product-focused. Detects defects in deliverables.

For CHAS:

QA example: Use a formal requirement sign-off gate before configuration starts.
QC example: Run functional testing and retesting with a defects log.

Monitoring & Evaluation (M&E): KPIs that tie to objectives

M&E ensures the project’s outcomes are tracked beyond just “tasks completed.” In a certificate context, you should define:

KPIs aligned with project objectives
Data sources (e.g., test results, user feedback, usage metrics)
Reporting frequency
What happens when KPIs indicate underperformance

CHAS KPIs (example)

KPI 1 (Operational accuracy): percentage of correct bookings in test scenarios (target 93.3% as above).
KPI 2 (User usability): percentage of nurses completing a booking scenario correctly (target ≥ 80%).
KPI 3 (Timeliness): go-live achieved by Week 10 (target: within ± 1 week of plan).
KPI 4 (Early adoption): number of appointments created in the first monitoring week (you can set a target if required by the assessment; if not, track actual and report trend).

Reporting cadence and formats that show governance

M&E reporting should be regular and structured. A simple cadence:

Weekly progress report (PM)
Bi-weekly stakeholder update (Clinic Manager)
Go-live checkpoint report (end of Week 9 or start of Week 10)
Monitoring report (end of Week 12)

Reporting content should include:

progress vs schedule baseline
budget status vs baseline
risk status (top risks unchanged, increased, reduced)
quality status (test results and training completion)
decisions and upcoming actions

Governance: approvals, sign-offs, and decision rights

Governance in short programmes may be simplified but must be explicit. For CHAS, the approvals might be:

Clinic Manager approval of charter
BA and Dev alignment on requirements
QA confirmation that testing and readiness checklist passed
Final closure sign-off at end of monitoring period

Include an “approval gate” approach:

Gate 1: Requirements sign-off (before configuration)
Gate 2: Testing complete (before training)
Gate 3: Go-live readiness checklist complete (before go-live)
Gate 4: Monitoring complete and final report accepted (closure)

Handling quality failures (counter-argument and response)

In exam questions, you should demonstrate what you do if quality targets aren’t met. For example:

If testing reveals critical defects:
- classify defects by severity
- prioritise fixes
- reassess schedule impact
- decide: delay go-live, or reduce non-critical features (change control)

A strong answer avoids vague statements like “we fix it” and instead includes:

triage logic
re-test plan
communication to stakeholders
potential schedule/budget implications

5) Integrative Case Study Exam Preparation: Baseline, Variance, Change, and Professional Documentation (Boston Certificate Mastery)

This final section synthesizes everything into an integrative “exam simulation” approach: you start from a baseline plan, track performance, identify variances, apply change control, and show decision-making. This is how many learners succeed in applied project management exams—by producing consistent, cross-referenced outputs rather than isolated lists.

The integrated “baseline vs actual” mindset

A project baseline typically includes:

scope baseline
schedule baseline
cost baseline
quality baseline (acceptance criteria)

In CHAS, we established:

Total project budget baseline: R 91,000
Timeline constraint: 12 weeks, with go-live around Week 10
Quality acceptance criteria examples (93.3% bookings accuracy in sample; ≥ 80% training task success; no open critical defects at go-live)

Now imagine the assessment asks: “After Week 6, report progress and decide on corrective actions.”

A realistic progress snapshot (Week 6) with consistent reasoning

Assume that by end of Week 6:

Requirements sign-off was completed on time (Milestone M2 achieved around Week 3).
Workflow configuration (3.1) was completed early (by Week 5).
Integration (3.2) is 2 days behind because data templates require rework after clarifying requirements.
Testing (3.3) has not started yet; it was planned to start at Week 6.

This means:

schedule variance exists (integration delay affects testing start)
risk R3 (testing rework) may be elevated because rework already occurred
cost variance may occur due to additional Dev or DC time

Translating delays into schedule variance language (exam-friendly)

When asked to quantify, use:

planned vs actual start/finish dates (in weeks or days)
remaining duration impacts
critical path implications (even if simplified)

Example exam sentence:

“Integration (3.2) is delayed by 2 working days, which pushes testing (3.3) by 2 working days unless corrective actions are implemented.”

If the schedule includes working days, 2 working days is 0.4 weeks. You can mention it as:

“~0.4 weeks delay.”

Cost variance: consistent logic with the baseline budget

You may be asked to comment on cost impact even without full accounting. For a certificate note, use proportional reasoning grounded in baseline categories.

Assume the additional rework cost is:

extra Dev time for 2 days, valued at R 22,000 / 10 working days (if you model it internally) is too complex unless the assessment expects it.

To keep it simple but consistent, you can say:

“Additional rework is likely to consume part of the contingency reserve of R 10,000.”
Provide an illustrative estimate: “If the rework costs approx. R 2,500, then contingency remaining is approx. R 7,500.”

But you must keep the arithmetic consistent if you present the number. Let’s do that:

Assume rework costs R 2,500 by Week 6 due to additional integration corrections. Then:

Contingency R 10,000 − R 2,500 = R 7,500 remaining.

If you later mention remaining contingency, it must stay R 7,500.

Risk reassessment after variance: updating your risk register

Schedule delays often indicate:

existing mitigation strategies may be insufficient
likelihood of downstream risks increases

In CHAS, R3 (“Testing finds critical defects requiring rework”) should increase likelihood because rework has already begun in integration.

Update:

R3 likelihood from 3 to 4 while impact remains 4 (score changes from 12 to 16).
This demonstrates you can adapt and “manage risk live,” not as a one-time list.

Applying corrective action vs change request (the key distinction)

Corrective action is within scope to fix performance issues. Change request is about altering scope, budget, or major deliverables.

Example:

Corrective action: re-prioritise tasks to start testing on partially completed integration modules (if integration can be modular and acceptance criteria allow).
Change request: add SMS reminders as a new deliverable—this alters scope.

In exams, you must show you know which one it is.

Example decision: use a schedule compression strategy without changing scope

Suppose corrective action to recover schedule is:

Begin limited testing on completed integration components (if requirements allow staged testing).
QA conducts parallel test case preparation while Dev completes remaining integration tasks.
Training materials are drafted early (overlap) to avoid a later cascade.

This is not a scope change; it is a schedule recovery technique and quality planning alignment.

Documenting the corrective action as an “exam deliverable”

You can present it as a structured plan:

Corrective action plan (CHAS)

Action: Start staged testing at end of Week 6 for completed modules.
- Owner: QA
- Duration: 3 working days
Action: Prep test cases and training deck concurrently with remaining integration.
- Owner: QA + BA
- Duration: 3 working days
Action: Rework integration templates using clarified requirements; enforce configuration checklist.
- Owner: Dev + DC
- Duration: 2 working days
Action: Update schedule baseline only after recovery is confirmed.
- Owner: PM
- Timing: end of Week 8 checkpoint

Then indicate expected outcome:

“Testing start is recovered by Week 8, restoring go-live to around Week 10.”

If recovery fails: escalate to change control

If the corrective actions cannot restore the schedule, go-live may slip. The exam may ask: “What do you do next?” Provide governance steps.

Escalation to change control

Collect data: actual completion of integration, defect log severity, remaining durations.
Calculate impact:
- schedule slip (e.g., “potential 1-week slip beyond target”)
- cost impact (additional labour) and how it affects contingency remaining.
Propose options:
1. Extend timeline (if possible)
2. Reduce non-critical scope elements (if allowed)
3. Reallocate resources (if feasible within budget)
Obtain approval from Clinic Manager and follow documented change control.

This is how you show maturity: you present options and trade-offs.

Closure and lessons learned: turning outputs into organisational value

A Boston certificate often values documentation. Closure should include:

final acceptance (sign-off)
final report (summary of outcomes vs objectives)
lessons learned (what worked, what didn’t, recommendations)

CHAS closure artefacts

Final report: includes achieved milestones (M1–M6), quality outcomes, risks status, budget final picture.
Lessons learned workshop:
- what improved after weekly feedback checkpoints
- where integration rework came from (e.g., unclear templates requirements)
- suggestions for future clinics (template clarification process early)

Professional writing style tips that directly improve marks

To finish strong, your answers should look like “work you’d submit”:

Use headings that mirror artefacts: Scope, WBS, Schedule, Budget, Risk, Stakeholder, Quality, M&E, Change control.
Avoid long narrative paragraphs. Use bullet lists and tables.
Always keep numbers consistent:
- Budget baseline is R 91,000
- Contingency is R 10,000, and after rework it becomes R 7,500
- Timeline is 12 weeks
- Go-live around Week 10
When you mention a KPI target, keep it consistent:
- booking accuracy target ~93.3% (28/30)
- training task success target ≥ 80%
- “no open critical defects at go-live”

Putting it all together: a compact “exam answer template” for CHAS

Below is a condensed structure you can reuse in timed assessments (adapt for your scenario).

CHAS answer template

Project charter summary
- Objective and constraints (12 weeks; go-live target Week 10)
Scope statement
- In-scope / out-of-scope; deliverables
WBS
- list major work packages and outputs
Schedule
- milestone list; dependencies summary; critical path note (brief)
Budget
- total baseline R 91,000; labour/tools/contingency; contingency R 10,000
Risk register
- top risks with likelihood/impact and response strategy; R1–R5
Stakeholder engagement
- power/interest approach; communication cadence
Quality plan
- acceptance criteria; QA vs QC activities; test and training evidence
M&E
- KPIs, data sources, reporting cadence
Change control

how you decide corrective actions vs change requests

Progress update example

Week 6 snapshot: integration delay 2 days; contingency reduced to R 7,500; schedule recovery strategy

Closure

final sign-off and lessons learned

Final consolidation checklist (what to practice before the exam/assessment)

A strong candidate typically practices by producing these artefacts quickly and accurately:

Project scope with clear in-scope/out-of-scope
WBS with logical decomposition into work packages
Activity list with dependencies and milestones
Baseline budget with total and contingency (CHAS: R 91,000; contingency R 10,000)
Risk register with likelihood/impact scoring and response plans
Stakeholder register with engagement approach
Quality objectives and measurable acceptance criteria
M&E KPIs and reporting cadence
Change control process with clear escalation logic
A short “Week X progress update” using variance language

If you want, I can also generate practice exam questions in a UNISA/CUT style specifically aligned to these notes (e.g., “Prepare a WBS and a Gantt chart schedule with milestones,” “Develop a risk register,” “Write a quality plan with measurable criteria,” “Perform a Week 6 progress variance report and propose corrective actions”).