Agility is often described in terms of iterative development. In fact, it's more of an iterative analysis process with the code being written and tested immediately after the requirements are discovered. The heart of this process is the user Story, a collection of requirement descriptions, value statements, cost estimates, architecture designs, and test cases-all rolled into one. While at first glance user Stories seem simple, they play a key role in all agile methods. What makes a good one? How do you write it? How do you make them the right size? Alan Shalloway answers all of these questions and more in this thought-provoking class. Unfortunately, it is not enough just to create a collection of stories. We need a way to organize them and to plan for their release. Alan concludes by discussing these important organizational issues.