Program Scheduling Capstone

By Amanda WilsonCalifornia Lutheran University

Spring 2003

What is Scheduling?

• A ScheduleSchedule is an event (task) driven roadmap for an entire program.

• The Schedule provides task details, durations, and links enabling effective program management.

• Identifies the Critical Path, Critical Path, so revisions to the Schedule can be made to problematic areas or in the event of delay.

What is Scheduling? (cont.)

A Schedule Schedule can be compared to an onion.

Underneath the top layer (critical path) another layer always exists.

Creating A Baseline Schedule

• Identify tasks to be performed (summary or key tasks)• Breakdown summary tasks into detail tasks

(use verbs for task definitions)• Establish durations for each task• Create Network Flow by connecting logic between tasks• Place constraints and milestones on the project’s START

and FINISH tasks• Rework Network logic and durations to assure zero or

positive slack• Set Baseline (freezes dates/times)

Creating A Baseline Schedule (cont.)

• The Baseline schedule, once set, is used as a measuring tool against future schedule status and overall schedule/program performance

• Once the Baseline schedule is established and approved by the customer this schedule cannot be altered without prior consent of the customer

Schedule Types

• Gantt Chart– Shows specific start and stop dates for tasks

• Milestone Chart– Major event oriented

• Line of Balance– Depicts production activity; actual vs. planned

• Network Flow Diagram– Identifies and defines all tasks and events and links

them in logical sequences (clearly depicts the critical path)

Schedule Types (cont.)

Critical Path

• Def: the series of tasks that must be completed on time for the project to be satisfactorily completed

• This is the path which is longest in duration; also known as “the driver”

• A schedule should have Slack or Float which is the amount of time a task can be delayed before affecting another task or the project schedule (critical path)

• Slack allows some flexibility to the schedule in case of unforeseen problems without delay to the entire program

Example – Create A Schedule

• Planning A Graduation Party– What are the tasks?– How much time will each task require?– When should I start so I am ready by

graduation day?– What are my constraints?– How should I link the task logic?– What is my critical path?

Example (cont.)

• TASKS and DURATIONS (in days – d)– Decide to have party (START) – 0d– Create guest list – 1d– Make invitations – 3d– Send invitations – 1d– Buy refreshments and utensils – 1d– Buy decorations – 2d– Set up decorations – 1d– Graduation/Party Day (FINISH) – 0d

Example (cont.)ID Task Name Duration Start Finish1 Graduation Party 0 days Fri 5/9/03 Fri 5/9/032 Create Guest List 1 day Fri 5/9/03 Sat 5/10/033 Make Invitations 3 days Sat 5/10/03 Tue 5/13/034 Send Invitations 1 day Tue 5/13/03 Wed 5/14/035 Buy Refreshments and Utensils 1 day Wed 5/14/03 Thu 5/15/036 Buy Decorations 2 days Wed 5/14/03 Fri 5/16/037 Set up Decorations 1 day Fri 5/16/03 Sat 5/17/038 Graduation/Party Day 0 days Sat 5/17/03 Sat 5/17/03

• Added Constraints:– You must send the invitations before you can buy refreshments

and before you can buy decorations– All other constraints can be seen through general logic regarding

the situation

Example – Network Flow Diagram

Summary

• A ScheduleSchedule is a roadmap for the entire length of a program

• A Schedule Schedule is DYNAMIC – always changing & evolving itself to meet program needs

• Key tool for program management and evaluation

• The ONION of a program stew!• GOOD SCHEDULE = PROGRAM SUCCESS

The End

QUESTIONS?