Presentation on theme: "Developing a Project Plan"— Presentation transcript: 1 Developing a Project Plan Show
2 Developing the Project Plan
3 Developing the Project Plan
4 From WBS/Work Packages to Network
5 Integration of WBS and OBS 6 WBS/Work Packages to Network
7 WBS/Work Packages to Network
8 WBS/Work Package to Network (cont’d) 9 Constructing a Project
Network
10 Constructing a Project Network (cont’d)
11 Constructing a Project Network (cont’d)
12 Basic Rules to Follow in Developing Project Networks 13 Activity-on-Node
(AON) - Fundamentals
14 Activity-on-Node Fundamentals 15 Activity-on-Node Fundamentals
(cont’d) 16 Network Information TABLE 6.1 17
Koll Business Center—Partial Network 18 Koll Business Center—Complete Network
19 Benefits of Graphical Networks
20 Network Computation Process 21 Network Information TABLE 6.2 22 Activity-on-Node Network 23 Activity-on-Node Network Forward Pass 24 Forward Pass Computation 25 Backward Pass Computation 26 Activity-on-Node Network Backward Pass
27 Determining Slack Is the amount of time an activity can be delayed after the start of a longer parallel activity or
activities. Is how long an activity can exceed its early finish date without affecting early start dates of any successor(s). Allows flexibility in scheduling scarce resources. If slack of one activity in a path is used, the ES for all activities that follow in the chain will be delayed and their slack reduced. Use of total slack must be coordinated with all participants in the activities that follow in the chain. After slack for
each activity is computed, the critical path(s) is (are) easily identified. When the LF = EF for the end project activity, the critical path can be identified as those activities that also have LF = EF or a slack of zero. The critical path is the network path(s) that has (have) the least slack in common.
28 Sensitivity The likelihood the original critical path(s) will change once the project is initiated. The critical path is the network path(s) that has (have)
the least slack in common. Sensitivity is a function of the number of critical or near-critical paths. A sensitive network would be one or more than critical paths and/or noncritical activities with very little slack. Under these circumstances the original critical path is much more likely to change once work gets under way on the project. Project managers assess the sensitivity of their network schedules to determine how much attention they
should devote to managing the critical path. 29 Activity-on-Node Network with Slack 30 Practical Considerations What are the basic rules to follow when developing a project network?BASIC RULES TO FOLLOW IN THE DEVELOPMENT OF PROJECT NETWORKS. Networks usually flow from left to right.. An activity cannot begin until all connected preceding activities have been completed.. Arrows in networks point to precedence and flow. ... . Each activity must have a unique identification number.. What are the two approaches used to develop project network?The two approaches used to develop project networks are AOA and AON.
Which of the following is not one of the basic rules to follow when developing project network?Which of the following is NOT one of the basic rules to follow when developing project networks? Conditional statements are allowed but looping statements are not allowed.
What information is needed to build a project network?What elements are included in a project network? the sequence of activities to complete the project, inter-dependencies of activities and work packages within a work breakdown structure.
|