• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
User Stories. Develop better products faster and cheaper.
 

User Stories. Develop better products faster and cheaper.

on

  • 5,718 views

Presentation on User Stories from Barcamp VRT (21/1/2012) Questions? twitter.com/bartvermijlen . Get your invite for private beta on http://www.userstorieshq.com

Presentation on User Stories from Barcamp VRT (21/1/2012) Questions? twitter.com/bartvermijlen . Get your invite for private beta on http://www.userstorieshq.com

Statistics

Views

Total Views
5,718
Views on SlideShare
4,745
Embed Views
973

Actions

Likes
19
Downloads
154
Comments
0

9 Embeds 973

http://www.wayup.be 416
http://bart.vermijlen.be 313
http://www.bartvermijlen.com 209
http://feeds.feedburner.com 15
http://ybyf.lcl 11
http://a0.twimg.com 4
http://4esoinf-cfc.blogspot.com 2
http://www.twylah.com 2
http://us-w1.rockmelt.com 1
More...

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    User Stories. Develop better products faster and cheaper. User Stories. Develop better products faster and cheaper. Presentation Transcript

    • User StoriesDevelop better products faster and cheaper.
    • about.me/bartvermijlenHi. This is me!
    • Where did we go wrong?Projects fail. Many projects fail. But why? How come?
    • Time Budget Quality ScopeA project has 4 dimensions. Where do they fail?
    • 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, …
    • ConversationBut the real value is not in the Card. The Card is just the fuel for Conversation. User Stories force you to talk about the right things.
    • ConfirmationA User Story also implies Confirmation. When is a User Story “confirmed”?
    • Confirmation Acceptance CriteriaWhen it’s Acceptance Criteria are met! These Criteria define when a User Story will be accepted as “ready”, how the piece offunctionality is tested, what the definition of “done” is for the User Story.
    • “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.
    • Describe what will happen, but not how it will happen.Don’t focus on technologies or processes. Describe what must happen for your user.
    • Focus on users and their actions.A user has a face. Keep that in mind. When you develop for children or their grandparents, put it in the center.
    • User centric scope definition = more time/money for qualityWhen you talk about scope the right way, development will go faster, and you’ll end up with more time to invest in quality and testing.
    • Fast deliveryObviously you’ll deliver early.
    • Further reading: Scrum and XP from the Trenches – H. Kniberg User Stories Applied – M. CohnRead these books. They’re Scrum and XP oriented, but don’t let that get in the way.
    • Userstorieshq.comCurrently we’re working on a little tool to manage your User Stories. Request your invite for private beta.
    • @bartvermijlen