Time Budget Quality ScopeMost of
the time, projects are delivered late, and out of budget. Quality is neglected and the product isn’t tested at a sufficient level.
Time Budget Quality Scope User
StoriesThe solution for the first three dimensions lies in the fourth dimension. If you define your scope using User Stories, a lot of trouble canbe avoided.
User Story: As a (type
of user) I want to (goal) so that (reason)What are User Stories? It’s a specific way to describe pieces of functionality from a user’s point of view. They consist of the type ofuser, the goal and the reason. This last one is important, as it reflects business value.
User Story: As a cyclist
I want to switch gears so that I can go fasterExample for a bike. Note that the business value is not in the gears but in going faster.
User Story: As a visitor
of the website I want to submit my email address so that I can receive the newsletterExample for a website. Here value is not in the submitting process, but actually getting that newsletter in your mailbox.
3 C’s: Card Conversation Confirmation
(Ron Jeffries) http://xprogramming.com/articles/expcardconversationconfirmation/A User Story is more than just that sentence. It consists of three C’s.
CardThe Card holds the “as
a (type of user) I want to (goal) so that (reason)”. By putting the story on a card, it’s easy to put on a wall,place it on the table, hold it in your hand, …
“Those who want the product
(software) must communicate with those who will build it.” Mike CohnA clear benefit of User Stories is the focus on communication between business and development. The balance between the two iscrucial. They are both equally responsible to negotiate the scope.
Don’t get caught up in
lengthy requirement documents that nobody reads. Don’t think when it’s written down, it’s clear for everyone.