story time! tech hangout 2014/07/30
DESCRIPTION
What is User Story and how we estimate them.TRANSCRIPT
![Page 1: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/1.jpg)
SCRUM: Story Time!
Dmitry Velykoivanenko, Galina Kostetskaya!Engineering Managers!
30/07/2014
![Page 2: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/2.jpg)
Today’s agenda
• What is a User Story?!• How to write a User Story?!• What is a Story Point?!• How to estimate a Story?!• Practice: Silent Grouping Technique!• Q&A
2 © Copyright Innovecs 2012
![Page 3: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/3.jpg)
Story
3 © Copyright Innovecs 2014
![Page 4: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/4.jpg)
User Story
A User Story is one or more sentences in the everyday or business language of the end user or user of a system that captures what a user does or needs to do as part of
his or her job function.
4 © Copyright Innovecs 2012
![Page 5: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/5.jpg)
Format
5 © Copyright Innovecs 2012
As a <role>, ! ! I want <goal/desire> !! ! ! ! ! so that <benefit>.
![Page 6: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/6.jpg)
Example
As an admin, I want to be able to delete pesky peasants’ accounts from my precious blog so that only the best remain.
6© Copyright Innovecs 2012
As a user, I want to be able to hit people over the internet so that I can show them how I feel.
As a user, I want to be able to register so that I don’t need to enter my data every time I visit the website.
![Page 7: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/7.jpg)
INVEST
7© Copyright Innovecs 2012
I! Independent! !N! Negotiable! !V! Valuable! !E! Estimable! !S! Scalable (small sized)!T! Testable!
![Page 8: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/8.jpg)
Benefits
8© Copyright Innovecs 2012
• Extreme brevity: can be done in weeks or days;!• Allows discussion of requirements throughout the
project lifetime;!• Needing very little maintenance;!• Being considered only at the time of use;!• Allowing the breaking of projects into small increments;!• Suitability for projects which have volatile or poorly
understood requirements;!• Making it easier to estimate development effort;!• Maintaining a close customer contact;
![Page 9: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/9.jpg)
Acceptance Criteria
Acceptance criteria define the boundaries of a user story, and are
used to confirm when a story is completed and working as intended.
9© Copyright Innovecs 2012
![Page 10: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/10.jpg)
Acceptance Criteria
A user cannot submit a form without completing all the mandatory fields
10© Copyright Innovecs 2012
Information from the form is stored in the registrations database
Protection against spam is working!
Payment can be made via credit card!
An acknowledgment email is sent to the user after submitting the form.
![Page 11: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/11.jpg)
Example
11© Copyright Innovecs 2012
Story: As a user, I want to be able to hit people over the internet so that I can show them how I feel.
Acceptance Criteria: Users should have a button they can press to hit people; The people hit should feel pain when they are hit; The button should be named “Hit people” with giant red letters; The users should not be able to hit the admin;
![Page 12: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/12.jpg)
Advice
12© Copyright Innovecs 2012
1. Start with the Users!2. Use Personas to Discover the Right Stories!3. Write Stories Collaboratively!4. Keep your Stories Simple and Short!5. Start with Epics!6. Decompose your Stories until they are Ready!7. Add Acceptance Criteria!8. Use Paper Cards!9. Keep your Stories Visible and Accessible!10. Don’t Solely Rely on User Stories!
![Page 13: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/13.jpg)
Definition of Ready
13© Copyright Innovecs 2012
A “ready” item should be clear, feasible and testable
![Page 14: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/14.jpg)
ESTIMATIONS
14© Copyright Innovecs 2012
![Page 15: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/15.jpg)
I HATE ESTIMATIONS
15© Copyright Innovecs 2012
![Page 16: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/16.jpg)
“5 months??? I am sure it can be done in 1! Just do it FASTER!”
![Page 17: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/17.jpg)
17© Copyright Innovecs 2012
![Page 18: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/18.jpg)
Why we can’t get rid of !estimations*!
18© Copyright Innovecs 2012
The main thing which happens during the estimation process is the development of the common understanding of the user story.
* besides nasty clients
![Page 19: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/19.jpg)
Surprise time
19© Copyright Innovecs 2012
Customers don’t really care about the hours, as their final goal is to get cost and timing. If you provide them cost and timing – they don’t care how you estimate – in store points, hours or bananas.
* besides nasty clients
![Page 20: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/20.jpg)
Uncertainty
20© Copyright Innovecs 2012
![Page 21: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/21.jpg)
Real life
21© Copyright Innovecs 2012
![Page 22: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/22.jpg)
Infinite time estimation meeting
22© Copyright Innovecs 2012
![Page 23: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/23.jpg)
Prepare
23© Copyright Innovecs 2012
1.Groom the backlog!2.Decompose complex user stories!3.Collaborate early!4.Print information!5.Have PO at hand!6.No laptops!7.Required participation !8.Bribes are ok!
* besides nasty clients
![Page 24: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/24.jpg)
Real life
24© Copyright Innovecs 2012
afterbefore
![Page 25: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/25.jpg)
Story point
25© Copyright Innovecs 2012
effort required to implement a story
![Page 26: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/26.jpg)
Estimation points
26© Copyright Innovecs 2012
![Page 27: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/27.jpg)
Process
27© Copyright Innovecs 2012
->!2h
![Page 28: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/28.jpg)
Planning poker
28© Copyright Innovecs 2012
![Page 29: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/29.jpg)
Practice time
29© Copyright Innovecs 2012
![Page 30: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/30.jpg)
The Silent Grouping Technique
30© Copyright Innovecs 2012
Preparation Lay the ground rules; set expectations
Round 1: Individual Placement Quickly get an initial size estimate for all of the user stories
Round 2: Group Placement Give everyone an opportunity to (silently) provide input to all user stories
Discussion and Reflection Resolve any disputes; reflect on experience; gain consensus before moving on; discuss insights
![Page 31: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/31.jpg)
Q&A time!
![Page 32: Story time! Tech hangout 2014/07/30](https://reader033.vdocuments.us/reader033/viewer/2022052622/5592328a1a28ab492f8b472e/html5/thumbnails/32.jpg)
Thank you!!!
Dmitry Velykoivanenko!Galina Kostetskaya!
!Engineering Managers!
!