OPMT301 Study Notes: Operations and Project Management (Durban University of Technology)

Operations and Project Management (OPMT301) is where you connect how organizations produce goods and deliver services (operations) with how they plan, manage, and deliver unique outcomes (projects). In a typical DUT assessment, you’re expected to demonstrate that you can apply core operational concepts—capacity, process design, quality, inventory, and supply chains—while also using standard project management tools like WBS, scheduling, risk management, and monitoring and control. These study notes are written in an exam-focused way, using practical examples, common workplace scenarios, and problem-solving checklists you can use directly in tests and assignments.

DUT OPMT301: Core Operations Management Concepts for Project Work

Operations management is the engine of delivery. Even when you’re doing a project (building, implementing, upgrading, launching), project success depends on operational realities: lead times, throughput, quality standards, bottlenecks, resource constraints, and how work flows through a system. In OPMT301, exam questions often test whether you understand the interfaces between operations and project execution: how operational constraints shape project plans, and how project decisions impact ongoing operations.

1) The Operations System: Inputs, Transformation, Outputs

A useful exam framing is to define an operations system as:

• Inputs: people, machines, materials, information, energy, capital
• Transformation process: converting inputs into outputs using defined processes
• Outputs: products/services, by-products, waste, compliance evidence, customer satisfaction

A typical DUT question may ask you to explain this system and then link it to project activities. Example: suppose a company runs a warehouse and wants to implement an automated picking system. The project (installation + training + commissioning) must respect operational inputs and transformation realities:

• Materials flow must continue during installation (minimize downtime).
• Workforce must be trained to operate new systems.
• Inventory policies must be updated so customer service levels are maintained.

Key link for exams: project plans must include operational continuity—because operations don’t stop just because a project is running.

2) Process Types and Their Implications (Job Shop, Batch, Mass, Continuous)

Operations systems can be categorized by how products/services move through processes. Common classifications include:

• Job shop: low volume, high variety, customized outputs (e.g., furniture custom production)
• Batch: medium variety, produce groups (e.g., bakery producing batches of bread)
• Mass production: high volume, standardized output (e.g., beverage bottling lines)
• Continuous: constant production flow (e.g., water treatment plant)

For projects, this matters because process type affects:

• Scheduling: job shop is harder to schedule; continuous is easier to forecast but sensitive to disruptions
• Resource planning: specialized skills needed in job shop
• Quality control: standardized processes can use tighter statistical monitoring
• Change management: mass/continuous operations may require planned shutdowns

Example scenario (exam-style)

A hospital wants to introduce a new surgical instrument sterilization process. This is closer to a continuous/standardized service environment. The project plan must consider:

1. Where sterilization capacity bottlenecks might occur during commissioning
2. Whether the facility can handle increased cycle times temporarily
3. How quality assurance checks will be performed without causing delays

3) Capacity Planning and Bottlenecks

Capacity is how much work a system can handle in a period. Capacity is constrained by the bottleneck resource—the step with the smallest effective capacity.

In operations and project management, the bottleneck often controls:

• Throughput (how fast outputs are completed)
• Lead time (time from start to finish)
• Ability to meet due dates
• Risk of missed service levels

Throughput logic (simple exam explanation)

If a process has multiple stages, the stage with the least capacity dominates overall throughput. If stage A can process 60 units/day, stage B 45 units/day, and stage C 55 units/day, then system throughput is capped at 45 units/day.

Exam tip: show the calculation

If a project depends on producing 900 units and the bottleneck allows 45 units/day, then base time for production is:

• ( 900 \div 45 = 20 ) days (ignoring variability and downtime)

Project scheduling must include adjustments for:

• setup times
• breakdowns
• learning curve
• quality rework

4) Quality Management: Prevention, Appraisal, and Failure Costs

Quality management in OPMT301 typically includes quality planning, assurance, and control. The exam frequently expects you to distinguish:

• Prevention costs: training, process design, documentation, preventative maintenance
• Appraisal costs: inspections, testing, audits
• Failure costs: scrap/rework, returns, complaints, downtime due to defects

A strong exam answer explains that quality is cheaper when planned, not only inspected at the end.

Common quality tools (how to use them in projects)

You may be asked to connect operations tools to project deliverables. Examples:

• Control charts for monitoring process stability
• Pareto analysis to prioritize top defect causes (the 80/20 idea)
• Cause-and-effect (fishbone) diagrams for root cause analysis
• Acceptance sampling in procurement quality checks

