PowerPoint Presentation

FELINESOFTPREVENTING SPRINT OVER RUN WITH GOOD USER STORIES

1

Felicity Morse (FM) - The Relationship2

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

2

The Example3Form Validation good bad and ugly

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 3

Well written User Stories4

3rd party system challenges5

Beach Search ErrorCoach Holiday Error

Left was much faster to build that right. Understanding this at user story definition stage is key to success

Simple 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

5

User Story Dependency6

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 stories

6

Optimisation of user stories

Simplification of user stories

7

Can you accept error?8

Jessica Enders Study

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.

8

Can you accept error?9Out 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

Lesson hear is do I really need to the extra overhead of validation thus greatly reducing complex for devs

9

Can you accept error?10

Form Validation11

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

11

Some bad happened12