User stories — broken vision broke the knees


Published on

Common misunderstandings of vision and how to predict and avoid them.

User stories vs MMFs vs requirements - make them work for you, not against you.

How all this stuff fit together?

Published in: Technology

User stories — broken vision broke the knees

  1. 1. Andris BarissVladimir TarasowBroken Vision Broke the KneesUser Stories
  2. 2. Vladimir TarasowAbout: netrat@netrat.euAndris BarissAbout:
  3. 3. Often this picture is used to illustrate the drawbacks of Waterfall,however the same causes can affect Agile projects, too.
  4. 4. Kept on crawlingin project with wrong or unclear Visionand requirements can harm you badly.
  5. 5. Real life example:● 2 people hospitalized● 2 people had serious health issues
  6. 6. "The problem with userrequirement capture isthat someone assumestheres a requirement."Dave Snowden
  7. 7. Eliminate uncertaintywith communication.Learn from yourmistakes and victories.Know the basics.
  8. 8. "Every book ever printed inevery language all availablein 60 seconds fromanywhere on the planet."
  9. 9. Product VisionDescribes why the project is undertaken.Describes what the desired end-state is.Shared by the Stakeholders, the ProductOwners, the Team and the end users.
  10. 10. How to avoid misunderstandings?Is it short, clear and focused?Is it compelling?Is it achievable?Does it describe how the product or itsmain feature meet the customer needs?Is it aligned with goals of all Stakeholders?Is it inspiring so that everybody involvedstrives for the same goal?
  11. 11. There is the need to makethe product UI moreintuitive. There are toomany support requestsrelated to usage of the tool,often associated with very“simple” problems.
  12. 12. RequirementRepresents a need.Must answer the questions What? and Why?Tries to identify with a clear sentencewhat is the problem to solve.
  13. 13. How to avoid misunderstandings?Simple: Can everybody understand this?Measurable: When is the Requirementfulfilled?Achievable: Do you have the resources?Relevant: Is it really a need for thecustomer?Traceable: Who is the stakeholder ororigin?Simple: Can everybody understand this?Measurable: When is the Requirementfulfilled?Achievable: Do you have the resources?Relevant: Is it really a need for thecustomer?Traceable: Who is the stakeholder ororigin?
  14. 14. As a provider search user,I need the ability to searchfor providers by specialtyso that I can more efficientlyrefer patients to specialists.
  15. 15. User StoryRepresent 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 <somecapabilities> so that <business value>Must contain also Acceptance Criteria thatdescribes how the user of the story wouldaccept the implemented functionality.
  16. 16. How to avoid misunderstandings?Dont put too much information intodescription.Acceptance criteria must be informative.Dont confuse acceptance criteria and testcases.Should be written in mere humanlanguage.
  17. 17. Sample User StoryTitle: Search for providers by provider specialty.Description: As a provider search user, I need theability to search for providers by specialty so that Ican more efficiently refer patients to specialists.Acceptance criteria: The provider search mechanismhas the ability to enter a specialty. The specialtysearch will have a list of provider specialties fromwhich to select. If there are more results than can fiton one page, the system will provide the capability toview the list in pages or sections.
  18. 18. Minimum Marketable FeatureRepresents a distinct and deliverablefeature of the system.Provides significant value to the customer.Consists of one or more user stories.
  19. 19. How to avoid misunderstandings?Simplify planning by eliminating technicaldependencies.Create a release plan that deploys high-value features first.Group functionality into minimumpackages that can be released individually.
  20. 20. How they allfit together?
  21. 21. Thank You!Please, leave feedback!
  22. 22. Materials used in the presentation:● The Project Cartoon (● Photo by Derrick Tyson● Photo by Expert Infantry● Photo by Sgt. Sean Mathis● Amazon Kindles 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 TarasowCredits
  23. 23. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License. To view a copy of thislicense, visit