Skip to main content
CBE NEXUS · GLOBAL HIGHER EDUCATION

Chapter 5: Time Management, Critical Path and Resource Planning

Undergraduate Bachelor of Project Management · Year 2 · Full study notes, applied methods and assessment guide

Chapter overview

This chapter develops undergraduate-level understanding of time management, critical path and resource planning. It combines conceptual explanations, practical methods, decision frameworks, worked examples and applied cases. Students should connect each method to project context, governance, people, evidence and measurable outcomes rather than treating tools as isolated templates.

Learning outcomes: explain the chapter's key terminology; apply relevant methods to a realistic project; interpret evidence and assumptions; evaluate limitations and risks; communicate a defensible recommendation; and connect project outputs with stakeholder needs and intended benefits.

Concept map: Time Management, Critical Path and Resource Planning

Project contextNeed and objectivesAnalysisEvidence and optionsDecisionAuthority and actionControlMeasure and learn

This diagram is a learning aid. Apply the sequence to the chapter topics and identify the feedback loops needed when assumptions or conditions change.

Chapter contents

1. Time management in project delivery2. Time, effort and duration3. Critical path and near-critical paths4. Resource planning5. Resource breakdown structure6. Resource calendars and working time7. Resource allocation and responsibility8. Resource levelling worked example9. Time management methods10. Critical chain and buffers11. Earned value management introduction12. Worked earned value example13. Forecasting final cost and completion14. Time-cost trade-offs15. Managing delays and recovery16. Capacity planning and bottlenecks17. Team productivity and wellbeing18. Case study: regional road rehabilitationAssessment questions

1. Time management in project delivery

Time management combines schedule development, personal and team work planning, prioritisation, coordination and control. The project schedule shows the integrated plan; short-term look-ahead plans translate it into actionable work. A team may have a credible master schedule yet still lose time through unclear daily priorities, late decisions, incomplete materials or unresolved access. Effective time management connects strategic milestones with weekly commitments and daily coordination. It also protects time for quality checks, safety briefings, stakeholder decisions and learning rather than treating every non-production activity as waste.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

2. Time, effort and duration

Effort is the amount of labour required, commonly expressed in person-hours or person-days. Duration is the elapsed time between start and finish. A task requiring 40 person-hours may take one person five eight-hour days, or two people about 2.5 days only if work can be divided efficiently and there is sufficient space, equipment and coordination. Adding people can increase communication overhead and may not shorten tasks with sequential or specialist dependencies. Estimates should distinguish effort, duration, waiting time and calendar time.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

3. Critical path and near-critical paths

The critical path determines the earliest completion date under the network logic. Near-critical paths have little float and can become critical after modest delay. Managers should monitor both. Focus on activities that drive the completion date, but do not ignore non-critical work whose delay could affect safety, quality, benefits or contractual obligations. Criticality can change as actual durations and dependencies evolve. Recalculate the network after significant changes rather than relying on an old diagram.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

4. Resource planning

Resource planning identifies the skills, labour, equipment, materials, facilities, information and funding required to perform the work. Start with the WBS and activity estimates, then aggregate demand by time period. Identify scarce skills and long-lead resources early. Resource plans should consider competence, supervision, shift patterns, fatigue, travel, accessibility and local labour conditions. For equipment, include mobilisation, setup, maintenance, breakdown contingency and demobilisation. For materials, consider storage, quality certification, delivery sequencing and waste.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

5. Resource breakdown structure

A resource breakdown structure organises resources by category and type, such as project management, design specialists, construction labour, plant, materials, software and facilities. It supports estimating, procurement and reporting. The structure should align with the WBS where useful so that resource costs and responsibilities can be traced to deliverables. Avoid counting the same resource twice across work packages. Resource codes should be consistent with finance and procurement systems.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

6. Resource calendars and working time

Resource calendars define availability and constraints. A standard workday may not apply to all teams: site crews, customer support, specialist consultants and suppliers may use different calendars. Public holidays, religious observances, weather, planned maintenance, training and statutory working-time requirements can affect availability. A realistic schedule respects legal limits and fatigue management. Overtime may be appropriate for a short, controlled recovery effort, but sustained overtime can increase errors, incidents, absence and staff turnover.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

7. Resource allocation and responsibility

Resource allocation assigns named roles or resource types to activities and clarifies expected effort, timing and authority. A responsibility assignment matrix such as RACI identifies who is Responsible, Accountable, Consulted and Informed. One role should normally be accountable for a decision or deliverable to avoid ambiguity. RACI does not replace job descriptions, contracts or statutory accountability. Confirm that assigned people have the competence and capacity to perform the work.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

8. Resource levelling worked example

