Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Agile Requirements Exploration: How Testers Add Value
Ähnlich wie Agile Requirements Exploration: How Testers Add Value (20)
Mehr von lisacrispin
Mehr von lisacrispin (16)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Agile Requirements Exploration: How Testers Add Value
- 5. • Share experiences • PracJce techniques to elicit, explore specificaJons, build shared understanding • Perhaps some brand new ideas! • Inspect and adapt as we go • You’ll leave with some experiments to try 5
- 8. 8 What’s slowing you down? Gehng in the way of shared understanding? • Write one problem per sJcky note. • Share with your table group. • Post on your wall chart by the parachute. Group related problems.
- 9. 9 Intro Req’ts & TesJng EssenJals Big Picture Release & Feature Levels Explore with Examples IteraJon Level Stories - 7 dimensions - funcJonal - non-func’l - quadrants - mindset - levels of detail - Using 7 dimensions - Tools to help - ATDD - Example mapping - using acceptance tests Wrap-up Wrap-UP
- 13. 13 Intro Req’ts & TesJng EssenJals Big Picture Release & Feature Levels Explore with Examples IteraJon Level Stories - 7 dimensions - funcJonal - non-func’l - quadrants - mindset - levels of detail - Using 7 dimensions - Tools to help - ATDD - Example mapping - using acceptance tests Wrap-up Wrap-UP
- 14. 14
- 15. 15 Meaning Descrip9on I Independent Self-contained, so no inherent dependency on another user story N NegoJable Can be changed and rewri6en unJl they are accepted into an iteraJon V Valuable Relevant and necessary; linked to a business goal E EsJmable Must be able to size (or esJmate) the story S Small Small enough to have a certain level of certainty T Testable Must be able to test it Origins: Bill Wake, 2003
- 16. func9onal nonfunc9onal www.DiscoverToDeliver.com/visual-language.php Source: DiscoverTo Deliver, Gottesdiener & Gorman, 2012
- 20. 20 As the scheduler, I need to schedule regular hours as well as add additional hours for overtime hours to the payroll system So that the drivers get paid correctly.
- 21. 21 Dimension Ques9ons User Is the scheduler an administrator of the system? Or is she a data entry person only? Data Is Jme measured in hours or minutes? AcJon Can the drivers add their hours in manually, or do they submit Jme sheets? How does she find out about extra hours? Control Do the Jmesheets have to be approved by a supervisor or somebody?
- 24. 24
- 26. 26 As the scheduler, I need to schedule regular hours as well as add additional hours for overtime hours to the payroll system So that the drivers get paid correctly.
- 27. 27 Dimension Ques9ons Interface Who / what else has access to the scheduling system? Environment Can it be entered remotely or is it desktop only? Quality A6ributes Are there performance requirements? Can I assume there is only one person accessing at a Jme? What level of security do we need for the scheduler?
- 29. 29 Intro Req’ts & TesJng EssenJals Big Picture Release & Feature Levels Explore with Examples IteraJon Level Stories - 7 dimensions - funcJonal - non-func’l - quadrants - mindset - levels of detail - Using 7 dimensions - Tools to help - ATDD - Example mapping - using acceptance tests Wrap-up Wrap-UP
- 32. 32
- 34. User Interface Action Data Control persona user role map context diagram prototype relationship map business process diagram capability map dependency graph story, story map use case value stream map data model state diagram business policy, rule decision table decision tree Source: DiscoverTo Deliver, Gottesdiener & Gorman, 2012
- 35. 35 As the scheduler, I need to schedule regular hours as well as add additional hours for overtime hours to the payroll system So that the drivers get paid correctly.
- 36. 36
- 39. 39
- 40. Scenarios for payment of hours 1. Regular hours only 2. Regular, plus overJme 3. Regular, plus addiJon call-out due to bus breakdown 4. Call-out only due to bus breakdown 40
- 41. 41 Scenarios Business Policies Regular hours only Seasonal part-Jme hours paid Regular plus overJme OverJme is paid at 1.5 x regular Call-out for bus breakdown AddiJonal compensaJon for extra call
- 44. 44 Intro Req’ts & TesJng EssenJals Big Picture Release & Feature Levels Explore with Examples IteraJon Level Stories - 7 dimensions - funcJonal - non-func’l - quadrants - mindset - levels of detail - Using 7 dimensions - Tools to help - ATDD - Example mapping - using acceptance tests Wrap-up Wrap-UP
- 46. • To elicit requirements • To reduce uncertainty • To test people’s understanding of the requirement 46 Credit and thanks to Brian Marick “That’s not right” can be music to your ears • Can become the actual tests • Are a form of specificaJon
- 47. 47 As a user, I want guidelines to create a strong password, so that I have limited risk for identity theft
- 48. 48 Copyright 2016 : Janet Gregory – DragonFire Inc. 1. Pick a partner table group 2. Using the blue index cards, invent 3 secret business rules for “Create a strong password” story 3. Write 3 (and only 3) examples on the white cards to express those rules <2 min> 4. Now pass them to your partner table. 5. Guess the rules based on the examples – write them on the sJcky notes, and pass them back 6. Let’s stop and reflect
- 50. 50 What did this exercise show you? What did you learn? Are rules or examples be6er? Why or why not?
- 53. 53 Create a story from your feature, write it on a yellow card. For example: • Send email to hotel staff … • Select an alternate bus …
- 54. For your story, 1. IdenJfy a couple of obvious business rules (blue cards) 2. Explore examples for at least one rule (green cards) 3. Are there quesJons (pink cards) 54
- 56. 56 Intro Req’ts & TesJng EssenJals Big Picture Release & Feature Levels Explore with Examples IteraJon Level Stories - 7 dimensions - funcJonal - non-func’l - quadrants - mindset - levels of detail - Using 7 dimensions - Tools to help - ATDD - Example mapping - using acceptance tests Wrap-up Wrap-UP
- 59. It may help priori/ze stories Example: Schedule a distributed team meeJng in our scheduling app. 1. MeeJngs with > 2 Madrid a6endees need a meeJng room 2. Remote a6endees must have video link 3. MeeJngs are during normal work hours for all a6endees (employees located across Europe). 59
- 62. Scenario example: As a user with valid login credenJals, I can log in and see the landing page. Test might look like: • Given Janet has a valid login, • When she enters her valid username and password, • Then she sees the landing page. 62 User Email Password Expected Result Comments Jara jara@example.com Passw0rd22 Logged in Valid login scenario
- 63. 63 As a driver called in as a replacement, When I submit hours including overtime, I receive the correct pay amount. Rule: 1.5 x regular pay if more than 1 hour over scheduled driving Jme Rule: 1 hour extra pay in addiJon to overJme hours if call-in replacement
- 65. Story As a driver called in as a replacement, When I submit hours including overJme, I receive the correct pay amount. Scenario Regular hours plus overJme plus call-in replacement pay business rule(s) OverJme is calculated as: (Total driving Jme minus regular hours) * overJme Given pre-condition(s), state Driver exists and drove his bus fixed data Driver: José, worked 40 hours, including 4 overJme hours when called in as a replacement Regular wage: 20 euros/hour OverJme percentage: 150% (1.5 x regular pay) When action Driver submits hours input data Hours submi6ed: 36 regular, 4 overJme call-in replacement Then observable outcome: message, output Total wages: 860 post-condition Paycheck cut
- 67. Driver Regular Wage Regular hours Over9me hours Total paid José 20.00 36.0 4.0 840.00 José 20.00 36.0 2.0 780.00 José 20.00 30.0 0.0 600.00 67
- 68. 1. Use the story from your example mapping 2. Create BDD acceptance tests using Given/ When/Then format 3. Then idenJfy possible examples (test data) that could be input in a tabular format 4. Show your tests to another table group. Do they understand the capability to be delivered? 68
- 73. 73 Intro Req’ts & TesJng EssenJals Big Picture Release & Feature Levels Explore with Examples IteraJon Level Stories - 7 dimensions - funcJonal - non-func’l - quadrants - mindset - levels of detail - Using 7 dimensions - Tools to help - ATDD - Example mapping - using acceptance tests Wrap-up Wrap-UP
- 76. Assemble op9ons Source: DiscoverTo Deliver, Gottesdiener & Gorman, 2012 76
- 77. 77
- 80. Ques9ons?