How to Jump-Start Requirements Gathering with User Stories

1. Introduction

• Overview
• Objectives

2. What is a user story

• Business focused requirements
• Written component
• Communication component
• Testing component

3. When are user stories written

• As soon as possible
• Continuously
• After an incremental deliverable

4. Who writes user stories

• Stakeholders
• Technical staff
• Business staff

5. How do you get user stories (techniques)

• Interviews
• Surveys
• Writing workshops (JAD type sessions)

6. What is a good user story

• Properties of a good story
• Do’s
• Don’ts
• Tricks

7. How do you manage user stories

• Card Decks
• Whiteboard (walls)
• Online tool

8. How do user stories support testing

• Testing begins with the first user story
• Customer test specifications

9. Summary

• User stories are not . . .
• User stories relationship to other requirements definition techniques
• Now what . . .

1 day

Business Analysts
Business Process Managers
Business process users
Subject Matter Experts
System Analysts
User liaison personnel
Anyone involved in defining or deciphering business system requirements.

NONE

Our instructors have extensive experience in applying these techniques on projects with business experts from a wide variety of fields.