15Dec/08
Requirements into failed project
Bunch of projects have died because of improper requirements. That shows ambiguous requirements create failed project. In contrast, defining the right set of requirement will improve the quality of the product. What makes such differences by requirements?
Requirement is a kind of communication. Properly documented requirements help reduce the gap between stockholders (who mostly require). And understanding requirements from the start synchronize development group with business users and their needs. The following is the list of proper solutions.
- Document the requirements clearly.
- Set priority of each requirements.
- Record the trace of the requirements.
- Technical team should communicate to business users.
- If there lies any change, be clear about the implications for scope and cost.
These rules are not the essential conditions to get the project succeed. But they're some of guidelines which can avoid project getting down into failure.