I recently described User Stories and the composition of a User Story Card – Card, Conversation and Confirmation. I’m not really sure if you would consider this user story example to be good, bad or indifferent – I guess it depends what you’re used to – but here is an example nevertheless! This is the front of the card. The
If you’re capturing user requirements using User Stories, write them on a postcard… (a blank one of course!). A User Story Card should ideally comprise 3 parts: Card, Conversation and Confirmation… Card The heading section of the card should include the name/description of the user story, any reference numbers, estimated size, etc. Conversation Most of the front of the card
User Stories are a simple way of capturing user requirements throughout a project – an alternative to writing lengthy requirements specifications all up-front. User Stories are derived from XP (Extreme Programming), however they can just as easily be used for requirements gathering in any agile development methodology, or indeed in any home-grown development process. A User Story is a simple
By Kelly Waters
“’Agile’ is one of the biggest buzzwords of the last decade. Agile methods often come across as rather more complicated than they really are. This book is an attempt to unravel that complexity. To simplify the concepts. This book breaks the concepts into small bite-sized pieces that are easy to understand and easy to implement and delivers the message in a friendly and conversational style. Allaboutagile.com is one of the most popular blogs about agile on the web. ”
Kelly Waters
Emma Hopkinson-Spark
“Whilst there are lots of ways you can vary the game depending on the teams you have and the learning outcomes you want, the basic flow of the game play is common to all.”
Emma Hopkinson-Spark
If you would like to get in touch with one of the team at 101 Ways, then please fill out the form below or email us at contact-us@101ways.com.