ABSTRACT
There is, however, one final link in the chain which is to the project scope, which is defined by the project requirements. There is no single good way to specify requirements, and there are lots of different types of medium that can be used to define or draw them out. Early testing that reveals a missed requirement can save one a fortune in time and money later on in the project. Bear in mind especially that a missed requirement is likely to mean the objective to which it is linked also gets missed, and the project is not considered to have been delivered. It is worth noting that, in a project where the requirements have been clearly defined and agreed, there should be no cost to the customer to rectify the snags, defects, or missed requirements. Scope creep is the term for the many—many—ways in which the simple, easily deliverable job that one start out with grows into a monster.
