Project Proposal

Project Information

Project:	Clapham
Project Time-frame:	Jan 2007 to Dec 2007
Summary:	Delivery of CCP4 version 6.1, including use of modules for intermediate releases, and new functionality. buccaneer rampage PISA crunch2, pmf phaser-EP iMosflm pointless/othercell refmac6 MrBUMP XIA2 OASIS06 idiffdisp/diffraction image autodep
Attached Worksheets:	Project Proposal > Target audience and benefits
Related Documents:	Project plan > Resource needs Glossary

Process impact: This proposal, along with drafts of related documents, will be used by management to determine whether or not to approve work on this project. A clear and precise project plan helps set expectations that will be used later to evaluate the success of the project.

Background and Motivation

TODO: Replace the example text below with text that describes your project. What are the needs or problems that you are trying to address? Why do these needs (still) exist? Why are these problems worth solving? Who is the customer? Write 2-4 paragraphs.

What is the setting and history behind this project?: Next in a series of CCP4 releases, although the plan is to extend the use of intermediary updates.
What is the problem to be addressed?: Developments have continued apace since the last release.
What are some current approaches to this problem?
Why is this problem worth solving or worth solving better?
How will this product be better than previous approaches?: Much more functionality.
Where is there more information on this problem?: The following pages provide additional background and motivation:

Goal

What is the goal of this project?

TIP: This should be relatively short since you can reference terms defined above.

Release of CCP4 6.1

What are the defining features and benefits of this product?

buccaneer
rampage
PISA
crunch2, pmf
phaser-EP
iMosflm
pointless/othercell
refmac6
MrBUMP
XIA2
OASIS06
idiffdisp/diffraction image
autodep

Where are other documents that further explain the goal of this project?

Scope

TODO: Replace the sample text below with a clear statement of the scope of your project. What are the high-level things that you plan to do, and that you will not do? What are your important simplifying assumptions? Try to guard against reasonable misunderstandings that might arise if you did not explain the scope. It can take the form of a paragraph, bullet list, in/out list, and/or UML context diagram.

In Scope	Out of Scope

Deliverables

TODO: Briefly list project deliverables. When you are done, what will you deliver to the customer? This can be copied from the draft project plan and simplified to reduce technical detail.

CCP4 6.1
downloads pages
documentation for programs
update procedure
update warnings

Risks and Rewards

TODO: Briefly list and rank major risks. Risks are detailed in the draft project plan. For this proposal document, you should select the most important risks from the project plan and explain them in non-technical terms.

What are the main risks of this project?

Usual creep in functionality due to delays.
Lose of staff effort to other projects, leaving.
Lose of expertise for above reason.

What are the main rewards if this project succeeds?

Increased functionality for users, and modular design that should reduce pressure for major releases.

Project Plan

See attached draft of project plan and resource needs.

TODO: Check for words of wisdom and discuss ways to improve this template. Or, evaluate the ReadySET Pro professional project proposal template.

Company Proprietary