This 52-minute video is a comprehensive introduction to User Stories, as practiced in Agile Development. Mike Cohn presents:
- resource allocation under imperfect schedules as a shared problem between developers and business people;
- user stories as 3 C’s: the Card supporting Conversations with Confirmation (of conditions of satisfaction);
- story details as (i) conditions of satisfaction, or (ii) sub-stories;
- epics as large stories, and user stories clustered into themes;
- story-writing workshops as supporting participative design.
While this talk was the last for the day, it’s better as the first for viewing as an easy introduction to the agile way.
Mike Cohn – User Stories for Agile Requirements from NDCOslo on Vimeo.
The technique of expressing requirements as user stories is one of the most broadly applicable techniques introduced by the agile processes. User stories are an effective approach on all time constrained projects and are a great way to begin introducing a bit of agility to your projects.In this session, we will look at how to identify and write good user stories. The class will describe the six attributes that good stories should 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.
Because requirements touch all job functions on a development project, this tutorial will be equally suited for analysts, customers, testers, programmers, managers, or anyone involved in a software development project. By the end of this tutorial, you will leave knowing the six attributes of a good story, learn a good format for writing most user stories, learn practical techniques for gathering user stories, know how much work to do up-front and how much to do just-in-time.
The slides are also available at http://www.mountaingoatsoftware.com/presentations/introduction-to-user-stories