or call (813) 319-5851
How to Initiate Requirements Gathering with User Stories
- Overview
- Outline
- Objectives
- Print (pdf)
- Course Calendar
- Contact Us
For many information technology (IT) projects, the subject matter experts (SME) do not know what information technology could and should do for them, yet the IT team needs to know what to deliver. One of the biggest challenges at this phase of the project is overcoming this “IT — SME communications gap”. How can you deal with these difficulties, gather reasonable "business requirements" early, and not waste the effort?
This business analysis training workshop introduces a technique referred to as User Stories (not to be confused with use case). The user story technique focuses on business requirements, needs, and goals for the solution. It avoids the trap of trying to get the users to define the technical specifications. It starts with a facilitated workshop approach to capture, in business language, the goals, objectives, or wants for the business system in the form of very short stories. Detail is added over time as needed to understand each story at an appropriate level. Business driven test scenarios are used to expand everyone’s understanding of each requirement. User stories enable constant and efficient communication among all parties interested in getting to the right solution.
User stories complement and supplement any other business analysis techniques that you are using. User stories will make your requirements elicitations techniques easier and more complete without adding an extra burden of effort. As a bonus user stories can also help in very early cost forecasting when it is too early to "estimate". (See our expansion course, "How to Estimate Early in a Project").
1. Introduction to User Stories
What Are User Stories
User Stories: “First Rules"
User Stories: Defined by Example
Major Components of User Stories
When Are User Stories Written?
2. Use Stories are Driven by Roles
When are user stories written
Who Writes User Stories
User Roles
Adding Role Details
Rewriting the Roles “Second Rules"
3. How do user stories support testing
From User Stories to Test Scenarios
Testing Begins with the First User Story
Tests and Cards
Questions to Guide the Test Process
Case 6: group/individual: Discussable/Testable Stories?
Case 7: pairs: Did You Write Testable Stories?
4. How do you get user stories (techniques)
How Do You Get to User Stories
Standard Techniques
Story Writing Workshops
How Do You Manage User Stories?
5. What is a good user story
Business Focused User Stories
Value and User Goals
Story Value
Value Measurement-Right Sized
Complex User Stories
Dependency
6. User Stories Summary
Good and Not-So-Good User Stories
Properties of a Good Story
Properties of a Bad Story
Not All Things Are Stories
Summary
- List the components of a user story
- Explain the strengths and weaknesses of User stories
- Identify the appropriate time to use user stories
- Describe how user stories support testing
- Describe what makes a "good" user story
We do not currently have a public offering of this class scheduled. To add your name to the waiting list or request alternate offers, please contact us.
Check All Scheduled Business Analysis Training Offers
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.
- Classroom Training
- The Art and Science of IT Business Analysis
- How to Plan and Monitor Business Analysis Activities
- How to Estimate Early in a Project
- How to Elicit (Gather), Write, and Analyze Requirements
- How to Write, Analyze, and Manage Requirements
- How to Elicit (Gather) Requirements
- How to Prepare and Facilitate Requirements Workshops
- How to Initiate Requirements Gathering with User Stories
- How to Prepare and Facilitate Productive JRP-JAD Sessions
- Requirements Definition Techniques for Subject Matter Experts
- How to Manage and Communicate Requirements
- How to Conduct Enterprise Analysis
- How to Model, Analyze, and Improve Business Processes
- How to Model, Analyze, and Improve Business Data
- How to Define and Document Use Cases
- All About Use Cases
- How to Model, Analyze, and Improve Business Processes and Data
- How to Test an Application using Business Requirements
- Requirements-based Validation Methods for Acceptance Testing
- Business Analysis Planning and Monitoring
- Requirements Elicitation and Enterprise Analysis
- Requirements Management and Communication
- Requirements Analysis Techniques
- Assessing and Validating Solutions
- Web-based Training
- How to Plan Business Analysis Activities and Manage Risks
- How to Track and Monitor Business Analysis Activities
- How to Estimate Early in a Project
- How to Discover Business and Stakeholder Requirements
- How to Write Effective Requirements
- How to Analyze Sets of Requirements
- How to Manage Changing Requirements
- How to Package and Communicate Requirements
- How to Build Business Process Models
- How to Analyze and Improve Business Processes
- How to Build Business Data Models
- How to Analyze and Improve Business Data
- How to Define and Document Use Cases
- How to Plan, Prepare, and Manage Acceptance Testing
- How to Find and Build Test Cases from Requirements
- Self-Paced Training
- More Free Stuff
- Requirements Life Cycle
- Our Learning Methods
- Print Course Catalog
- RSG Noiseletters
- Business Analysis Bookstore
- Business Process Modeling (BPM)
- Business Rules
- Business Systems Analysis
- Requirements
- Requirements - Miscellaneous
- Requirements Analysis
- Requirements Definition
- Requirements Documentation
- Requirements Elicitation
- Requirements Engineering
- Requirements Management
- Requirements Traceability
- Requirements Validation
(813) 319-5851