Handling Non-Functional Requirements on an Agile Project
When adjectives and adverbs appear in User Stories, they can be easily overlooked and seen as simple adornments to the story. There are a couple schools of thought on how to handle non-functional requirements on Agile projects. Mike Cohn recommends writing a User Story for each non-functional requirement, while others recommend creating task cards to drive out specification using Thomas Gilb’s approach. In this session, examples of various techniques for handling non-functional requirements will be demonstrated, with a discussion of pros and cons of each technique.
This session will be presented in a tutorial fashion with an emphasis on learn by example, using real examples of User Stories, task cards, and other candidate deliverables that support exploration of non-functional requirements on an Agile project.
- Learn how to recognize non-functional requirements “hiding” in a User Story
- Learn how to express a non-functional requirement as a User Story
- Learn how to create acceptance criteria to support a non-functional User Story
- Learn how to handle non-functional requirements as supporting tasks
- Learn best practices on expressing non-functional requirements that are free of ambiguity