Agile Toronto 2018 - Sharpen Your Agile Ax ... Story Splitting Time
1 like243 views
These are the slides from my session at Agile Toronto 2018 titled, "Let's Sharpen Your Agile Ax ... It's Story Splitting Time." Description of Talk: Do you want to write great User Stories (a.k.a. small features that are part of a product) that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with completing stories (of business value) that are potentially shippable within a fraction of an iteration/sprint? During this session we will do a quick refresher on User Story formatting to include Acceptance Criteria. The reason for the refresher is that over the last few years, despite people using User Stories, I have experienced their usage far from the intended purpose. After the refresher, we will learn at least 3 techniques for splitting stories in this interactive workshop.
Agile Toronto 2018 - Sharpen Your Agile Ax ... Story Splitting Time
- 1. excella.com | @excellaco Lets Sharpen Your Agile Ax: Its Story Splitting Time Brian Sjoberg (@onek2go)
- 2. excella.com | @excellaco Introductions Story Splitting
- 3. excella.com | @excellaco Introductions Agile/Lean Coach at Excella Team and Organizational levels DC Scrum User Group
- 4. excella.com | @excellaco Outline User Story Acceptance Criteria (AC) Splitting Techniques
- 5. excella.com | @excellaco User Story Story Splitting 5
- 6. excella.com | @excellaco User Story Placeholder to facilitate communication Represents a customers request to the team that creates a product Helps prevent misunderstanding Best option so far
- 7. excella.com | @excellaco Create Shared Understanding Im glad we all agree. Credit: User Story Mapping
- 8. excella.com | @excellaco Create Shared Understanding Oh! Credit: User Story Mapping
- 9. excella.com | @excellaco Create Shared Understanding Ah Ha! Credit: User Story Mapping
- 10. excella.com | @excellaco Create Shared Understanding Im glad we all agree. Credit: User Story Mapping
- 11. Starving Student on a Low Budget to find and purchase food quickly from my mobile device I can fill my stomach without spending a lot of money As a WHO WHAT WHY What is most important? The Who, the What, or the Why? I want So that Need to understand Why the Who wants the What. Important to know Whom this work is going to benefit.
- 12. excella.com | @excellaco Notes about the customer Customer is the person/group requesting value from team building the product Ideally, Product Owner would write the user story for the team but in reality that rarely happens
- 13. 13
- 14. excella.com | @excellaco Notes about the customer Customer is the person/group requesting value from team building the product Ideally, Product Owner would write the user story for the team but in reality that rarely happens Usually, an expert assists the customer and Product Owner in understanding what they really want/need
- 15. excella.com | @excellaco Review Who is the Who in a user story? Is the Who ever the team doing the work, e.g., As a developer, I want to go do something, so that I can do something else.? Who typically writes the user story?
- 16. excella.com | @excellaco Acceptance Criteria Story Splitting 16
- 18. excella.com | @excellaco Present Tense Indicative Statements Correct There is a button in the upper left corner of the screen Incorrect Put the button in the upper left corner There will be a button in the upper left corner We need a button in the upper left corner
- 19. excella.com | @excellaco Today Future
- 24. excella.com | @excellaco Unambiguous Correct The drop down contains each of the days of the week The screen loads in 1.5 seconds or less 95% of the time with strong 4G signal Incorrect The drop down contains Monday, Tuesday, etc Load time is sufficiently fast
- 26. excella.com | @excellaco Acceptance Criteria Present Tense Indicative Statements, i.e., they are either TRUE or FALSE Generally FALSE before the product has been built Must be TRUE for the user story to be accepted Include Functional and Non-Functional Requirements Complete (All I See Is All There Is) Un-ambiguous (no etc., TBDs) Include Examples when helpful
- 27. excella.com | @excellaco Splitting Techniques Story Splitting
- 30. AC Splitting Acceptance Criteria I can search by name I can search by model I can search by category As a <new user persona> I want to search by name So that <new more specific benefit> As a <new user persona> I want to search by model So that <new more specific benefit> As a <new user persona> I want to search by category So that <new more specific benefit>
- 31. excella.com | @excellaco Group Exercise Form groups of 2 or 3 Discuss ways to split the story on the worksheet
- 33. excella.com | @excellaco Group Exercise Form groups of 2 or 3 Discuss ways to split one or more of the stories on the worksheet
- 35. excella.com | @excellaco Group Exercise Form groups of 2 or 3 Discuss ways to split one or more of the stories on the worksheet
- 36. excella.com | @excellaco Timeline Analysis Splitting Pretend User Story is done What happens when the functionality is used? If there is a sequence, then it may be possible to break into smaller stories Credit: SmallerStories.com
- 37. excella.com | @excellaco Group Exercise Form groups of 2 or 3 Discuss ways to split one or more of the stories on the worksheet
- 38. excella.com | @excellaco Lettuce Wrap Up Story Splitting
- 39. excella.com | @excellaco Lettuce Wrap Up User Story Acceptance Criteria Splitting Techniques Acceptance Criteria Conjunction Generic Words Timeline
- 40. excella.com | @excellaco Thank You Comments/Feedback Brian.Sjoberg@Excella.com @onek2go 301-404-0765
- 42. excella.com | @excellaco Three Cs of User Stories Card Small and could fit on a 3 x 5 card Conversation It is placeholder for a conversation to occur in the future. Pointer to other documents Confirmation Objectives identified through conversation are placed here. 42
- 43. excella.com | @excellaco Definition of Ready
- 44. excella.com | @excellaco When Can We Start? When the Definition of Ready (DoR) is met, the user story could be developed. The Definition of Ready applies to all of a teams user stories and is more generic, e.g.: Immediately actionable Negotiable Valuable Estimated Sized-appropriatey Testable
- 45. excella.com | @excellaco Product Backlog Refinement Definition of Ready I N V E S T Why is this needed?
- 46. excella.com | @excellaco Definition of Done
- 47. excella.com | @excellaco When Are We Finished? When the Definition of Done (DoD) and Acceptance Criteria (AC) are both met, the user story is DONE. The DoD applies to all of a teams user stories and is more generic AC pertain to a specific story
- 48. excella.com | @excellaco DoD Example All Code Checked-in Unit Tests Passing Acceptance Criteria Passing Integration Test Passing Performance Test Passing Within a Product Back Item (PBI) Within a Sprint Within a Release Security Audit Passing Regression Test Passing