Agile Requirements Management: Developing and Using Agile User Stories

Course Description

All agile methods are empirical in nature – they seek out validation and feedback as early, regularly and with as much fidelity as possible. This means requirements must be structured as increments of functionality which can be integrated, demonstrated and potentially released early and often. User Stories are the preferred practice for delivering these incremental requirements in a user centric, value focused way. Without well-written user stories, teams will struggle to realize the full benefits of agile. But learning to write, estimate and prioritise good user stories for all but the most trivial real world applications is not easy. In this course we present some of the concepts underlying the use of user stories including ‘Late Elaboration’ and collaboration to drive innovation. We cover the structure of user stories, acceptance criteria, their use in planning, ‘right-sizing’ them, estimation using story points, and value and risk based prioritization. We include several exercises where participants can practice creating good user stories, understand the differences between them and tradition requirements, try estimating them and apply them to a real-world project of their choosing.
1 days
Contact us for pricing

Prerequisites

No specific pre-requisite skills. This course is targeted at Product Owners but can also be useful for ScrumMasters, Project Managers, Product Managers and senior Development Team members involved in defining or managing requirements.

Summary course outline

Requirements development in Scrum

Defining your stakeholders and understanding their needs
The Product Vision

Exercise: Creating a Product Vision

From themes to epics/features to user stories and spikes – Late Elaboration for Agility
Defining Product Increments: Techniques for splitting stories
The INVEST criteria for user stories
Creating and refining the Product Backlog
User stories and acceptance criteria with examples

Exercise: Defining User stories with Acceptance Criteria

Patterns for splitting epics to stories

Exercise: Decomposing Epics to Stories

Prioritisation of user stories and other elements of the product backlog – defining value and risk
Defining Product and Release scope – Minimal Marketable Feature Set
Estimation
Relative Estimation, Story Points
Joint Estimation – Planning Poker

Exercise: Relative Estimation using Planning Poker and Triangulation

Workshop: 2 hour ‘Backlog Refinement’ on target in-house project

Agileagile programmingagile testingSoftware testingSoftware testUser storiesrequirements managementagile requirements managementagile user storiesrequirements gathering