A project is behind schedule. Possible management actions include revising the completion date, holding to the planned completion date but hiring more staff, and holding to the planned completion date but working current staff overtime. What are the implications of the alternatives?
How much of the development effort should be expended on quality assurance and how does that affect completion time and total cost?
What is the impact of different distributions of effort among project phases (e.g., should the division of effort between development and testing be 80:20 or 60:40 percent)?
The major issues which the project plan addresses are:
Schedule and milestones
Software quality assurance plans
Configuration management plans
Project minotoring plans
Risk management plans
Major cost estimation techniques System level focus, efficient Less detailed basis; less stable Bottom-up More detailed basis More stable Fosters individual commitment May overlook systems costs Requires more effort Method Strengths Weaknesses Algorithmic Objective, repeatable, analysable formulae Efficient, good for sensitivity analysis Objectively calibrated to experience Subjective inputs Assessment of exceptional circumstances Calibrated to past, not future Expert judgement Assessment of representativeness interactions, exceptions No better than participants Biases, incomplete recall Analogy Based on representative experience Representativeness of experience Parkinson Correlates with some experience Re-enforces poor practice Price-to-win Often gets contract! Generally produces large overruns Top-down