user stories
My User Stories Aren’t Long Enough… Except When They Are Too Long
Product managers/owners often hear from our software development team that all of our user stories are too short, insufficient, skimpy, lacking detail. Except when we hear that all of our user stories are long-winded, verbose, overspecifying how instead of what. What’s really happening?
Read More
Getting Well Written Requirements from Business Analysts
A lot has been said and written about user stories and their role in an agile context. But what are people actually writing as user stories? It doesn’t matter if you are agile or traditional in your approach, poorly written requirements are one of the major causes of project failure. This is where the Business […]
Read More
The A.A.R.T. of Writing User Stories
Current user stories used to manage Agile requirements can be improved by clearly identifying, linking, and tracking Actors, Action, Results, and Tests. (A.A.R.T).
Read More
From Value to Solutions in Agile
Agile uses mostly user stories to capture requirements. In his blog post, Jean-Jacques Dubray explains that there is a problem with user stories because they tend to focus on the solution and not on the problem definition.
Read More
The User Stories Iceberg
This short video presents the Mike Cohn’s Iceberg Analogy for User stories. It discusses User Stories and the Backlog, how you can perform grooming and rightsizing and how you should establish a grooming cadence for sprint, release and roadmap.
Read More
User Stories Are Not Requirements
The common wisdom is that Agile register requirements using the user stories format: “”As a , I want <goal/desire> so that “. In this article, Earl Beede explains why user stories are not requirements.
Read More