Suppose a project has one safety inspector available for 5 days per week. Two inspections, each requiring 3 days, are scheduled in parallel during the same week. The plan demands 6 inspector-days but only 5 are available. Options include moving one inspection using available float, obtaining a qualified second inspector, splitting the inspection if technically acceptable or changing the sequence. The manager must verify that the solution does not violate hold points or safety requirements. Simply assigning the same inspector to both activities creates an impossible plan.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

9. Time management methods

Time blocking allocates protected periods to important work. Prioritisation ranks tasks by value, urgency, dependency and risk. Look-ahead planning identifies constraints that could prevent work in the next few weeks. Daily coordination aligns teams on immediate tasks, access and safety. Kanban boards visualise work in progress and bottlenecks. These methods support the project schedule; they do not replace integrated dependency analysis. Select a method that fits team size, work type and information needs.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

10. Critical chain and buffers

Critical chain scheduling considers both task dependencies and resource constraints. It identifies a chain of activities that accounts for resource availability and uses buffers to protect completion from variation. A project buffer protects the final delivery date; feeding buffers protect the critical chain from delays on non-critical paths. Buffer consumption is monitored to trigger action. The approach can improve focus but depends on credible estimates, realistic resource commitments and disciplined management of multitasking.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

11. Earned value management introduction

Earned value management (EVM) integrates scope, schedule and cost performance. Planned Value (PV) is the budgeted value of work scheduled by a status date. Earned Value (EV) is the budgeted value of work actually completed. Actual Cost (AC) is the cost incurred for that work. Schedule Variance SV = EV − PV; Cost Variance CV = EV − AC. Schedule Performance Index SPI = EV/PV; Cost Performance Index CPI = EV/AC. Interpret these measures alongside schedule forecasts and quality evidence.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

12. Worked earned value example

Assume PV is 50,000, EV is 40,000 and AC is 45,000 at the reporting date. SV = 40,000 − 50,000 = −10,000, indicating less budgeted work has been completed than planned. CV = 40,000 − 45,000 = −5,000, indicating the completed work cost more than its budgeted value. SPI = 40,000/50,000 = 0.80; CPI = 40,000/45,000 ≈ 0.89. The figures suggest schedule and cost inefficiency. They do not identify the cause, so the manager should investigate productivity, rework, price changes and measurement quality.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

13. Forecasting final cost and completion

Estimate at Completion (EAC) can be calculated in different ways depending on assumptions. If current cost efficiency is expected to continue, EAC = BAC/CPI, where BAC is Budget at Completion. If the remaining work is expected to follow the original plan, EAC may be AC + (BAC − EV). Estimate to Complete (ETC) is the expected cost of remaining work; Variance at Completion (VAC) = BAC − EAC. State the chosen formula and rationale. A single index should not be extrapolated blindly when the project has experienced a one-off event.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

14. Time-cost trade-offs

Time-cost analysis compares the additional cost of shortening an activity with the value or necessity of earlier completion. Direct costs may include extra crews, overtime, expedited transport or premium equipment. Indirect costs may include site overheads, financing, supervision and delay damages. The cheapest schedule is not always the shortest. Crashing decisions should target critical activities and be recalculated after each change because another path may become critical. Consider whether acceleration increases defects, safety exposure or downstream operational disruption.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

15. Managing delays and recovery

When delay occurs, establish the facts: affected activities, cause, start date, responsibility, impact on the critical path, available float and contractual notice requirements. Develop recovery options such as resequencing, alternative suppliers, additional shifts, design resolution, partial handover or approved scope changes. Document assumptions and obtain required approvals. Do not promise an accelerated completion date before confirming resources and dependencies. A recovery plan should include monitoring triggers and a fallback if the intervention fails.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

16. Capacity planning and bottlenecks

A bottleneck is a resource or process stage whose limited capacity constrains overall throughput. Identify bottlenecks through queue length, utilisation, waiting time, work-in-progress and cycle time. Increasing capacity elsewhere may simply create larger queues before the bottleneck. Improve flow by protecting bottleneck availability, reducing setup time, resolving quality defects upstream and ensuring that inputs arrive when needed. Capacity planning should account for variability, not just average demand.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

17. Team productivity and wellbeing

Productivity is influenced by competence, tools, information quality, work environment, motivation, workload, coordination and leadership. Excessive multitasking creates context-switching costs. Unrealistic targets can encourage shortcuts and unsafe behaviour. Managers should plan breaks, reasonable workloads, training, accessible facilities and clear escalation routes. Monitor indicators such as rework, absenteeism, safety observations and staff feedback, while respecting privacy. Sustainable performance is more reliable than short bursts of overwork.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

18. Case study: regional road rehabilitation

