Abstract image of a woman sitting on books and studying on a laptop

Effective user stories for your agile or Scrum team

Download as PPTX, PDF
DigitalCatapultDevelopmentPractices, profile picture
DigitalCatapultDevelopmentPractices

The document provides training material focused on effective user stories in agile software development, outlining the definition, structure, and best practices for writing user stories. It emphasizes the importance of competencies to be gained, such as understanding the components of user stories, the investment criteria (INVEST), and maintaining a healthy backlog. Overall, the material encourages interactive learning through classroom activities and discussions to enhance understanding of agile requirements.

Technology
1 of 60
Downloaded 134 times
1
2
Most read
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Effective User Stories Andrew Rusling Agile Coach @andrewrusling
WARNING, WARNING, WARNING Pre-reading these slides will significantly damage the learning opportunity for yourself. This training material is designed to be delivered in a class room situation, with activities and discussion. If you intend to attend this training, please do not read past the competencies slide (4). 2
Contents 1. Why 2. What 3. INVEST 4. Getting to Done 5. Re-writing 6. Backlog health 7. Wrap up 3
Competencies to be gained At the end of this session I hope that you will be able to: • Summarise why User Stories are used for Agile Software Development • Describe the key elements of a User Story • Write out one of two common templates for User Stories • Summarise how User Story text and Acceptance Criteria differ • List the three C's • Compare user stories based on the strength of their INVEST properties • List the four items that are necessary for a story to be Done • Write User Stories based on a detailed request • Re-write poor User Stories into Effective User Stories • Identify a healthy backlog • List several ways a backlog can become unhealthy • Identify an unhealthy backlog 4
Why 5
Agile Software Development Agile values and principles • Business people working daily with the team • Frequent deliveries of working software • Frequent feedback • Embrace change 6
Agile Requirements Agile needs an approach to requirements, that is: • Lightweight • Change friendly • Collaborative 7
What 8
User Stories 9 Title As a [PERSONA] I want [GOAL] So that [BUSINESS BENEFIT] Title Persona – Type of User, potentially described as an imaginary person. Goal – Change / Functionality / Action, how we intend for the software to change. Business Benefit – Either directly beneficial to the business, or implied benefit to the business by impacting the behaviour of the Persona. Re-enforcing elements In order to [BUSINESS BENEFIT] As a [PERSONA] I want [GOAL]
An example 10 Authorize loans As a Bank Branch Manager I want to be able to authorize loans to a higher financial limit than Bank Tellers So that I can minimize financial risk and allow for high value loans at the same time
The three C’s 11 Card • Promise for a conversation • Token (Visual, Tangible) • Story on front • Acceptance Criteria on back Conversation • PO and Team • With customer • Elaborate details Confirmation • PO verification • Automated tests
User Stories are NOT • Items that get ‘approved’ • Detailed Requirements • Use Cases 12
INVEST 13
INVEST by Bill Wake • Of order of user story delivery • Of internal and especially external dependencies Independent • Flexible scope • None specific language • Explain the intention, not the implementation Negotiable • Value is clear to everyone • Persona matches Benefit & Goal will deliver the benefit. • Avoid technical / role specific language Valuable • Clear and concise explanation • Avoid technical / role specific language Estimatable • Easily fits into a Sprint. i.e. < 20% of velocity. • Definitely not > 33% of velocity Small • Can be automated • Avoid external testing / long test suites Testable 14
Compromises are necessary Big stories are usually: • Independent • Negotiable • Valuable but not • Estimable • Testable • Small. They may also contain gold plating. 15 Non Negotiable stories are usually, Estimable & Testable Splitting into Smaller stories, may reduce Value and increase dependencies (especially if split poorly).
Exercise INVESTing 16
INVESTing in our Stories As a top tier player of Towering Inferno I might need a total score in excess of the current limit of 9999. I would like this limit raising to one million So that I can obtain a huge total score. As a top tier player of Towering Inferno I would like the total score limit raised from 9999 to 1 million So that I can obtain a huge total score. As a top tier player of Towering Inferno I would like the total score limit raised to one million So that the artificial limit of 9999 does not hinder my enjoyment of the game
INVESTing in our Stories As a top tier player of Towering Inferno I might need a total score in excess of the current limit of 9999. I would like this limit raising to one million So that I can obtain a huge total score. ‘So that’ duplicates the ‘I want’, is less concise then middle story. As a top tier player of Towering Inferno I would like the total score limit raised from 9999 to 1 million So that I can obtain a huge total score. As a top tier player of Towering Inferno I would like the total score limit raised to one million So that the artificial limit of 9999 does not hinder my enjoyment of the game ‘So that’ explains the business value for the change
INVESTing in our Stories As a fan of South Park I want a humorous South Park themed game, that includes a couple of difficult mini games So that I can play a game that challenges and entertains me As the project team I want a prototype with 1st cut art of a humorous South Park game (no mini games needed) So that we can determine if the project is worth proceeding with As a fan of South Park I want a mini game feels like ten pin bowling with the main characters So that I can have a laugh at some of their crazy antics, that are different to the main game.
INVESTing in our Stories As a fan of South Park I want a humorous South Park themed game, that includes a couple of difficult mini games So that I can play a game that challenges and entertains me This is a HUGE story. As the project team I want a prototype with 1st cut art of a humorous South Park game (no mini games needed) So that we can determine if the project is worth proceeding with This is the smallest story As a fan of South Park I want a mini game feels like ten pin bowling with the main characters So that I can have a laugh at some of their crazy antics, that are different to the main game. This is a BIG story.
INVESTing in our Stories As a top tier player of Towering Inferno I want to receive a larger bonus than low tier players in the weekly draw So that I feel I am valuable player, that the game values As a Towering Inferno Game Manager I want the weekly bonus amounts to be configured in WeeklyBonusAmounts table in the database So that I can encourage our top tier players to keep playing As a Towering Inferno Game Manager I want to be able to set bonus amounts by player tier in the weekly draw So that I can encourage our top tier players to keep playing
INVESTing in our Stories As a top tier player of Towering Inferno I want to receive a larger bonus than low tier players in the weekly draw So that I feel I am valuable player, that the game values Not a good business value, everyone wants to be paid more. As a Towering Inferno Game Manager I want the weekly bonus amounts to be configured in WeeklyBonusAmounts table in the database So that I can encourage our top tier players to keep playing Specifies implementation As a Towering Inferno Game Manager I want to be able to set bonus amounts by player tier in the weekly draw So that I can encourage our top tier players to keep playing No implementation details, has real business value
INVESTing in our Stories As a Data Analyst I want API documentation in the same format as Twitter API documents So that it is easy to get started with the Data Mangler service As a Data Analyst I want API documentation for the Data Mangler service So that it is easy to get started using it As the Product Owner I want API documentation in the same format as Twitter API documents So that it is easy to get started with the Data Mangler service
INVESTing in our Stories As a Data Analyst I want API documentation in the same format as Twitter API documents So that it is easy to get started with the Data Mangler service Too specific, it locks down choice / may miss out on better ideas As a Data Analyst I want API documentation for the Data Mangler service So that it is easy to get started using it Is Negotiable, appropriate user, with a clear business value As the Product Owner I want API documentation in the same format as Twitter API documents So that it is easy to get started with the Data Mangler service PO is usually the wrong user, they rarely get business benefit
Getting to Done 25
Getting to Done 26 • From the User Story text has been satisfied Intention • All completed Acceptance Criteria • All completed • Or accepted as Not Applicable Definition of Done • Product Owner has reviewed and accepted the story. Reviewed
Acceptance Criteria vs. User Stories User Story • Intention • Negotiable • Open yet concise Acceptance Criteria • Requirements • Once set non-negotiable • Specific and concise 27
Acceptance Criteria • Explain Product Owner expectations • Can clarify scope (either in or out) • Can clarify assumptions • Can detail implementation (but only when critical) • Written on the back of the index card. • Can be detailed, but should not be a specification. • Added/Change over time (including within the Sprint) • Not mandatory, but often used. 28
Acceptance Criteria an example 29 Acceptance Criteria • £ Limit will be hard coded in this version. • User must manually load the loan (no notification of loan awaiting approval)
Context 30 Product Backlog User Story Title Story text Acceptance Criteria Notes Definition of Done Software Persona Persona Persona Release Plan Tests • • • •
Exercise 31 Story vs Acceptance Criteria
Home Chef My Supermarket is an existing web site that allows shoppers to fill a grocery basket then shop around between supermarkets to get the best deal before arranging the shopping to be delivered. HomeChef is our application, that we are building. It already allows our users to quickly generate shopping lists from their favourite recipes. 32
Identify User Story, Acceptance Criteria, Notes 33 We are going to integrate HomeChef to MySupermarket, allowing our users to quickly order the groceries they need to cook a weeks worth of their favourite recipes. This should be a seamless process, that is resistant to errors and network drop outs. Our user research shows ours will not wait for longer than 15 seconds for any action in our application. Once the user has selected several recipes, there should be an easy to see and use option to send their combined shopping list to their My Supermarket account. It would be nice if there was some indication that the transfer is processing, while the user waits. Investigations have shown that configuring a My Supermarket account in our software will be difficult. A hard coded configuration exists that you can use. We expect that it is our most thrifty home cooks that will use this feature. Other users may not view the extra step worth it for the cost saving it provides. User Story Acceptance Criteria Notes
Resulting elements 34 We are going to integrate HomeChef to MySupermarket, allowing our users to quickly order the groceries they need to cook a weeks worth of their favourite recipes. This should be a seamless process, that is resistant to errors and network drop outs. Our user research shows ours will not wait for longer than 15 seconds for any action in our application. Once the user has selected several recipes, there should be an easy to see and use option to send their combined shopping list to their My Supermarket account. It would be nice if there was some indication that the transfer is processing, while the user waits. Investigations have shown that configuring a My Supermarket account in our software will be difficult. A hard coded configuration exists that you can use. We expect that it is our most thrifty home cooks that will use this feature. Other users may not view the extra step worth it for the cost saving it provides. User Story Acceptance Criteria Notes
Result as User Story 35 Integrate HomeChef to MySupermarket As a thrifty home cook I want to easily be able to send my shopping list to my MySupermarket account So that I can save money and time on my weekly shopping Acceptance Criteria • Must be resistant to errors and network drop outs • Do not have to configure the account details, that will be a different story Notes • A transferring animation is a nice to have
Identify User Story, Acceptance Criteria, Notes 36 ‘Daily Journal’ needs to add photo support to the website version. We are losing younger people to our competitor ‘PhotoJournal’ and have to stop this. It is crucial that we support a wide variety of image types so that we don’t exclude many users. So jpg, jpeg, png, etc must be accepted. With the current database issues we need to limit the upload size so that we avoid further outages. Analysis is ongoing regarding which image types are most used and information will be forth coming. This feature can not damage our reputation as the fastest journaling app on the market. We are going to launch a media campaign next month: ‘Daily Journal the fastest journal app, now includes photos with five amazing filters. It is your one-stop journaling app.’ User Story Acceptance Criteria Notes
Resulting elements 37 ‘Daily Journal’ needs to add photo support to the website version. We are losing younger people to our competitor ‘PhotoJournal’ and have to stop this. It is crucial that we support a wide variety of image types so that we don’t exclude many users. So jpg, jpeg, png, etc must be accepted. With the current database issues we need to limit the upload size so that we avoid further outages. Analysis is ongoing regarding which image types are most used and information will be forth coming. This feature can not damage our reputation as the fastest journaling app on the market. We are going to launch a media campaign next month: ‘Daily Journal the fastest journal app, now includes photos with five amazing filters. It is your one-stop journaling app.’ User Benefit is not clearly represented Business Benefit is to stop losing customers User Story Acceptance Criteria Notes
Result as User Story 38 Add photos with filters to website As a young journal writer I want to include fun looking photos with my journal entries So that my entries are more engaging and memorable Acceptance Criteria • Supports photo types ??? • Photo size limited to ??? • Performance must remain fastest on the market. • At least five filters must be implemented. Notes • Due prior to end of next month, to align with media campaign.
Exercise Rewriting 39
To rewrite Ensure that every team member has enough knowledge to deploy the services and run the tests Needs to be a shared document on how to do this to support team and inform new members 40
One possible answer 41 Team able to deploy and test services As a development team members I want to know how to deploy and test the CRH services So that I can gain fast feedback, without interrupting busy team members Acceptance Criteria • NONE (Definition of Done already covers off the requirement to test things) Notes • NONE
To rewrite Onboard Mary Evans Data 535K lines tilde separated field with SME / Collection owner - not consistent grouping in this field Business value is to count 200+ collection owners 3 times Pre process, parse Store audit log persistently 42
One possible answer 43 Onboard mary evans data In order to score highly on our SME engagement metric As the Digital Catapult I want to upload the data from Mary Evans in batches that maximise the number of batches each SME has some data Acceptance Criteria • NONE Notes • SME’s need to appear in three batches to count as engaged.
To rewrite Implement Hub Control Service Ping all services in domain every xSecs as health check PostGres as store (can be log too) API to inform of status 1 for registration of service 1 get address of one of registered service 1 to receive info about service Clean-up service 44
One possible answer 45 Hub control service As a hub repository owner I want the ability to actively monitor and to programmatically check the health of my hub repository So that I can offer a good level of service to my customers Notes • Ping all services in domain every xSecs as health check • PostGres as store (can be log too) • API to inform of status • 1 for registration of service • 1 get address of one of registered service • 1 to receive info about service • Clean-up service
To rewrite Clean and well tested deployment instructions Business value - lowered rework, lowered risk to reputation Chef cookbooks working Need a catalogue of these one click services For Beta users to set up their own services 46
One possible answer 47 Deployment Instructions In order to save time deploying the CRH As a beta user I want clean easy to follow deployment instructions Acceptance Criteria • Chef cookbooks working • Need a catalogue of these one click services Notes • NONE
Backlog health 48
A healthy backlog is 49 • Prioritised by PO for ROI • Ordered by team for dependencies, etc. Ordered • Top contains 1.5 to 2 sprints of INVESTments • Next comes Chunks • Followed by Epics Balanced • A mixture of work that roughly matches team capability • Considering cross skilling / up skilling may be a better investment in the long term Diverse
A healthy backlog 50 Waterline • Ordered • Balanced • Diverse
Exercise Backlog health 51
Why is it unhealthy? What symptoms will occur? 52 • Not prioritised • Not ordered • Too many priority 1’s • No guidance from PO • Hard to plan sprints
Why is it unhealthy? What symptoms will occur? 53 • All INVESTments • Hard to see the big picture • Extra effort to maintain the backlog • Lots of grooming effort will be wasted • Lots of stories will be thrown away
Why is it unhealthy? What symptoms will occur? 54 • Not enough INVESTments • Hard to plan sprint • Waste time in planning grooming stories (usually in a rush)
Why is it unhealthy? What symptoms will occur? 55 • Not enough diversity • May not fit team capabilities • Hard to balance work in the sprint
Wrap Up 56
Summary 57
Competencies to be gained I hope that you are now able to: • Summarise why User Stories are used for Agile Software Development • Describe the key elements of a User Story • Write out one of two common templates for User Stories • Summarise how User Story text and Acceptance Criteria differ • List the three C's • Compare user stories based on the strength of their INVEST properties • List the four items that are necessary for a story to be Done • Write User Stories based on a detailed request • Re-write poor User Stories into Effective User Stories • Identify a healthy backlog • List several ways a backlog can become unhealthy • Identify an unhealthy backlog 58
Time to share
Reference Material How to write a useful User Story – article from Gov.uk User Stories explained – article with examples in Agile Atlas 60