Example

A project to implement a new packaging line has a quality issue: 6% of packages fail sealing tests. The project team should:

1. Identify defect types (leaks, misalignment, incomplete seal)
2. Use Pareto to rank causes (e.g., seal temperature, operator technique, machine calibration)
3. Take corrective actions that are preventive (calibrate machine, update operator training)
4. Implement control plans so the problem doesn’t return after project completion

5) Inventory and Service Levels: Why Projects Care About Stock

Inventory management affects operations cost and service reliability. Projects interact with inventory because:

• projects consume materials and equipment
• projects can temporarily reduce supply availability for operations
• procurement lead times can delay critical path tasks

Key inventory concepts that often appear in exams:

• Lead time: time between ordering and receiving
• Reorder point (ROP): inventory level at which a new order should be placed
• Safety stock: buffer for demand variability and supply delays
• Economic order quantity (EOQ): balancing ordering costs and holding costs (where taught)

Example calculation (common exam structure)

Assume:

• Average daily demand = 50 units/day
• Lead time = 7 days
• Safety stock = 100 units

Then:

• Reorder point ( = 50 \times 7 + 100 = 350 + 100 = 450 ) units

If a project delays delivery of raw materials for 10 days, the operations plan must consider whether safety stock will prevent stockouts. If inventory drops below ROP earlier than expected, the project becomes a service risk.

6) Scheduling Operational Work During Project Implementation

A classic exam prompt asks: “How should operations be managed during a project implementation to reduce disruption?” Typical elements:

• Phased rollout: implement in stages to reduce operational risk
• Parallel runs: test new process while maintaining old process until stability
• Buffer resources: add overtime shifts or temporary staff
• Maintenance windows: schedule shutdowns during off-peak periods
• Stakeholder communication: ensure operations teams understand changes

Case-style example

A textile company upgrades dyeing machines. The dyeing department runs continuously. If the project requires machine downtime for calibration, the project manager might:

• schedule calibration overnight
• use alternate machine capacity for short periods
• prioritize production orders to reduce late deliveries

The exam expects you to show logical linkage between project actions (downtime schedules) and operational outcomes (delivery reliability, throughput).

DUT OPMT301: Project Management Fundamentals (Scope, Time, Cost, and Integration)

Project management is not separate from operations—it organizes work to produce defined outcomes under constraints. OPMT301 often tests whether you can apply standard project management processes in a structured way, from initiation to closure, using planning tools and monitoring techniques.

1) What Makes a Project Different from Operational Work?

A project is typically characterized as:

• Unique: not repetitive routine
• Temporary: has a defined start and end
• Has constraints: scope, time, cost, quality, and resources
• Requires coordination: multiple disciplines and stakeholders

Operations management is ongoing. Projects create changes: new processes, new assets, new systems, improved service levels.

Exam answer framework

When asked to differentiate:

• Projects aim for transformation (deliverable creation/transition).
• Operations aim for stable ongoing transformation (service/product delivery).

Example: introducing a new ERP system is a project; using the ERP system afterward is operations.

2) Project Life Cycle: Initiation to Closure

A coherent project life cycle typically includes:

1. Initiation: define purpose, feasibility, stakeholders, authorization
2. Planning: scope definition, WBS, schedule, budget, risk plan, quality plan
3. Execution: resource allocation, deliverables development, change management
4. Monitoring & Control: track progress, performance measurement, corrective actions
5. Closing: acceptance, handover, lessons learned, final reports

Exam tip: connect life cycle to key documents

• Initiation: business case, project charter (or equivalent)
• Planning: scope statement, WBS, schedule baseline, cost baseline
• Execution: resource assignments, procurement plan, communication plan
• Monitoring/control: status reports, variance analysis, change requests
• Closing: acceptance sign-off, final lessons learned

3) The Triple Constraint and “Hidden” Constraints

The triple constraint—scope, time, cost—is central. Yet many exam questions reward mentioning “hidden constraints”:

• quality requirements
• risk tolerance
• compliance standards
• stakeholder expectations
• procurement constraints
• resource availability (skills, equipment)

Key reasoning

If the project manager compresses time, scope may reduce or cost may increase. If quality standards are increased, cost usually rises or time expands.

4) Scope Management: Requirements to Deliverables