A road rehabilitation project must coordinate survey, traffic management, material supply, drainage, earthworks, pavement layers, testing and reopening. Weather and traffic volumes constrain working windows. A quarry delivery bottleneck may limit paving even when crews and equipment are available. Resource planning should align plant, skilled operators, laboratory technicians, traffic marshals and materials. A look-ahead plan identifies permits, utility relocations and test results needed before each workfront begins. Schedule updates should show both physical progress and road-user impacts.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

Additional applied study: Look-ahead planning and constraint removal

A look-ahead plan examines upcoming work over a short horizon, often several weeks, and tests whether each activity is ready to start. Typical constraints include incomplete design information, permits, materials, labour, equipment, access, predecessor work, safety controls and stakeholder decisions. Assign an owner and due date to each constraint. A task should be treated as ready only when its prerequisites are satisfied. This approach reduces idle time and prevents teams from mobilising to work fronts that cannot proceed. Review the plan frequently and escalate constraints that exceed the authority of the workstream lead.

For assessment, support your analysis with a clear project example, state the assumptions used and explain how the team would record, communicate and review the decision. Strong answers distinguish a method's intended benefit from its limitations and show how it connects to the approved project objectives.

Additional applied study: Time management across multiple projects

People assigned to several projects face competing priorities and frequent context switching. Portfolio or programme leaders should make priority decisions explicit, limit excessive work in progress and reserve capacity for urgent operational issues. A resource manager should not assume that a person can deliver 100% of nominal hours across unrelated assignments because meetings, coordination, learning and unplanned support consume time. Use capacity forecasts and discuss trade-offs with sponsors. If every project is labelled urgent, the organisation has not made a prioritisation decision and delivery performance will suffer.

For assessment, support your analysis with a clear project example, state the assumptions used and explain how the team would record, communicate and review the decision. Strong answers distinguish a method's intended benefit from its limitations and show how it connects to the approved project objectives.

Additional applied study: Interpreting performance indicators responsibly

Performance indicators are signals for investigation, not automatic verdicts. A low SPI may reflect delayed measurement, incomplete earned-value rules or genuine schedule slippage. A high utilisation rate can indicate productive use or dangerous overload. A low cost variance can mean efficiency or delayed recording of invoices. Pair quantitative indicators with site observation, user feedback, quality results and risk information. Check definitions, data freshness and possible incentives to manipulate reporting. A useful dashboard prompts the right conversation and decision; it should not reward teams for improving a metric while harming the project outcome.

For assessment, support your analysis with a clear project example, state the assumptions used and explain how the team would record, communicate and review the decision. Strong answers distinguish a method's intended benefit from its limitations and show how it connects to the approved project objectives.

University examination and revision questions

Attempt each question using definitions, explanation, evidence, examples and evaluation. Where a question asks for application, state your assumptions and show how the method would be used in a real project.

Question 1: Define the central concept in this chapter and explain why it matters.

Model answer: A strong answer defines the concept precisely, identifies its purpose, explains its relationship with other project controls and gives a practical example. It should distinguish the concept from related terms and state the consequences of applying it poorly.

Question 2: Explain how the chapter's methods support project decision-making.

Model answer: The methods organise evidence, clarify assumptions, expose dependencies and make trade-offs visible. They support decisions when their inputs are reliable, their limitations are understood and the decision is made by an authorised person.

Question 3: Discuss three common implementation challenges and suitable responses.

Model answer: Typical challenges include incomplete information, competing stakeholder priorities and limited resources. Responses include early engagement, transparent prioritisation, realistic estimates, explicit ownership, risk review and controlled change.

Question 4: Apply the chapter to a public-sector or organisational project.

Model answer: Begin with the need and intended beneficiaries. Define the deliverables, constraints and stakeholders; select relevant tools; identify risks and controls; explain how progress will be measured; and state how the output will be accepted and sustained.

Question 5: Evaluate why professional judgement remains necessary when using project tools.

Model answer: Tools simplify complex conditions and depend on assumptions. Professional judgement is required to interpret evidence, identify bias, assess context, understand ethical consequences and decide when specialist advice or escalation is necessary.

Chapter summary

This chapter develops undergraduate-level understanding of time management, critical path and resource planning. It combines conceptual explanations, practical methods, decision frameworks, worked examples and applied cases. Students should connect each method to project context, governance, people, evidence and measurable outcomes rather than treating tools as isolated templates. The central lesson is to use project management methods as connected decision aids. Maintain clear ownership, test assumptions, communicate honestly, involve affected stakeholders and review evidence as the project evolves. A sound method is only valuable when it improves decisions and contributes to a result that can be accepted, operated and sustained.

Official Education References

Use these official organisations for curriculum guidance, examinations and further learning information.