More Related Content

PDF
Workshop - Writing Good User Stories
Easy Agile
 
PPTX
User stories in agile software development
Sandra Svanidzaitė, PhD, CBAP
 
PPT
Writing Effective User Stories
Janeve George
 
PDF
Effective User Stories
Derek Neighbors
 
PPTX
Project Management vs. Program Management: Strategies for Transition Success
Ruffin Veal and Associates, Inc.
 
PDF
Introduction to Systems Engineering
Animesh Chaturvedi
 
PPTX
Strategies to split user stories
cpolc
 
PDF
User story splitting techniques
Ashutosh Rai
 
Workshop - Writing Good User Stories
Easy Agile
 
User stories in agile software development
Sandra Svanidzaitė, PhD, CBAP
 
Writing Effective User Stories
Janeve George
 
Effective User Stories
Derek Neighbors
 
Project Management vs. Program Management: Strategies for Transition Success
Ruffin Veal and Associates, Inc.
 
Introduction to Systems Engineering
Animesh Chaturvedi
 
Strategies to split user stories
cpolc
 
User story splitting techniques
Ashutosh Rai
 

What's hot (20)

PDF
User Stories Fundamentals
Moisés Armani Ramírez
 
PPTX
User Stories explained
Martin Lapointe, M.T.I.
 
