Chapter 5. Requirements and User Stories
In this chapter I discuss how requirements on a Scrum project are handled differently than on a traditional project. With this context in place, I describe the role of user stories as a common format for representing items of business value. I focus on what user stories are, how they can represent business value at multiple levels of abstraction, and how to determine when the user stories are good. I then describe how to handle nonfunctional requirements and knowledge-acquisition work on a Scrum project. I end by detailing two techniques for gathering user stories.
Scrum and sequential product develo...
- Chapter 5. Requirements and User Stories
- from Essential Scrum: A Practical Guide to the Most Popular Agile Process
- Publisher: Addison-Wesley Professional
- Released: July 2012
As an experienced engineer or developer, you have obviously worked with requirements and understand their role in the development process. However, requirements are handled differently on agile projects than they are on traditional projects. This lesson discusses requirements from an agile perspective and provides you with the understanding needed to participate in defining product requirements and creating user stories. Multiple scenarios and examples are provided to help you create and refine user stories.
Share this highlighthttp://www.safaribooksonline.com/a/essential-scrum-a/27250/