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.
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“.
User stories can be considered as the most used form to manage requirements in Agile. However, as often with agile concepts Agile that look simple in theory, using them in practice generates many questions: What should user stories contain? When should they be ready to be developed? What is an optimal backlog size? This is the type of issues that Allan Kelly discusses in his interesting Little Book about Requirements and User Stories.
Many Agile coaches are former software developers, some are not. But when technology moves on, well known Agile approaches can be challenged. Applying the Agile approach of vertical story slicing on microservices is one such example. This talk explains on how as Agile coaches we can coach in technical areas where technology may have moved on, thus challenging the perceived coaching approaches to helping teams become self-organising.
User stories are one of the main format to record user needs in the Agile world. There is however a debate on the amount of information that should be available to the Scrum team before starting the sprint. In this article, Zuzi Šochová recommends to minimize the size of user stories and to define simple conditions of satisfaction instead of writing acceptance criteria.
Agile reminds us that the focus of any set of requirements needs to be on an outcome rather than a collection of whats and whos. Storytelling is a powerful tool to elevate even the most diehard requirements analyst from a discussion of individual requirements to a discussion of outcomes. Outcomes are the big picture that acts as an anchor for whole efforts and which is continuously broken down into more and more detailed product backlogs.
We all know the “Definition of Done” used in Scrum for items that should be potentially shippable to the customer at the end of the sprint. In his book Essential Scrum, Kenneth Rubin discusses the “Definition of Ready” that applies to product backlog items that should be ready to be developed before the start of the sprint.