Prototyping
Using prototypes to gather requirements

In many cases, the "sample" does not survive its initial use. The quality of the "sample" is not indicative of the intended quality of the final product.

Prototyping can be an expensive exercise, but the requirements acquired from observing the system in action may provide requirements that help bring the project to a successful conclusion. By speeding up the requirements gathering process, prototyping may end up saving more money than it costs.

Prototyping also serve as demonstration activity. Stakeholders who get a chance to see the sample in action--flaws and all--will often walk away with a stronger sense of the project's goals and a feeling that progress has been made. Where investors are involved, this may mean additional funding to keep the project going.

Prototyping also works when developing a service. In this case, we may refer to a pilot program rather than a prototype. Pilots run through simulated scenarios or short-term testing periods, and often require decisions or actions on the part of the participants.

If viewed with too much importance, prototyping could lead to a false sense of accomplishment and an overly optimistic view of the project's final results. However, these possibilities can be controlled through proper communication with stakeholders.

A picture may be worth a thousand words, but a prototype could be worth millions.

ClearlyPUT's Requirementing process uses a prototype to capture requirements.

Summary

Prototyping--either as a physical object (prototype) or a simulated scenario (pilot)--provides useful data for establishing Business Requirements. Observation of the prototype or pilot may reveal additional requirements that were not otherwise apparent. Successful prototyping can be the key factor that keeps a project going.

Requirementing Steps