Lesson outcomes

After completing this lesson, learners should be able to:

• Explain the fundamental principles of project management.
• Define project objectives, scope, deliverables and constraints.
• Schedule resources to achieve objectives on time and within budget.
• Use Gantt charts, PERT and the Critical Path Method.
• Apply project-management methods to customer order activities.
• Monitor and control variations between planned and actual performance.

1. Understanding project management

Project management is a structured approach to planning, executing, monitoring and completing a temporary set of activities intended to achieve defined objectives.

A project normally has:

• A clear objective
• Defined starting and completion dates
• Specific deliverables
• An approved budget
• Allocated resources
• Identified stakeholders
• Measurable quality requirements
• Associated risks and constraints

Supply-chain projects may include:

• Introducing a warehouse-management system
• Relocating a distribution centre
• Implementing a new supplier contract
• Completing a large customer order
• Redesigning a transport network
• Launching a new product
• Conducting an inventory-reduction programme

2. Project objectives

Project objectives describe what the project must achieve. Effective objectives should be:

• Specific
• Measurable
• Achievable
• Relevant
• Time-bound

For example:

Deliver and install 200 units at the customer’s Gauteng sites by 30 November, within the approved budget and agreed quality standards.

Clear objectives guide planning, resource allocation, performance measurement and decision-making.

3. Project scope

The scope defines what is included and excluded from the project.

A scope statement may specify:

• Required outputs
• Work to be completed
• Delivery locations
• Product quantities
• Quality requirements
• Responsibilities
• Assumptions
• Constraints
• Exclusions
• Acceptance criteria

Uncontrolled additions to the project are known as scope creep. Scope changes can increase costs, extend deadlines and place pressure on resources.

4. Project constraints

Projects require a balance between several connected constraints.

             Scope
            /     \
           /       \
        Time ———— Cost
             |
           Quality

A change to one constraint may affect the others. For example, shortening a delivery deadline may require additional vehicles or overtime, which increases cost.

Other constraints may include:

• Resource availability
• Supplier capacity
• Regulatory requirements
• Technology
• Operational risk
• Customer expectations

5. Project lifecycle

A typical project progresses through five stages:

1. Initiation: Confirm the requirement, purpose and feasibility.
2. Planning: Define scope, tasks, schedule, resources, budget and risks.
3. Execution: Perform the planned work and produce deliverables.
4. Monitoring and control: Compare actual results with the plan and manage deviations.
5. Closure: Confirm acceptance, close commitments and record lessons learned.

6. Work Breakdown Structure

A Work Breakdown Structure (WBS) divides a project into smaller, manageable units of work.

For a customer order, the WBS could include:

Customer order project
├── Confirm requirements
├── Check inventory
├── Procure shortages
├── Prepare products
├── Conduct quality checks
├── Package the order
├── Arrange transport
├── Deliver and install
└── Obtain customer acceptance

Breaking the project into tasks makes it easier to:

• Estimate time and cost
• Allocate responsibilities
• Identify dependencies
• Schedule resources
• Monitor progress

7. Task sequencing and dependencies

Tasks must be placed in a logical order.

Common dependencies include:

• Finish-to-start: One task must finish before another begins.
• Start-to-start: Two activities may begin together.
• Finish-to-finish: Two activities must be completed together.
• External dependency: Progress depends on a customer, supplier or authority.

For example, goods cannot be dispatched until picking, packing and quality checks have been completed.

8. Resource scheduling

Resource scheduling determines when people, equipment, materials and funds are required.

Resources may include:

• Employees and specialist skills
• Inventory and materials
• Vehicles
• Warehouse space
• Handling equipment
• Technology
• Suppliers and contractors
• Financial resources

Effective scheduling requires the project manager to:

1. Identify the activities.
2. Estimate the duration of each activity.
3. Determine the required resources.
4. Check resource availability.
5. Allocate resources to activities.
6. Resolve conflicts and shortages.
7. Monitor actual utilisation.

Resource levelling

Resource levelling adjusts the schedule when the demand for a resource exceeds its availability.

For example, if one vehicle is required for two deliveries at the same time, the organisation may:

• Reschedule one delivery.
• Use another vehicle.
• Appoint a transport provider.
• Split the load.
• Change the delivery sequence.

9. Project budget

A project budget may include:

• Materials
• Labour
• Transport
• Equipment
• Technology
• Supplier services
• Storage
• Insurance
• Contingency allowance

Actual expenditure should be compared with the approved budget throughout the project.

A cost variance may be calculated as:

Cost variance = Budgeted cost − Actual cost

If the budget is R500,000 and actual cost is R530,000:

Cost variance = R500,000 − R530,000 = −R30,000

The negative result indicates that the project is R30,000 over budget.

10. Gantt charts

A Gantt chart shows project activities against time. It can display:

• Activity start and finish dates
• Task duration
• Overlapping activities
• Milestones
• Dependencies
• Progress

