NMU JPM301 (Project Management 3A) is a course where the exam typically rewards structured thinking: how you plan, schedule, budget, manage quality, handle contracts, and make decisions under constraints. These exam notes are written in a South African university study style for Nelson Mandela University (NMU) and are aligned with the kinds of questions that appear in Project Management assessments—especially those that test your ability to apply theory to realistic project scenarios. You’ll find worked examples, common exam question patterns, and “past paper style” practice guidance across planning, scheduling, risk, procurement, stakeholder management, monitoring & control, and project governance.
Section 1: NMU JPM301 Foundations — Project Life Cycle, Governance, and Exam-Writing Patterns
Project Management exams at university level usually start by checking whether you can define the core concepts and then apply them. In JPM301, expect questions that look like: “Given a project brief… identify the best approach to phase gates, stakeholders, and governance” or “Explain how monitoring and controlling differs from planning.” The marks often go to clarity, correct terminology, and logical sequencing rather than memorising one textbook definition.
The Project Life Cycle (What the exam expects you to “show”)
Most exam questions revolve around the idea that projects move through phases. A typical structure you’ll see (and should adapt to the question wording) is:
- Initiation / Concept
- Problem statement
- Project purpose and objectives
- Business case (why it’s worth doing)
- High-level stakeholder identification
- Planning / Design
- Scope definition
- Work Breakdown Structure (WBS)
- Schedule and cost estimation
- Risk planning, quality planning, communication planning
- Procurement planning and contracting strategy
- Execution / Implementation
- Team mobilisation
- Procurement execution
- Quality assurance activities
- Communication and stakeholder management in action
- Monitoring & Controlling
- Track progress vs plan
- Manage changes and corrective actions
- Monitor risks and performance metrics
- Closing / Handover
- Deliverables acceptance
- Lessons learned
- Final reporting and contract closure
Exam tip: When asked about phases, don’t only list them. Write how the outputs of one phase become inputs to the next. For example, “During planning, the WBS and schedule become the baseline against which monitoring measures performance.”
Project Governance and the “Stop/Go” mindset
Governance is where many students lose marks because they talk about “management” generally instead of governance mechanisms. A governance approach typically includes:
- Roles and responsibilities
- Sponsor / steering committee (oversight, funding decisions)
- Project manager (execution and coordination)
- Team leads / functional managers (resource delivery)
- Decision gates / phase approvals
- After initiation: approve business case and project charter
- After planning: approve scope baseline, budget baseline, and schedule baseline
- During execution: approve major change requests
- At close: accept deliverables and confirm benefits realisation plans
What the examiners want: If you can explain why phase gates exist—control risk, prevent scope creep, ensure readiness—you score higher.
Worked mini-scenario (common in past-paper style questions)
You are given a project to renovate a campus facility. The project sponsor requests changes mid-way due to “new requirements” from an external stakeholder.
A high-scoring answer would say:
- During planning, you established a scope baseline and change control procedure.
- During monitoring & controlling, you assess the impact of changes on scope, cost, time, quality, and risk.
- The steering committee approves changes based on the business case and available contingency.
- Execution continues only after the change request is authorised and updates to baselines are formally approved.
Stakeholders: identification, influence, and engagement strategy
Expect questions on stakeholder mapping and engagement. A frequent exam pattern is: “Identify stakeholders and suggest engagement methods.”
Use a structured method:
- Identify stakeholders
- Internal: sponsor, project manager, project team, operations department, finance, HR
- External: clients/users, regulators, suppliers/contractors, local community, consultants
- Assess influence & impact
- High influence / high impact: manage closely
- High influence / low impact: keep satisfied and informed
- Low influence / high impact: keep informed and ensure their needs are met
- Low influence / low impact: monitor and communicate minimally
- Choose engagement approach
- Workshops for requirements clarification
- Regular progress reports for steering committee
- Formal approvals at phase gates
- Consultation sessions for community/regulators
“Engagement methods” that score marks
- Workshops (to co-create scope or requirements)
- Newsletters / dashboards (for routine updates)
- Risk reviews (for risk escalation)
- Approval forums (phase gates, change control)
Project objectives and scope boundaries
Many exams include a short section on scope, objectives, and the difference between:
- Objectives (what you aim to achieve)
- Deliverables (what you will produce)
- Scope (what is included/excluded)
A strong answer uses both the SMART perspective and the scope boundaries perspective.
SMART example tied to project management
If the project is to implement a new student support system:
- Specific: “Implement an automated ticketing and escalation system”
- Measurable: “Reduce average response time from 48 hours to 24 hours”
- Achievable: depends on integration capability and staffing levels
- Relevant: supports improved service delivery
- Time-bound: “Within 6 months of project start”
The scope boundaries should then specify:
- Included: ticket creation, SLA workflow, reporting dashboard
- Excluded: redesigning all academic programmes, replacing the entire student information system (unless explicitly in scope)
Exam-writing checklist for theory questions
When asked “Explain…” or “Discuss…” include:
- Definition (1–2 lines)
- Key components (bullets or short list)
- Applied example (1 short scenario)
- Importance (why it matters for success)
This approach mimics high-quality responses expected in South African university assessment styles.
Section 2: Scope, WBS, Scheduling, Costing, and Baselines — The Core “Numerical” Skills Area
Even when JPM301 questions are not heavy on complex calculations, they often test your logic around planning and baselines. If you can translate project requirements into a WBS and then build a schedule and budget, you will score well. Many students struggle because they “know the terms” but cannot apply them consistently.
Work Breakdown Structure (WBS): turning scope into manageable work
A WBS decomposes the work into smaller components. Exams often test both:
- The ability to construct a WBS (even partially)
- The ability to explain why WBS matters for cost/schedule/monitoring
WBS structure rule-of-thumb
- Decompose until each work package can be estimated and scheduled.
- Ensure each work package has:
- A clear output/deliverable
- An owner (responsible party)
- An estimated duration or effort
- Associated resources and cost estimate (or at least a cost category)
Example WBS (renovation project)
Project: Renovate a campus facility for improved usability.
A simplified WBS:
- 1.0 Project Management
- 1.1 Project initiation and charters
- 1.2 Planning and baselines approval
- 1.3 Progress reporting & change control
- 2.0 Site Preparation
- 2.1 Site surveys and inspections
- 2.2 Temporary barriers and access control
- 2.3 Demolition planning
- 3.0 Construction and Fit-out
- 3.1 Electrical rework
- 3.2 Plumbing rework
- 3.3 Flooring and finishing
- 4.0 Commissioning and Handover
- 4.1 Testing and inspections
- 4.2 Defect rectification
- 4.3 Handover documentation
An examiner may ask you to:
- Identify work packages suitable for cost estimation
- Suggest where risks are likely (e.g., site conditions under “Site Preparation”)
Scheduling fundamentals: sequencing, dependencies, and critical thinking
Scheduling is more than listing tasks. The exam expects you to recognise dependencies and sequencing.
Common dependency types
- Finish-to-Start (FS): Task B starts after Task A finishes
- Start-to-Start (SS): Task B can start when Task A starts
- Finish-to-Finish (FF): Task B finishes when Task A finishes
- Start-to-Finish (SF): less common in standard practice
Worked “exam style” scheduling logic (without requiring software)
Suppose you have these activities with dependencies:
| Activity | Duration (days) | Dependency |
|---|---|---|
| A: Finalise drawings | 10 | None |
| B: Procurement of materials | 12 | FS after A |
| C: Prepare site | 7 | FS after A |
| D: Install electrical | 9 | FS after B and C |
| E: Commissioning | 5 | FS after D |
You can infer:
- A finishes at day 10
- B can start day 10 and finishes day 22
- C can start day 10 and finishes day 17
- D needs both B and C, so D can start at day 22 (because B completes later), finish at day 31
- E starts at day 31, finish at day 36
The total project duration becomes 36 days.
Exam tip: If the question asks “What is the critical path?”, show the logic:
- The path that determines the total duration is A → B → D → E (because delays there delay the end date).
Cost estimation and budgets: baseline creation
A common JPM301 theme is the relationship between:
- cost estimates,
- contingency,
- and the approved cost baseline.
Cost categories you should recognise
- Direct labour
- Direct materials
- Subcontractor costs / procurement costs
- Equipment rental
- Overheads
- Contingency (for known-unknowns)
- Management reserve (for unknown-unknowns, depending on the syllabus)
Baseline meaning (and why it’s tested)
A baseline is the authorised plan against which actuals are measured.
- Time baseline: planned schedule dates
- Cost baseline: planned budget by time/phase
- Scope baseline: approved scope statements and deliverables
If the exam asks “How do changes affect baselines?”, answer:
- Evaluate impact on triple constraint (scope, time, cost)
- Submit change request
- Approve/reject
- If approved, update baselines and communicate
Time-cost trade-offs and resource constraints
Students often think “more resources = faster” always. Exams may test the understanding that:
- adding resources can reduce duration but increases cost,
- and sometimes causes inefficiency (coordination overhead).
Example: trade-off reasoning
A construction phase is planned for 20 days at cost R200,000. A stakeholder demands completion in 16 days.
You propose:
- Add one extra subcontract team for days 11–20 to reduce duration.
- Expected new cost becomes R245,000.
- There is a risk of rework due to coordination and interface issues.
A high-scoring answer will show:
- schedule reduction feasibility,
- cost impact,
- quality and risk impact,
- and whether the business case supports the change.
Milestones, deliverables, and reporting baselines
Milestones are points in time with measurable completion.
Example milestones for the renovation project:
- M1: Drawings approved (day 10)
- M2: Materials procurement complete (day 22)
- M3: Electrical installation complete (day 31)
- M4: Handover accepted (day 36)
These milestones help monitoring & controlling because they provide “checkpoints” for progress measurement.
What the exam expects: When asked about monitoring, refer to milestones and baseline comparisons, not just “track progress.”
Section 3: Risk Management, Quality Management, Procurement & Contracts — Turning Plans into Controlled Execution
In JPM301, risks and quality are tested both conceptually and through applied scenarios. Procurement/contracting questions often appear as short essays, where the student must show understanding of contract types, procurement steps, and how contracting influences risk allocation.
Risk management: identification to response planning
A strong risk management answer typically follows:
- Identify risks
- Analyse risks (likelihood and impact)
- Evaluate priorities (risk ranking)
- Plan responses
- Implement responses
- Monitor and control risks
Risk identification sources (things you should list)
- WBS and schedule review (what tasks are complex?)
- Stakeholder analysis (who can block approvals?)
- Resource constraints (skills availability)
- External factors (weather, regulatory timelines)
- Assumptions and dependencies
Risk analysis: likelihood and impact (use a simple scale)
If the question gives probabilities and consequences, use them. If it doesn’t, use your own consistent scale.
A common classroom approach:
- Likelihood: 1 (low) to 5 (high)
- Impact: 1 (low) to 5 (high)
- Risk score = likelihood × impact
Example (consistent numbers):
- Risk R1: material delivery delayed
- Likelihood 4, impact 5 → score 20
- Risk R2: design changes requested late
- Likelihood 3, impact 4 → score 12
- Risk R3: minor workmanship defects
- Likelihood 2, impact 2 → score 4
Prioritise R1 and R2.
Risk response strategies: what to say and when
You should recognise common response categories:
- Avoid: change plan to remove risk
- Mitigate: reduce likelihood or impact
- Transfer: shift risk (e.g., insurance, performance bonds, contract clauses)
- Accept: acknowledge risk and plan contingency
Applied example: delivery delays
If material delivery delays are high likelihood/high impact:
- Mitigate: use pre-qualified suppliers, order earlier, add lead time buffer
- Transfer: include penalties for late delivery in supplier contract
- Accept: only if contingency exists and schedule can absorb delays
Integrating risk with schedule and cost
Exams like questions that ask: “Where does contingency appear?” The correct idea:
- Schedule contingency: additional buffer or float to absorb delays
- Cost contingency: budget reserved for risk events
A strong answer connects risk response to baseline adjustments.
Consistency example (numerical logic)
Assume:
- Planned construction cost = R200,000
- You allocate cost contingency = R20,000
- Therefore total budget including contingency = R220,000
If the question later asks “What happens if delay risk materialises?” answer:
- Use contingency funds first to cover additional costs,
- If contingency is exhausted, submit change request for more budget or revise scope/time.
Quality management: assurance vs control
Quality is often tested through a distinction between:
- Quality assurance (QA): processes to prevent defects
- Quality control (QC): inspections/tests to detect defects
Example: renovation project quality
QA actions:
- Clear method statements for electrical works
- Approved installation standards
- Training and checklists before work begins
QC actions:
- Electrical safety tests after installation
- Snag inspections at handover
- Testing fixtures for functionality
Quality planning: criteria and acceptance standards
In exam answers, always mention criteria. If you only say “ensure quality,” you lose marks.
Quality criteria examples:
- Electrical compliance with required standards
- Workmanship specifications
- Completion documentation requirements
- Handover checklist completion (as a measurable acceptance condition)
Procurement & contracting: choosing the right approach
Procurement questions may include:
- What are the steps in procurement?
- Why tendering?
- How do contract types allocate risk?
A structured procurement answer:
- Procurement planning
- what to buy / outsource
- timing and strategy
- Request for proposal / tender
- define specifications and evaluation criteria
- Evaluation and award
- price + capability + compliance
- Contract negotiation and signing
- terms and conditions
- Contract execution and performance monitoring
- claims, variations, progress reporting
- Close out
- acceptance, final invoices, lessons learned
Common contract types you may be expected to know
While syllabi can differ, these are widely taught:
- Fixed-price (lump sum)
- Lower contractor cost risk
- Higher client risk for scope changes unless variations are tightly controlled
- Cost-plus (reimbursable)
- Higher client cost uncertainty
- Lower risk to contractor
- Time and materials
- Useful when scope uncertain
- Unit-price
- Payment based on quantities
- Performance-based contracts
- Payment tied to outcomes/targets
Risk allocation logic (what to write)
- If scope is clearly defined: fixed-price can work well.
- If scope is uncertain: cost-plus or time-and-materials might be more appropriate.
- If you want to incentivise outcomes: performance-based can align incentives.
Contract variations and change management
Procurement is where “changes” become expensive. In exam answers, show how variation requests should align with the project change control process:
- Variation must document:
- cause,
- impact on cost/time,
- justification,
- updated schedule implications,
- updated risk/quality considerations
- Approvals should follow governance:
- project manager recommendation,
- sponsor/steering committee approval depending on threshold
Exam tip: Use consistent vocabulary—“change request,” “variation,” “baseline update,” “approval”—across your response.
Section 4: Monitoring & Controlling — Performance Measurement, Change Control, and Managing Project Execution
This section captures the operational heart of the course: how you monitor progress, measure performance, manage changes, and report. Many students know “monitoring exists,” but exams ask for what you measure and how you respond when you are off track.
The monitoring & controlling cycle
A typical monitoring cycle can be written as:
- Measure actual performance
- deliverable completion
- milestones hit
- costs incurred
- Compare actual vs baseline
- schedule variance
- cost variance
- scope variance (what’s missing/added)
- Analyse causes
- root causes: procurement delays, resource shortages, design changes, quality rework
- Recommend corrective actions
- schedule compression
- re-sequencing activities
- re-estimating costs
- improving QA to prevent rework
- Update plans and baselines (if approved)
- Communicate to stakeholders
- steering committee updates
- team re-plan instructions
Earned Value Management (EVM): likely exam content
Many project management syllabi include EVM concepts. Even if the exam uses simplified numbers, your conceptual correctness matters.
EVM uses:
- PV (Planned Value): value of work planned by a certain date
- EV (Earned Value): value of work actually completed by that date
- AC (Actual Cost): actual cost incurred by that date
Key derived metrics:
- SV (Schedule Variance) = EV − PV
- CV (Cost Variance) = EV − AC
- SPI (Schedule Performance Index) = EV / PV
- CPI (Cost Performance Index) = EV / AC
Past-paper style worked example (simple but consistent)
Assume by week 6:
- PV = R300,000 (planned work should be worth R300,000)
- EV = R240,000 (actual work completed is worth R240,000)
- AC = R270,000 (actual cost spent is R270,000)
Compute:
- SV = EV − PV = 240,000 − 300,000 = −R60,000
- negative means behind schedule
- CV = EV − AC = 240,000 − 270,000 = −R30,000
- negative means over budget
- SPI = EV / PV = 240,000 / 300,000 = 0.80
- CPI = EV / AC = 240,000 / 270,000 = 0.89
Exam interpretation: SPI < 1 and CPI < 1 indicates both schedule underperformance and cost overrun.
Forecasting note (if EVM is asked further)
Depending on the syllabus, you may be asked:
- Estimate future performance or estimate EAC (Estimate at Completion).
A common EAC assumption: - EAC = BAC / CPI (if cost performance is expected to continue)
If BAC (Budget at Completion) is, for example, R600,000:
- EAC = 600,000 / 0.89 ≈ R674,157
This shows the potential cost increase.
Change control: the exam’s favourite “process” question
Change control is often tested in an “explain the steps” format.
Change control steps (what to write)
- Identify change
- request logged
- Create change request
- description, reason, affected baselines
- Evaluate impact
- cost, time, scope, quality, risk
- Decide
- approve, reject, defer, or require rework
- Implement
- update baselines and plans if approved
- Communicate
- inform stakeholders and update documentation
Example: change request with cost/time impact
Suppose electrical installation scope increases:
- Add extra sockets and cabling due to a new lab use case.
- Estimated additional cost = R25,000
- Estimated schedule delay impact = 3 days
- Quality risk increases due to more complex wiring paths (likelihood from 2 to 3, impact from 3 to 4)
In an exam answer, you’d say:
- quantify schedule and cost impact,
- assess risk and quality impact,
- recommend whether to approve based on business priorities.
Progress reporting and stakeholder communication
Many students describe “communication” vaguely. A better exam answer includes:
- What reports include
- When they are produced
- Who receives them
- How they influence decisions
Example reporting plan
- Weekly project team report: tasks completed, issues, next week plan
- Monthly steering committee report: milestone status, EVM metrics (if used), risk register updates, change requests
- Ad hoc notifications: urgent risks, safety incidents, contract disputes
Corrective and preventive actions (CAPA concept)
Exams may ask you to distinguish:
- Corrective action: fix the problem already happening
- Preventive action: reduce likelihood of future problems
Example:
- Corrective: rework faulty wiring discovered in QC test
- Preventive: implement stricter QA checklists and supervisor sign-offs before installation
Lessons learned: closing the loop
A high-quality JPM301 answer mentions:
- capturing lessons learned,
- ensuring they are stored and accessible,
- applying them to similar future projects.
If the exam includes “closing,” mention that lessons learned feed into organisational process assets and improve future planning.
Section 5: Past-Paper Style Practice — Typical JPM301 Question Types, How to Answer Them, and Worked Mini-Papers
This section consolidates everything into past-paper style guidance: the kinds of questions examiners commonly set, what marks are likely awarded, and how to structure your response. The goal isn’t only to “say what to do,” but to show you how to write exam answers that score.
Common JPM301 exam question types (and mark-winning structure)
Type A: “Discuss the role of …” (theory with application)
Examples:
- Discuss project governance and phase gates.
- Discuss risk management and its integration with planning.
Structure to use:
- Definition (1 paragraph)
- Components (bullets)
- Why it matters (link to success criteria)
- Short example (tie to a scenario)
Type B: “Explain differences between …” (comparison)
Examples:
- Differentiate QA vs QC.
- Differentiate planning vs monitoring.
Structure:
- Table or bullet comparison:
- focus
- timing
- objective
- outputs
- Provide one mini example for each
Type C: “Given a scenario, identify and propose …”
Examples:
- Given a schedule and delays, identify the critical path and propose recovery.
- Given a stakeholder complaint, propose an engagement plan.
Structure:
- Identify problem clearly
- List plausible causes
- Choose the most likely root cause
- Propose actions with time/cost/risk impacts
- Tie actions to baseline and governance
Type D: “Compute and interpret performance” (EVM or schedule logic)
Examples:
- PV/EV/AC calculations and interpretation
- Schedule duration based on dependencies
Structure:
- Show formulae
- Substitute values
- Compute results
- Interpret what it means (behind schedule / over budget)
- Provide one corrective recommendation consistent with results
Past-paper style mini-paper 1: Governance, scope, and change control (essay)
Question (mock):
A university department initiates a project to develop an online booking system for lab resources. During execution, a new policy requires additional reporting features. As project manager, explain how you would manage the change to protect scope, schedule, and budget.
High-scoring answer outline:
- Recognise the change as a change request triggered by new policy.
- Describe how to log and document it:
- requirement description (what reporting features),
- affected deliverables,
- reason (policy update),
- impacted baselines (scope, schedule, cost).
- Evaluate impact:
- cost increase estimate,
- time estimate to build/test/report features,
- risk implications (integration complexity, QA effort).
- Ensure governance:
- steering committee/sponsor decision depending on thresholds.
- Implement:
- if approved, update scope baseline, time baseline, and cost baseline,
- communicate revised plan to team and stakeholders.
- If rejected:
- propose alternative compliant solution within baseline
- or defer to a future phase with benefits justification.
Key marks you should explicitly mention:
- baseline protection,
- formal approval,
- documented impact assessment,
- communication and re-planning.
Past-paper style mini-paper 2: Scheduling logic and critical path reasoning
Question (mock):
Given the following activities and dependencies for a project to renovate a facility, determine the earliest completion time and identify the critical path.
Use the same data as earlier to ensure internal consistency:
| Activity | Duration (days) | Dependency |
|---|---|---|
| A: Finalise drawings | 10 | None |
| B: Procurement of materials | 12 | FS after A |
| C: Prepare site | 7 | FS after A |
| D: Install electrical | 9 | FS after B and C |
| E: Commissioning | 5 | FS after D |
Expected calculations:
- A: day 0–10
- B: day 10–22
- C: day 10–17
- D: depends on both B and C → starts at day 22, finishes day 31
- E: day 31–36
- Earliest completion: 36 days
- Critical path: A → B → D → E
High-scoring “why” line:
- Delays on A, B, or D directly delay the end date because those activities determine the start of D and D determines the start of E.
Past-paper style mini-paper 3: Earned Value interpretation and corrective actions
Question (mock):
By week 6 of a project, PV = R300,000, EV = R240,000, AC = R270,000. Calculate SV, CV, SPI, CPI and interpret the results. Recommend one corrective action.
Calculations:
- SV = EV − PV = 240,000 − 300,000 = −R60,000
- CV = EV − AC = 240,000 − 270,000 = −R30,000
- SPI = EV / PV = 240,000 / 300,000 = 0.80
- CPI = EV / AC = 240,000 / 270,000 ≈ 0.89
Interpretation:
- Negative SV: behind schedule
- Negative CV: over budget
- SPI < 1: schedule performance is 20% worse than planned
- CPI < 1: cost efficiency is about 11% worse than planned
Corrective action examples (choose one and justify):
- If schedule is behind due to procurement delays:
- expedite procurement (at controlled cost), resequence dependent tasks if possible
- If cost overruns are due to rework:
- strengthen QA to reduce defects and rework cost
- If both: propose integrated schedule recovery plan and cost control (review resource allocation and prevent further scope creep)
A good answer selects one action and links it to the most likely cause implied by overrun + under-earning.
Past-paper style mini-paper 4: Risk register entries and response selection
Question (mock):
Create a short risk analysis for a renovation project and propose responses. Provide at least three risks with likelihood, impact, risk score, and response strategy.
Use the earlier consistent example set:
- R1: Material delivery delayed (Likelihood 4, Impact 5 → score 20)
- R2: Design changes requested late (Likelihood 3, Impact 4 → score 12)
- R3: Minor workmanship defects (Likelihood 2, Impact 2 → score 4)
Expected response strategies:
- R1 (20): mitigate/transfer
- order earlier, add lead time buffer, include delivery penalties
- R2 (12): mitigate/avoid
- strengthen change control and stakeholder sign-off at phase gates
- R3 (4): accept/mitigate
- normal QC procedures and defect rectification plan
High-scoring answers also mention how these responses affect planning:
- extra time buffer for R1,
- clearer scope approvals for R2,
- inspection plan for R3.
Past-paper style mini-paper 5: QA vs QC short comparison
Question (mock):
Differentiate between quality assurance and quality control in the context of electrical installation for a campus renovation project. Provide one example of each.
High-scoring answer:
- QA (process-focused, prevention):
- “QA includes approved method statements, training, and checklists to ensure wiring is installed according to standards before work starts.”
- QC (product-focused, detection):
- “QC includes electrical safety testing after installation and snag inspections before handover.”
Why this earns marks:
- clear distinction + context-specific examples.
How to approach “past paper” questions even when you don’t see the exact same numbers
Exams often recycle structures even when the scenario changes. Use this strategy:
- Identify the topic (governance, scheduling, risk, quality, procurement, monitoring)
- Pick the correct framework (life cycle, WBS, dependency logic, risk matrix, QA/QC, change control, EVM)
- Map the scenario details to the framework (stakeholders become stakeholders, delays become schedule variance, defects become QC actions)
- Write the answer in marks-friendly sections
- bullets for lists
- short paragraphs for explanations
- formulas if calculations are needed
- Use consistent wording
- “baseline,” “change request,” “mitigate,” “approve,” “monitoring & controlling,” “quality assurance/control”
High-yield “what examiners look for” checklist (use in your revision)
- Correct terms: baseline, WBS, milestone, governance, risk response, QA/QC, EVM
- Correct sequence: initiation → planning → execution → monitoring/controlling → closing
- Applied logic: always tie theory to a scenario
- Quantitative correctness: PV/EV/AC formulas and arithmetic if numbers are given
- Clear interpretation: not just “SPI=0.8” but “behind schedule”
- Governance alignment: approvals and phase gates are mentioned when change occurs
- Consistency: you don’t contradict earlier assumptions (same project duration, same cost baseline logic)
Final Revision Map (Condensed but Still Exam-Ready)
To revise efficiently for NMU JPM301, structure your revision sessions around the same five pillars:
- Project life cycle & governance
- phase gates, decision making, stakeholder engagement
- Scope → WBS → schedule → cost baselines
- dependencies, milestone logic, contingency rationale
- Risk & quality management
- risk scoring, response strategies, QA vs QC distinction
- Monitoring & controlling
- EVM concepts (PV/EV/AC), variance interpretation, corrective actions
- Procurement & contracts + change control
- procurement steps, contract risk allocation, variations aligned to baselines
When you practise, choose one “mock scenario” and run it through all pillars (life cycle, WBS, schedule, risk register, QA/QC, procurement steps, EVM interpretation). That single scenario-based practice usually matches how JPM301-style exams test whether you can think like a project manager under real constraints.
If you want, share your most recent NMU JPM301 exam paper (or question photos) and I can produce a targeted past-paper commentary: model answers, marking rubrics, and a practice set using the exact question formats from your paper.