PDF
Writing Good User Stories (Hint: It's not about writing)
one80
 
PPTX
User Story Workshop
Peter Antman
 
PPT
Introducing Agile User Stories
Ram Srivastava
 
PDF
User Story Splitting
trishly
 
PPTX
User Story
Sunil Jakkaraju
 
PDF
Story of user story
Balaji Sathram
 
PPTX
User Story Splitting.pptx
Paul Boos
 
PPTX
Writing User Stories (04/2012)
Mai Quay
 
PPTX
Agile User Stories
kahgeh75
 
PPTX
Agile Story Writing
Intelliware Development Inc.
 
PDF
IIT Academy: 204 User stories and acceptance criteria
Steven HK Ma ｜ 馬國豪
 
PPTX
How to Break the Requirements into User Stories
ShriKant Vashishtha
 
PDF
User Story Smells & Anti-patterns
Fadi Stephan
 
PDF
User Stories
Dr. Tathagat Varma
 
PDF
Cheat Sheet: 8 ways to split your user stories
Payton Consulting
 
PDF
Ten Concrete Techniques to Split User Stories
Night Wolf
 
PPT
Invest In Good User Stories
Craig Brown
 
PPTX
21 Story Splitting Patterns
Kent McDonald
 
User Stories Fundamentals
Moisés Armani Ramírez
 
User Stories explained
Martin Lapointe, M.T.I.
 
Writing Good User Stories (Hint: It's not about writing)
one80
 
User Story Workshop
Peter Antman
 
Introducing Agile User Stories
Ram Srivastava
 
User Story Splitting
trishly
 
User Story
Sunil Jakkaraju
 
Story of user story
Balaji Sathram
 
User Story Splitting.pptx
Paul Boos
 
Writing User Stories (04/2012)
Mai Quay
 
Agile User Stories
kahgeh75
 
Agile Story Writing
Intelliware Development Inc.
 
IIT Academy: 204 User stories and acceptance criteria
Steven HK Ma ｜ 馬國豪
 
How to Break the Requirements into User Stories
ShriKant Vashishtha
 
User Story Smells & Anti-patterns
Fadi Stephan
 
User Stories
Dr. Tathagat Varma
 
Cheat Sheet: 8 ways to split your user stories
Payton Consulting
 
Ten Concrete Techniques to Split User Stories
Night Wolf
 
Invest In Good User Stories
Craig Brown
 
21 Story Splitting Patterns
Kent McDonald
 
Ad

Similar to Effective user stories for your agile or Scrum team (20)

PPT
A ready to use Template for pitching your Business for funding! See updated v...
Alok Rodinhood Kejriwal
 
PPTX
How to Succeed in the F2P Market: Stats, Best Practices and Common Mistakes |...
Jessica Tams
 
PPTX
R2 Games USA - Maximizing F2P Game Monetization Presentation (Respawn 2016)
David Piao Chiu
 
PPTX
The Whole Story of The User Story
XPDays
 
PPTX
User Story Workshop
Steve Rogalsky
 
PPTX
6 Easy Steps to writing that perfect Job Description (JD)
Alok Rodinhood Kejriwal
 
PDF
Jenny Martin - Death by User Stories | Agile Delivery 2017
Kayleigh Tiernan
 
PDF
R2 Games F2P Monetization Presentation and Clicker Heroes Case Study: Best Pr...
David Piao Chiu
 
PDF
Agile Story Writing
Intelliware Development Inc.
 
PPTX
Xp 2016 superchargeyourproductbacklogwithuserstories-suzannelaz
Laz Allen
 
PDF
User Stories Training
Clarion Marketing
 
PPTX
Gamification
HyeonKyu Shin
 
PPT
Luke Hohmann's Software Guru 2009 Keynote: Innovation In Software
Enthiosys Inc
 
PDF
Session15+16-User Story (2).pdf
PeterTran514407
 
PPTX
User story tune up
nhoreillys
 
PPTX
R2 Games - F2P Monetization Deck (May 2015 COMPRESSED)
David Piao Chiu
 
PPTX
How to Foster Engagement and Understanding Using Agile
Salesforce Admins
 
PDF
[Webinar] conditional jump
Tars
 
PPTX
SF Game Dev Meetup (Oct 2019): To Self-Publish Or Not To Self-Publish, David ...
David Piao Chiu
 
PDF
User-Stories-for-Agile-Requirements-Norwegian-Developers-Conference-2014.pdf
SLowe7
 
A ready to use Template for pitching your Business for funding! See updated v...
Alok Rodinhood Kejriwal
 
How to Succeed in the F2P Market: Stats, Best Practices and Common Mistakes |...
Jessica Tams
 
R2 Games USA - Maximizing F2P Game Monetization Presentation (Respawn 2016)
David Piao Chiu
 
The Whole Story of The User Story
XPDays
 
User Story Workshop
Steve Rogalsky
 
6 Easy Steps to writing that perfect Job Description (JD)
Alok Rodinhood Kejriwal
 
Jenny Martin - Death by User Stories | Agile Delivery 2017
Kayleigh Tiernan
 
R2 Games F2P Monetization Presentation and Clicker Heroes Case Study: Best Pr...
David Piao Chiu
 
Agile Story Writing
Intelliware Development Inc.
 
Xp 2016 superchargeyourproductbacklogwithuserstories-suzannelaz
Laz Allen
 
User Stories Training
Clarion Marketing
 
Gamification
HyeonKyu Shin
 
Luke Hohmann's Software Guru 2009 Keynote: Innovation In Software
Enthiosys Inc
 
Session15+16-User Story (2).pdf
PeterTran514407
 
User story tune up
nhoreillys
 
R2 Games - F2P Monetization Deck (May 2015 COMPRESSED)
David Piao Chiu
 
How to Foster Engagement and Understanding Using Agile
Salesforce Admins
 
[Webinar] conditional jump
Tars
 
SF Game Dev Meetup (Oct 2019): To Self-Publish Or Not To Self-Publish, David ...
David Piao Chiu
 
User-Stories-for-Agile-Requirements-Norwegian-Developers-Conference-2014.pdf
SLowe7
 
Ad

More from DigitalCatapultDevelopmentPractices (8)

PPTX
Agile & Lean PMO
DigitalCatapultDevelopmentPractices
 
PPTX
Agile Scrum Lean & Kanban explained in a flash
DigitalCatapultDevelopmentPractices
 
PPTX
Kanban for Business
DigitalCatapultDevelopmentPractices
 
PPTX
Lean for Business Teams
DigitalCatapultDevelopmentPractices
 
PPTX
Collaborative Techniques
DigitalCatapultDevelopmentPractices
 
PPTX
Agile Project Management
DigitalCatapultDevelopmentPractices
 
PPTX
Agile for Business
DigitalCatapultDevelopmentPractices
 
PPTX
Agile Estimation
DigitalCatapultDevelopmentPractices
 
Agile & Lean PMO
DigitalCatapultDevelopmentPractices
 
Agile Scrum Lean & Kanban explained in a flash
DigitalCatapultDevelopmentPractices
 
Kanban for Business
DigitalCatapultDevelopmentPractices
 
Lean for Business Teams
DigitalCatapultDevelopmentPractices
 
Collaborative Techniques
DigitalCatapultDevelopmentPractices
 
Agile Project Management
DigitalCatapultDevelopmentPractices
 
Agile for Business
DigitalCatapultDevelopmentPractices
 
Agile Estimation
DigitalCatapultDevelopmentPractices
 

Recently uploaded (20)

PPTX
Build automations faster and more reliably with UiPath ScreenPlay
AndreeaTom
 
PDF
CEH Module 2 Footprinting CEH V13, concepts
ammarhassan185568
 
PPTX
SGT Report The Beast Plan and Cyberphysical Systems of Control
hopegirl587
 
PPTX
AI-driven Assurance Across Your End-to-end Network With ThousandEyes
ThousandEyes
 
PDF
The-Future-of-Automotive-Quality-is-Here-AI-Driven-Engineering.pdf
Kalilur Rahman
 
PDF
Lung cancer patients survival prediction using outlier detection and optimize...
IAESIJAI
 
PDF
Advancing precision in air quality forecasting through machine learning integ...
IAESIJAI
 
PPTX
Internet of Everything -Basic concepts details
sendilkumar66
 
PDF
Human Computer Interaction Miterm Lesson
JasperGarcia9
 
PDF
AI.gov: A Trojan Horse in the Age of Artificial Intelligence
Michael Weaver
 
PDF
Data Virtualization in Action: Scaling APIs and Apps with FME
Safe Software
 
PDF
CXOs-Are-you-still-doing-manual-DevOps-in-the-age-of-AI.pdf
Kalilur Rahman
 
PDF
“The Future of Visual AI: Efficient Multimodal Intelligence,” a Keynote Prese...
Edge AI and Vision Alliance
 
PDF
Decision Optimization - From Theory to Practice
Eray Cakici
 
PDF
ment.tech-Siri Delay Opens AI Startup Opportunity in 2025.pdf
thomasnova26
 
PDF
The AI Revolution in Customer Service - 2025
Body of Knowledge
 
PDF
Aug23rd - Mulesoft Community Workshop - Hyd, India.pdf
Ravi Tamada
 
PDF
Co-training pseudo-labeling for text classification with support vector machi...
IAESIJAI
 
PDF
The-2025-Engineering-Revolution-AI-Quality-and-DevOps-Convergence.pdf
Kalilur Rahman
 
PDF
MENA-ECEONOMIC-CONTEXT-VC MENA-ECEONOMIC
Mustafa Kuğu
 
Build automations faster and more reliably with UiPath ScreenPlay
AndreeaTom
 
CEH Module 2 Footprinting CEH V13, concepts
ammarhassan185568
 
SGT Report The Beast Plan and Cyberphysical Systems of Control
hopegirl587
 
AI-driven Assurance Across Your End-to-end Network With ThousandEyes
ThousandEyes
 
The-Future-of-Automotive-Quality-is-Here-AI-Driven-Engineering.pdf
Kalilur Rahman
 
Lung cancer patients survival prediction using outlier detection and optimize...
IAESIJAI
 
Advancing precision in air quality forecasting through machine learning integ...
IAESIJAI
 
Internet of Everything -Basic concepts details
sendilkumar66
 
Human Computer Interaction Miterm Lesson
JasperGarcia9
 
AI.gov: A Trojan Horse in the Age of Artificial Intelligence
Michael Weaver
 
Data Virtualization in Action: Scaling APIs and Apps with FME
Safe Software
 
CXOs-Are-you-still-doing-manual-DevOps-in-the-age-of-AI.pdf
Kalilur Rahman
 
“The Future of Visual AI: Efficient Multimodal Intelligence,” a Keynote Prese...
Edge AI and Vision Alliance
 
Decision Optimization - From Theory to Practice
Eray Cakici
 
ment.tech-Siri Delay Opens AI Startup Opportunity in 2025.pdf
thomasnova26
 
The AI Revolution in Customer Service - 2025
Body of Knowledge
 
Aug23rd - Mulesoft Community Workshop - Hyd, India.pdf
Ravi Tamada
 
Co-training pseudo-labeling for text classification with support vector machi...
IAESIJAI
 
The-2025-Engineering-Revolution-AI-Quality-and-DevOps-Convergence.pdf
Kalilur Rahman
 
MENA-ECEONOMIC-CONTEXT-VC MENA-ECEONOMIC
Mustafa Kuğu
 

Effective user stories for your agile or Scrum team

  • 1. Effective User Stories Andrew Rusling Agile Coach @andrewrusling
  • 2. WARNING, WARNING, WARNING Pre-reading these slides will significantly damage the learning opportunity for yourself. This training material is designed to be delivered in a class room situation, with activities and discussion. If you intend to attend this training, please do not read past the competencies slide (4). 2
  • 3. Contents 1. Why 2. What 3. INVEST 4. Getting to Done 5. Re-writing 6. Backlog health 7. Wrap up 3
  • 4. Competencies to be gained At the end of this session I hope that you will be able to: • Summarise why User Stories are used for Agile Software Development • Describe the key elements of a User Story • Write out one of two common templates for User Stories • Summarise how User Story text and Acceptance Criteria differ • List the three C's • Compare user stories based on the strength of their INVEST properties • List the four items that are necessary for a story to be Done • Write User Stories based on a detailed request • Re-write poor User Stories into Effective User Stories • Identify a healthy backlog • List several ways a backlog can become unhealthy • Identify an unhealthy backlog 4
  • 6. Agile Software Development Agile values and principles • Business people working daily with the team • Frequent deliveries of working software • Frequent feedback • Embrace change 6
  • 7. Agile Requirements Agile needs an approach to requirements, that is: • Lightweight • Change friendly • Collaborative 7
  • 9. User Stories 9 Title As a [PERSONA] I want [GOAL] So that [BUSINESS BENEFIT] Title Persona – Type of User, potentially described as an imaginary person. Goal – Change / Functionality / Action, how we intend for the software to change. Business Benefit – Either directly beneficial to the business, or implied benefit to the business by impacting the behaviour of the Persona. Re-enforcing elements In order to [BUSINESS BENEFIT] As a [PERSONA] I want [GOAL]
  • 10. An example 10 Authorize loans As a Bank Branch Manager I want to be able to authorize loans to a higher financial limit than Bank Tellers So that I can minimize financial risk and allow for high value loans at the same time
  • 11. The three C’s 11 Card • Promise for a conversation • Token (Visual, Tangible) • Story on front • Acceptance Criteria on back Conversation • PO and Team • With customer • Elaborate details Confirmation • PO verification • Automated tests
  • 12. User Stories are NOT • Items that get ‘approved’ • Detailed Requirements • Use Cases 12
  • 14. INVEST by Bill Wake • Of order of user story delivery • Of internal and especially external dependencies Independent • Flexible scope • None specific language • Explain the intention, not the implementation Negotiable • Value is clear to everyone • Persona matches Benefit & Goal will deliver the benefit. • Avoid technical / role specific language Valuable • Clear and concise explanation • Avoid technical / role specific language Estimatable • Easily fits into a Sprint. i.e. < 20% of velocity. • Definitely not > 33% of velocity Small • Can be automated • Avoid external testing / long test suites Testable 14
  • 15. Compromises are necessary Big stories are usually: • Independent • Negotiable • Valuable but not • Estimable • Testable • Small. They may also contain gold plating. 15 Non Negotiable stories are usually, Estimable & Testable Splitting into Smaller stories, may reduce Value and increase dependencies (especially if split poorly).
  • 17. INVESTing in our Stories As a top tier player of Towering Inferno I might need a total score in excess of the current limit of 9999. I would like this limit raising to one million So that I can obtain a huge total score. As a top tier player of Towering Inferno I would like the total score limit raised from 9999 to 1 million So that I can obtain a huge total score. As a top tier player of Towering Inferno I would like the total score limit raised to one million So that the artificial limit of 9999 does not hinder my enjoyment of the game
  • 18. INVESTing in our Stories As a top tier player of Towering Inferno I might need a total score in excess of the current limit of 9999. I would like this limit raising to one million So that I can obtain a huge total score. ‘So that’ duplicates the ‘I want’, is less concise then middle story. As a top tier player of Towering Inferno I would like the total score limit raised from 9999 to 1 million So that I can obtain a huge total score. As a top tier player of Towering Inferno I would like the total score limit raised to one million So that the artificial limit of 9999 does not hinder my enjoyment of the game ‘So that’ explains the business value for the change
  • 19. INVESTing in our Stories As a fan of South Park I want a humorous South Park themed game, that includes a couple of difficult mini games So that I can play a game that challenges and entertains me As the project team I want a prototype with 1st cut art of a humorous South Park game (no mini games needed) So that we can determine if the project is worth proceeding with As a fan of South Park I want a mini game feels like ten pin bowling with the main characters So that I can have a laugh at some of their crazy antics, that are different to the main game.
  • 20. INVESTing in our Stories As a fan of South Park I want a humorous South Park themed game, that includes a couple of difficult mini games So that I can play a game that challenges and entertains me This is a HUGE story. As the project team I want a prototype with 1st cut art of a humorous South Park game (no mini games needed) So that we can determine if the project is worth proceeding with This is the smallest story As a fan of South Park I want a mini game feels like ten pin bowling with the main characters So that I can have a laugh at some of their crazy antics, that are different to the main game. This is a BIG story.
  • 21. INVESTing in our Stories As a top tier player of Towering Inferno I want to receive a larger bonus than low tier players in the weekly draw So that I feel I am valuable player, that the game values As a Towering Inferno Game Manager I want the weekly bonus amounts to be configured in WeeklyBonusAmounts table in the database So that I can encourage our top tier players to keep playing As a Towering Inferno Game Manager I want to be able to set bonus amounts by player tier in the weekly draw So that I can encourage our top tier players to keep playing
  • 22. INVESTing in our Stories As a top tier player of Towering Inferno I want to receive a larger bonus than low tier players in the weekly draw So that I feel I am valuable player, that the game values Not a good business value, everyone wants to be paid more. As a Towering Inferno Game Manager I want the weekly bonus amounts to be configured in WeeklyBonusAmounts table in the database So that I can encourage our top tier players to keep playing Specifies implementation As a Towering Inferno Game Manager I want to be able to set bonus amounts by player tier in the weekly draw So that I can encourage our top tier players to keep playing No implementation details, has real business value
  • 23. INVESTing in our Stories As a Data Analyst I want API documentation in the same format as Twitter API documents So that it is easy to get started with the Data Mangler service As a Data Analyst I want API documentation for the Data Mangler service So that it is easy to get started using it As the Product Owner I want API documentation in the same format as Twitter API documents So that it is easy to get started with the Data Mangler service
  • 24. INVESTing in our Stories As a Data Analyst I want API documentation in the same format as Twitter API documents So that it is easy to get started with the Data Mangler service Too specific, it locks down choice / may miss out on better ideas As a Data Analyst I want API documentation for the Data Mangler service So that it is easy to get started using it Is Negotiable, appropriate user, with a clear business value As the Product Owner I want API documentation in the same format as Twitter API documents So that it is easy to get started with the Data Mangler service PO is usually the wrong user, they rarely get business benefit
  • 26. Getting to Done 26 • From the User Story text has been satisfied Intention • All completed Acceptance Criteria • All completed • Or accepted as Not Applicable Definition of Done • Product Owner has reviewed and accepted the story. Reviewed
  • 27. Acceptance Criteria vs. User Stories User Story • Intention • Negotiable • Open yet concise Acceptance Criteria • Requirements • Once set non-negotiable • Specific and concise 27
  • 28. Acceptance Criteria • Explain Product Owner expectations • Can clarify scope (either in or out) • Can clarify assumptions • Can detail implementation (but only when critical) • Written on the back of the index card. • Can be detailed, but should not be a specification. • Added/Change over time (including within the Sprint) • Not mandatory, but often used. 28
  • 29. Acceptance Criteria an example 29 Acceptance Criteria • £ Limit will be hard coded in this version. • User must manually load the loan (no notification of loan awaiting approval)
  • 30. Context 30 Product Backlog User Story Title Story text Acceptance Criteria Notes Definition of Done Software Persona Persona Persona Release Plan Tests • • • •
  • 31. Exercise 31 Story vs Acceptance Criteria
  • 32. Home Chef My Supermarket is an existing web site that allows shoppers to fill a grocery basket then shop around between supermarkets to get the best deal before arranging the shopping to be delivered. HomeChef is our application, that we are building. It already allows our users to quickly generate shopping lists from their favourite recipes. 32
  • 33. Identify User Story, Acceptance Criteria, Notes 33 We are going to integrate HomeChef to MySupermarket, allowing our users to quickly order the groceries they need to cook a weeks worth of their favourite recipes. This should be a seamless process, that is resistant to errors and network drop outs. Our user research shows ours will not wait for longer than 15 seconds for any action in our application. Once the user has selected several recipes, there should be an easy to see and use option to send their combined shopping list to their My Supermarket account. It would be nice if there was some indication that the transfer is processing, while the user waits. Investigations have shown that configuring a My Supermarket account in our software will be difficult. A hard coded configuration exists that you can use. We expect that it is our most thrifty home cooks that will use this feature. Other users may not view the extra step worth it for the cost saving it provides. User Story Acceptance Criteria Notes
  • 34. Resulting elements 34 We are going to integrate HomeChef to MySupermarket, allowing our users to quickly order the groceries they need to cook a weeks worth of their favourite recipes. This should be a seamless process, that is resistant to errors and network drop outs. Our user research shows ours will not wait for longer than 15 seconds for any action in our application. Once the user has selected several recipes, there should be an easy to see and use option to send their combined shopping list to their My Supermarket account. It would be nice if there was some indication that the transfer is processing, while the user waits. Investigations have shown that configuring a My Supermarket account in our software will be difficult. A hard coded configuration exists that you can use. We expect that it is our most thrifty home cooks that will use this feature. Other users may not view the extra step worth it for the cost saving it provides. User Story Acceptance Criteria Notes
  • 35. Result as User Story 35 Integrate HomeChef to MySupermarket As a thrifty home cook I want to easily be able to send my shopping list to my MySupermarket account So that I can save money and time on my weekly shopping Acceptance Criteria • Must be resistant to errors and network drop outs • Do not have to configure the account details, that will be a different story Notes • A transferring animation is a nice to have
  • 36. Identify User Story, Acceptance Criteria, Notes 36 ‘Daily Journal’ needs to add photo support to the website version. We are losing younger people to our competitor ‘PhotoJournal’ and have to stop this. It is crucial that we support a wide variety of image types so that we don’t exclude many users. So jpg, jpeg, png, etc must be accepted. With the current database issues we need to limit the upload size so that we avoid further outages. Analysis is ongoing regarding which image types are most used and information will be forth coming. This feature can not damage our reputation as the fastest journaling app on the market. We are going to launch a media campaign next month: ‘Daily Journal the fastest journal app, now includes photos with five amazing filters. It is your one-stop journaling app.’ User Story Acceptance Criteria Notes
  • 37. Resulting elements 37 ‘Daily Journal’ needs to add photo support to the website version. We are losing younger people to our competitor ‘PhotoJournal’ and have to stop this. It is crucial that we support a wide variety of image types so that we don’t exclude many users. So jpg, jpeg, png, etc must be accepted. With the current database issues we need to limit the upload size so that we avoid further outages. Analysis is ongoing regarding which image types are most used and information will be forth coming. This feature can not damage our reputation as the fastest journaling app on the market. We are going to launch a media campaign next month: ‘Daily Journal the fastest journal app, now includes photos with five amazing filters. It is your one-stop journaling app.’ User Benefit is not clearly represented Business Benefit is to stop losing customers User Story Acceptance Criteria Notes
  • 38. Result as User Story 38 Add photos with filters to website As a young journal writer I want to include fun looking photos with my journal entries So that my entries are more engaging and memorable Acceptance Criteria • Supports photo types ??? • Photo size limited to ??? • Performance must remain fastest on the market. • At least five filters must be implemented. Notes • Due prior to end of next month, to align with media campaign.
  • 40. To rewrite Ensure that every team member has enough knowledge to deploy the services and run the tests Needs to be a shared document on how to do this to support team and inform new members 40
  • 41. One possible answer 41 Team able to deploy and test services As a development team members I want to know how to deploy and test the CRH services So that I can gain fast feedback, without interrupting busy team members Acceptance Criteria • NONE (Definition of Done already covers off the requirement to test things) Notes • NONE
  • 42. To rewrite Onboard Mary Evans Data 535K lines tilde separated field with SME / Collection owner - not consistent grouping in this field Business value is to count 200+ collection owners 3 times Pre process, parse Store audit log persistently 42
  • 43. One possible answer 43 Onboard mary evans data In order to score highly on our SME engagement metric As the Digital Catapult I want to upload the data from Mary Evans in batches that maximise the number of batches each SME has some data Acceptance Criteria • NONE Notes • SME’s need to appear in three batches to count as engaged.
  • 44. To rewrite Implement Hub Control Service Ping all services in domain every xSecs as health check PostGres as store (can be log too) API to inform of status 1 for registration of service 1 get address of one of registered service 1 to receive info about service Clean-up service 44
  • 45. One possible answer 45 Hub control service As a hub repository owner I want the ability to actively monitor and to programmatically check the health of my hub repository So that I can offer a good level of service to my customers Notes • Ping all services in domain every xSecs as health check • PostGres as store (can be log too) • API to inform of status • 1 for registration of service • 1 get address of one of registered service • 1 to receive info about service • Clean-up service
  • 46. To rewrite Clean and well tested deployment instructions Business value - lowered rework, lowered risk to reputation Chef cookbooks working Need a catalogue of these one click services For Beta users to set up their own services 46
  • 47. One possible answer 47 Deployment Instructions In order to save time deploying the CRH As a beta user I want clean easy to follow deployment instructions Acceptance Criteria • Chef cookbooks working • Need a catalogue of these one click services Notes • NONE
  • 49. A healthy backlog is 49 • Prioritised by PO for ROI • Ordered by team for dependencies, etc. Ordered • Top contains 1.5 to 2 sprints of INVESTments • Next comes Chunks • Followed by Epics Balanced • A mixture of work that roughly matches team capability • Considering cross skilling / up skilling may be a better investment in the long term Diverse
  • 50. A healthy backlog 50 Waterline • Ordered • Balanced • Diverse
  • 52. Why is it unhealthy? What symptoms will occur? 52 • Not prioritised • Not ordered • Too many priority 1’s • No guidance from PO • Hard to plan sprints
  • 53. Why is it unhealthy? What symptoms will occur? 53 • All INVESTments • Hard to see the big picture • Extra effort to maintain the backlog • Lots of grooming effort will be wasted • Lots of stories will be thrown away
  • 54. Why is it unhealthy? What symptoms will occur? 54 • Not enough INVESTments • Hard to plan sprint • Waste time in planning grooming stories (usually in a rush)
  • 55. Why is it unhealthy? What symptoms will occur? 55 • Not enough diversity • May not fit team capabilities • Hard to balance work in the sprint
  • 58. Competencies to be gained I hope that you are now able to: • Summarise why User Stories are used for Agile Software Development • Describe the key elements of a User Story • Write out one of two common templates for User Stories • Summarise how User Story text and Acceptance Criteria differ • List the three C's • Compare user stories based on the strength of their INVEST properties • List the four items that are necessary for a story to be Done • Write User Stories based on a detailed request • Re-write poor User Stories into Effective User Stories • Identify a healthy backlog • List several ways a backlog can become unhealthy • Identify an unhealthy backlog 58
  • 60. Reference Material How to write a useful User Story – article from Gov.uk User Stories explained – article with examples in Agile Atlas 60

Editor's Notes

  • #10: You can use whatever format you like for User Stories, they are not locked in stone.
  • #12: https://www.flickr.com/photos/ajc1/ - conversation
  • #18: Give attendees 2 minutes to decide on the best and worst examples. Importantly they should also explain WHY is it good or bad. Notes for all of these exercises: We are being picky during these exercises (language both written and read, comprehension of the written word, personal preference for writing style and amount of detail) It is the concepts that are key! i.e. What questions to ask yourself when writing/reading these stories. Context is missing, which makes it hard
  • #25: Avoid using Product Owner as the User. The key reason being that the ‘Product Owner’ as a user cuts out the chance for the team to challenge the business benefit. It usually indicates that we don’t really understand what the benefit is, hence why should we do this story. Other reason is that the PO never gets business benefit, either the User or Company gets benefit. So with the PO as user we can not link the ‘as a’ line to the ‘so that’ line.
  • #60: https://www.flickr.com/photos/chuckthephotographer/