Presentation on theme: " Projects are usually infrequent or one- time. No two projects are the same. Projects are usually fairly long. Several months to many years Involve."— Presentation transcript:
Projects are usually infrequent or one- time. No two projects are the same. Projects are usually fairly long. Several months to many years Involve different people in different phases Most people are only involved with a part of the project
The three main goals of project management are… 1. Complete the project on time or earlier. 2. Complete the project on budget or under. 3. Meet the specifications to the satisfaction of the customer.
Defining a project’s scope, time frame, allocated resources and objective, is essential. A Project Objective Statement provides the objectives and essence of the project. A Specific time frame should be designated for starting and ending the project. Necessary resources must be defined, either in dollar terms or in personnel allocation.
Functional Structure: The team is housed in a specific functional area. Assistance from other areas must be negotiated. Pure Project: Team members work exclusively for the project manager, which is best for large projects. Matrix Structure: A compromise between the functional and project structures. Members remain in various functional areas and the project manager coordinates across functional areas. Dual authority can cause problems.
Software Project Management Aimed to ensure that the software is delivered on time, within budget and schedule constraints, and satisfies the requirements of the client Management of software projects is different from other types of management because: Software is not tangible Software processes are relatively new and still “under trial” Larger software projects are usually “one-off” projects Computer technology evolves very rapidly
Writing proposals Planning the project Scheduling the project Estimating the cost of the project Monitoring and reviewing the project’s progress Selecting, hiring, and evaluating personnel Writing reports and giving presentations 7
Project Planning A project plan should be drawn at the start of the project. This plan drives the project and needs to be continuously adjusted The role of the project manager is to anticipate possible problems and be prepared with solutions for these problems Other plans that need be developed: Quality plan Validation and verification plan Configuration management plan Maintenance plan Staff development plan 8
Project Planning Milestone = end-point of a specific, distinct software process activity or task (for each milestone a report should be presented to the management) Deliverable = project result delivered to the client In order to establish milestones the phases of the software process need be divided in basic activities/tasks. Example for requirements engineering 9
Project Scheduling…… Software managers: Divide the project in activities/tasks Estimate time and resources needed to finish the project Allocate resources to tasks Try to employ efficiently all the project personnel Minimize dependencies between tasks and teams Prepare contingency plans Rely on experience and intuition 10
Project Scheduling Graphical notations used in software project scheduling: Tables: summary description of tasks Bar charts: show schedule against the time Activity charts: graphs that depict dependencies between tasks and indicate the critical path (the longest path in the activity graph) 12
Three project management techniques 1. P rogram E valuation and R eview T echnique 2. C ritical P ath M ethod are often jointly referred to as PERT/CPM PERT & CPM were originally distinctive, but today the differences are minor and are often jointly referred to as PERT/CPM PERT (Program Evaluation and Review Technique) was utilized when activity times involved risk. CPM (Critical Path Method) was used when activity times were certain. 3. G raphic E valuation and R eview T echnique
1.Describe the Project (Defining all the tasks that must be completed, and in what sequence.) 2.Develop the Model (Graphically diagram the network showing task relationships) 3. Developing the Schedule (Insert the time estimates for each task) 4.Analyzing cost-time trade-offs (Insert the cost of each task.) 5. Assess Risks (Probability analysis)
What is the project? When does the project start and end? What activities make up the project? Activities are defined as the smallest units of work that a project manager is expected to schedule and control. “...a manager’s project description should reflect only the level of detail that he or she needs in order to make scheduling and resource allocation decisions.” Task Ownership: Each activity must have an owner who is responsible for seeing that the work is accomplished.
A project is a sequence of activities. Large projects have interrelated sequences. Except for the first activity, every activity in a project has one or more activities that must be done immediately prior. These are called Precedent activities They must be defined before the project begins. EG: In order to bury a body you must first dig a hole.
A Network Diagram visually displays the interrelated activities using nodes (circles) and arcs (arrows) that depict the relationships between activities. It is a graphical diagram. For very large projects it may only be a numerical arrangement of activities rather than graphical. Two types of Graphical Network Models Activity On Arc (AOA) Activity On Node (AON) (We will use AON in the following examples) In AON, activities and their relationships are depicted by lines and circles (nodes).
Activity-on -Arc (AOA) Activity-on-Node (AON) Time Activity E Activity Link We will use this! DE
What AON Nodes look like. Early Start Early Finish Late Finish Late Start Activity Activity Duration Slack The earliest you can complete an activity--determined by adding the activity time (duration) to the early start time. This is the latest you can finish an activity without delaying project completion. It is the same as the Latest Start time of the next activity. If there are two or more subsequent activities, this time is the same as the earliest of those “Latest Start” times. The is the earliest you can start an activity. It is determined by the earliest finish time of the precedent activity. If there are two or more precedent activities, this time is the same as precedent activity with the latest “Early Finish” time. This is the Latest Finish time minus the activity duration. Slack (S) is the difference, if any, between the earliest start (ES) and latest start times (LS) or the early finish (EF) and late finish (EF) times. S = LS - ES or S = LF - EF
Example: A homework Assignment Early Start Early Finish Late Finish Late Start Home- work #2 1 hour Slack If it takes one hour, the earliest you can complete this assignment is one hour after class ends. One hour after your late start time. The earliest you can start this assignment it is immediately after this class ends. You can wait until one hour before the class in which it is due to start it; in this case one week from now. The slack in this case would be one week, expressed in hours, since that is the unit of time used for the activities. It would be how long you could delay doing the assignment.
Precedence Relationships Precedence relationships determine a sequence for accomplishing activities. They specify that any given activity cannot start until its preceding activity or activities have been completed. In our AON approach, the nodes (circles) represent activities, and the arcs represent the precedence relationships between them. AON STU Activity On Node approach “S” precedes “T” which precedes “U” Nodes are simplified in the following examples.
Activity Relationships T U S T & U cannot begin until S has been completed. S T U S & T must be completed before U can be started.
Activity Relationships S T U V U & V can’t begin until S & T have been completed. S T U V U cannot begin until S & T have been completed. V cannot begin until T has been completed.
Activity Relationships STV U T & U cannot begin until S has been completed; V cannot begin until both T & U have been completed.
SV U This is a logic error. “S” cannot be an immediate predecessor of both “U” &”V” if “U” is also an immediate predecessor. Logic errors are hard to identify except on the network diagrams. If you see a triangle, then it is a logic error. Eliminate the short cut.
Hospital Upgrade (A sample project) Immediate Activity DescriptionPredecessor(s) Responsibility ASelect administrative and medical staff. BSelect site and do site survey. CSelect equipment. DPrepare final construction plans and layout. EBring utilities to the site. FInterview applicants and fill positions in nursing, support staff, maintenance, and security. GPurchase and take delivery of equipment. HConstruct the hospital. IDevelop an information system. JInstall the equipment. KTrain nurses and support staff.
ASelect administrative and medical staff.—Johnson BSelect site and do site survey.—Taylor CSelect equipment.AAdams DPrepare final construction plans & layout.BTaylor EBring utilities to the site.BBurton FInterview applicants and fill positions inAJohnson nursing, support staff, maintenance, and security. GPurchase and take delivery of equipment.CAdams HConstruct the hospital.DTaylor IDevelop an information system.ASimmons JInstall the equipment.E,G,HAdams KTrain nurses and support staff.F,I,JJohnson Hospital Upgrade (A sample project) Immediate Activity DescriptionPredecessor(s) *Responsibility *We won’t be using the “Responsibility” data, but it is important.
Hospital Upgrade Diagramming the Network Finish Start A B C D E FGHI J K Immediate Predecessors A–12 B–9 CA10 DB EB24 FA10 GC35 HD40 IA15 JE,G,H4 KF,I,J6 Activity Times (wks)
Hospital Upgrade FinishStart A B C D E F G H I J K Path Time (wks) A-I-K33 A-F-K28 A-C-G-J-K67 B-D-H-J-K69 B-E-J-K43 Paths are sequences of activities between a project’s start and finish.
Hospital Upgrade FinishStart A B C D E F G H I J K Path Time (wks) A-I-K33 A-F-K28 A-C-G-J-K67 B-D-H-J-K69 B-E-J-K43 Project Expected Time is 69 wks. The longest path is the critical path
Now we insert the time estimates. This is where we distinguish between PERT & CPM. CPM is used when activity times are Certain. Decision making under Certainty You are certain of the time each activity will require to complete. PERT is used when activity times are not certain. (Decision making under risk)
PERT is used when activity times are uncertain. Decision making under risk (“P” for probabilistic) Three time estimates are required for each activity. OPTIMISTIC TIME: Best time if everything goes perfectly REALISTIC TIME: Most likely time PESSIMISTIC TIME: A worst-case situation Expected Time = (B + 4M + P)/6 In this example, the most likely time is given a weight of 4, and the other two times (pessimistic and optimistic) are each given weights of 1. Software allows you to change these as needed, but the denominator must be the total of the weights given.
If the activity times are risky, the project team must make three time estimates for each activity and use PERT. Risky activity times enable the use of a probability distribution and risk assessment. For this example the times will be certain. (CPM) Activity slack is the maximum length of time that an activity can be delayed without delaying the entire project. (The difference between the earliest we can start an activity and the latest we can start it without delaying the project.) For the hospital we can’t go beyond 69 weeks since that is the project length. Hospital Upgrade Developing the schedule
Earliest Start Time (ES) for an activity is the earliest finish time of the immediately preceding activity. Earliest Finish Time (EF) for an activity is its earliest start time plus how long it takes to do it (estimated duration). Latest Start Time (LS) is the latest you can finish the activity minus the activity’s estimated duration. Latest Finish Time (LF ) is the latest start time of the activity that immediately follows it. (Latest start and finish times for each activity are computed starting at the project’s last activity completion time and working forward.) For simplicity, all projects start at time zero. Hospital Upgrade Developing the schedule
Earliest Start and Earliest Finish Times K6K6 C 10 G 35 J4J4 H 40 B9B9 D 10 E 24 I 15 Finish Start A 12 F 10 0 Earliest start time 12 Earliest finish time 0 9 9 33 9 1919 59 22 57 12 22 59 63 12 27 12 22 63 69
Earliest Start and Earliest Finish Times Critical Path The Critical Path takes 69 weeks K6K6 C 10 G 35 J4J4 H 40 B9B9 D 10 E 24 I 15 Finish Start A 12 F 10 0 9 9 33 9 1919 59 22 57 12 22 59 63 12 27 12 22 63 690 12 Path (wks) Time A-I-K33 A-F-K28 A-C-G-J-K67 B-D-H-J-K69 B-E-J-K43
K6K6 C 10 G 35 J4J4 H 40 B9B9 D 10 E 24 I 15 Finish Start A 12 F 10 0 9 9 33 9 1919 59 22 57 12 22 59 63 12 27 12 22 63 690 12 Latest Start and Latest Finish Times (Working from the last activity toward the first activity) 48 63 53 63 59 63 24 59 19 59 35 59 14 24 9 19 2 14 0 9 Latest finish time 63 69 Latest start time
Slack for activity “I” is 36 weeks (27-63) or (12-48)
A Gantt Chart is a project schedule, usually created by the project manager using computer software, that superimposes project activities, with their precedence relationships and estimated duration times, on a time line. Activity slack is useful because it highlights activities that need close attention. Slack is the amount of time an activity can be delayed without delaying the earliest start time of any activity that immediately follows. All activities on the critical path have zero slack and thus cannot be delayed without delaying the project completion.
Activity Slack Analysis Slack is the difference between LS and ES or the EF and LF. NodeDurationESLSSlack A12022 B9000 C1012142 D10990 E2493526 F10125341 G3522242 H4019 0 I15124836 J459 0 K663 0
There are always cost-time trade-offs in project management. You can completing a project early by hiring more workers or running extra shifts. There are often penalties if projects extends beyond some specific date, and a bonus may be provided for early completion. Crashing a project means expediting one or more activities to reduce overall project completion time and total project costs. Not all activities can be shortened.
Total Project Costs = direct costs + indirect costs + penalty costs Direct costs include labor, materials, and any other costs directly related to project activities. Indirect costs include administration, depreciation, financial, and other variable overhead costs. These can be reduced by reducing total project time. The shorter the duration of the project, the lower the indirect costs will be. Penalty costs are essentially late fees.
The objective of cost analysis is to determine the project schedule that minimizes total project costs. When crashing an activity or project, extra money is spent on direct costs, but money is saved on indirect costs and possible penalties. A minimum-cost schedule is determined by starting with the normal time schedule and shortening activities along the critical path in such a way that the costs of crashing (direct costs) do not exceed the savings in indirect costs and penalty costs. Hospital Upgrade Minimizing Costs
a. Determine the project’s critical path(s). b. Find the activity or activities on the critical path(s) with the lowest cost of crashing (shortening) per week. c. Reduce the time for this activity until… a. it cannot be further reduced, or b. another path becomes critical, or c. the increase in direct costs exceed the savings that result from shortening the project. (shortening lowers indirect costs) d. Repeat this procedure until the total project costs are no longer decreased. Sophisticated project management software will do this. Hospital Upgrade Minimum Cost Schedule
Of the five critical-path activities, the contractor says D and H cannot be shortened. J is the least costly to shorten at $1000 a week. Contractor says it can be shortened to 1 week.
Risk is a measure of the probability (and consequences) of not reaching completing a project on time. A major responsibility of the project manager at the start of a project is to develop a risk-management plan. A Risk-Management Plan identifies the key risks to a project’s success and prescribes ways to circumvent them.
1. Service/Product Risks: If the project involves new service or product, several risks can arise. Market risk comes from competitors. Technological risk can arise from advances made once the project has started, rendering obsolete the technology chosen for service or product. Legal risk from liability suits or other legal action. 2. Project Team Problems: Poor member selections and inexperience, lack of cooperation, etc. 3. Operations Risk: Information inaccuracy, miss- communications, bad project timing, weather…
What is the probability that our sample project will finish in 69 weeks as scheduled? If the answer is “100%” the only answer for “Why” is: Because we used CPM! (This means we were certain of all of our activity times.) If we weren’t certain, we should have used PERT You can’t do risk analysis if you use CPM
With PERT’s three time-estimates, we get a mean (average) time and a variance for each activity and each path. We also get a project mean time and variance. In order to compute probabilities (assuming a normal distribution) all we need are the activity means and variances. most computer packages calculate this for you.
The probability of a project being completed by a given date is a function of the mean activity times and variances along the critical path(s). The probability of any specific activity being completed by a given date is a function of the mean activity times and variances along the longest path leading up to that activity. If you have more than one critical path, focus on the path with the greatest variance. A near-critical path may also be a problem, depending on the mean and variance of it’s activities.
A Beta distribution is often used for the three estimates of each activity This allows skewed distributions. Optimistic------Most likely -----------------------Pessimistic (3 ------------- 5 ---------------------------------- 11) Normal distributions are needed for probabilities. A distribution of activity-means is a normal distribution, even though each activity time may be a beta distribution.
Beta Distribution Mean mab Time Probability Pessimistic Optimistic Each activity may have its three time estimates skewed (Beta Distribution), but the path along which this activities lie has a normal distribution and thus a mean and variance.
Assume a PERT project critical path takes 40 days, and that the variance of this path is 2.147 You wish to know the probability of the project going over 42 days. Compute the standard deviation of the critical path. (Take the square root of the variance of 2.147.) Std. Dev. = 1.465 POM/QM software gives you the variance of the critical path. Compute the Z value: Z = (absolute time difference) / Std. Dev. In this example, Z = (42 days - 40 days) / 1.465 = 1.365 Look up the Z value of 1.365 in a Normal Distribution table to get the probability of the project taking 42 days. Subtract it from 100% to get the probability of going over 42.
Look up the Z value (1.365) in the table of normal distribution. (In this case you need to interpolate between the Z values of.9313 and.9147).9139 or 91.39% is the probability of the project taking up to 42 days. Going over 42 days is thus 100 - 91.39 = 8.61%
Project duration (weeks) 4042 Probability of meeting the schedule in 42 weeks is 91.39% Length of critical path is 40 weeks Normal distribution: Sum of Variances along critical path = 2.147 Std. Dev. = 1.465 weeks Probability of exceeding 42 weeks is 8.61%
2 = (variances of activities along critical path) z = T – C 2 2 = 1.78 + 1.78 + 2.78 + 5.44 + 0.11 = 11.89 z = 72 – 69 11.89 What is the Probability of it taking 72 weeks? Critical Path = B - D - H - J – K = 69 weeks T = 72 weeks C = 69 weeks Hospital Upgrade A 69-week Project Look up Z value in normal distribution table P z =.8078 or 80.78% (Probability of it taking 72 weeks) Z = 0.870 Critical Path Variance
Look up the Z value (0.870) in the table of normal distribution..8078 or 80.78% is the probability of the project taking up to 72 wks. Going over 72 weeks would be 100 – 80.78 = 19.22%
Project duration (weeks) 6972 Probability of taking 72 weeks is 0.8078 or 80.78% Probability of taking 72 weeks is 0.8078 or 80.78% Length of critical path is 69 weeks Length of critical path is 69 weeks Normal distribution: Mean = 69 weeks; = 3.45 weeks Probability of exceeding 72 weeks is 0.1922 or 19.22% Probability of exceeding 72 weeks is 0.1922 or 19.22% Hospital Upgrade Probability of Completing Project On Time
Excessive Activity Duration Estimates: Many time-estimates come with a built-in cushion that management may not realize. Latest Date Mentality: The tendency for employees to procrastinate until the last moment before starting. Failure to Deliver Early, even if the work is completed before the latest finish date.
Path Mergers occur when two or more activity paths combine at a particular node. Both paths must be completed up to this point, which will eliminate any built-up slack. Multitasking is the performance of multiple project activities at the same time. Work on some activities is often delayed for other work. Loss of Focus by a manager can happen if the critical path changes frequently.
Enables Resource Management & Allocation You can move slack resources to critical points Focuses on your critical activities Visualize relationships (The big picture) Enables Cost analysis
Can be complex to set up relationships in large project Time estimates are often biased. Near critical paths are easily overlooked.
Gives more flexibility to project planning than PERT/CPM Allows any individual activity to either be completed or not completed (Succeed or fail) PERT & CPM both require all activities be successfully completed. GERT does not require this. GERT Allows looping back (redoing an activity) or skipping an activity entirely. There are computerized GERT packages.