Think User Stories Are Enough? Think Again!
Some of the key tenets of the Agile Manifesto are that we should prioritize user interactions over documentation and embrace the fact that requirements will constantly change. This 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. Adam will discuss how we can use user stories and other types of requirements, including use cases, diagrams, flowcharts, and methods for capturing nonfunctionality requirements on agile projects. He'll dive into the benefits and drawbacks to the different approaches and give examples of when you should use each one. You'll explore why user stories are useful and what limitations they have, learn what other approaches for capturing requirements you can use, and get a roadmap for deciding what types of requirement to use for different situations.