📘 IT4306 · BIT LEVEL II · SEM 4

Topic 6 — Project Schedule Management

Study Questions & Model Answers · Managing IT Projects — Kathy Schwalbe, 9th Edition

📋 10 Questions 🎓 2nd Year University 🗂 CPM · PERT · Gantt · Crashing
0 / 10 answered
How to use: Click any question card to expand the model answer and diagrams. All answers are based on the UCSC IT4306 lecture slides and Managing Information Technology Projects, Kathy Schwalbe, 9th Edition. Track your progress with the bar above.
01
Why is project schedule management considered the most critical dimension of IT project management? What makes time unique compared to other project constraints?
Importance of Schedules
+
▸ MODEL ANSWER

Project schedule management is the most critical constraint because time is the least flexible resource — it passes regardless of what happens on a project, unlike cost or scope which can often be renegotiated.

The 2003 Standish CHAOS Report found that 50% of IT projects were challenged, with average time overruns reaching 82% — up from 63% in 2000. Schedule issues are the primary source of conflict on projects, especially in the second half of a project.
📊 Conflict Intensity Over the Life of a Project
Formation Early Phases Middle Phases End Phases Conflict Intensity Schedules Priorities Manpower Cost
  • Schedule issues peak during the middle and end phases — precisely when pressure is highest.
  • Cultural differences also cause conflicts: some cultures treat deadlines as strict while others treat them loosely.
  • Technical errors, poor communication, and weak scope management further amplify schedule overruns.
02
Distinguish between the Activity-on-Arrow (AOA) and Precedence Diagramming Method (PDM/AON) network diagrams. Include diagrams and state their key advantages and limitations.
Network Diagrams · AOA vs PDM
+
▸ MODEL ANSWER
🔷 AOA (Activity-on-Arrow) — Project X
1 2 3 4 5 6 7 8 A=1 B=2 C=3 D=4 E=5 F=4 G=6 H=6 I=2 J=3 Activities on arrows · Nodes are events · Red = critical path segment
🔶 PDM / AON — Activity node structure
A Start: 6/1Finish: 6/1 Dur: 1d D Start: 6/2Finish: 6/7 Dur: 4d H Start: 6/10Finish: 6/17 Dur: 6d Activities are boxes · Arrows show relationships · Supports all 4 dependency types
FeatureAOA / ADMPDM / AON
Activity shown asArrowBox (node)
Nodes representStart/end eventsActivities
Dependency typesFinish-to-Start onlyAll 4 types (FS, SS, FF, SF)
Dummy activitiesNeeded for shared predecessorsNot required
PM SoftwareRarely usedIndustry standard (MS Project)
03
Explain the four types of task dependencies used in PDM, with diagrams and practical IT project examples for each.
Task Dependency Types
+
▸ MODEL ANSWER
🔗 Four Task Dependency Types
① Finish-to-Start (FS) A B B cannot START until A finishes e.g. Testing starts after development finishes ② Start-to-Start (SS) A B B cannot START until A starts e.g. Docs can start when coding starts ③ Finish-to-Finish (FF) A B B cannot FINISH until A finishes e.g. UAT cannot finish until bug-fixes finish ④ Start-to-Finish (SF) A B B cannot FINISH until A starts e.g. Old system stays until new system starts Lag time = positive delay between tasks (e.g. wait 2 days for concrete to set) Lead time = overlap/negative value (task B starts before A fully completes)
04
Define the Critical Path Method (CPM). Describe the forward pass and backward pass, and identify the critical path using the Project X network.
CPM · Critical Path Analysis
+
▸ MODEL ANSWER
CPM is a network diagramming technique to predict total project duration. The critical path is the longest path through the network — it determines the shortest possible completion time. Activities on it have zero total float.
🔁 Forward Pass & Backward Pass — Node notation
ES=0 Start LS=0 ES=0 EF=5 A=5 LS=5 LF=10 ES=0 EF=10 B=10 LS=0 LF=10 ES=10 EF=17 C=7 LS=10 LF=17 Critical (TF=0) Non-critical (TF=5) ES of C = max(EF of A, EF of B) = 10

