Skip to main content
CBE NEXUS · GLOBAL HIGHER EDUCATION

Chapter 4: Work Breakdown Structures and Project Scheduling

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

Chapter overview

This chapter develops undergraduate-level understanding of work breakdown structures and project scheduling. 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: Work Breakdown Structures and Project Scheduling

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. Schedule management foundations2. From WBS to activities3. Activity sequencing and dependencies4. Network diagrams5. Duration estimating6. Three-point estimating and PERT7. Critical path method8. Worked critical path example9. Float and schedule flexibility10. Milestones and baselines11. Resource calendars and capacity12. Resource levelling and smoothing13. Leads, lags and fast tracking14. Schedule compression decision15. Schedule risk and contingency16. Progress measurement and forecasting17. Schedule control and change18. Case study: school construction scheduleAssessment questions

1. Schedule management foundations

A project schedule represents activities, durations, logical relationships, resources, milestones and calendar constraints. It translates scope into a time-based delivery model. A credible schedule helps the team understand when work can begin, what must happen first, where resources are needed and which events threaten completion. It is not simply a list of dates. The schedule should be built from the approved scope and WBS, with assumptions and constraints stated. It should be detailed enough to control near-term work and provide a meaningful view of later phases.

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. From WBS to activities

The WBS identifies deliverable components; activity definition identifies the work required to produce them. A work package may be decomposed into survey, design, review, approval, procurement, installation and testing activities. Each activity should have a clear description, owner, expected output and measurable completion condition. Avoid activities that are too broad to estimate or too small to manage. Activity lists should be checked against scope to ensure that all authorised work is represented and no unrelated tasks have been introduced.

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. Activity sequencing and dependencies

Dependencies describe logical relationships between activities. Finish-to-start means the successor begins after the predecessor finishes. Start-to-start means the successor begins after the predecessor starts. Finish-to-finish links completion; start-to-finish is uncommon and used only in special circumstances. Dependencies may be mandatory because of physical or legal requirements, discretionary because of preferred practice, or external because they rely on parties outside the project. Document the reason for important links. Excessive discretionary links can make the schedule unnecessarily rigid.

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. Network diagrams

A network diagram displays activities and dependencies, helping identify paths through the project. In activity-on-node diagrams, each node represents an activity and arrows represent relationships. Forward pass calculations determine earliest start and finish; backward pass calculations determine latest start and finish without delaying the project completion date. The difference between latest and earliest dates gives float. Network logic should be checked for loops, missing predecessors, open ends and unrealistic constraints. A schedule with many hard date constraints may hide the true critical path.

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. Duration estimating

Duration estimates should reflect work content, productivity, available resources, calendar conditions, approvals and uncertainty. Expert judgement, analogous estimating, parametric estimating and bottom-up estimating are common methods. Analogous estimates use similar past work; parametric estimates apply a measurable rate, such as installation units per day; bottom-up estimates aggregate detailed work package estimates. State the basis and assumptions. A 10-day task does not necessarily require 10 person-days: duration and effort are different measures.

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. Three-point estimating and PERT

Three-point estimating recognises uncertainty by using optimistic (O), most likely (M) and pessimistic (P) durations. A common PERT expected duration is (O + 4M + P)/6. For example, if O=4 days, M=6 days and P=14 days, expected duration is (4+24+14)/6 = 7 days. The estimate is not a guarantee; it is a weighted planning value based on assumptions about the distribution of outcomes. The range should be reviewed when new information becomes available.

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. Critical path method

The critical path is the longest-duration path through the network and determines the earliest possible project completion under the schedule logic. Activities on the critical path normally have zero total float. Delaying one of them delays the project unless corrective action or a logic change is made. There can be more than one critical path, and near-critical paths deserve attention because small changes can make them critical. The critical path is not necessarily the path with the most activities; it is the path with the greatest total duration.

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. Worked critical path example

Consider activities A (2 days) and B (3 days) beginning at the start. C (4 days) follows A; D (2 days) follows B; E (3 days) requires both C and D. Path A-C-E lasts 2+4+3=9 days. Path B-D-E lasts 3+2+3=8 days. The critical path is A-C-E and the earliest completion is 9 days. E cannot start until both predecessor paths are complete. If B-D slips by one day, it becomes equal to the critical path and removes its one day of float; a further delay would affect completion.

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. Float and schedule flexibility

Total float is the time an activity can be delayed without delaying the project completion date, subject to the network logic. Free float is the time an activity can be delayed without delaying the early start of its immediate successor. Float is a property of the network and can change when durations, logic or constraints change. It should not be treated as spare time that every team can independently consume. Project managers monitor float erosion because a sequence of small delays can remove schedule resilience before the final milestone is visibly affected.

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. Milestones and baselines

A milestone is a significant event with zero duration, such as design approval, permit issue, equipment delivery, commissioning or handover. Milestones help sponsors understand progress and decision points. The approved schedule baseline is the reference for measuring performance. Current forecasts should be shown separately from the baseline so that variance remains visible. Re-baselining should occur only through authorised governance, not simply to make a late project appear on time. Maintain a record of the original baseline and approved changes.

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. Resource calendars and capacity