Gantt charts make the schedule easy to communicate, but complex dependencies may require more detailed network-planning tools.

11. PERT charts

The Programme Evaluation and Review Technique (PERT) represents project activities and their relationships in a network.

PERT is useful when activity durations are uncertain. It may use three time estimates:

• Optimistic time (O): Shortest reasonable duration
• Most likely time (M): Expected duration under normal conditions
• Pessimistic time (P): Longest reasonable duration

Expected duration can be calculated as:

Expected time = (O + 4M + P) ÷ 6

If an activity has:

• Optimistic time: 2 days
• Most likely time: 5 days
• Pessimistic time: 8 days

Then:

Expected time = (2 + 4(5) + 8) ÷ 6 = 5 days

12. Critical Path Method

The Critical Path Method (CPM) identifies the longest sequence of dependent activities required to complete the project.

Activities on the critical path have no available scheduling flexibility. A delay in one of these activities normally delays the entire project.

Example:

A: Confirm order — 1 day
        ↓
B: Procure stock — 5 days
        ↓
C: Prepare order — 2 days
        ↓
D: Inspect order — 1 day
        ↓
E: Deliver order — 2 days

Critical-path duration: 11 days

The critical path helps managers focus attention and resources on activities that directly affect the completion date.

13. Project risks

Supply-chain project risks may include:

• Supplier delays
• Inventory shortages
• Vehicle breakdowns
• Port or border delays
• Poor-quality products
• Inaccurate customer information
• Labour shortages
• System failures
• Infrastructure disruptions
• Exchange-rate changes
• Budget overruns
• Scope changes

A risk register should record:

• Risk description
• Likelihood
• Impact
• Risk rating
• Preventive controls
• Contingency action
• Responsible person
• Review date

14. Stakeholder management

Project stakeholders may include:

• Customer
• Project sponsor
• Project manager
• Sales
• Procurement
• Warehouse
• Production
• Transport
• Finance
• Suppliers and contractors

A communication plan should specify:

• Information required
• Report format
• Frequency
• Responsible person
• Recipients
• Escalation procedures

15. Quality control

Quality requirements should be included in the project plan and monitored throughout execution.

Controls may include:

• Approved specifications
• Inspection checklists
• Product testing
• Supplier quality checks
• Packaging standards
• Delivery verification
• Customer acceptance
• Corrective-action procedures

Quality should be built into the process rather than checked only at the end.

16. Applying project management to order management

A project-management approach is particularly useful for:

• Large customer orders
• Complex or customised products
• Orders involving several locations
• Export or import orders
• Projects requiring installation
• Orders involving several suppliers
• Time-sensitive customer requirements

Order-management project flow

Confirm order and scope
        ↓
Break work into activities
        ↓
Sequence and schedule activities
        ↓
Allocate resources and budget
        ↓
Execute procurement, production and fulfilment
        ↓
Monitor time, cost, quality and risks
        ↓
Deliver and obtain customer acceptance
        ↓
Close and review the order

Each order should have defined:

• Customer requirements
• Quantities and specifications
• Required delivery date
• Milestones
• Responsible persons
• Inventory and procurement requirements
• Production and warehouse activities
• Transport arrangements
• Quality controls
• Communication requirements

17. Monitoring project performance

Actual performance should be compared with the project baseline.

Performance can be monitored using:

• Progress reports
• Milestone reviews
• Gantt-chart updates
• Budget reports
• Risk registers
• Quality results
• Customer feedback
• Exception reports

18. Managing variations

A variation is a difference between the project plan and actual performance.

Variations may result from:

• Incorrect planning assumptions
• Changes in customer requirements
• Supplier delays
• Resource shortages
• Unexpected costs
• Quality failures
• Operational disruptions

A controlled response should:

1. Identify the variation.
2. Measure its effect on scope, time, cost and quality.
3. Determine the root cause.
4. Develop possible corrective actions.
5. Obtain required approval.
6. Update the project plan.
7. Communicate the change.
8. Monitor the result.

Changes should not be implemented informally where they affect approved scope, cost or completion dates.

19. Project closure

A project or major customer order should be formally closed by:

• Confirming completion of deliverables
• Obtaining customer acceptance
• Closing orders and supplier commitments
• Completing final payments
• Returning unused resources
• Resolving outstanding issues
• Archiving records
• Reviewing actual performance
• Documenting lessons learned

Lessons learned should be used to improve future supply-chain projects and customer-order processes.

Lesson Summary

Project management provides a structured method for completing supply-chain activities within defined scope, time, cost and quality requirements. A Work Breakdown Structure divides the work into manageable tasks, while Gantt charts, PERT and the Critical Path Method support sequencing and scheduling. Effective resource allocation, risk management, stakeholder communication and quality control help keep projects on track. Applying these principles to complex customer orders improves coordination, accountability and delivery performance. Variations must be measured, authorised and controlled, and each project should conclude with formal acceptance and a review of lessons learned.