Conclusion: Unless the attributes of user stories (agile) or high-level requirements (waterfall) are succinct and testable, business systems specifications will lack rigour and could compromise the system’s integrity. To ensure these attributes, i. e. succinct and testable, are present, the stories and high-level requirements should be peer reviewed to identify content that is unclear or just expressing an unrealistic ‘want/wish’ list.

It is important the stories or high-level requirements contain sufficient context to enable systems requirements, i. e. functional and non-functional, to be developed because unless they do it will be difficult to prioritise them based on business drivers.

Similarly, the results of user acceptance testing should be peer reviewed to ensure the agreed requirements have been met and the output is verifiable.

Existing Client Login

Please complete all required fields!

This advisory paper is only available to IBRS advisory clients. To find out more about becoming an IBRS advisory client complete the attached form and we will be in touch.

Name^*

Please let us know your name.

Email^*

Please let us know your email address.

Number^*

Please enter a valid phone number

Subscribe to IBRS InTouch for weekly updates outlining content and insights from our advisors Invalid Input

^*

I consent to IBRS collecting my details through this form.

Invalid Input

Invalid Input

Read more ...