A schedule must reflect when people, equipment, facilities and suppliers are available. Resource calendars record working days, shifts, holidays, maintenance periods and other constraints. Resource loading assigns effort or units to activities; resource histograms show demand over time. If a specialist is assigned to several simultaneous tasks, the plan may be mathematically linked but operationally impossible. Resource availability should be confirmed with functional managers and suppliers before committing to dates.

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. Resource levelling and smoothing

Resource levelling adjusts activity dates to resolve over-allocation, potentially changing the critical path and completion date. Resource smoothing uses available float to adjust work while keeping the end date unchanged where possible. These techniques answer different questions. Levelling prioritises feasible resource use; smoothing seeks a more even profile within schedule constraints. Any change should be checked against contractual milestones, dependencies, cost and risk. A schedule should not assume unlimited overtime as a default solution.

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. Leads, lags and fast tracking

A lead allows a successor to start before the predecessor is fully complete where partial progress is safe and logical. A lag inserts waiting time between activities, such as a curing period or required review. Fast tracking overlaps activities that would normally be sequential; it can shorten duration but increases rework and coordination risk. Crashing adds resources to shorten critical activities, usually increasing cost. Evaluate these options against safety, quality, procurement lead times and the probability that early work will need to be redone.

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. Schedule compression decision

Suppose a critical installation activity takes 10 days with one crew. Adding a second crew may reduce duration to 7 days but increases labour and coordination costs. Before crashing, verify that the workface can safely support two crews, materials are available and supervision is adequate. If the activity is not on the critical path, shortening it may not reduce project completion. Compare the cost per day saved across candidate critical activities and consider the new critical path after each compression decision.

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. Schedule risk and contingency

Schedule risk arises from uncertain durations, approvals, weather, interfaces, supplier performance, labour availability, design maturity and rework. A risk-adjusted schedule includes realistic allowances based on evidence and the level of uncertainty. Buffers should be visible and governed rather than hidden inside every task. Monte Carlo simulation can estimate the probability of meeting a date by repeatedly sampling uncertain activity durations and recalculating the network. The output is a probability distribution, not a promise; its quality depends on input assumptions and correlations.

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. Progress measurement and forecasting

Progress should be measured using objective evidence, such as completed quantities, approved deliverables, passed tests or accepted milestones. Percent complete based only on opinion can overstate performance. Forecasts should use actual start and finish dates, remaining duration, current logic and known risks. Variance analysis compares current forecast with baseline dates. Trend charts show whether performance is improving or deteriorating. Explain causes and corrective actions, not just red/amber/green status.

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. Schedule control and change

Schedule control compares actual progress with the baseline, analyses variances, forecasts completion and recommends corrective action. Changes to scope, logic, calendars or resources should be documented and assessed. Recovery plans may resequence work, add capacity, remove non-essential scope through approval or negotiate milestones. Avoid changing logic merely to conceal a delay. Communicate the consequences to suppliers, users and sponsors, especially where one party's recovery action creates risk for another.

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: school construction schedule

A school construction project may include land survey, design, approvals, procurement, site establishment, earthworks, foundations, frame, envelope, services, finishes, testing, furniture and handover. Some activities can overlap, but foundations depend on approved design and setting out; services coordination must occur before walls and ceilings close; commissioning requires completed systems and utilities. Rainy seasons may affect earthworks and access. Long-lead equipment should be procured early. The schedule should include inspections, community communication, teacher orientation and operational readiness, not only physical construction.

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: Schedule quality checks

A schedule quality review checks whether every activity has a clear description, logical predecessor and successor where appropriate, realistic duration, assigned owner and suitable calendar. Look for open ends, excessive constraints, negative lags, unrealistic date commitments, missing approvals and activities with no link to deliverables. Compare the schedule with procurement plans, resource calendars, risk registers and contract milestones. Ask experienced delivery staff to challenge the logic. A schedule that passes software validation may still be unrealistic if it assumes instant decisions or ignores physical access, inspection and handover requirements.

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: Schedule communication and reporting

Different audiences need different schedule information. Delivery teams need near-term activities, constraints and handoffs; sponsors need milestone forecasts, critical path movement, major risks and decisions required; suppliers need interface dates and notice periods; users need expected service interruptions and transition dates. Reports should distinguish baseline dates, actual dates and current forecasts. Explain the reason for variance and the action being taken. Use consistent status dates and data rules so that progress from different workstreams can be compared. Avoid presenting a detailed Gantt chart without a short narrative explaining what matters.

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: Schedule governance and lessons learned

Schedule governance defines who can approve baseline changes, how delay events are notified, what evidence is required and how recovery plans are assessed. Contractual notice requirements may be time-sensitive and should be handled by authorised personnel. At closure, compare estimates with actual durations and record the reasons for variance: scope growth, productivity, weather, approvals, design changes, supplier performance or inaccurate assumptions. Lessons should be specific enough to improve future estimating and sequencing. Do not use hindsight to blame individuals for uncertainty that could not reasonably have been known.

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 work breakdown structures and project scheduling. 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.