To Create a Plan You Need… Work Breakdown Structure Dependencies Milestones The Network Early/Late Start/End dates Slack/Float Critical Path
Task Dependencies Task A is said to be dependent on task B if task B must precede task A (task B must be finished before task A can start) Task B is called a predecessor of task A Task A can have many predecessors Only immediate predecessors are referred to as predecessors
Network Diagram A pictorial representation of the sequence in which the project work can be done Shows the relationships (dependencies!) between tasks MS Project creates network diagrams for you (=Gantt chart in MS Project)
Network Diagram What order do I do these tasks in?
Why are they important? You can plan more effectively--you can see the relationship between activities Easier to reschedule--you can see impact of changes Allows you to monitor and control the project--compare it against baseline
Identifying Dependencies Dependencies are caused by constraints: Technical constraints –Discretionary –Best practices –Logical –Unique situations
Identifying Dependencies Dependencies are caused by constraints: Management Inter-Project
Calculating Slack/Float What is the earliest/latest possible start of each task?
Late and Early Start/Finish Early start/finish--earliest possible time that a task can start/finish without causing delay Late start/finish--latest possible time that a task can start/finish without causing delay
Early Start/Finish ES = latest finish of predecessors + 1 EF = (ES + duration) - 1
Late Start/Finish LF = earliest start of successors - 1 LS = (LF - duration) + 1