• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Better User Stories for Faster Velocity

Better User Stories for Faster Velocity



A slideshow presentation created for a talk by Carole Court.

A slideshow presentation created for a talk by Carole Court.



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds


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.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • Well written user stories means more can be fitted into the sprint and badly written means a sprint could over run a more time required on planning
  • You can deliver the same information to someone in many ways, how they interpret it is what define whether you get what you intended- Reduce sprint time
  • Left was much faster to build that right. Understanding this at user story definition stage is key to successSimple for the user is simple for the developer if you get it right you get it write for everyone. Would have like to of done is use the beach search and have the rooms in the code
  • Challenges of agile and user sorties getting exchanged for other ones. Was to have post code look but dose not at present. IA need to work in part as well as whole in order to ensure bugs are not raised because of dropped user stoires
  • Simplification of user stories
  • Jessica Enders conducted a study on users entering phone numbers into a field without validation and was their choice to enter either a landline or mobile. ‘Less than half a percent of users made an observable mistake when entering their phone number. From 2089 mobile numbers in total, 8 had an observable error; from 643 landline numbers, 3 had an observable error.’ http://formulate.com.au/research/phone-numbers-electronic-forms/Jessica continues to state that the error percentage is low as user provided their primary contact number many times.
  • Lesson hear is do I really need to the extra overhead of validation thus greatly reducing complex for devs
  • “We recently changed how we handled error messages, and the changes received a lot of positive feedback. Instead of telling users what is wrong, we told them how to fix it. For example, we used to display the error message ‘Low Voltage Error.’ Now we display ‘Check Power Cable.’ We had character limits, but you get the idea. This approach reduced support calls and certainly improved user confidence.”James Dyson contributing to a discussion on the Society for Technical communication (STC) website for Usability and User Experience Community (UUX) which back this up.Tell the user how to fix the problem rather than stating what the problem is as will help them to resolve the error

Better User Stories for Faster Velocity Better User Stories for Faster Velocity Presentation Transcript

  • Preventing Sprint Over Run With Good User Stories
  • The Relationship Bad user story Sprint time up
  • The Example Form Validation good bad and ugly
  • Well written User Stories Email validate for @ and .com Vs Email field validate based on standard validation approach.
  • 3rd party system challenges Beach Search Error Coach Holiday Error
  • User Story Dependency
  • Optimisation of user stories
  • Can you accept error? Jessica Enders Study
  • Can you accept error? Out of a total of 2,721 phone number how many do you think incorrectly entered their number? Less than half a percent. - 2089 Mobile number 8 - 643 landline numbers 3
  • Can you accept error?
  • Form Validation
  • Some bad happened
  • Thanks Thanks Carole @cazlovam @felinesoft