Checklist for Contents and Notations of Project Plans
This document helps project managers to plan a software development project. It contains questions concerning the contents of a project plan and the notations used.
- Does the plan contain the definition of the project, including a statement of its objectives and with reference to related projects?
- Have you described the scope of development?
- Have you developed a time scheduling for your project identifying the tasks to be performed, also including resource constraints?
- Have you divided the project into phases according to a convenient phase model?
- Does the definition of development phases include definitions of required inputs and outputs and how the outputs will be verified?
- Have you defined milestones?
- Have you determined the results that have to exist for each milestone?
- Is it possible to verify whether the results meet the relevant requirements?
- Do the results contain or reference acceptance criteria for forwarding to subsequent phases?
- Is it possible to finish each task in the given time?
- Do you in advance worry about any problems with the given deadlines?
- Have you planned for buffers in case deadlines are not met?
- Have you planned procedures for action in case deadlines are not met?
- Have you planned for progress reviews to ensure that outstanding resource issues are resolved and to ensure effective execution of the development plan?
- Have you defined the date of acceptance testing?
- Have you established budgets for the project?
- Have you respected internal meetings?
- Have you established staffing estimates?
- Have you planned the staff according to their abilities?
- Have you developed estimates of the computing resources required to operate and maintain the system?
- Has the customer agreed to the time schedule and the resources planned?
- Do you in advance worry about any personnel bottleneck?
- Does the plan include a description of development methods and tools to be used during the project?
- Does the plan include rules, practices, and conventions for development?
- Have you determined the programming language?
- Have you determined the documents to be prepared?
- Have you defined the organizational structure of the project, including the team structure and use of sub-contractors?
- Have you stated the persons responsible for:
- different phases in the project?
- setting up processes to prevent errors?
- for identifying and recording quality problems?
- for controlling further processing until problem is resolved?
- Have you described the interfaces between
- project management and development,
- customer and project staff,
- senior management and project management?
- Have you used the introduced notation (e.g. network plans)?
- Is the notation suitable to mark critical deadlines?
- Does the notation give the possibility to show schedule overruns?
- Does the plan include related plans, e.g.
- quality plan
- configuration management plan
- documentation plan
- integration, and
- test plan?
Fairley, R.E.: Software Engineering Concepts. McGraw-Hill Book Company, New York 1985.
Frühauf, K.; Ludewig, J. und Sandmayr, H.: Software-Projektmanagement und Qualitätssicherung. vdf Verlag, Zürich 1988 und Teubner Verlag Stuttgart 1988.
Rook, P.: Project planning and control. McDermid, J.A. 1991, Software Engineer's reference book, chap. 27, Butterworth-Heinemann, Oxford/England 1994.