Stakeholder issues
Steve McConnell, in his book Rapid Development, details a number of ways users can inhibit requirements gathering:
- Users don't understand what they want or users don't have a clear idea of their requirements
- Users won't commit to a set of written requirements
- Users insist on new requirements after the cost and schedule have been fixed.
- Communication with users is slow
- Users often do not participate in reviews or are incapable of doing so.
- Users are technically unsophisticated
- Users don't understand the development process.
- Users don't know about present technology.
This may lead to the situation where user requirements keep changing even when system or product development has been started.
No comments:
Post a Comment