This article provides an overview on the derivation and application of user stories, which are the primary concept that represent the user requirements in agile software development approaches like Scrum. Its goal is to describe the user story in detail, because it contains the key agile practices that help align solutions directly to the user’s specific needs, assuring quality at the same time.
The art of writing good User Stories is the most difficult for new teams. The mistakes made at that point lead to wrong Test Cases, wrong understanding of requirements and the worst of all wrong implementation which can be direct cause of rejecting the deliverables at the end of the iteration. This article presents the five most common mistakes people make writing user stories.
A survey says that 64% of the functionalities included in software products are never or almost never used! In this blog post, Emiliano Soldi shares some ideas on how to avoid this and prioritize user stories.
Scrum teams often use user stories for backlog items. Unfortunately, one of the most important aspects of a story – its extremely short length – has been subtly transformed over time and user stories have lost their original essence and potency.
This post presents a structured and hierarchical product backlog board that considers non-functional requirements and display high priority items that are ready to code.
In this blog post, Mike Treadway explains the technique of using story points for story estimation during agile planning sessions.
It’s obvious, but warrants mention: What we do in the future is likely to be different from what we’re doing today. The implications for user stories should be obvious: User stories are temporary. Saving them for posterity doesn’t serve the primary purpose of user stories, and doing anything that makes them less temporary can turn user stories from benefit to detriment.
Scrum Expert Copyright © 2009-2024 Martinig & Associates