---
title: "Principles of scheduling"
subject: "ICT Project Management"
chapter: 8
key: "semester_7/ict_project_management:scheduling-principles"
source: https://www.bctengineer.com/q/semester_7/ict_project_management/scheduling-principles
site: BCT Engineering
---

# Principles of scheduling

ICT Project Management · Chapter 8: Project Time Management

- Asked in: year not given
- Answer checked by Claude Opus 5.5 (high effort) on 2026-10-14
- Page: https://www.bctengineer.com/q/semester_7/ict_project_management/scheduling-principles
- Whole chapter: https://www.bctengineer.com/md/semester_7/ict_project_management/chapter-8

## Question

What are the principles of scheduling?

## Short answer

Key scheduling principles include basing the schedule on the WBS, defining clear dependencies and realistic estimates, identifying the critical path, considering resource availability, and including milestones. The schedule should be baselined, tracked against actuals, and controlled via change control to manage variances.

## Answer

Scheduling is the process of deciding in what order and when the project's activities will be done. The following principles help to build a realistic and controllable schedule.

1. **Base the schedule on the WBS**: schedule every work package; no work outside the WBS.
2. **Define clear activities and dependencies**: use finish-to-start, start-to-start, finish-to-finish, start-to-finish relationships; recognise mandatory, discretionary and external dependencies.
3. **Estimate durations realistically**: involve the people who will do the work; use three-point estimates; do not pad hidden buffers.
4. **Identify the critical path**: focus management on activities with zero float.
5. **Consider resource availability**: schedule with actual resource limits, apply levelling and avoid over-allocation.
6. **Include milestones** for key deliverables and approvals.
7. **Use appropriate level of detail**: more detail for near-term work, less for future (rolling wave).
8. **Allow for risk and contingency**: add schedule reserves or project buffer instead of padding every activity.
9. **Do not over-commit people**: assume productive time (e.g. 6 hours/day), not full 8.
10. **Baseline and track the schedule**: save an approved baseline, compare progress, update regularly.
11. **Communicate the schedule** to all stakeholders using Gantt charts and milestone charts.
12. **Control changes**: revise only through change control.
13. **Keep the schedule simple and flexible**: use suitable software; update as information changes.
14. **Involve the team** to gain commitment.
15. **Consider calendars**: holidays, working days (e.g. Dashain, Tihar in Nepal), shifts.

| Principle | Purpose |
|---|---|
| WBS basis | Complete coverage |
| Critical path focus | Control of completion date |
| Resource consideration | Feasibility |
| Baseline | Measure progress |

Following these principles reduces delays and cost overruns.

## Check yourself

The answer's key points as multiple-choice questions, with the correct option and why.

1. Why should a schedule be based on the WBS?
   A. So that resources are ignored
   B. So every work package is scheduled and no work is outside the WBS
   C. So buffers are hidden in each task
   D. So that no milestones are needed
   Answer: B. Basing the schedule on the WBS gives complete coverage of scope. (Key point: WBS basis)

2. On which activities should management focus most closely?
   A. Critical path activities with zero float
   B. Milestones only
   C. Activities with the largest float
   D. Activities with the most resources
   Answer: A. Critical path activities have zero float, so delay in them delays the project. (Key point: Critical path focus)

3. How should uncertainty be handled in a schedule?
   A. Add schedule reserve or project buffer instead of padding every activity
   B. Ignore risk
   C. Pad every activity by 20%
   D. Assume 8 productive hours with no allowance
   Answer: A. Principles advise reserves or buffers rather than hidden padding. (Key point: Padding and reserves)

4. What should be assumed for people's daily productive time?
   A. Around 6 hours rather than a full 8
   B. Zero overtime hours but 10 hours
   C. 12 hours
   D. Exactly 8 hours
   Answer: A. Do not over-commit people; assume productive time such as 6 hours per day. (Key point: Productive hours)