Forward Pass rules:

  • ES of first activity = 0.  EF = ES + Duration
  • When multiple paths converge, take the largest (latest) EF

Backward Pass rules:

  • LS of last node = its ES.  LF = LS of successor
  • LS = LF − Duration. When multiple paths diverge, take the smallest LS
📍 Project X — All Paths & Critical Path
Path 1: A–D–H–J = 1+4+6+3 = 14 days ★ Path 2: B–E–H–J = 2+5+6+3 = 16 days ← CRITICAL PATH Path 3: B–F–J = 2+4+3 = 9 days Path 4: C–G–I–J = 3+6+2+3 = 14 days

Activities B, E, H, and J all have Total Float = 0. Any delay on these activities will directly delay the project finish date of 16 days.

05
Differentiate between Free Float and Total Float. Provide formulas, a diagram, and explain their role in schedule trade-off decisions.
Free Float · Total Float · Slack
+
▸ MODEL ANSWER
⏱ Free Float vs Total Float — Visual Explanation
0 4 8 12 16 Project Duration (days) B(2) E(5) H(6) J(3) CP→ A(1) D(4) FF = 2d A–D → F(4) Total Float = 7d B–F →
Free Float = ES of next activity − EF of current activity
Total Float = LF − EF    OR    Total Float = LS − ES
  • Free Float ≤ Total Float always.
  • Critical path activities always have Total Float = 0.
  • If two activities converge to one successor, only one can have free float.
  • In Project X: Task F has the most slack (Free = 7d, Total = 7d) — it's the most flexible.
06
What is PERT? Write its formula and apply it to the textbook example. Why is PERT preferred over a single-point estimate?
PERT · Three-Point Estimation
+
▸ MODEL ANSWER
PERT (Program Evaluation and Review Technique) is used when there is a high degree of uncertainty in activity duration estimates. It uses three-point estimates to produce a weighted average that accounts for risk.
📐 PERT Three-Point Estimate — Distribution
Optimistic 8 days Most Likely 10 days Pessimistic 24 days PERT = 12d Duration (workdays)
PERT Weighted Average = (Optimistic + 4 × Most Likely + Pessimistic) / 6
= (8 + 4 × 10 + 24) / 6 = 72 / 6 = 12 workdays

Without PERT a PM would use 10 days (most likely). PERT gives 12 days — accounting for the risk of the pessimistic scenario. The extra 2 days reflects the right-skewed uncertainty typical in IT projects.

Three-point estimates are also required for Monte Carlo simulations, which model thousands of schedule scenarios to quantify overall project risk.

07
Describe Project Crashing. What are the key strategies, the correct iterative procedure, and why must crashing always target the critical path?
Project Crashing · Schedule Compression
+
▸ MODEL ANSWER
Project Crashing reduces total project duration with the least additional cost by adding resources to selected critical activities. It trades cost for time.
🔧 Crashing Decision Process
1. Identify Critical Path activities 2. Find cheapest crash per-day option 3. Crash by 1 iteration / day 4. Re-check Critical Path (it may change!) Target reached? No Yes ↓ ✓ DONE — Report Cost ⚠ Parallel CPs Crash both paths!

Key terms:

  • Crash Duration — shortest possible time an activity can be completed.
  • Additional Cost/Day — extra cost per day of compression for a task.
  • Project Overhead/Day — daily overhead saved by reducing the total project duration.
