From the course: Agile at Work: Planning with Agile User Stories
Join today to access over 24,600 courses taught by industry experts.
Identify user stories
From the course: Agile at Work: Planning with Agile User Stories
Identify user stories
- Identifying and writing a user story is a low effort, typically 5% or less of what is needed to implement it. The remaining effort is evenly spread between discussing it and writing the acceptance criteria. In the video, Developing a Product Backlog, I introduce user stories' progressive level of depth benefit. Large quantities of user stories can be identified with a relatively low level of effort. The bulk of the effort, acceptance criteria and in-depth discussions, are not needed until a story is prioritized high in the product backlog by the product owner, and is likely to be implemented in the next iteration or two. User story writing has a lifecycle, beginning with identification and ending when ready to implement. These are the steps I work with teams new to Agile to use: Identified and written. Initial relative sizing by the team members. Initial prioritization by the product owner. Story becomes high priority. Discussion and writing of acceptance criteria and supporting…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.
