A pilot project is one where you try out your new ideas. In the context of implementing process and tools, this means that you try new process and new tools. 

It implies that you may add additional resources, use key people, and adjust budget and plans accordingly. It also implies that you monitor the project extra carefully, because it's by evaluating and learning from the pilot project that you'll start using the new process and tools on real projects.   

Select as your pilot:

  • A complete software-development project, considered low risk from a technical and financial perspective. 

  • The first complete iteration of a real software-development project, with the caveat that the main focus is on learning and improving the process, not on developing the software.

An alternative may be to select an intended software-development project, which is considered low risk from a technical and financial perspective. That way, you limit the scope of the project and make it your pilot project. 

To get the most out of a pilot project, it's important that the pilot uses the real development environment and that there is a real project pressure. 

The pilot project needs to be staffed with some key people who:

  • Have the ear of the masses

  • Can act as a mentor

  • Are considered an expert in some area

It's difficult to give precise guidelines regarding time and resources. However, the following figures are common for many pilot projects:

  • Fewer than 10 people

  • Less than four months

  • One mentor 50%

Here is one suggested definition of the term pilot project: 

A pilot project (noun) is an activity planned as a test or trial.



© Copyright IBM Corp. 1987, 2004. All Rights Reserved.

Rational Unified Process   2003.06.13