Agile Business Analysis

Developing Agile Requirements with User Stories

Registration Fee: $795.00 per person

Team Registration Fee (3 or more attendees): $695.00 per person

Related Seminars
Business Analyst Guide to Agile Practices
Agile Planning and Estimating
Agile Team Boot Camp 
Introduction to Agile - Self Directed
Agile Team Challenges - Self Directed
Agile Certified Practition (PMI-ACP) Exam Prep
 
Duration - 2 Days In Person - 12 Hours Virtual (3 sessions @ 4 hours per session)
Availability - On Site In Person, Private Virtual Classroom, Open Enrollment
Get a quote for an on-site or private virtual session. 
 
Overview
 
User Stories are the most common means of representing requirements on agile projects. A user story describes system functionality that is valuable to a user or purchaser of a system. Acceptance tests are written to clarify and verify the behavior of user stories.
 
This highly interactive workshop will provide the skills needed to gather and document requirements in an agile project.  Through the use of hands on activities and demonstrations, participants will learn how to identify stakeholders, define the project’s vision, model user roles and personas, write user stories and acceptance tests, identify appropriate requirements gathering techniques, and employ user stories to plan releases and iterations. Participants will also discover and how to map their existing requirements processes to an agile approach.
 
What You Will Learn - Objectives
                                                                                                                     

  • Learn how user stories affect the agile planning process
  • Identify stakeholders and roles on agile projects
  • Develop a meaningful vision statement 
  • Identify and describe user roles and personas
  • Write and evaluate user stories
  • Identify and document nonfunctional requirements and business rules
  • Learn how to manage changes to the Product Backlog
  • Learn the characteristics of an effective user representative
  • Learn how to use lightweight techniques for iterative requirements gathering
  • Learn how to conduct story writing workshops using low fidelity prototypes
  • Learn how to create a user story map
  • Write acceptance criteria for user stories
  • Identify common story “smells”
  • Learn to prioritize and estimate user stories for iterations and releases
  • Learn how agile retrospectives are used to evaluate and improve iterations
 
Who Should Attend - Intended Audience
 
This workshop is intended for users, product managers, business analysts, developers, or testers who are currently responsible, or will be in the near future, for gathering and documenting requirements using agile methods.
 
Virtual Classroom Schedule
 
Virtual classroom sessions are conducted as follows:
1:00 pm to 5:00 pm DAILY, Eastern Time (New York) 
 
Virtual sessions are delivered using Cisco Webex Meeting Center. When you join the online meeting using the link provided in a confirmation email, you will be asked to either phone a US toll number or connect using a computer head set. If you phone in to the audio conference using the toll number provided, long distance toll charges will apply. If you connect using a computer head set with microphone (VOIP), no toll charges will apply. 
 
Agenda
 
1. The Big Picture
 
  • Workshop agenda
  • Introductions
  • How agile values affect business analysis
  • The benefits and risks of an agile approach to requirements
  • The agile requirements process
 
2. Defining the Vision
 
  • Roles in agile development
  • Identifying project stakeholders
  • Activity: Identify stakeholders
  • Defining the project vision
  • Agile planning processes
  • Activity: Define the vision
 
3. Modeling User Roles
 
  • Defining user roles 
  • Activity: Brainstorm user roles
  • Prioritizing user roles
  • Developing personas
  • Activity: Describe a user role and a persona
 
4. Writing User Stories
   
  • Writing user stories
  • Guidelines for good stories 
  • Activity: Identify and write user stories
  • Capturing other types of requirements
  • Activity: Write nonfunctional requirements and business rules
  • Managing agile requirements

5. Discovering and Grooming User Stories
 
  • Lightweight requirements gathering
  • Working with user proxies
  • Using models to get stories ready
  • Conducting a story-writing workshop
  • Activity: Conduct a story-writing workshop
  • User story mapping
  • Activity: Create a user story map
  • Building requirements runway
 
6. Testing User Stories
 
  • Writing acceptance test scenarios
  • Detecting story smells
  • Activity: Write acceptance test scenarios for user stories
  • Handling defects
 
7. Planning with User Stories
 
  • Planning iterations and releases
  • Prioritizing the product backlog
  • Activity: Prioritize stories for an iteration
  • Estimating with story points
  • Using stories to plan releases and iterations
 
8. Workshop Retrospective
 
  • Workshop review
  • Agile retrospectives
  • Activity: Workshop retrospective 

Open Enrollment Seminar Schedule

Buy The Use Case Handbook

Self Directed Seminars - On Demand

Business Analyst Guide to Agile Practices

Agile Business Analysis

Agile Estimating and Planning

Agile Team Boot Camp

Defining and Writing Better Requirements

Business Analysis Fundamentals

Business Analyst Guide to Data Modeling

Business Analyst Guide to Process Modeling

Data Modeling Essentials

BA/PM Guide to Understanding Business Architecture

Build and Leverage Your Business Architecture

Business Analyst Guide to Asking Better Questions

BA/PM Guide to Communicating Requirements to Offshore Teams

Business Analyst Guide to Use Cases

From Use Cases to Test Cases

Use Case Boot Camp

Software Testing Essentials

Business Analyst Guide to SOA

Requirements Definition Week™

Mentoring and Consulting

Project Management Simulations - On Demand