User stories — broken vision broke the knees
-
Upload
vladimir-tarasow -
Category
Technology
-
view
1.598 -
download
0
description
Transcript of User stories — broken vision broke the knees
![Page 1: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/1.jpg)
Andris BarissVladimir Tarasow
Broken Vision Broke the Knees
User Stories
![Page 2: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/2.jpg)
Vladimir Tarasow
About: http://about.me/netratE-mail: [email protected]
Andris Bariss
About: lv.linkedin.com/in/andrisbarissE-mail: [email protected]
![Page 3: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/3.jpg)
Often this picture is used to illustrate the drawbacks of Waterfall, however the same causes can affect Agile projects, too.
![Page 4: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/4.jpg)
![Page 5: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/5.jpg)
Kept on crawling in project with wrong or unclear Vision and requirements can harm you badly.
![Page 6: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/6.jpg)
Real life example:● 2 people hospitalized● 2 people had serious health issues
![Page 7: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/7.jpg)
"The problem with user requirement capture is that someone assumes there's a requirement."
Dave Snowden
![Page 8: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/8.jpg)
Eliminate uncertainty with communication.
Learn from your mistakes and victories.
Know the basics.
![Page 9: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/9.jpg)
"Every book ever printed in every language all available
in 60 seconds from anywhere on the planet."
![Page 10: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/10.jpg)
Product Vision
Describes why the project is undertaken.
Describes what the desired end-state is.
Shared by the Stakeholders, the Product Owners, the Team and the end users.
![Page 11: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/11.jpg)
How to avoid misunderstandings?
Is it short, clear and focused?
Is it compelling?
Is it achievable?
Does it describe how the product or its main feature meet the customer needs?
Is it aligned with goals of all Stakeholders?
Is it inspiring so that everybody involved strives for the same goal?
![Page 12: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/12.jpg)
There is the need to make the product UI more
intuitive. There are too many support requests
related to usage of the tool, often associated with very
“simple” problems.
![Page 13: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/13.jpg)
Requirement
Represents a need.
Must answer the questions What? and Why?
Tries to identify with a clear sentence what is the problem to solve.
![Page 14: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/14.jpg)
How to avoid misunderstandings?
Simple: Can everybody understand this?
Measurable: When is the Requirement fulfilled?
Achievable: Do you have the resources?
Relevant: Is it really a need for the customer?
Traceable: Who is the stakeholder or origin?
Simple: Can everybody understand this?
Measurable: When is the Requirement fulfilled?
Achievable: Do you have the resources?
Relevant: Is it really a need for the customer?
Traceable: Who is the stakeholder or origin?
![Page 15: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/15.jpg)
As a provider search user,I need the ability to search for providers by specialty
so that I can more efficiently refer patients to specialists.
![Page 16: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/16.jpg)
User Story
Represent a description of a “solution” — from a functional point of view.
Be a single sentence in the form: As a <type of user> I want <some capabilities> so that <business value>
Must contain also Acceptance Criteria that describes how the user of the story would accept the implemented functionality.
![Page 17: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/17.jpg)
How to avoid misunderstandings?
Don't put too much information into description.
Acceptance criteria must be informative.
Don't confuse acceptance criteria and test cases.
Should be written in mere human language.
![Page 18: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/18.jpg)
Sample User StoryTitle: Search for providers by provider specialty.
Description: As a provider search user, I need the ability to search for providers by specialty so that I can more efficiently refer patients to specialists.
Acceptance criteria: The provider search mechanism has the ability to enter a specialty. The specialty search will have a list of provider specialties from which to select. If there are more results than can fit on one page, the system will provide the capability to view the list in pages or sections.
![Page 19: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/19.jpg)
Minimum Marketable Feature
Represents a distinct and deliverable feature of the system.
Provides significant value to the customer.
Consists of one or more user stories.
![Page 20: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/20.jpg)
How to avoid misunderstandings?
Simplify planning by eliminating technical dependencies.
Create a release plan that deploys high-value features first.
Group functionality into minimum packages that can be released individually.
![Page 21: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/21.jpg)
How they all fit together?
![Page 22: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/22.jpg)
![Page 23: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/23.jpg)
![Page 24: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/24.jpg)
![Page 25: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/25.jpg)
Thank You!
Please, leave feedback!
http://spkr8.com/t/23061
![Page 26: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/26.jpg)
Materials used in the presentation:● The Project Cartoon (http://www.projectcartoon.com/)● Photo by Derrick Tyson● Photo by Expert Infantry● Photo by Sgt. Sean Mathis● Amazon Kindle's vision statement● 'New to User Stories?' by William F. Nazzaro and Charles Suscheck● 'Minimum Marketable Feature' from Wikipedia, the free encyclopedia● 'Minimum viable product' from Wikipedia, the free encyclopedia● 'Phased Releases' by James Shore● Illustrations by Vladimir Tarasow
Credits
![Page 27: User stories — broken vision broke the knees](https://reader034.fdocuments.in/reader034/viewer/2022051411/54584722af7959795d8b520d/html5/thumbnails/27.jpg)
This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License. To view a copy of this
license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/.