Developing Agile Requirements
How to Employ User Stories to Capture and Test Better Requirements
A Two-Day Seminar
Credits: 12 PDUs / 12 CDUs
Dates and Locations
A user story is a brief and clear description of system functionality that is of real value to a user. Written from the users' perspective, good user stories drive effective requirements development, acceptance testing and ultimately the delivery of value to the customer by the system. In this workshop, you will learn how to write effective user stories and acceptance tests, and how to map your existing requirements processes to an agile approach.
Workshop Objectives
- Write a vision statement
- Identify and describe user roles
- Write user stories
- Know the characteristics of an effective user representative
- Understand how to use lightweight techniques for iterative requirements gathering
- Write acceptance tests for user stories
- Understand the prioritization of stories for iterations and releases
What You Will Learn
- How to identify stakeholders and roles on agile projects
- How to develop a meaningful vision statement
- How to identify and describe user roles and personas
- How to write and evaluate user stories
- How to write agile use cases
- How to identify and document nonfunctional requirements and business rules
- How to manage changes to agile requirements
- How to be an effective user representative
- How to use lightweight techniques for iterative requirements gathering
- How to conduct story writing workshops using low fidelity prototypes
- How to write acceptance tests for user stories
- How to identify common story types
- How to prioritize and estimate user stories for iterations and releases
- How to use agile retrospectives to evaluate and improve iterations
Who Should Attend:
This workshop is intended for users, product managers, business analysts, developers, or testers who will gather and document requirements using agile methods.
Seminar Outline
- The Big Picture
- How agile values affect requirements engineering
- The benefits and risks of an agile approach to requirements
- The agile requirements process
- Defining the Vision
- Roles in agile development
- Identifying project stakeholders
- Defining the project vision
- Agile planning processes
- Modeling User Roles
- Defining user roles
- Prioritizing user roles
- Developing personas
- Writing User Stories
- Writing user stories
- Guidelines for good stories
- Writing agile use cases
- Capturing other types of requirements
- Managing agile requirements
- Gathering User Stories
- Lightweight requirements gathering
- Working with user proxies
- Conducting interviews
- Using observation
- Group techniques
- Building low-fidelity user interface prototypes
- Testing User Stories
- Writing acceptance tests
- Detecting story smells
- Writing acceptance tests for user stories
- Handling defects
- Planning with User Stories
- Planning iterations and releases
- Prioritizing the product backlog
- Estimating with story points
- Using stories to plan releases and iterations
- Workshop Retrospective
- Workshop review
- Agile retrospectives
Back to top of page...
PMI®, PMP®, and PMBOK® are registered trademarks of the Project Management Institute, Inc. registered in the United States and other nations. CBAP® and IIBA® are registered trademarks of International Institute of Business Analysis. ©2010-2020 Orion Development Group. All Rights Reserved.