Object Oriented Software Engineering   View all facts   Glossary   Help
subject > representation > document > project plan
Next documentrelease notes    Updocument    Previous documentproblem statement   

project plan
subjectfact 
project planhas definition A document used in project management describing all aspects of the project's process, including the process model, tasks, risks, cost estimates, team structure and schedule2001-08-30 14:57:08.0
describes the overall process model2001-08-30 14:57:08.0
describes the problem to be solved, as in the requirements document2001-08-30 14:57:08.0
describes the proposed team structure, the skills needed on that team, the plan for on-going training and the allocation of general responsibilities to team members2001-08-30 14:57:08.0
describes the risks and difficulties that are expected to be most critical to this project, or to specific subsystems and how they are to be monitored and resolved2001-08-30 14:57:09.0
describes the stakeholders2001-08-30 14:57:09.0
divides the system into subsystems and releases, that can be allocated to people or teams2001-08-30 14:57:09.0
gives a brief history of the project to date - you can update this as the project proceeds2001-08-30 14:57:09.0
gives references to related projects and any documents produced so far, such as requirements definitions2001-08-30 14:57:09.0
includes Gantt and PERT charts showing the allocations of tasks to people, the periods of time they will work on each task, as well as the critical path(s)2001-08-30 14:57:09.0
includes the present cost estimates for the tasks and subsystems, showing all calculations, and including pessimistic and optimistic values2001-08-30 14:57:09.0
is a subtopic of 11.6 - Contents of a Project Plan2001-08-30 14:57:09.0
is a kind of document2001-08-30 14:57:09.0
lists the tasks to be completed for each subsystem and release2001-08-30 14:57:09.0
outlines the techniques to be employed for requirements gathering, design, implementation, quality assurance, change management; risk management, and ongoing project management; documents to be produced, including contents of these documents; ways to measure and track the project2001-08-30 14:57:09.0
should contain
      Purpose
    1. Background information
    2. Processes to be used
    3. Subsystems and planned releases
    4. Risks and challenges
    5. Tasks
    6. Cost estimates
    7. Team
    8. Schedule and milestones
2001-08-30 14:57:09.0
states the business objectives for the project, including quantified anticipated benefits2001-08-30 14:57:09.0
documentshould be written for a particular audience2001-08-30 14:55:21.0

Next documentrelease notes    Updocument    Previous documentproblem statement