Project Plan
Project Information
Project: PROJECTNAME
Project Time-frame: STARTDATE - ENDDATE
Attached worksheets: Plan > Resource needs
Related Documents: Project proposal > Target audience and benefits
Software development methodology
Glossary
Process impact: This plan will be used to evaluate and manage the project. Key assumptions that affect the plan should be documented here. The project plan should be updated throughout the life-time of the project.
TODO: Fill in the information above and below. Add or remove rows as needed. Use the worksheet to help identify and scope resource needs.
Summary of Project
ONE OR TWO SENTENCES HERE. For more information see the Project proposal.
IF YOU PLAN TO ORGANIZE YOUR WORK ACCORDING TO A ROUGH BREAKDOWN OF SOFTWARE COMPONENTS, BRIEFLY DESCRIBE THOSE COMPONENTS HERE. FOUR TO TEN BULLETS.
Summary of Methodology
What general development approach will be used?
THREE TO FIVE SENTENCES OR BULLETS HERE. COVER GENERAL APPROACH, IMPORTANT ASSUMPTIONS, KEY PRACTICES, AND PROJECT COORDINATION CONTROLS. For more information see the Software Development Methodology.
How will the project team be organized?
The development team will consist of ...
The change control board will consist of ...
What development and collaboration tools will be use?
We plan to use the following tools extensively through out the project:
Project website
Project mailing lists
Issue tracking system
Version control system
Automated build system
Automated unit test system
How will changes be controlled?
Requests for requirements changes will be tracked in the issue tracker
The change control board (CCB) will review requested changes and authori ...