The Scrum approach to agile software development marks a dramatic departure from waterfall management. Scrum and other agile methods were inspired by its shortcomings. Scrum emphasizes collaboration, functioning software, team self management, and the flexibility to adapt to emerging business realities.

Scrum User Stories

Submitted by admin on Fri, 10/24/2008 - 15:02
In Scrum, work is typically expressed in the Product Backlog as user stories. A team may write its user stories in a number of ways as long as they are written from the perspective of the end user. Team members are encouraged to think of their work from the perspective of who will use it (hence “user” story). A team can express a story as a noun (i.e. “text message” on a cell phone project) or a sentence or phrase (i.e. “debug GPS tracking system”). Many Scrum teams have adopted the user story template popularized by Rachel Davies and Mike Cohn, which identifies who the end user is, what the end user wants, and why in a single sentence. This model of the user story is often written like this: “As a [end user role], I want [the desire] so that [the rationale]. User stories are intended to help teams and Product Owners focus on the customer. Thus, it would be inappropriate to write "As a Product Owner I want ___" or "As a software architect I want ____." Work that doesn't directly serve a customer need is better expressed as a Sprint Task related to a User Story. These are identified during the Sprint Planning Meeting. Watch a Product Owner and Scrum Team write user stories. (Around the 7 minute mark.) Image removed.


Here is a very simple and concise article I found on User stories. Must read:

Add new comment

Restricted HTML

  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type> <li> <dl> <dt> <dd> <h2 id> <h3 id> <h4 id> <h5 id> <h6 id>
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.