Let me tell you a Story – CukeUp! AU 2016

Transcript

1. @tooky http://cucumber.io/st Steve Tooke Let me tell you a story
4. VISA subscriptions In order to increase subscriptions visitors should be able to subscribe online with a VISA card
5. “User stories are slippery,
6. “User stories are slippery, so we call them Product Backlog Items”
7. We never finish them in an iteration How do I trace them to features Hard to estimate Not enough detail to start coding Nothing I can test Difficult to prioritise
8. As a <role> I want to <do something> So that <I get some value>
9. In order to <get some value> <role> should be able to <do something>
11. “A boundary object is a concept in sociology to describe informa7on used in different ways by different communi7es. They are plas7c, interpreted differently across communi7es but with enough immutable content to maintain integrity” --Wikipedia User Stories are Boundary Objects
12. -- Leigh & Griesemer
13. “They are weakly structured in common use, and become strongly structured in individual-site use. They may be abstract or concrete. -- Leigh & Griesemer
14. “They are weakly structured in common use, and become strongly structured in individual-site use. They may be abstract or concrete. They have different meanings in different social worlds but their structure is common enough to more than one world to make them recognizable means of translation. -- Leigh & Griesemer
15. “They are weakly structured in common use, and become strongly structured in individual-site use. They may be abstract or concrete. They have different meanings in different social worlds but their structure is common enough to more than one world to make them recognizable means of translation. The creation and management of boundary objects is key in developing and maintaining coherence across intersecting social worlds.” -- Leigh & Griesemer
17. http://www.agileproductdesign.com/blog/dont_know_what_i_want.html Depth first (incremental)
18. http://www.agileproductdesign.com/blog/dont_know_what_i_want.html Breadth first (iterative)
19. Iterative and Incremental http://itsadeliverything.com/revisiting-the-iterative-incremental-mona-lisa
20. Parallel development
21. The one where... User stories & acceptance criteria Examples
22. The one where... User stories & acceptance criteria Examples
23. The one where... User stories & acceptance criteria Examples Open questions
24. The one where... User stories & acceptance criteria Examples Open questions Domain learning
26. •Must support VISA •Does not need to support MasterCard, Switch •... •Customers should be prevented from entering invalid credit card number • ... Credit Card Acceptance criteria:
27. The one where .... ... we validate content of the card number User Enters Outcome @£$%@£$%@£$%@£$% Error message 4575 9879 6752 1245 Error message 4575987967521240 OK
28. Acceptance Criteria (Rules) Examples User Story
29. Acceptance Criteria (Rules) Examples Examples help us to explore and test the acceptance criteria together User Story
31. In order to introduce a competitive element participants should be able to get points for a successful answer SCORING THE GAME
32. Get points for a correct answer Acceptance criteria:
33. Is it only the first team that gets the answer right that scores? Do teams start with a score of 0? Are all answers worth the same? Can the score be negative? What happens if the answer is wrong?
34. Teams start with a score of 0 Acceptance criteria: Correct answers score points Incorrect answers lose points Score can’t be negative Points awarded decrease ...
35. Teams start with a score of 0 Acceptance criteria:
36. Feature: Team Scoring Teams start with zero score Scenario: Score starts at 0 Given I register a team When I retrieve my score Then my score is 0
37. http://www.growing-object-oriented-software.com/figures.html From Growing Object-Oriented Software by Nat Pryce and Steve Freeman
38. Correct answer gets 10 points Acceptance criteria:
39. Feature: Team Scoring Teams start with zero score Correct answer gets points Scenario: Score starts at 0 Given I register a team Then my score is 0 Scenario: Correct answer gets 10 points Given I register a team When I submit a correct answer Then my score is 10
40. Points awarded for an answer depend on its difficulty Acceptance criteria:
41. Teams start with zero score. Correct answer gets points depending on how difficult it is. Scenario: Score starts at 0 Scenario: Correct easy answer scores 10 Given I register a team When I submit a correct easy answer Then my score is 10 Scenario: Correct hard answer scores 50 Given I register a team When I submit a correct hard answer Then my score is 50
42. Acceptance criteria User Story Examples Feature: Team Scoring Teams start with zero score. Correct answer gets points depending on 
 how difficult it is. Scenario: Score starts at 0 Given I register a team Then my score is 0 Scenario: Correct easy answer scores 10 Given I register a team When I submit a correct easy answer Then my score is 10 Scenario: Correct hard answer scores 50 Given I register a team When I submit a correct hard answer Then my score is 50
43. Acceptance criteria User Story Examples Feature: Team Scoring Teams start with zero score. Correct answer gets points depending on 
 how difficult it is. Scenario: Score starts at 0 Given I register a team Then my score is 0 Scenario: Correct easy answer scores 10 Given I register a team When I submit a correct easy answer Then my score is 10 Scenario: Correct hard answer scores 50 Given I register a team When I submit a correct hard answer Then my score is 50
44. Acceptance criteria User Story Feature: Team Scoring Teams start with zero score. Correct answer gets points depending on 
 how difficult it is. Scenario: Score starts at 0 Given I register a team Then my score is 0 Scenario: Correct easy answer scores 10 Given I register a team When I submit a correct easy answer Then my score is 10 Scenario: Correct hard answer scores 50 Given I register a team When I submit a correct hard answer Then my score is 50
45. Acceptance criteria User Story Feature: Team Scoring Teams start with zero score. Correct answer gets points depending on 
 how difficult it is. Scenario: Score starts at 0 Given I register a team Then my score is 0 Scenario: Correct easy answer scores 10 Given I register a team When I submit a correct easy answer Then my score is 10 Scenario: Correct hard answer scores 50 Given I register a team When I submit a correct hard answer Then my score is 50
46. User Story Feature: Team Scoring Teams start with zero score. Correct answer gets points depending on 
 how difficult it is. Scenario: Score starts at 0 Given I register a team Then my score is 0 Scenario: Correct easy answer scores 10 Given I register a team When I submit a correct easy answer Then my score is 10 Scenario: Correct hard answer scores 50 Given I register a team When I submit a correct hard answer Then my score is 50
47. User Story Feature: Team Scoring Teams start with zero score. Correct answer gets points depending on 
 how difficult it is. Scenario: Score starts at 0 Given I register a team Then my score is 0 Scenario: Correct easy answer scores 10 Given I register a team When I submit a correct easy answer Then my score is 10 Scenario: Correct hard answer scores 50 Given I register a team When I submit a correct hard answer Then my score is 50
48. Feature: Team Scoring Teams start with zero score. Correct answer gets points depending on 
 how difficult it is. Scenario: Score starts at 0 Given I register a team Then my score is 0 Scenario: Correct easy answer scores 10 Given I register a team When I submit a correct easy answer Then my score is 10 Scenario: Correct hard answer scores 50 Given I register a team When I submit a correct hard answer Then my score is 50
49. Steve Tooke 
 Twitter: @tooky Blog: tooky.co.uk E-mail: tooky@cucumber.io