User Stories are a worldwide default approach for Agile teams to capture stakeholders’ needs. But how do you go about developing a good User Story? A common misconception is that User Stories are a replacement for requirements documents. During this course, we will debunk that myth. Based on years of leading Agile projects, our experienced practitioners will teach you how to use this powerful technique.
Note – this course is not ‘padded’ with an introduction to Agile. We expect attendees to have a basic understanding of Agile techniques such as Scrum or Kanban.
Product owners, business analysts, product managers, developers and testers. In short, anyone who works, or will be working with requirements on Agile projects.
By the end of this workshop attendees will have learned:
- What makes a good User Story
- How to develop testable User Stories with acceptance criteria
- How to translate the product vision into Epics and User Stories using two common techniques – Story Mapping and Impact Mapping
- Story sizing: how to use Themes, Epics, and Stories and when to split them into smaller chunks
- How to define User Story boundaries using acceptance criteria
- How User Stories fit with Acceptance Test-driven Development (ATDD) and Specification by Example
- Demonstrate a range of techniques for estimating User Stories
- Work through how to manage a Product Backlog of User Stories
- How User Stories relate to the Definition of Done and Definition of Ready
- How to manage non-functional requirements
Print/Share Course Description
Prior knowledge of Scrum and Agile methods is beneficial. You should have a background knowledge of Agile projects and/or have actively worked on a Scrum team, with a good understanding of the basic Scrum framework. At a minimum, attendees should read the Scrum Guide.