Menu
I frequently hear "X% of software project fail due to bad requirements". The X in that statement has ranged from about 70 to 95. However, I seldom hear how requirements go bad. In fact, the statement itself suggests there were actually requirements.
What makes a "bad" requirement? How can one be avoided?
997
When the requirements are not clear we need to record that the estimates are based on unconfirmed assumptions. The next step is to report the risks to the leadership so that the issue can get the visibility and identify any impact to the timeline. Assign an owner and include a resolution target date.
Key to improving the quality of your requirements is to include the following in your requirement quality improvement plans: – Develop and enforce a formal requirement elicitation, development, and management process. – Train your team in your requirement development and management process.
216: What can be done if requirements are changing continuously? A. Work with the project's stakeholders early on to understand how requirements might change so that alternate test plans and strategies can be worked out in advance, if possible.
Bad Requirements They are bad if they are ambiguous, incomplete, not verifiable, etc. If stakeholders give you bad requirements and you document those, you will end up with a system that is incomplete in many critical aspects.
For successful requirement elicitation you need to
Usually the problem lies in a lack of communication and understandability between the customer and the developer. Moreover keep in mind that sometimes even the customer itself doesn't exactly have a good picture of what he wants. Therefore discussion, paper prototypes etc. are really important.
This pic is my favourite :)
185
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
