Beruflich Dokumente
Kultur Dokumente
The planned dates for performing activities and the planned dates for meeting milestones.
Rahul-ppt
A project schedule is required to ensure that required project commitments are met. A schedule is required to track progress toward achieving these commitments.
Rahul-ppt
Establishing objectives Determining available resources Sequencing activities Identifying precedence relationships Determining activity times & costs Estimating material & worker requirements Determining critical activities
Rahul-ppt
An unrealistic deadline Changing but unpredicted customer requirements Underestimation of efforts needed Unforeseen technical difficulties Unforeseen human difficulties Miscommunication among project staff Failure to recognize that project is falling behind schedule
Rahul-ppt
Compartmentalization define distinct tasks Interdependency-parallel and sequential tasks Time allocation - assigned person days, start time, ending time Effort validation - be sure resources are available
Rahul-ppt
Defined Responsibilities people must be Assigned Defined Outcomes- each task must have an output Defined Milestones - tasks should be associated with a
project milestone.
Rahul-ppt
40-20-40
Rahul-ppt
02-03 % planning 10-25 % requirements analysis 20-25 % design 15-20 % coding 30-40 % testing and debugging
Rahul-ppt
10
2012
31% 53%
Critical Failures
Challeng ed
Success
16%
2
Rahul-ppt
8
11
300K 421K
525K
852k
Rahul-ppt
12
13
Rahul-ppt
14
Project network diagrams are the preferred technique for showing activity sequencing A project network diagram is a schematic display of the logical relationships among, or sequencing of, project activities
15
Rahul-ppt
Terminology
Activity - A specific task or set of tasks that are required by the project, use up resources, and take time to complete Event - The result of completing one or more activities. An identifiable end state occurring at a particular time. Events use no resources. Network - The combination of all activities and events define the project and the activity precedence relationships
Rahul-ppt 16
Terminology
Path - The series of connected activities (or intermediate events) between any two events in a network Critical - Activities, events, or paths which, if delayed, will delay the completion of the project. A projects critical path is understood to mean that sequence of critical activities that connect the projects start event to its finish event
Rahul-ppt
17
Late Start Time (LsT)-The latest possible time an activity can begin without delaying the project. Early Start Time (EsT)-The Earliest possible time an activity can start. Slack-The amount of Time a project activity can be delayed without delaying a succeeding activity or the project finish date also called Float Slack = Late Start Time - Early Start Time
Rahul-ppt 18
CPM is a project network analysis technique used to predict total project duration. A critical path for a project is the series of activities that determines the earliest time by which the project can be completed.
The critical path is the longest path through the network diagram and has the least amount of slack or float
Rahul-ppt 19
First develop a good project network diagram. Add the durations for all activities on each path through the project network diagram. The longest path is the critical path
Rahul-ppt
20
Consider the following project network diagram. Assume all times are in days.
C=2
start
4 5
E=1
A=2
B=5
3
D=7 F=2
finish
22
Rahul-ppt
Dependencies (milestone)
T1 (M1) T2, T4 (M2) T1, T2 (M3) T1 (M1) T4 (M5) T3, T6 (M4) T5, T7 (M7) T9 (M6) T11 (M8)
23
14/7/13
8 days
15 days
M1
25/7/13
T3
4/8/13
15 days
T1 4/7/13
5 days
M4 M3
T9
25/8/13
Start
15 days
T6
20 days
M6
7 days
T2
25/7/13
T7
10 days
T11
11/8/13 5/9/13
M2 T4
10 days
T5
18/7/13
M7
15 days
M8
10 days
M5
25 days
T10
T12
T8
End
Rahul-ppt
19/9/13
24
14/7/13
8 days
15 days
M1
25/7/13
T3
4/8/13
15 days
T1 4/7/13
5 days
M4 M3
T9
25/8/13
Start
15 days
T6
20 days
M6
7 days
T2
25/7/13
T7
10 days
T11
11/8/13 5/9/13
M2 T4
10 days
T5
18/7/13
M7
15 days
M8
10 days
M5
25 days
T10
T12
T8
= Critical
Path
Rahul-ppt
End
19/9/13
25
4/7 Start
11/7 18/7
T4 T1 T2 M1
25/7
1/8
8/8
15/8
22/8
29/8
5/9
12/9
19/9
26/9
T7
T3
M5 M3 M2 T6 T8
T5
M4 M7
T9 T10
M6 T11 M8 T12
End
Rahul-ppt 26
4/7 Start
11/7 18/7
T4
25/7
1/8
8/8
15/8
22/8
29/8
5/9
12/9
19/9
26/9
T1
T2 M1 T7
T3
M5 M3 M2 T6 T8
T5
M4 M7
T9 T10
M6 T11 M8 T12
End
Rahul-ppt
27
4/7
8/8
15/8
22/8
29/8
5/9
12/9
19/9
26/9
Task T1 T2 T3 T4 T5 T6 T7 T8
Software Engineer Sujeet Amit Roshan Laxman Sagar Manish Babloo Rohit
Manish
T4 T8 T11 T12
Amit
T1 T3 T9
Nalini
T2 T6
T10
Uday
T7 T5
T9
T10 T11 T12
Noopur
Nalini Anshu Uday
Rahul-ppt
Roshan
Resources can influence the critical path, e.g. Frank with T8-T11
28
PERT is a network analysis technique used to estimate project duration when there is a high degree of uncertainty about the individual activity duration estimates PERT uses probabilistic time estimates based on using optimistic, most likely, and pessimistic estimates of activity durations
29
Rahul-ppt
Dont plan for everyone to work at 100% capacity all the time Hold progress meetings with stakeholders and be clear and honest in communicating schedule issues
Rahul-ppt
30
Microsoft Project It is a pricier option ($599.95 for the Standard version and $999.95 for the Professional version). Microsoft Project is highly integrated, allowing you to track a number of variables and produce Gantt charts as well as network diagrams..
Rahul-ppt 31
ZOHO Projects:
Its a web-based application. You can access your schedule from anywhere. ZOHO Projects can generate Gantt charts, but doesnt offer PERT charts.
Rahul-ppt
32
Primavera P6:
It is intended for use by larger organizations, and may not be ideal for managers working with smaller projects.
Rahul-ppt 34
The seeds of major software disasters are usually sown in the first three months of commencing the software project. Factors: Hasty scheduling, irrational commitments, unprofessional estimating techniques. carelessness of the project management function.
Rahul-ppt 35
Rahul-ppt
36
Rahul-ppt
37