So you've written your user stories, now what?
•
7 gefällt mir•397 views
Elabor8 consultants, Trish, Charlotte and Saad presented this in Sydney's Agile BA/PO meetup. Apart from the story of minions' arrival in Sydney, the session covered topics like: - Building the right thing by creating better specifications - Difference between acceptance criteria and scenarios - Tips to writing better acceptance criteria + scenarios - What's an executable specification and how are scenarios converted in to automated tests
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie So you've written your user stories, now what?
Ähnlich wie So you've written your user stories, now what? (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
So you've written your user stories, now what?
- 3. Real Villain
- 4. Real Villain
- 7. The Analysis
- 11. User story What How When Who Start Write user story • Card • Conversation • Confirmation AS a <<user>> I WANT TO <<action>> SO THAT <<value>> • Planning • Refinement • Anytime ! EVERYONE ONLY !
- 13. Acceptance criteria What How When Who Start Write user story Write acceptance criteria • Illustrates requirements • Business rules • Boolean response • Checklist • Gherkin • After writing user story • Before implementing story • Refine continuously EVERYONE ONLY !
- 15. Tips - Writing better acceptance criteria • Connection to database established • Database populated with email data • Integration with mailing server established • Email sent by mailing server based on data fetched from database • Email received as soon as new meetup is scheduled 1. Describe WHAT, not HOW: Don’t mix purpose of the test with the mechanics of test execution Start Write user story Write acceptance criteria
- 16. Tips - Writing better acceptance criteria 2. SHADED FIGS Scary Happy Angry Delinquent Embarrassing Desolate Forgetful Indecisive Greedy Stressful Start Write user story Write acceptance criteria *From Gojko’s book: 50 quick ideas to improve your tests
- 17. Tips - Writing better acceptance criteria 2. SHADED FIGS Path Possible testing Ideas Scary What if same email gets sent multiple times? (from user’s perspective) Is there a situation where a meetup is scheduled and no email is sent (from meetup organizer’s perspective) Happy Receiving email as soon as a new meetup is scheduled Angry Can a customer get email for a wrong meetup? Delinquent Can organizer see the email read receipts? Can a user see who else has received an invite? Embarrassing An email with empty body? Incorrect recipient's name, for example Desolate Will a user get email for a meetup by default? (first time user) Forgetful What if user opts in for notifications but does not save changes? Indecisive A user who keeps on changing his notification settings – On/off then on Greedy What if organizer wants to send email to everyone on meetup.com and not just that particular meetup members Stressful Will the email be sent to ALL members of the group within 1 minute? Start Write user story Write acceptance criteria
- 18. Acceptance criteria in checklist - example ✓An email is sent to all meetup members as soon as new meetup is scheduled (Happy) ✓Members receive an email only if they opted-in for the notifications (Happy) ✓No email notification should be sent to non-members (Angry) ✓Don’t re-send email if email delivery fails (Scary) ✓New meetup members to receive email by default (Desolate) ✓Email sent to ALL members of the group within 1 minute (Stressful) Start Write user story Write acceptance criteria
- 20. Tips - Writing better acceptance criteria • Email received as soon as new meetup is scheduled Make sure to test the business value: • Can the customer RSVP to the event though? BUT Start Write user story Write acceptance criteria
- 21. What How When Why Gherkin Start Write user story Write acceptance criteria • Language that most test tools understand. • Used for documentation and automated tests. Can be used for both acceptance criteria and scenarios. Allows requirements and tests to utilise the same approach. GIVEN <<input>> WHEN <<action>> THEN <<output>>
- 22. Then and now Waterfall • Pre-condition • Trigger • Post-condition Code • Input • Task • Output BDD • Given • When • Then Start Write user story Write acceptance criteria
- 24. Acceptance criteria in Gherkin - example Given a meetup.com member has joined a meetup (Input), And global notification is turned on, And notification for the meetup is turned on, When a meetup is scheduled (Action), Then an email notification is received (Output). Start Write user story Write acceptance criteria
- 25. Acceptance criteria in Gherkin - example Given a meetup.com member has NOT joined a meetup (Input), And global notification is turned on, When a meetup is scheduled (Action), Then NO email notification is received (Output). Start Write user story Write acceptance criteria
- 26. Activity 1 Step 1: Separate into a team of 6-8 Step 2. Each teams make sure you have: • 2 * User Stories (Without Acceptance criteria) • 1 * Problem Statement from minions • 1 * High-level Wireframe *You can come up with your own stories based on the Problem Statement and Wireframe with inputs from our Minion Charlotte (PO) Step 3: Let’s Write Some Acceptance Criteria together
- 27. Feedback
- 28. Scenarios What How When Who Start Write user story Write acceptance criteria Create scenarios Concrete example that illustrates an acceptance criteria. GIVEN <<input>> WHEN <<action>> THEN <<output>> • After acceptance criteria • Refine continuously EVERYONE ONLY !
- 30. Acceptance criteria vs. Scenarios Start Write user story Write acceptance criteria Create scenarios Acceptance Criteria Scenarios WHAT Business Rules Concrete examples WHEN After writing the user story After writing the acceptance criteria WHO Team Team HOW Checklist or Gherkin (without examples) Gherkin (with concrete examples) WHY Helps with sizing and development Helps with development and testing
- 31. How to write scenarios Step 1: Identify what you need to test (When) Step 2: List down inputs (Given) • List examples • Define boundaries (edges, positive, negative) Step 3: List down outputs (Then) • List examples • Define boundaries (edges, positive, negative) Start Write user story Write acceptance criteria Create scenarios
- 32. Tips – writing better scenarios 1: Always have 1 ‘When’. 2: Limit your ‘Ands’. 3: Use ‘Background’ for repeating conditions. 4: Add a title for your ‘Scenarios’ 5: Given – Past When – Present Then – Future 6: Given – Passive (Data) When – Active (Action) Then – Passive (Data) 7: Use tables for your inputs or outputs. Start Write user story Write acceptance criteria Create scenarios
- 33. Scenarios – example Background: Given a meetup.com member named ‘Saad’, And ‘Saad’ signed up using ‘saad@email.com.au’ Scenario: Notification is received from the Agile BA/PO meetup Given Saad has joined the Agile BA/PO meetup, And global notification is turned on And the notification for Agile BA/PO meetup is turned on, When the Agile BA/PO meetup is scheduled, Then the email notification for the Agile BA/PO meetup will be sent. Start Write user story Write acceptance criteria Create scenarios
- 34. Scenarios – example Scenario: Notification is not received when Saad’s mailbox is full Given Saad has joined the Agile BA/PO meetup, And global notification is turned on And the notification for Agile BA/PO meetup Is turned on, And Saad’s mailbox is full, When the Agile BA/PO meetup is scheduled, Then Saad will not receive the email notification for the Agile BA/PO meetup. And email will not be re-sent. Start Write user story Write acceptance criteria Create scenarios
- 35. Scenarios – example: Background: Given a meetup.com member named ‘Saad’, And ‘Saad’ signed up using ‘saad@email.com.au’ Scenario: Given Saad has joined <Meetup group>, And global notification is <Global notification>, And <Individual setting>, When the Agile BA/PO meetup is scheduled, Then email is <Result> to Saad’s email address. Scenario Meetup group Global notification Individual setting Result 1 Agile BA_PO On On Sent 2 Agile BA_PO On Off Not sent 3 Agile BA_PO Off On Not sent 4 Agile BA_PO Off Off Not sent 5 Agile Coaching On On Sent Start Write user story Write acceptance criteria Create scenarios
- 37. Executable specification What How When Who Start Write user story Write acceptance criteria Create scenarios Turn in to executable specification End Specification that can run as an automated test • Programming • Step definitions & testing code • Using a test execution engine • Developers • TestersAfter writing the scenarios
- 40. Wrap-up Start Write user story Write acceptance criteria Create scenarios Turn in to executable specification End GIVEN <<context>> WHEN <<event>> THEN <<expected outcome>> AS a <<user>> I WANT TO <<action>> SO THAT <<value>> • Reduce rework • Frequent validation • Living documentation • Reduce friction in translating business requirements in to technical solutions • Don’t just build the product right, build the right product – Make products that matter!
- 41. Recommended books + References • https://elabor8.com.au/a-practical-blog-on-how-to-write-scenarios-using-bdd/ • https://watirmelon.blog/2013/05/09/should-your-acceptance-criteria-be-specified-as-givenwhenthen-or-checklists • https://lizkeogh.com/2011/06/20/acceptance-criteria-vs-scenarios/