Presentation is loading. Please wait.

Presentation is loading. Please wait.

Project Scheduling. Why Are Projects Late? an unrealistic deadline established by someone outside the software development group changing customer requirements.

Similar presentations


Presentation on theme: "Project Scheduling. Why Are Projects Late? an unrealistic deadline established by someone outside the software development group changing customer requirements."— Presentation transcript:

1 Project Scheduling

2 Why Are Projects Late? an unrealistic deadline established by someone outside the software development group changing customer requirements that are not reflected in schedule changes; an honest underestimate of the amount of effort and/or the number of resources that will be required to do the job; predictable and/or unpredictable risks that were not considered when the project commenced; technical difficulties that could not have been foreseen in advance; human difficulties that could not have been foreseen in advance; miscommunication among project staff that results in delays; a failure by project management to recognize that the project is falling behind schedule and a lack of action to correct the problem

3 How to Change an Unrealistic Deadline Perform a detailed estimate of effort and time using historical data Using an incremental process model, develop a strategy to deliver critical functionality by the deadline – document the plan Meet with the customer and explain why the imposed deadline is unrealistic. Offer the incremental development strategy as an alternative

4 Scheduling Principles compartmentalization—define distinct tasks interdependency—indicate task interrelationship effort validation—be sure resources are available defined responsibilities—people must be assigned defined outcomes—each task must have an output defined milestones—review for quality

5 TIMELINE CHARTS When creating a software project schedule, the planner begins with a set of tasks (the work breakdown structure). If automated tools are used, the work breakdown is input as a task network or task outline. Effort, duration, and start date are then input for each task. In addition, tasks may be assigned to specific individuals. a timeline chart, also called a Gantt chart A timeline chart can be developed for the entire project. Alternatively, separate charts can be developed for each project function or for each individual working on the project

6 Gantt Chart

7 Critical path method In 1957, DuPont developed a project management method designed to address the challenge of shutting down chemical plants for maintenance and then restarting the plants once the maintenance had been completed. Given the complexity of the process, they developed the Critical Path Method (CPM) for managing such projects.

8 Benefits Provides a graphical view of the project. Predicts the time required to complete the project. Shows which activities are critical to maintaining the schedule and which are not.

9 Steps Specify the individual activities. Determine the sequence of those activities. Draw a network diagram. Estimate the completion time for each activity. Identify the critical path (longest path through the network) Update the CPM diagram as the project progresses.

10 1. Specify the Individual Activities From the work breakdown structure, a listing can be made of all the activities in the project. This listing can be used as the basis for adding sequence and duration information in later steps. 2. Determine the Sequence of the Activities Some activities are dependent on the completion of others. A listing of the immediate predecessors of each activity is useful for constructing the CPM network diagram. 3. Draw the Network Diagram Once the activities and their sequencing have been defined, the CPM diagram can be drawn. CPM originally was developed as an activity on node (AON) network, but some project planners prefer to specify the activities on the arcs.

11 4. Estimate Activity Completion Time The time required to complete each activity can be estimated using past experience or the estimates of knowledgeable persons. CPM is a deterministic model that does not take into account variation in the completion time, so only one number is used for an activity's time estimate. 5. Identify the Critical Path The critical path is the longest-duration path through the network. The significance of the critical path is that the activities that lie on it cannot be delayed without delaying the project. Because of its impact on the entire project, critical path analysis is an important aspect of project planning.

12 Determining the following six parameters for each activity which can identify the critical path: ES: earliest start time: the earliest time at which the activity can start given that its precedent activities must be completed first. –ES (K)= max [EF(J) : J is an immediate predecessor of K] EF: earliest finish time: equal to the earliest start time for the activity plus the time required to complete the activity. –EF (K)= ES (K) + Dur (K) LF: latest finish time: the latest time at which the activity can be completed without delaying the project. –LF (K)= min [LS(J) : J is a successor of K] LS: latest start time: equal to the latest finish time minus the time required to complete the activity. –LS (K)= LF(K) – Dur (K) TS: Total Slack: the time that the completion of an activity can be delayed without delaying the end of the project

13 –TS (K)= LS(K) – ES(K) FS: Free Slack: the time that an activity can be delayed without delaying both the start of any succeeding activity and the end of the project. –FS (K)= min [ES(J) : J is successor of K] – EF(K) The slack time for an activity is the time between its earliest and latest start time, or between its earliest and latest finish time. Slack is the amount of time that an activity can be delayed past its earliest start or earliest finish without delaying the project. The critical path is the path through the project network in which none of the activities have slack, that is, the path for which ES=LS and EF=LF for all activities in the path. A delay in the critical path delays the project. Similarly, to accelerate the project it is necessary to reduce the total time required for the activities in the critical path.

14 Example ActivityImmediate PredecessorDuration (Weeks) ANone5 B 3 CA8 DA, B7 ENone7 FC, D, E4 GF5

15 Network diagram D E B AC FG End Start

16 ActivityDuration ES (Max of predece ssor EF) EF (ES + T) LS (LF - Time) LF (Min of success or LF) TS= LS- ES FS= LF - EF A5050500 B3033632 C85135 00 D751261311 E7076 66 F4 17131700 G5 22171300

17 The critical path is: A-> C-> F-> G

18 Gantt Chart The Gantt chart enumerates the activities to be performed on the vertical axis and their corresponding duration on the horizontal axis. The tasks identified and enlisted are based on task dependency table. It is possible to schedule activities by either early start or late start logic. In the early start approach, each activity is initiated as early as possible without violating the precedence relations.

19 This Gantt chart would identify major milestones with their achievement criteria. It must contain duration estimation of all the necessary activities to be carried out during the project development along with the human resources responsible for the respective tasks.

20 Assignment part 1 1.Draw Gantt Chart 2.Draw PERT Network 3.Identify Critical Activities Q-1Calculate the Estimated Time from the given table and then perform the above mentioned activities Activity Immediate Predecessor Optimistic Time (Hrs) Most Likely Time (Hrs) Pessimistic Time (Hrs) A-46 8 B-14.5 5 CA33 3 DA45 6 EA0.51 1.5 FB, C34 5 G 11.5 5 HE, F56 7 I 25 8 JD, H2.52.75 4.5 KG, I35 7

21 Assignment part 2 Q- 2 Use the following information to 1.Draw Gantt Chart 2.Draw PERT Network 3.Identify Critical Activities ActivityImmediate PredecessorEstimated Time A-9 B-8 C-10 DB3 EB4 FA4 GA3 HG5 IG4 JC, E, F, H8

22 Reference Roger S. Pressman Chapter 24


Download ppt "Project Scheduling. Why Are Projects Late? an unrealistic deadline established by someone outside the software development group changing customer requirements."

Similar presentations


Ads by Google