Strategy 1: Minimum Duration
Strategy 2: Minimum Cost
Strategy 3: Crash by N Days
⚠ Crashing ≠ always cheaper
08
What is a Gantt Chart? Distinguish it from a Tracking Gantt Chart. Explain all symbols and list its advantages and disadvantages.
Gantt Charts · Tracking · Milestones
+
▸ MODEL ANSWER
📅 Gantt Chart — Symbols & Tracking
Task Name Week 1 Week 2 Week 3 ▼ Phase 1 (Summary) ← Thick bar = Summary task Task A Planned Task B (Tracking) Planned vs Actual shown Baseline (planned) Actual (delayed) Milestone ◆ M1: Sign-off Slipped Milestone ◇ Planned Actual (late!) Task D (dependency) ← Arrow = dependency
SymbolMeaning
◆ Black diamondMilestone (zero-duration significant event)
Thick black barSummary task (WBS parent)
Lighter barIndividual task duration
Arrow between barsDependency between tasks
◇ Open diamondSlipped milestone (completed later than planned)
Top/Bottom barsTracking: planned (top) vs actual (bottom)

Milestones must satisfy SMART criteria: Specific, Measurable, Assignable, Realistic, Time-framed.

AdvantageDisadvantage
Easy to read and communicateDoes not naturally show dependencies
Standard industry formatWBS logic can be obscured at scale
Tracking variant shows planned vs actualDependency arrows only appear if tasks are linked in software
09
Explain Critical Chain Scheduling. How does it differ from CPM? Define project buffer, feeding buffer, Parkinson's Law, and Murphy's Law in this context.
Critical Chain · Buffers · TOC
+
▸ MODEL ANSWER
Critical Chain Scheduling is based on the Theory of Constraints (TOC) by Eliyahu M. Goldratt. Unlike CPM which assumes unlimited resources, critical chain explicitly accounts for scarce resource availability and uses buffers to protect the project completion date.
🛡 Critical Chain — Feeding Buffers & Project Buffer
Critical Chain (main path) Feeder paths Task X Task Y Task Z Project Buffer FINISH F-Task 1 FB F-Task 2 FB FB = Feeding Buffer PB protects finish date
  • Project Buffer (PB) — time added before the final project due date. Protects the delivery date from accumulated delays on the critical chain.
  • Feeding Buffer (FB) — time added before a critical chain task if preceded by non-critical tasks. Prevents off-path delays from propagating into the critical chain.
  • Multitasking — critical chain minimises simultaneous task assignments because humans perform poorly when switching contexts frequently.
  • Murphy's Law: "If something can go wrong, it will." People pad individual estimates. Critical chain removes task-level padding and consolidates protection into shared buffers.
  • Parkinson's Law: "Work expands to fill the time allowed." Without individual buffers, teams focus on actual work duration rather than filling allocated time.
10
List and briefly describe all seven processes of Project Schedule (Time) Management as defined in the PMBOK framework. What are the primary outputs of the schedule development process?
7 Processes · PMBOK · Schedule Management
+
▸ MODEL ANSWER
🔄 7 Processes of Project Time Management — Flow
1. Plan Schedule Management 2. Define Activities Activity list · Milestones 3. Sequence Activities Network diagram 4. Estimate Resources Type · Quantity · Availability 5. Estimate Durations Effort · PERT · 3-point 6. Develop Schedule Gantt · CPM · PERT · Critical Chain 7. Control Schedule Progress reports · Earned value · Variance
#ProcessKey Output
1Plan Schedule ManagementSchedule management plan
2Define ActivitiesActivity list, attributes, milestones
3Sequence ActivitiesNetwork diagram with dependencies
4Estimate Activity ResourcesResource requirements per activity
5Estimate Activity DurationsDuration estimates (PERT, 3-point)
6Develop the ScheduleProject schedule, schedule baseline, schedule data, project calendars
7Control the ScheduleProgress reports, variance analysis, earned value

The primary outputs of Process 6 (Develop Schedule) are the project schedule, a schedule baseline, schedule data, project calendars, and project management plan/document updates. Key tools include Gantt charts, CPM, PERT, and Critical Chain Scheduling.