A Little Book About Requirements and User Stories

Heuristics for Requirements in an Agile World

De: Allan Kelly

Narrado por: Stacy Gonzalez

“How do I make my user stories smaller?”
“What is the right size for a user story?”
“What is the difference between an Epic and a Story? And where do Tasks and Sub-Tasks fit in?”
“Who writes user stories?”
“Why user stories?”
"Do I have to use user stories?"

Allan Kelly found himself answering these questions, and similar ones, again and again so...he sat down to write the answers and this book was born.

In this book Allan discusses the role of user stories: they are not requirements, they are tokens for work to be done and a placeholder for a conversation. He gives his two golden rules: stories must be small and they must be beneficial to the business - further he describes what beneficial is, how to put a value on a story, and how to maximize the return on investment.

He gives particular attention to the difference between requirements and specification and how these ideas line up with user stories and acceptance criteria. Along the way he takes epics, tasks, definition of done, backlog structuring, acceptance tests, and much else.

In short, it's a little audiobook about user stories and all that goes with them.

©2017 Allan Kelly (P)2019 Allan Kelly

All the reminders agile practitioners need

This book provides a good pace and content for agile practitioners relook on how we do things. While the majority focus are on user stories and how to write good ones, some elements of agile ways of working are being reminded as well.

perfect book for scrum masters

perfect book for scrum masters, not only covers, user stories, it also covers important details of scrum execution points

Simplistic view, lacking end to end example

Few or none of the user story examples fit in a 2 week sprint timebox in a real world scenario. And its not clear by any means how splits that cannot alone bring any business value can ever be addressed. The book lacks a real end to end example and most important, guidance on how to address the typical pitfalls found in the agile approach.