lunes, 28 de abril de 2008

Unsuccess on requirements collection

In most of the projects, the requirement collection activity is a single point of failure. Without an organized requirement collection, the subsequent phases of a project has huge impacts. Also considering that estimation is also based on the requirements, requirement collection activity plays a vital role.
The following are the common failures in requirement collection activity:

a) Failure to set the scope and clearly define the boundaries
b) Failure to get the buy-in from the all stakeholders (clearly stating the limitations and scope)
c) Failure to foresee likely changes in business/requirements
d) Failure to document the expectations in an easily understandable format
e) Failure to ensure that the understanding from the design/development team is in conformance with the expectations.

Although requirement collection & documentation may not be 100%precise, only when we strive towards it, the project will be successful.