Lecture 4 - Project Planning and Management (Compatibility Mode) PDF
Lecture 4 - Project Planning and Management (Compatibility Mode) PDF
Lecture 4
outline
• several aspects:
› develop scheme for scheduling and committing resources
› results in map showing product design process activities scheduled
› procedure to develop needed information and distributing in to the
right people at the right time
• 1) identify tasks
› WBS
› generates check list – nothing is forgotten
› specific as possible
› level of detail depends on purpose and who will use it
» too little – not enough planning
» too much – obscures tasks and milestones
› large projects:
» produce un-detailed schedule covering entire project
• supplemented by more detailed schedules
• become clearer over time
• 2) objectives for each task
› each task characterized by clear objective
› information contained in deliverables
five steps in planning
• 3) estimate personnel, time, other resources
› identify who and for how long involved in meeting objectives
› estimate total time
• “design takes time”
› usually 2X original estimate
» pessimistic view:
• take best estimate, double it, increase units by one step
• 1 day = 2 weeks!
five steps in planning
• bar/Gantt chart
› list activities and times
› bars indicate start/finish
» hollow – planned
» filled – actual
› advantage – shows start/finish
› disadvantage – relationships between activities
five steps in planning
five steps in planning
• 5) estimate costs
project management
• monitoring
› schedules used for monitoring
› don’t have to be rigid
» things change
» serves as a yardstick to measure progress, to show where and
how to change plans
› progress must be continually monitored
» where are we?
» can we meet commitments?
• if not, must divert/reallocate resources, revise schedules
» don’t always want to do, but is mandatory
» combine with technical reviews
effective project management
• controlling
› adjustment of work when needed
» to meet overall time and money commitments
› must take appropriate action in light of information gained from
monitoring
› scheduling/monitoring not control
» must be deliberately exercised
• what actions must be taken to keep project on schedule
• implementation of these actions
› most common error
» not acting soon enough
• delayed due to:
– poor monitoring
– not facing facts
– e.g. solution to problem around corner
– but: when it becomes clear that won’t work, must stop
– redirect efforts – saves time and money
questions?