Scrum Agile Project Management

Mistakes We Make Writing User Stories

August 8, 2011 0

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.

Prioritizing User Stories

August 5, 2011 0

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.

The Short Short Story

June 7, 2011 0

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.

The Product Backlog Board

May 10, 2011 0

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.

Story Point Estimation

May 6, 2011 0

In this blog post, Mike Treadway explains the technique of using story points for story estimation during agile planning sessions.

User Stories are Temporary

September 29, 2010 0

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.

Writing the Product Backlog Just in Time and Just Enough

May 5, 2010 0

Some people want to take the stance that no work should be done in advance of the sprint. That is clearly untenable. To see why, let’s take that view to its extreme: If we did nothing in advance to understand what we’re building, we’d show up at the planning meeting and say, “Hey, what should we build this sprint? We were working on an eCommerce site yesterday, but I think maybe we should switch to writing a word processor…” The team would literally have nothing written down—no product backlog / user stories / prioritized feature list at all.

1 5 6 7 8