Date post: | 17-Jan-2016 |
Category: |
Documents |
Upload: | avis-hope-gregory |
View: | 214 times |
Download: | 1 times |
Project Management
McGraw-Hill/Irwin Copyright © 2012 by The McGraw-Hill Companies, Inc. All rights reserved.
You should be able to:1. Discuss the behavioral aspects of projects in terms of
project personnel and the project manager2. Explain the nature and importance of a work breakdown
structure in project management3. Give a general description of PERT/CPM techniques4. Construct simple network diagrams5. List the kinds of information that a PERT or CPM analysis
can provide6. Analyze networks with deterministic times7. Analyze networks with probabilistic times8. Describe activity ‘crashing’ and solve typical problems
Instructor Slides 17-2
ProjectsUnique, one-time operations designed to
accomplish a specific set of objectives in a limited time frame
Examples:The Olympic GamesProducing a movieSoftware developmentProduct developmentERP implementation
Instructor Slides 17-3
Instructor Slides 17-4
Projects go through a series of stages– a life cycle
Projects bring together people with a diversity of knowledge and skills, most of whom remain associated with the project for less than its full life
Organizational structure affects how projects are managed
Instructor Slides 17-5
The project manager is ultimately responsible for the success or failure of the project
The project manager must effectively manage: The work The human resources Communications Quality Time Costs
Instructor Slides 17-6
Behavioral problems can be created or exacerbated by Decentralized decision making Stress of achieving project milestones on time and
within budget Surprises
The team must be able to function as a unit Interpersonal and coping skills are very important Conflict resolution and negotiation can be an important
part of a project manager’s job
Instructor Slides 17-7
Many problems can be avoided or mitigated by: Effective team selection Leadership Motivation Maintaining an environment of
IntegrityTrustProfessionalism
Being supportive of team efforts
Instructor Slides 17-8
Project championA person who promotes and supports a project
Usually resides within the organizationFacilitate the work of the project by ‘talking up’
the project to other managers, and who might be asked to share resources with the project team as well as employees who might be asked to work on parts of the project
The project champion can be critical to the success of a project
Instructor Slides 17-9
WBSA hierarchical listing of what must be done
during a projectEstablishes a logical framework for identifying the
required activities for the project1. Identify the major elements of the project2. Identify the major supporting activities for each
of the major elements3. Break down each major supporting activity into a
list of the activities that will be needed to accomplish it
Instructor Slides 17-10
Instructor Slides 17-11
Instructor Slides 17-12
PERT (program evaluation and review technique) and CPM (critical path method) are two techniques used to manage large-scale projects
By using PERT or CPM Managers can obtain:1. A graphical display of project activities2. An estimate of how long the project will take3. An indication of which activities are most critical to timely
project completion4. An indication of how long any activity can be delayed
without delaying the project
Instructor Slides 17-13
Network diagram Diagram of project activities that shows sequential
relationships by use of arrows and nodes Activity on arrow (AOA)
Network diagram convention in which arrows designate activities
Activity on node (AON)Network convention in which nodes designate activities
Activities Project steps that consume resources and/or time
Events The starting and finishing of activities
Instructor Slides 17-14
DeterministicTime estimates that are fairly certain
ProbabilisticTime estimates that allow for variation
Instructor Slides 17-15
Finding ES and EF involves a forward pass through the network diagram Early start (ES)
The earliest time an activity can startAssumes all preceding activities start as early as possible
For nodes with one entering arrow ES = EF of the entering arrow
For activities leaving nodes with multiple entering arrows ES = the largest of the largest entering EF
Early finish (EF)The earliest time an activity can finish
EF = ES + t
Instructor Slides 17-16
Finding LS and LF involves a backward pass through the network diagram Late Start (LS)
The latest time the activity can start and not delay the project The latest starting time for each activity is equal to its latest
finishing time minus its expected duration: LS = LF - t
Late Finish (LF) The latest time the activity can finish and not delay the project
For nodes with one leaving arrow, LF for nodes entering that node equals the LS of the leaving arrow
For nodes with multiple leaving arrows, LF for arrows entering node equals the smallest of the leaving arrows
Instructor Slides 17-17
Slack can be computed one of two ways:Slack = LS – ESSlack = LF – EF
Critical pathThe critical path is indicated by the activities
with zero slack
Instructor Slides 17-18
Knowledge of slack times provides managers with information for planning allocation of scarce resources Control efforts will be directed toward those activities
that might be most susceptible to delaying the project
Activity slack times are based on the assumption that all of the activities on the same path will be started as early as possible and not exceed their expected time
If two activities are on the same path and have the same slack, this will be the total slack available to both
Instructor Slides 17-19
The beta distribution is generally used to describe the inherent variability in time estimates
The probabilistic approach involves three time estimates: Optimistic time, (to)
The length of time required under optimal conditions Pessimistic time, (tp)
The length of time required under the worst conditions
Most likely time, (tm)The most probable length of time required
Instructor Slides 17-20
The expected time, te ,for an activity is a weighted average of the three time estimates:
The expected duration of a path is equal to the sum of the expected times of the activities on that path:
6
4 pmoe
tttt
path on the activities of timesexpected ofmeanPath
Instructor Slides 17-21
The standard deviation of each activity’s time is estimated as one-sixth of the difference between the pessimistic and optimistic time estimates. The variance is the square of the standard deviation:
Standard deviation of the expected time for the path
2
2
6
op tt
pathon activities of Variancespath
Instructor Slides 17-22
Knowledge of expected path times and their standard deviations enables managers to compute probabilistic estimates about project completion such as:The probability that the project will be
completed by a certain timeThe probability that the project will take
longer than its expected completion time
Instructor Slides 17-23
deviation standardPath
meanPath - timeSpecifiedz
Instructor Slides 17-24
A project is not complete until all project activities are complete
It is risky to only consider the critical path when assessing the probability of completing a project within a specified time. To determine the probability of completing the project within a
particular time frame
Calculate the probability that each path in the project will be completed within the specified time
Multiply these probabilities
The result is the probability that the project will be completed within the specified time
Instructor Slides 17-25
IndependenceAssumption that path duration times are
independent of each otherRequires that
1. Activity times are independent2. Each activity is on only one path
The assumption of independence is usually considered to be met if only a few activities in a large project are on multiple paths
Instructor Slides 17-26
When activity times cannot be assumed to be independent, simulation is often used Repeated sampling is used
Many paths are made through the project networkIn each pass, a random value for each activity time is
selected based on the activity time’s probability distribution
After each pass, the project’s duration is determinedAfter a large number of passes, there are enough data
points to prepare a frequency distribution of the project duration
Probabilistic estimates of completion times are made based on this frequency distribution
Instructor Slides 17-27
Budget control is an important aspect of project managementCosts can exceed budget
Overly optimistic time estimatesUnforeseen events
Unless corrective action is taken, serious cost overruns can occur
Instructor Slides 17-28
Activity time estimates are made for some given level of resources
It may be possible to reduce the duration of a project by injecting additional resources Motivations:
To avoid late penaltiesMonetary incentivesFree resources for use on other projects
Instructor Slides 17-29
Crashing Shortening activity durations
Typically, involves the use of additional funds to support additional personnel or more efficient equipment, and the relaxing of some work specifications
The project duration may be shortened by increasing direct expenses, thereby realizing savings in indirect project costs
Instructor Slides 17-30
To make decisions concerning crashing requires information about:
1. Regular time and crash time estimates for each activity
2. Regular cost and crash cost estimates for each activity
3. A list of activities that are on the critical pathCritical path activities are potential candidates for crashing
Crashing non-critical path activities would not have an impact on overall project duration
Instructor Slides 17-31
General procedure:
1. Crash the project one period at a time
2. Crash the least expensive activity that is on the critical path
3. When there are multiple critical paths, find the sum of crashing the least expensive activity on each critical path
If two or more critical paths share common activities, compare the least expensive cost of crashing a common activity shared by critical paths with the sum for the separate critical paths
Instructor Slides 17-32
Instructor Slides 17-33
Among the most useful features of PERT:1.It forces the manager to organize and quantify
available information and to identify where additional information is needed
2.It provides the a graphic display of the project and its major activities
3.It identifiesa. Activities that should be closely watchedb. Activities that have slack time
Instructor Slides 17-34
Potential sources of error:1. The project network may be incomplete2. Precedence relationships may not be correctly
expressed3. Time estimates may be inaccurate4. There may be a tendency to focus on critical path
activities to the exclusion of other important project activities
5. Major risk events may not be on the critical path
Instructor Slides 17-35
To better manage projects, managers need to be aware of certain aspects of the project:1. Time estimates are often pessimistic and with attention
can be made more realistic2. When activities are finished ahead of schedule, that
fact may go unreported, so managers may be unaware of resources that could potentially be used to shorten the critical path
The critical chain is analogous to the critical path of a network
A key feature of the critical chain approach is the use of various buffers Feeding Project Capacity
Instructor Slides 17-36
Technology has benefited project management CAD
To produce updated prototypes on construction and product-development projects
Communication softwareHelps to keep project members in close contactFacilitates remote viewing of projects
Project management softwareSpecialized software used to help manage projects
Assign resources Compare project plan versions Evaluate changes Track performance
Instructor Slides 17-37
Advantages include: Imposes a methodology and common project
management terminology Provides a logical planning structure May enhance communication among team members Can flag the occurrence of constraint violations Automatically formats reports Can generate multiple levels of summary and detail
reports Enables “what if” scenarios Can generate a variety of chart types
Instructor Slides 17-38
Risks are an inherent part of project management Risks relate to occurrence of events that have undesirable
consequences such asDelaysIncreased costsInability to meet technical specifications
Good risk management involvesIdentifying as many risks as possibleAnalyzing and assessing those risksWorking to minimize the probability of their occurrenceEstablishing contingency plans and budgets for dealing
with any that do occur
Instructor Slides 17-39
Projects present both strategic opportunities and risks It is critical to devote sufficient resources and attention to projects Projects are often employed in situations that are characterized by
significant uncertainties that demandCareful planningWise selection of project manager and teamMonitoring of the project
Project software can facilitate successful project completionBe careful to not focus on critical path activities
to the exclusion of other activities that may become critical
It is not uncommon for projects to fail When that happens, it can be beneficial to examine the probable
reasons for failure
Instructor Slides 17-40