background preloader

Introduction to User Stories

Introduction to User Stories
1. Introduction to User Stories A good way to think about a user story is that it is a reminder to have a conversation with your customer (in XP, project stakeholders are called customers), which is another way to say it's a reminder to do some just-in-time analysis. In short, user stories are very slim and high-level requirements artifacts. 2. Initial User Stories (Informal) As you can see in Figure 1 user stories are small, much smaller than other usage requirement artifacts such as use cases or usage scenarios. Figure 1. Important considerations for writing user stories: Stakeholders write user stories. Figure 2. 2. Figure 3. 4. There are two areas where user stories affect the planning process on agile projects: Scheduling. Figure 4. 5. As you can see in the Disciplined Agile Delivery (DAD) life cycle of Figure 5, there are several distinct "phases" or seasons in the life cycle (some people will refer to the agile delivery life cycle as a release rhythm). Inception. Figure 5. 6. 7.

http://www.agilemodeling.com/artifacts/userStory.htm

Related:  User StoryRequirementsPaolo Demagistris knowledge base

kaeru User stories reimagined Since the concept of user stories was introduced it has been used (and misused) in so many ways. The stories were intended to replace formal requirements (that were, for practical reasons, not followed anyway) and use cases (that were way too cumbersome to write). A story is supposed to be a promise to have a conversation around the subject of the story, to eliminate misunderstandings through speech, not writing. This means that a user story can be very high-level and somewhat abstract, and the discussion around it will make it more tangible. User Story Example I recently described User Stories and the composition of a User Story Card – Card, Conversation and Confirmation. I’m not really sure if you would consider this user story example to be good, bad or indifferent – I guess it depends what you’re used to – but here is an example nevertheless! This is the front of the card. The Card section describes the user story.

Use Cases or User Stories? Murali Krishna tells us: Failure to effectively transition to Agile development is often based on a fundamental failure to understand what a User Story is. 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. Agile Alliance Group News Retrospectives and feedback loops are at the heart of any successful Agile/Scrum implementation. They’re the tool we use to help teams improve. Yet in two day introduction to Agile classes they often get glossed over.

How to create a User Story Map User story mapping is becoming a popular technique through the efforts of Jeff Patton and others that allows you to add a second dimension to your backlog. Here are a few reasons you should consider using this technique: It allows you to see the big picture in your backlog.It gives you a better tool for making decisions about grooming and prioritizing your backlog. It promotes silent brainstorming and a collaborative approach to generating your user stories.It encourages an iterative development approach where your early deliveries validate your architecture and solution.It is a great visual alternative to traditional project plans.It is a useful model for discussing and managing scope.Allows you to visualize dimensional planning and real options for your project/product.

How to write meaningful User Stories - Subcide I’ve seen a lot of projects fail when by all accounts, they shouldn’t have. The reason for this nearly every time, was that the requirements gathering stage of a project was done poorly, or sometimes not at all. Sometimes this is driven by budget or deadline constraints, and sometimes it’s because the people responsible are just unaware of how to go about gathering requirements in a structured manner, and if you’re one of those people, or know one of those people, then please read on. The Marketing Mix: Product Products come in several forms. Consumer products can be categorized as convenience goods, for which consumers are willing to invest very limited shopping efforts. Thus, it is essential to have these products readily available and have the brand name well known. Shopping goods, in contrast, are goods in which the consumer is willing to invest a great deal of time and effort. For example, consumers will spend a great deal of time looking for a new car or a medical procedure.

INVEST in Good Stories, and SMART Tasks (French) In XP, we think of requirements of coming in the form of user stories. It would be easy to mistake the story card for the "whole story," but Ron Jeffries points out that stories in XP have three components: Cards (their physical medium), Conversation (the discussion surrounding them), and Confirmation (tests that verify them). A pidgin language is a simplified language, usually used for trade, that allows people who can't communicate in their native language to nonetheless work together. User stories act like this.

Related: