User Story Mapping is one of the most powerful collaboration tools for planning complex development activities. However, what are the differences between a good story map and a great one? How does one design and lead a great mapping session?
The book Executable Specifications with Scrum by Mario Cardinal starts with a strong statement: “This book aims to solve the recurring challenge encountered by many software development teams: They do not build the right software.” This is an ambitious goal, especially when you want to achieve it in a little bit more than 100 pages.
Business value, business value, business value. This presentation from Allan Kelly explores how to put a value on stories in a backlog while uncovering new requirements, elaborating specifications and valuable opportunities.
Are you sick of seeing your Scrum team treated as a sausage machine for turning user stories into code? Can your software developers only talk about how long something will take, or how exactly it will be built?
Fifty Quick Ideas to Improve your User Stories is another book from Gojko Adzic, a consultant and author that already produced some very good books on Agile requirements like Impact Mapping and Specification by Example. It goal is to help people involved with Agile requirements to improve their discussion with the stakeholders and the planning activities associated with user stories. This is clearly not a book for beginners on how to write user stories.
Do you find that user stories grow and multiply until you can’t fit them in your Scrum sprints? Are you struggling to see the big picture? Are you lost in user story hell? This presentation examines the OOPSI (Outcome, Output, Process, Scenarios, Inputs) technique and demonstrates how it accelerates delivery by ensuring that you are always working on the right thing and can see the bigger picture.
Before including a user story in a Scrum sprint, it is important to clarify and confirm its acceptance criteria.In recent years, lots of Agile software development teams have been using a simple collaborative technique called Example Mapping to break down user stories. It was conceived co-founder of Cucumber, Matt Wynne, who wrote the seminal post introducing the practice “Introducing Example Mapping“.