Project Information

Project:	PIMS
Project Time-frame:	1 July 2004 - 1 July 2009
Attached worksheets:	Plan > Work Breakdown Structure Plan > Resource needs Stakeholder list Quality plan
Related Documents:	Project proposal > Target audience and benefits Risks Software development methodology Glossary

Process impact: This plan will be used to evaluate and manage the project. The headings used, and associated documents, are as specified in the CCLRC's Corporate Project Management Handbook. Key assumptions that affect the plan should be documented here.

Summary of Methodology

What general development approach will be used?

This project will use Rolling Wave planning with operational prototyping. There will be more than one release a year. For more information see the Software Development Methodology.

Change Control

TBD.

Once a requirement has been baselined, release scheduling, software design, and later coding all rely on it, so there is a real cost of change. These costs are often large enough to make projects fail.

We have a "Change Control Board" to review proposed changes to the data model. It will also be necessary to assign responsibility for approving changes to requirements. The project manager will report an estimated cost before a change is approved.

Organisation Breakdown Structure

Safety plan

There are no special safety issues during the implementation of the software. It will be necessary to visit laboratories during requirements discovery - lab safety rules must be followed.

There are some safety requirements for the system to be delivered. These will be designed for, implemented, and tested appropriately.

Cost Breakdown Structure

Our budget is dominated by staff costs. We will not need to separate cost planning from labour resource planning.

Contingency

We have a fixed budget, fixed staffing levels, and a fixed time scale. The main flexibility in the project is in the scope of the facilities delivered. In addition we may attract new partners. We will take the technical measures necessary to keep a door open for new collaborators.

Project Planning Dependencies

Does this project conflict or compete for resources with any other project?

No, this is the only project that we are working 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, we predict that team members will spend an average of 20% of their time planning future releases during this release time frame.

Does this project depend on the success of any other project?

Yes, for post-crystallization facilities. See stakeholders list.

Does any other project depend on this project?

No, project is not producing any components that will be used in other current projects.

Are there any other important dependencies that will affect this project?

Yes. See risks list.