Prior to agile development, requirements gathering was a long, exhaustive process designed to produce a comprehensive document with all the details in it. Changes to this document usually required a big process. With few exceptions, this approach did not fit the changing needs of modern business.

When agile development came on the scene, documentation was often seen to be the enemy and development was engaged with little to no planning or understanding of what was being developed.

Now, many organizations struggle between these two polarities. How do you engage with requirements ahead of time to make sure you build the right thing while still allowing for quick responsiveness to changing business needs?

In this session, we'll look at principles and practices around gathering requirements that work them into an incremental, flow-based delivery practice.

You'll learn:
- The role of a high-level feature list
- A simple, acronym-free guide to writing user stories
- Acceptance criteria for capturing details
- How to balance keeping the development queue stocked with the risk incurred by premature analysis
- The value of capturing conversations
- What to do with all this stuff when you're done with it