Effective User Stories for Agile Requirements September 13, 2006 in Software Development Best Practices

Projects start with their requirements. How those requirements are documented or expressed has a tremendous influence on the rest of the project. User stories originated in the agile processes but are useful even if you are not planning to use an agile process. The technique of expressing requirements as user stories is one of the most broadly applicable techniques introduced by Extreme Programming. However, user stories are an effective approach on all time constrained projects.

In this tutorial, we will look at how to identify and write good user stories. We’ll see the six attributes all good stories must exhibit and present thirteen guidelines for writing better stories. We will explore how user role modeling can help when gathering a project’s initial stories. During this hands-on workshop we will have the opportunity to practice identifying user roles and writing stories on a case study. This class will be equally suited for programmers, testers, managers and even customers and analysts who are interested in applying these agile techniques to their projects.

Sdbp2006_userstories-1
5.2 MB
pdf
September 13, 2006
Software Development Best Practices
90 minutes
user stories 2006
download Presentation

RailsStudio.com   Page copy protected against web site content infringement by Copyscape Valid XHTML 1.0 Strict [Valid RSS] RSS Bookmark and Share