Good Practice: Obtaining a realistic requirement set is essential to your project's success and the well-being of the project team.
For many projects, the total set of user requirements can be ambitious, making it difficult or even impossible to deliver a solution that meets all the requirements, in a way, that is robust, cost-effective, maintainable and can be rolled out quickly to a large user base.
It is essential to match the user requirements specification against the available technology and solutions you can implement in a timely, robust and practical way. This situation can result in an agreement that some requirements, say 20%, will not be delivered. Such a compromise will ensure that the remaining 80% can be delivered quickly. This compromise is essential for global projects with a large user base. On such projects, the speed and ease of implementation is an important consideration for the overall solution.
To be successful at requirements gathering and to give your project an increased likelihood of success, follow these rules:
Common Mistakes
Question 14: Are the user requirements realistic?
Question 15: Have you based your development on an iterative prototyping approach?
Question 16: Have you conducted structured testing?
Question 17: Do you have a comprehensive implementation plan?