Scope is what the project includes (and excludes). Scope management includes:

• collecting requirements
• defining scope
• creating WBS
• validating deliverables
• controlling scope changes

WBS: The Backbone of Planning

A Work Breakdown Structure (WBS) decomposes the project deliverables into smaller manageable work packages.

A good exam answer explains:

• WBS supports scheduling and costing
• WBS improves clarity and accountability
• Work packages become inputs to risk, quality, and procurement planning

Example WBS mini-structure: “Implement a clinic appointment system”

1. System selection and procurement
   • vendor evaluation
   • contract and procurement
2. Data preparation
   • migrate patient records
   • data cleansing
3. Configuration and integration
   • configure appointment rules
   • integrate with billing
4. Testing and training
   • user acceptance testing
   • training sessions
5. Rollout and changeover
   • go-live planning
   • parallel run support
6. Handover
   • documentation
   • support transition

In an exam, you might be asked to identify the WBS level appropriate for a given task. For instance, “train reception staff” is a work package under testing/training.

5) Time Management: Activities, Sequencing, and Critical Path

Time management includes:

• defining activities
• sequencing
• estimating durations
• developing schedule
• controlling schedule

A typical scheduling approach uses the critical path method (CPM), where the sequence of activities with zero float determines project duration.

Exam-friendly critical path description

• Assign durations to activities
• Determine logical dependencies (what must happen first)
• Identify longest path through the network diagram
• Critical activities affect overall end date directly

Simple network example (conceptual)

If:

• A → B → D totals 12 weeks
• A → C → E totals 10 weeks
• then the critical path is A → B → D (12 weeks), unless constraints change.

6) Cost Management: Estimation and Budget Baselines

Cost management focuses on:

• estimating costs (labor, materials, equipment, overhead)
• determining budget (baseline)
• controlling costs (track variance)

A project budget often includes:

• direct costs: labor, materials, equipment
• indirect costs: project management overhead, facilities
• contingency reserves (for identified/unknown risks)

Variance and performance measurement

You may see exam questions requiring explanation of:

• cost variance (actual cost vs planned cost)
• schedule variance (actual time vs planned time)
• causes of variance and corrective actions

7) Project Integration Management: Coordinating Change

Integration management is the “glue”:

• develop project charter
• develop project management plan
• manage execution
• monitor & control
• manage changes across all knowledge areas

Change is inevitable. Exam answers should show how changes are handled through:

1. change request
2. impact assessment (scope/time/cost/quality/risk)
3. approvals
4. updates to baselines
5. communication and implementation

Example: change request in manufacturing project

A project to install a new production line includes production trials. A stakeholder asks to add an additional quality inspection station. The PM should assess:

• added cost (additional equipment + installation)
• schedule impact (delays commissioning)
• integration risks (software/hardware compatibility)
• quality benefits (reduced defect rate)

DUT OPMT301: Scheduling, Monitoring, Risk, and Quality Control in Projects

Operations constraints and project planning are not enough; the project must be monitored and adjusted. OPMT301 exam questions often test your ability to use tools like risk registers, monitoring dashboards, corrective actions, and quality control plans—especially how they connect to project deliverables and operational continuity.

1) Monitoring and Control: Measuring Performance

Monitoring and control compares planned results (baselines) against actual performance. Core monitoring outputs typically include:

• status of deliverables
• schedule progress (percent complete)
• cost progress
• risk status updates
• quality findings (defects, audit results)
• procurement progress

Exam-style performance reporting

A strong answer often includes:

• What is on track?
• What is off track?
• Why is it off track?
• What actions are being taken?
• What decisions are required from stakeholders?

Example: monthly project status report for a “warehouse layout redesign”

Planned: finalize new layout drawings by 15 June; complete installation by 30 July.
Actual: drawings finalized 22 June; installation started 5 August due to delayed shelving deliveries.

Monitoring should highlight:

• schedule variance (7 days delay drawings)
• cause (procurement lead time)
• impact (installation start delayed)
• mitigation (expedite delivery, adjust sequence)

2) Earned Value Concepts (Where Taught) and Variance Reasoning

Some DUT curricula cover Earned Value Management (EVM) basics. Even when not formally examined, the logic—planned vs earned vs actual—helps structure cost and schedule analysis.

Use a clear vocabulary:

