Project Plan
Project Information
| Project: |
Clapham |
| Project Time-frame: |
Jan 07 - Dec 07 |
| Attached worksheets: |
|
| Related Documents: |
|
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 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 project team will consist of Martyn Winn, Peter Briggs, Francois Remacle, Norman Stein, Ronan Keegan.
- Specific Roles (TBD)
- What development and collaboration tools will be use?
- We plan to use the following tools
extensively through out the project:
- Project website (this)
- 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
- How will this plan be updated?
- This project plan will be updated as needed throughout the
project. It will be placed under version control and instructions
for accessing it will be on the project
website. Any change to the plan will cause an automatic
notification to be sent to a project mailing list.
Work Breakdown Structure and Estimates
TODO: List tasks that will be needed for this project. Keep
dividing tasks into subtasks until you feel that you have enough
detail to expose risks and make reasonable estimates in ideal
engineering hours.
TIP: Label each step uniquely to show its position in the WBS,
e.g., Step 1.1.4.A. Use numbers for steps that you intend to do
in sequence, and use letters for steps that you intend to do in
parallel. E.g., Step 1.1 comes before Steps 1.2.A and 1.2.B, but
those two steps may be done in parallel, and Step 1.3 will be done
after all 1.2.* steps have been finished. Don't worry about
renumbering if you delete a step.
| Step | Description | Estimate |
|---|
| 0. | Preparation | |
|---|
| 1. | Stage 1 - modular updates | |
|---|
| 2. | Stage 2 - downloads pages outline | |
|---|
| 3. | Stage 3 - import of libraries | |
|---|
| 4. | Stage 4 - import of programs | |
|---|
| 5. | Stage 5 - import of interfaces | |
|---|
| 6. | Stage 6 - testing | |
|---|
| 7. | Postmortem report | |
|---|
| Total | 1.25 years |
|---|
Deliverables in this Release
TODO: List project deliverables in detail, with delivery dates.
| Deliverable |
Description |
Date |
| CCP4 6.1
| update of ccp4 suite
| Sept 30. 2007
|
| CCP4 6.0.99 |
test release |
July 30. 2007 |
Risk Management
TODO: List and rank the major risks of this project, and what you plan to
do to mitigate each risk. If you don't plan to do anything to
mitigate the risk, state that. Use the risk list below, or the
risks worksheet.
Please see the risks worksheet.
Project Planning Dependencies
- Does this project conflict or compete for resources with any
other project?
- Yes, there is a clash with the support of the
suite, which has hopefully been included in the timetable.
on.
- Are the same human or machine resources allocated to maintenance
of past versions and/or planning of future versions during this
release time period?
- Yes, but only indirectly through the maintenance of
the suite as a whole.
- Does this project depend on the success of any other
project?
- No, this project stands alone.
- Does any other project depend on this project?
- Yes, to a certain extent the data preparation
for experimental phasing.
- Are there any other important dependencies that will affect this project?
- Yes, the clipper libraries.