User Story Workshop. BA-Squared, LLC

Size: px

Start display at page:

Download "User Story Workshop. BA-Squared, LLC"

MargaretMargaret Fletcher
5 years ago
Views:

1 User Story Workshop BA-Squared, LLC

2 User Story Level of Detail User Stories elaborate over time, just like other requirements. Start high level and break them into smaller pieces. Product View Release View Sprint/Iteration View

3 User Stories A Placeholder for Conversation A user story represents a small, concise statement of functionality needed to deliver value User stories can be used To capture and prioritize needs As a basis for additional analysis As a basis to estimate and report As a start for generating user acceptance tests To monitor progress towards value To trace requirements INDEPENDENT NEGOTIABLE-VALUABLE-ESTIMABLE- SMALL-TESTABLE

4 User Stories and Cake A user story is not a layer, nor a phase, it is an entire vertical piece of value!

5 User Story As a Order Quoter I need to be able to enter a order scenario so I can give my customer a quote for their order Enter Order Scenario

6 Story Elaboration Its not suppose to be perfectly detailed out nor perfect the first time we write it! Plan and elaborate iteratively and progressively as stories get prioritized. Example: Product View: As a online customer I want to create a profile so I can do business with your organization online Release View: As an online customer I want to create the minimum profile information needed to make a purchase so I can buy a product online from you Release View: As an online customer I want to be able to enter my preferences on my profile so I can determine how often I want to hear about sales Sprint View: As a premium customer I want to be able set my communication preferences to only so I don t receive mail at my house Sprint View: As a premium customer I want to be able set up what types of information I get so I don t get information I don t want Sprint View: As a premium customer I want to be able set up how often I would like to receive information so that I don t get it more often than I would like.

7 Bad Smells a. Product Owner is a user of the story b. Developer is the user of the story c. Acceptance Criteria specifies look and feel d. Only specifying what the user wants e. Stories written by tech layer - (front end, database, back end, etc ) f. No Acceptance Criteria g. Non-Functional Requirements are the User Story h. Too much detail i. Stories depend on other stories

8 Bad Smell? User Story As a facebook user I want to share an article I saw on my feed so my friends can read cool things. As a facebook user I want to see more about 10 profiles per page when I search for a friend, so I can find that friend I am looking to send a message to AC: The page should allow me to navigate through the multiple pages of results I should paginate through 10 profiles at a time The font on the page should be Arial 12 Black Narrow The color of the font should be #36hd5tmf The profile thumbnails should be 20 pixels in size As a user I want to UI to be designed before we start any development on the database, so we can approve the design before coding. AC: Schedule the design review Review with key stakeholders Get approval for the design As a facebook user I want the system to be able to handle up to 10,000,000 users online at a time so I am able to use the site when I want to and Facebook can grow. AC: When I am the 10,000,001st user online I am able to use the site.

9 Bad Smell? User Story As a facebook user I want the system to be able to handle up to 10,000,000 users online at a time so I am able to use the site when I want to and Facebook can grow. AC: When I am the 10,000,001st user online I am able to use the site. As a facebook user I want to send a message to a friend from my profile page so I can quickly communicate with friends. AC: I want to click from my feed to message a friend I want the message to have pre set quick words As a facebook user I want facebook to integrate with Instagram so that the database can share information AC: We have the UI on facebook built, next need to pass that data to the database. As a facebook user I want to be able to enter something in a search-bar on the top of the page AC: To search the user must enter the name in the search-bar on top of each page The search must contain at least 3 characters This is only the enter something in search bar part. As a product owner I want the website to allow users to update their privacy settings As a developer I need to upgrade the platform and database to the latest version we received from the vendor.

10 Technical Stories Still need to be prioritized by the Product Owner, BAs can help the team write them with a business value lens In order to <business value>, <technical user> needs to <technical task>. In order to display the most up to date rates to customers, the DBA needs to switch out the rate tables to a new format.

11 Slicing User Stories Select a user story and slice it! Splitting Strategies: - Ambiguous Verbs and Nouns - Add Meaningful Adjectives - Process Step - Business Rules/Scenarios/Exceptions - Operational Tasks - By User Role

12 Slice This! As a Amazon.com shopper, I want to chat with a representative, so I can get help quickly and quietly and avoid calling in over the phone.

13 Acceptance Criteria vs. Acceptance Tests Acceptance Criteria Tell us what conditions, scenarios, and rules that confirm the story is working; in the user role language Start with 5-10 bullet points What it looks like to have this feature working from a user point of view Non-Functional Requirements Scenarios, rules, logic Plus other supporting information Decision Tables/Matrix Process flows Etc. Acceptance Tests/Detailed Test Cases Are the scripts that tell us how to test

14 Examples: US: User point of view of required functionality As a customer I want to be able to see a summary of my claims for the month when looking at my account details so I can see how much my insurance covers. Acceptance Criteria: Definition of what it looks like when working The claim summary should show from the 1 st day of the month forward The claim summary should show pending and confirmed values The claim summary should expand to show individual claims

15 Examples: Acceptance Criterial cont. GIVEN Conditon WHEN Action THEN - Result - Given I have claims this month, When I select to see a summary of my claims, then it defaults to show my curclaimsrent months claims - Given I have no claims this month, When I select to see a summary of my claims, then it defaults to show me a message that there are no claims this month - Given I have claims from previous months, When I select to see a summary of my claims, then it shows me previous months to select to see claims for

16 Review

How to Write Effective Use Cases? Written Date : January 27, 2016

How to Write Effective Use Cases? Written Date : January 27, 2016 Written Date : January 27, 2016 One of the most difficult problem in software development is capturing precisely what you want to build. Inaccurate requirement will end-up with significant delay, rework