I got asked today by my Boss, “what is a story?” so i gave him a 5 minute overview, then i realised i could share this.
Simply put a story is a very short (should fit on an description of a piece of functionality.
A story serves several purposes.
It is used to estimate and identify areas of risk during initial release planning and ongoing through development.
A story is always written from the business perspective, and is normally based on an action (e.g. display search results, search stock).
A story is testable through the UI if application is UI based.
Our Stories are written using the form: “As an X I want to Y so I can Z”
Stories answer these questions:
- Who is ‘doing’ the story (As an X).
- What action is being taken (I want to Y).
- What business need is the story hitting? (so I can Z).
They are at first very high level and i’ve found that initial story cards are almost always revised and rewritten. They are usually rewritten to lower levels of granularity so that at development time they are testable.
They are small enough that it only takes one iteration to complete. If they are too complex, they are expanded into narratives.
Stories can be either functional or non-functional, E.g. performance should be a story.
ThoughtWorks write the stories on ThoughtWorks branded index cards which are 147mm wide and 104mm high which are bigger than the index cards we could get from our stationers. (Who stocks these size cards? Viking have them on-line, but staples have them in store only. They are called 6×4 index cards by both)
They write on the cards to ensure the story is kept to a small size, this helps the customer “see” what they are saying. The cards are usually kept visible on a board. a Kanban board.
In Agile projects, it’s common practice to share the project status via “big visible charts” on a wall in the project room (or elsewhere if a room is not available).
Kanban is a Japanese word which loosely translated, means card or sign. In a “Lean” production system, Kanban is a method which uses standard units or lot sizes (our story cards). The methodology dictates that a new card is only “pulled” into the system when the work represented by a card that is “in Play” is completed.
It works really well. I was away from the project for a couple of days to deal with recruitment. When i returned to the meeting i was able to jump straight in after reading the board for few minutes and attending the morning meeting.