Topic Teasers Vol. 77: Agile Non-Functional Requirements

Have a question you would like to submit as a potential Topic Teaser? Send a message to Barbee Davis today!

  Agile   Scrum   Stakeholder Management  

We have switched to agile practices and, if I do say so myself, I think we are doing an awesome job. However, even though we are carefully creating backlog lists and writing user stories, more often than not our end product or service still does not meet the expectations of our internal and external customers. Has something been left out of what we were taught?

A. Agile does provide a way to use non-functional requirements in its methodology, but often it is overlooked or not stressed when new teams are preparing their first few projects. Make a point to add them into your new process.

B. The reason agile projects are completed so much faster and provide so much more value is that with the Scrum practice methodology, it is no longer necessary to consider vague things like non-functional requirements. If they aren’t going to function anyway, why bother with them.

C. User stories are only written if there is a need for outside personas to be created to represent users. Non-functional requirements are the ones assigned to those personas who would not be interested in your product or service, and therefore can be excluded from consideration.

D. Many projects have both functional and non-functional requirements that impact the outcome of the project. That is why only traditional processes should be used. Agile processes …

Please log in or sign up below to read the rest of the article.