1. Program Scheduling Capstone By Amanda Wilson California Lutheran University Spring 2003

2. What is Scheduling? ScheduleA Schedule is an event (task) driven roadmap for an entire program. The Schedule provides task details, durations, and links enabling effective program management. Critical Path,Identifies the Critical Path, so revisions to the Schedule can be made to problematic areas or in the event of delay.

3. What is Scheduling? (cont.) Schedule A Schedule can be compared to an onion. Underneath the top layer (critical path) another layer always exists.

4. 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)

5. 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

6. 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)

7. Schedule Types (cont.)

8. 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

9. 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?

10. 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

11. Example (cont.) 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

12. Example – Network Flow Diagram

13. Summary ScheduleA Schedule is a roadmap for the entire length of a program ScheduleA 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

14. The End

15. QUESTIONS?