Using User Stories

I have used user stories for some time to develop products and am currently using this process in developing several products it is good to be able to outline the process quickly. To do this I use a simple construct and process to help to in-bed this practice. I will quickly go through this process.

Phase 1

The user story is a quick way of explaining requirements by giving them a simple format that allows the requirements to be documented without thinking of how and when they will solve this issue. A basic construct for this could be shown like this:

As an (User), I want to/ I need to (Feature), so I can/ with a goal off achieving (Purpose or Reason)

• As an Accountant, I need to see a monthly profit and Loss when I open the client details so I can get the information quickly
• As an client, I want to be able to order the same trips again easily so I can get the flight booked quickly

Phase 2

This is creating basic outline specification to define the User Stories in more detail. this is done quickly through developing some basic outline. These should be done in maybe a period of an hour or so, and it is important at this stage that it is kept light.

User Stories: These form the outline and the title of the card.

Wire-frames and Details: draft a quick wire-frame of the screen and the outline so that the team (product owner and development team) have a common understanding. These are basic wire-frames often drafted on paper and then converted in to a more detailed form at a later date after the meeting. This is also accompanied by a brief narrative of the functionality of the feature or features that have to be created to achieve this user stories.

Test Criteria: A brief outline of outcomes that will show the stores have been achieved.

Estimation: An outline of the the time and resource involved in developing this User Story

Phase 3

When the User Story is moved in to the next block of development or as it moves up the pile it will be refined further in to more detail. Through conversation and in documentation (to the degree that is required by the team) at each stage as the information is updated the story and other artifacts are refined and detailed more.

This process has helped to outline functionality so that the project is truly achieving the aim and goals, I have to stress that this only works if all involved from the design team and development team are focused, dedicating the time and effort to do this.

Popularity: 26% [?]

Related posts:

1. Software Demos – Bringing the user on Board
2. Agile Development in a Commercial Organisation
3. 50% of Facebook User Access on a Mobile Device
4. Pair Programming- Software Development Learning Steps
5. Agile Retrospective – Lessons Learned