Thanks to Andrew Binstead @AndrewBinstead which recommended “Fifty Quick Ideas to Improve Your User Stories” I heard about it.
I have only show the book description posted in Amazon that is a great summary of the main features of the book.
including the URL with ASIN code
This book will help you write better user stories, spot and fix common issues, split stories so that they are smaller but still valuable, and deal with difficult stuff like crosscutting concerns, long-term effects and non-functional requirements. Above all, this book will help you achieve the promise of agile and iterative delivery: to ensure that the right stuff gets delivered through productive discussions between delivery team members and business stakeholders.
Who is this book for?
This is a book for anyone working in an iterative delivery environment, doing planning with user stories. The ideas in this book are useful both to people relatively new to user stories and those who have been working with them for years. People who work in software delivery, regardless of their role, will find plenty of tips for engaging stakeholders better and structuring iterative plans more effectively. Business stakeholders working with software teams will discover how to provide better information to their delivery groups, how to set better priorities and how to outrun the competition by achieving more with less software.
Who is this book not for?
This book doesn’t cover the basics of stories. We assume that readers know what Card-Conversation-Confirmation means, what INVEST is and how to apply the basic strategies for splitting user stories. This isn’t the first book you should read about user stories, if those terms are unfamiliar. There are plenty of good basic books out there, so read them first and then come back. Please don’t hate us because we skipped the basics, but there is only so much space in the book and other people cover the basics already well enough.
Unsurprisingly, the book contains exactly fifty ideas. They are grouped into five major parts:
– Creating stories: This part deals with capturing information about stories before they get accepted into the delivery pipeline. You’ll find ideas about what kind of information to note down on story cards and how to quickly spot potential problems.
– Planning with stories: This part contains ideas that will help you manage the big-picture view, set milestones and organise long-term work.
– Discussing stories: User stories are all about effective conversations, and this part contains ideas to improve discussions between delivery teams and business stakeholders. You’ll find out how to discover hidden assumptions and how to facilitate effective conversations to ensure shared understanding.
– Splitting stories: The ideas in this part will help you deal with large and difficult stories, offering several strategies for dividing them into smaller chunks that will help you learn fast and deliver value quickly.
– Managing iterative delivery: This part contains ideas that will help you work with user stories in the short and mid term, manage capacity, prioritise and reduce scope to achieve the most with the least software.
As part of my duty as Agile Coach I strongly recommend this book for Product Owner because it would be an amazing and powerful guide to improve the way of dealing (defining, updating and splitting) with user stories!!!