• Planned Value (PV): what you planned to accomplish by a time
• Earned Value (EV): what you actually accomplished by the time, measured in terms of budget
• Actual Cost (AC): what you actually spent

If EV < PV, the project is behind schedule (in value terms). If EV < AC, project is over budget (in cost terms).

Example logic (educational)

If by week 6:

• PV = R 600 000 (planned work)
• EV = R 540 000 (earned work)
• AC = R 570 000 (actual cost)

Then:

• schedule performance: EV/PV = 0.9 (behind)
• cost performance: EV/AC ≈ 0.947 (over budget slightly)

Even if your exam doesn’t require formulas, using this reasoning earns marks.

3) Risk Management: Risk Identification to Response Planning

Risk management is often assessed through:

• identification (what could go wrong)
• analysis (likelihood vs impact)
• response planning (avoid, mitigate, transfer, accept)
• monitoring (track triggers)

A risk register typically includes:

• risk description
• category (technical, schedule, cost, procurement, safety, external)
• likelihood rating
• impact rating
• risk score
• response strategy
• owner
• contingency plan and trigger

Example risk register entry (warehouse automation project)

• Risk: delayed delivery of conveyor parts
• Category: procurement/supply chain
• Likelihood: Medium
• Impact: High
• Response: mitigation by dual sourcing and expediting; contingency buffer days
• Trigger: supplier updates indicate delivery shift > 5 working days
• Owner: procurement manager

4) Likelihood-Impact Matrices and Ranking Risks

Exams may ask you to justify why one risk is prioritized over another.

A common approach:

• Rate likelihood (e.g., Low/Medium/High)
• Rate impact (e.g., Low/Medium/High)
• Multiply or assign a scoring rule to rank risks

How to write a high-scoring justification

For each top risk, explain:

• Why likelihood and impact are high
• How the risk affects critical path activities
• Why the selected response matches the risk nature

5) Managing Uncertainty: Contingency vs Management Reserve

Two terms appear commonly:

• Contingency reserve: funds/time to handle risks that are specifically identified
• Management reserve: funds for unknowns, or general uncertainties not yet identified in detail

Exam answers should clarify that contingency is tied to risk responses; management reserve is for broader executive discretion.

6) Quality Planning in Projects: Defining What “Acceptable” Means

Project quality management includes:

• quality planning
• quality assurance
• quality control

Quality assurance vs quality control (important differentiation)

• Quality assurance: process-oriented; ensures the project will produce deliverables that meet requirements (e.g., audits, standards, training).
• Quality control: product/service testing/inspection; checks deliverables against standards.

Example: water pump installation project

Quality assurance actions:

• ensure installation procedures follow standard operating procedures
• verify contractor competence
• inspect materials traceability process

Quality control actions:

• pressure testing after installation
• check performance against spec (flow rate, pressure limits)
• record results and obtain sign-off

7) Change Control: Protecting Scope, Time, Cost, and Quality

Change control prevents uncontrolled scope expansion and schedule chaos. An exam question might ask: “What steps should be followed to manage change?”

A standard process:

1. submit change request (what/why/impact)
2. review request (feasibility, alignment with objectives)
3. impact assessment (time/cost/quality/risk)
4. decision/approval (change/no change/revise)
5. implement approved changes
6. update baselines and communicate

Counter-argument to include in exams

Sometimes an exam asks you whether rigid change control can hinder responsiveness. A balanced answer:

• Rigid control can slow urgent improvements.
• However, without control, unplanned changes cause cost overruns and rework.
• The solution is to implement fast-track change procedures for low-impact changes while still requiring assessment.

8) Communication Management: Who Needs What, When?

Communication is integral to risk control and operational continuity. Projects typically require:

• stakeholder register
• communication plan (frequency and channels)
• meeting cadence (steering committee, project team)
• escalation paths

Example communication plan snippet

• Daily: site coordination meeting (field team)
• Weekly: progress meeting (PM + functional leads)
• Bi-weekly: steering committee update (management)
• Monthly: financial review and risk review

In exams, you should mention that communication is part of “control” because it surfaces issues early.

DUT OPMT301: Integrating Operations Strategy with Project Delivery (Supply Chain, Lean, and Process Improvement)

Many OPMT301 questions blend operations strategy with project delivery, asking how to improve performance and sustainability of outcomes. This section focuses on how project management techniques support operational improvement initiatives like lean transformations, supply chain reliability, and process redesign.

