Skip to main content

What's in a User Story?

Being Agile: my occasional ramblings on Agile development & Extreme Programming

I constantly run into people who claim to be Agile but don't understand XP (extreme programming). And a lot of people fail to grasp the essence of XP because they get stuck on an XP principle that they find threatening - 'pair programming' and 'test driven development' are the usual suspects.

I'll focus on Pair Programming and TDD another day. Today I want to discuss the most important and fundamental aspect of XP - User Stories.

User Stories are like better, state-of-the-art Use-Cases - simpler and lending themselves to be scheduled individually.

Think of a User Story as a fine-grained Use-Case, leading to better estimation of effort, tracking of progress, and higher quality of implementation (fewer bugs due to requirements that are fine-grained, thorough and less ambiguous).

A User Story looks just like a bug would in a bug tracking system:
  • a one-line title summarizing the requirement that the user story encapsulates
  • a detailed description consisting of a bulleted list of acceptance criteria
  • a schedulable unit of work whose progress can be tracked
It is the schedulable nature of a User Story that gives it a huge advantage over any other form of requirement gathering, including Use Cases.

Next Time: How to schedule User Stories

Comments

Popular posts from this blog

Splitting User Stories vs. Rally's "split" feature (that has nothing to do with it!)

Agile tool Rally has a "split" feature it recommends to handle "unfinished work" in a Scrum Sprint: Manage Unfinished Work - Split user stories ( new link ) Below are my observations on the "Split" feature in Rally (followed by a few excellent articles on Splitting User Stories):   This "split" feature in Rally has numerous problems: 1. Nothing to do with Splitting User Stories It has nothing to do with "Splitting a User Story" which is an advanced but fairly well-understood field in Agile, and a tool for Product Managers to use in one of the two scenarios: The Product Manager does it before an Iteration commences (i.e. during backlog creation or release planning) to create User Stories by business value that are right-sized, i.e. they can be comfortably implemented inside an iteration; The Product Manager does it in Iteration Planning or in the middle of an Iteration to reduce scope by removing/simplifying accept

User Stories: you're not Agile without them

Failure to effectively transition to Agile development is often based on a fundamental failure to understand what a User Story is. Allow me to explain. The most important aspect of a User Story is that it's an independently *schedulable* unit of requirement (feature). The key to achieving the "independently schedulable" characteristic of a user story is that you express it in terms of how a "user" would use it. This leads you to a unit of functionality that's implemented end-to-end (UI to backend) that a user can actually interact with. Not surprisingly, because of the focus on how a user would think about a feature, a user stories are highly readable - and could very well be written by the users themselves. However, the other important and less obvious aspect of a User Story is the emphasis on communication with the end-user and getting confirmation on the acceptance criteria. Describing all the requirements as User Stories for a decent sized product is

Venture Quotes for a softening economy

Guess who said the following? "There's a lot of hot air and arrogance in the (VC) business that we all would be better off without" "...useless pontificating in front of entrepreneurs working harder than (VCs)..." "...VCs who constantly speak of deals and projects , reveal their self-interest and slight the labor and dreams of the entrepreneurs" If you think it's some disgruntled entrepreneurs who don't "get it", think again. In the past, I've made some pretty strong but heartfelt things, and I could have said the above, but I didn't . Read on here to learn who uttered these pearls of wisdom.