Developing Agile Requirements

How to Employ User Stories to Capture and Test Better Requirements

A Two-Day Seminar

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.

What You Will Learn

  • Identify stakeholders and roles on agile projects
  • Develop a meaningful vision statement
  • Describe user roles and personas
  • Write and evaluate user stories
  • Write agile use cases
  • Document nonfunctional requirements and business rules
  • Manage changes to agile requirements
  • Be an effective user representative
  • Use lightweight techniques for iterative requirements gathering
  • Conduct story writing workshops using low fidelity prototypes
  • Write acceptance tests for user stories
  • Identify common story types
  • Prioritize and estimate user stories for iterations and releases
  • Use agile retrospectives to evaluate and improve iterations

Seminar Outline

I. The Big Picture

  • How agile values affect requirements engineering
  • The benefits and risks of an agile approach to requirements
  • The agile requirements process

II. Defining the Vision

  • Roles in agile development
  • Identifying project stakeholders
  • Defining the project vision
  • Agile planning processes

III. Modeling User Roles

  • Defining user roles
  • Prioritizing user roles
  • Developing personas

IV. Writing User Stories

  • Guidelines for good stories
  • Writing agile use cases
  • Capturing other types of requirements
  • Managing agile requirements

V. Gathering User Stories

  • Lightweight requirements gathering
  • Working with user proxies
  • Conducting interviews
  • Using observation
  • Group techniques
  • Building low-fidelity user interface prototypes

VI. Testing User Stories

  • Writing acceptance tests
  • Detecting story smells
  • Writing acceptance tests for user stories
  • Handling defects

VII. Planning with User Stories

  • Planning iterations and releases
  • Prioritizing the product backlog
  • Estimating with story points
  • Using stories to plan releases and iterations

VIII. Workshop Retrospective

  • Workshop review
  • Agile retrospectives

Who Should Attend

  • Product Managers
  • Business Analysts
  • Developers, Users or Testers who will gather and document requirements using agile methods.

Credits: 12 PDUs / 12 CDUs

Project Management InstituteIIBA

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.