Key takeaways

• What makes a good user story, 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?

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 - 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 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.