1) Operations Strategy and How Projects Implement Strategy

Operations strategy describes how an organization competes through operations. Common strategic dimensions:

• cost leadership (efficiency)
• differentiation (quality, flexibility)
• speed (short lead times)
• reliability (consistent delivery)
• sustainability and compliance

Projects can be used to implement these strategies by:

• upgrading capacity
• improving process flow
• reducing defects and rework
• implementing digital systems
• changing supply chain relationships

Example

If a company’s operations strategy is “reduce lead time from 10 days to 6 days,” then projects must deliver changes that actually remove lead time components, such as:

• shorter procurement lead times
• reduced waiting between stages
• faster approvals and testing
• improved dispatch scheduling

2) Lean Thinking in Projects: Eliminating Waste and Improving Flow

Lean thinking focuses on value to the customer and systematic elimination of waste. In a project context, lean principles show up as:

• mapping current processes (value stream mapping)
• identifying waste (waiting, overprocessing, defects, unnecessary motion, excess inventory)
• designing a future-state with improved flow

Waste categories you can mention in exams

• Overproduction
• Waiting
• Transportation
• Inventory
• Motion
• Overprocessing
• Defects

Mini case study: “Factory layout change”

A manufacturing plant experiences long delays in material movement between cutting and assembly.

Project deliverables might include:

• redesigned layout
• new material handling equipment
• updated work instructions

Operational impact goals:

• reduce transportation time
• reduce waiting
• reduce work-in-progress inventory

A strong exam answer includes both:

• project plan components (deliverables and schedule)
• operations improvements (flow and waste reduction)

3) Process Improvement Life Cycle: From Problem to Control

Operational improvement projects often follow cycles similar to:

• Diagnose (root causes)
• Design (new process)
• Implement (changeover + training)
• Control (monitoring and standardization)

A common exam mapping uses DMAIC-style logic (especially if taught):

• Define problem and goals
• Measure current performance
• Analyze root causes
• Improve process
• Control with ongoing monitoring

Example with operational metrics

Suppose an enterprise wants to reduce delivery failures from 8% to 3% in 3 months.

Project measurement:

• baseline failure rate
• improved inspection/quality controls
• training improvements
• updated dispatch scheduling

Then control:

• monitor defect rates weekly
• audit adherence to updated SOPs
• track customer complaints

4) Supply Chain and Procurement: Managing Dependencies

Projects depend on procurement for materials and services. Operationally, procurement performance affects lead time and availability.

Typical procurement planning tasks:

• supplier selection and evaluation
• contracting approach (fixed price, time and materials)
• logistics planning (transport, warehousing)
• quality requirements for purchased items
• acceptance criteria and inspection

Risk intersection: procurement delays

If a project has a critical activity dependent on a supplier lead time, then procurement risks directly affect schedule and operations continuity.

A high-mark exam response explains:

• what the dependency is
• what the risk is
• how to mitigate (dual sourcing, expediting, safety stock, buffer time)
• what contingency triggers action

5) Maintenance Strategies: Preventive vs Corrective in Projects

Operational systems require maintenance. Projects often include equipment installation and transition to operational maintenance.

Maintenance strategy impacts:

• reliability during early operations after project completion
• long-term cost
• safety compliance

Examples

• Preventive maintenance plan: scheduled checks reduce breakdown probability.
• Corrective maintenance plan: respond after failure—often higher cost.

In project planning, teams should:

• define maintenance responsibilities (who maintains)
• train operational staff
• schedule commissioning tests
• document maintenance procedures for handover

6) Technology and Digital Operations: Implementation as a Project Deliverable

Digital transformations are common project themes. Examples:

• ERP systems
• inventory tracking
• production scheduling software
• appointment systems in clinics

Operational outcomes should be measurable:

• reduction in stockouts
• improved order accuracy
• shorter fulfillment times
• improved reporting reliability

Exam advice: include both technical and operational change

A project that installs software must also:

• update operational workflows
• train users
• migrate data
• ensure integration interfaces work (APIs, data formats)

7) Sustainability and Compliance in Operational Projects

In South African contexts, compliance considerations often appear (though specifics depend on course emphasis). Projects in industry must account for:

• environmental impact measures
• safety and health compliance
• waste management procedures
• audit trails and documentation

Exam answers score higher when you:

• connect compliance to quality and risk
• show how compliance requirements influence schedule (testing, approvals)
• clarify how compliance evidence will be collected and handed over

