Requirements, User Stories and Backlogs
In Agile, like traditional software development, work begins with customer requirements. But rather than a large English document most Agile teams work with small *User Stories* and backlogs.
In this workshop we will look at how Agile teams work with User Stores and use multiple backlogs to guide their work. We will look at:
Making better stories with added value?
What is the right size for a User Story?
How do I write strong User Stories?
When do I use a Story and when do I use and Epic?
How do I determine business value?
Finally we will look at how backlogs can be structured to provide forward planning and visibility.
This workshop is highly interactive, participants will get to write stories, critique stories and assign a monetary value to each and every story.
• User Stories: what makes a good one, what makes a bad one
• The difference between requirements and specifications
• How *specification by example* and acceptance test criteria are used with stories to add detail
• How stories are prioritised, value? risk? business benefit?
• How value can be assigned to stories and value changes
This 1-day workshop contains lessons for anyone working with User Stories and Backlogs in an Agile setting. Those who write stories - typically Product Owners, Business Analysts and Product Managers - will benefit, so too will those who receive User Stories to be developers and tested - programmers, testers, and designers.
Managers and Scrum Masters who work with these teams will also benefit from a deeper look backlog management.
The workshop does not lead to any official qualification. Rather it is intended as a practical course, with the bulk of the day being taken up by practical exercises and simulations.
As a Scrum Alliance Registered Education Provider (REP) Learning Connexions will award 6 Scrum Educational Units (SEUs) towards your CSP (Certified Scrum Professional) to all successful candidates.