Exam #2 Flashcards
Project Schedule importance
key technical aspect of project management serves as the main integration point for planning efforts and includes most project plans
Project Schedule steps
is a tool that
1)merges all of the work to be performed(WBS)
2) their estimated duration/effort
3) their task relationships(Activity on node)
4)assigned resources,
5) risks response
to a calendar
Final Project schedule should be
complete (all WBS), accepted(by stakeholders) , realistic (time expectations, formal (documented)
time decomposition
breaking down project deliverables into smaller and more manageable activities
analogous estimating
top down estimating; history
parametric estimating
multiplying work to be done by a known productivity rate
contingency reserves
used for known unknowns by project manager
management reserves
used for unknown unknown by management sh
shorten schedule
crashing:add resources to critical path activities only
fast tackling: perfrom critical path activities in parallel
process improvements: gaining over productivity
overtime: get extra time
critical path
The earliest path through the project, given
the current task relationships and estimated
durations
mandatory dependencies
hard dependencies or logic
discretionary dependencies
permed way of doing things
external dependencies
project depended on external environment factors(weather, permits)
straight line depreciation
Ann. Dep. = (Purchase Price – Salvage Value) / Usable Life
Developing initial budget
use bottom up approach and excel
estimating the budget phases
initial phase: ROM (-50,+50)
planning phase: definitive estimate (-5,+10)
Estimating costs
analogous estimating: top-down estimating using history
parametric estimating: multiply the quantity of work to be performed by a productivity rate
Finalizing budget
once the project schedule nears completion and actual resources have been identified
project control
processes that enure that project objectives are met by monitoring and measuring progress regularly to identify variances from plan so that corrective action can be taken if necessary
Principles of project control
PDA (prevention, detection, action)
Management fundamentals for project control
pay attention early (15% completion rule almost no project recovers from a variance at the 15% completion point
Powerful technique for porject control
milestone and checkpoints
Performance reporting
answer 3 big questions:
Where do we stand
what variances exist and how are we solving them
has the forecast changed
variances responses
take corrective action, ignore small problems, cancel the project if necessary, reset baselines,