8) Operational Handover: Closing the Loop Between Project and Operations

A project ends, but operations begins with handover. Operational handover includes:

• documentation (SOPs, manuals, drawings)
• training and competency confirmation
• performance testing and acceptance
• support transition (who to contact post-go-live)
• monitoring period for early-life issues

Example: facility expansion project handover

Project closure deliverables might include:

• as-built drawings
• equipment warranty documentation
• training attendance records
• operational readiness checklist
• final commissioning test report

A strong OPMT301 exam answer states that handover is part of achieving operational success, not just administrative closure.

DUT OPMT301: Exam Practice—How to Answer Common Questions and Solve Quantitative Problems

This section focuses on how OPMT301 exam questions are structured and how to respond effectively. Many candidates lose marks not because they lack knowledge, but because they don’t apply it in the expected format. Use these frameworks to produce consistent, high-quality answers under time pressure.

1) Typical OPMT301 Question Formats

You may encounter:

1. Explain/describe questions
   Example: “Explain the differences between project work and operational work.”
2. Compare and contrast
   Example: “Compare quality assurance and quality control.”
3. Apply concepts to a scenario
   Example: “A project is delayed due to procurement—identify risks and propose mitigation.”
4. Process and tool questions
   Example: “Create a WBS for a given project description.”
5. Quantitative scheduling/capacity
   Example: “Compute reorder point; identify bottleneck capacity; estimate production time.”
6. Risk register and mitigation
   Example: “List risks, rank them, and propose response strategies.”

2) The “Mark-Driven” Answer Structure

A high-scoring response typically includes:

• Definition (1–2 lines)
• Core concept (key points)
• Application (connect to scenario)
• Justification (why it matters, what impact it has)
• Example (brief but relevant)
• Conclusion (1–2 lines)

Example: explain “bottleneck”

• Define bottleneck as resource with lowest effective capacity
• Explain throughput capped by bottleneck
• Link to project scheduling (critical path and lead times)
• Provide numeric mini-example
• Mention mitigation (additional shifts, buffering, parallel steps)

3) Quantitative Mini-Practice Sets (with Consistent Logic)

Mini-set A: Reorder point calculation (inventory)

Given:

• Daily demand = 50 units
• Lead time = 7 days
• Safety stock = 100 units

Reorder point:

• ( 50 \times 7 + 100 = 450 ) units

Exam extension question:

• If inventory falls to 420 units, what should happen?
  Answer:
• It’s below ROP (450), so a new order should be placed immediately or expedited depending on procurement lead time agreement.

Mini-set B: Production time with bottleneck

Given:

• Bottleneck capacity = 45 units/day
• Demand/order size = 900 units

Time required:

• ( 900 \div 45 = 20 ) days

Exam extension:

• If a project requires 20 days production and there’s 2 days planned downtime for maintenance, total schedule time becomes:
• 22 days

(You should explain the assumption clearly: downtime reduces available production days.)

Mini-set C: Schedule reasoning (critical path concept)

If three paths exist through a network:

• Path 1 duration = 12 weeks
• Path 2 duration = 10 weeks
• Path 3 duration = 11 weeks

Critical path is the longest: 12 weeks.
Exam follow-up:

• If an activity on the 12-week path is delayed by 1 week, project duration increases by 1 week (unless float exists, which you must mention).

4) Building a WBS Under Exam Conditions

When asked to create a WBS from a scenario, don’t produce overly detailed lists that consume time. Aim for 3–7 main deliverables with 2–5 work packages each.

Example approach

Scenario: “Install and commission a solar-powered water heating system at a student residence.”

WBS might include:

1. Site assessment and design
   • survey site conditions
   • finalize system design
2. Procurement
   • purchase panels and storage tanks
   • arrange transport/installation tools
3. Installation
   • mount panels
   • install piping and tanks
4. Electrical and plumbing integration
   • install controllers
   • test safety connections
5. Commissioning and handover
   • performance testing
   • user training and documentation

Exams often reward:

• alignment with deliverables
• logical grouping
• clarity that work packages are manageable and assignable

5) Risk Register Writing: How to Earn Marks Quickly

A strong risk register entry includes:

• Risk statement (clear and specific)
• Category
• Likelihood and impact (or qualitative equivalents)
• Response strategy (avoid/mitigate/transfer/accept)
• Owner
• Trigger/contingency

