Think User Stories are Enough…Think Again!
One of the key tenets of the agile manifesto is that we should prioritize user interactions over documentation, and embrace the fact that requirements will constantly change. This tenet has led to the adoption of user stories as the almost exclusive form of requirements documentation in agile projects. User stories are incredibly valuable in expressing the desires of users in a consistent, simple, and easily understood format. However, Adam Sandman has seen many projects and customers get into trouble by relying on them as the sole type of requirement. Join Adam as he discusses how we can use user stories and other types of requirement, including use cases, diagrams, flowcharts and methods for capturing non-functionality requirements (such as performance and security) on agile projects. In addition, I will discuss the benefits and drawbacks to the different approaches with examples of when you should use each of them. Takeaways include why user stories are useful, and what limitations they have; what other approaches for capturing requirements can be used; and a roadmap for deciding what types of requirement to use for different situations.