Example template (copy into exams as needed)

• Risk: [short description]
• Category: [schedule/cost/procurement/safety/external]
• Likelihood: [Low/Med/High]
• Impact: [Low/Med/High]
• Response: [Mitigate by…, Transfer…, Avoid…]
• Owner: [role]
• Trigger: [what signals the risk is occurring]
• Contingency: [what to do if trigger happens]

6) Quality Plan Answers: Assurance vs Control

If asked to propose a quality plan, include:

• Standards and criteria (what defines acceptance)
• Assurance actions (process checks)
• Control actions (tests/inspections)
• Records (what evidence will be produced)
• Responsibilities (who signs off)

Example

Quality requirement: “Installed pumps must meet pressure test spec X.”

Quality control:

• pressure test after installation
• record results
• reject and rework if failure

Quality assurance:

• verify installation procedure compliance
• ensure technicians trained on correct procedures
• audit tool calibration status before test

7) Change Control Answers: Provide Steps and Trade-Offs

When asked: “What is change control?” don’t just say “approve changes.” Mention:

• documentation required
• assessment of impact on time/cost/scope/quality
• approvals and update baselines
• communication to stakeholders
• possible fast-tracking of minor changes (balanced view)

Include a counterpoint if required

If the question asks whether strict change control is always beneficial:

• Argue that strict control can slow decisions.
• But without control, rework and cost overruns increase.
• Therefore use differentiated approvals: fast-track low-impact changes, full review for high-impact changes.

8) Common Mistakes That Lose Marks

Avoid these pitfalls:

• Vague answers: always connect to the project/operations scenario.
• No application: definitions alone usually don’t score enough.
• Confusing assurance with control.
• No assumptions in calculations (always state formulas and inputs).
• No linkage to consequences: explain “so what?” (impact on schedule/cost/quality).
• Forgetting operational continuity during project execution.

9) Quick Summary of “What to Include” in a High-Mark Answer

Use this checklist during revision:

• ✅ Definitions and key terms
• ✅ At least one relevant example
• ✅ Correct use of operational/project distinction
• ✅ For scheduling: mention dependencies and bottlenecks
• ✅ For risk: include response strategies and triggers
• ✅ For quality: distinguish assurance vs control
• ✅ For change: mention impact assessment and baselines
• ✅ For quantitative: show steps and units

Cluster Focus: Durban University of Technology (DUT) Project Management Study Material—How This Fits OPMT301

Because this guide belongs to the Durban University of Technology (DUT) Project Management Study Material collection, the emphasis remains aligned with how DUT learners typically approach OPMT301: structured problem-solving, operational realism, and disciplined project control. In exam settings, your marks often depend on how well you:

• link operations constraints (capacity, inventory, quality) to project plans,
• use standard project management logic (WBS, schedule/critical path, baselines),
• demonstrate risk and quality control thinking, not just theory,
• and communicate decisions clearly using stakeholder-aware language.

If you build your exam responses around the frameworks in these notes—define, apply, justify, and conclude—you’ll produce answers that are both technically correct and aligned with typical marking approaches in university assessments.

Final Revision Sheet (Condensed for Last-Minute Review)

• Operations system: inputs → transformation → outputs; projects must respect operational continuity.
• Process types: job shop (custom), batch (groups), mass (standard high volume), continuous (constant flow).
• Capacity & bottlenecks: system throughput constrained by lowest effective capacity.
• Inventory & lead times: projects affect stock availability; use reorder points and safety stock logic.
• Quality: prevention vs appraisal vs failure costs; assurance vs control.
• Project basics: unique, temporary, constrained; triple constraint scope-time-cost plus quality and risk.
• Life cycle: initiation → planning → execution → monitoring/control → closing.
• WBS: decomposes deliverables into manageable work packages; supports scheduling and costing.
• Scheduling: sequencing + durations + critical path logic; float considerations.
• Monitoring/control: compare baselines vs actuals; explain variance causes and corrective actions.
• Risk management: risk register with likelihood/impact, response strategy, owner, triggers, contingency.
• Change control: document → assess impacts → approve → update baselines → communicate.
• Lean/process improvement: map current flow, remove waste, implement and control with ongoing monitoring.
• Handover: documentation + training + commissioning evidence + operational readiness.

These are the core moves that usually separate a good OPMT301 exam answer from an average one.