Quick Intro to Story Mapping and Planning

Transcript

1. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Quick Intro Story Mapping and Planning
2. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Practices Story Mapping Example Mapping Scenario: Playlist without name is auto-numbered Given existing Playlists | My Playlist #1 | | My Playlist #2 | When a new playlist without name is added Then that new playlist is given the name ‘My Playlist #3’ Scenario: Playlist without name gets next available slot Given existing Playlists | My Playlist #1 | | My Playlist #3 | When a new playlist without name is added Then that new playlist is given the name ‘My Playlist #2’ Scenario writing
3. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Story Mapping To break a big feature/project into smaller parts while keeping the big picture in sight, and defining the slices in which we can split delivery.
4. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Example Mapping To discover together, and agree unambiguously what the expected result will be when we've implemented a story by generating examples of how it will behave.
5. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Scenario Writing To apply some rigour to our examples, to ensure we use the same language, and verify our understanding, while also allowing us to turn these specifications into executable tests. Scenario: Playlist without name is auto-numbered Given existing Playlists | My Playlist #1 | | My Playlist #2 | When a new playlist without name is added Then that new playlist is given the name ‘My Playlist #3’ Scenario: Playlist without name gets next available slot Given existing Playlists | My Playlist #1 | | My Playlist #3 | When a new playlist without name is added Then that new playlist is given the name ‘My Playlist #2’
6. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Geek and Poke’s Advanced Scrum – Licensed CC-BY 3.0
7. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Story Mapping “The flat backlog is poor explanation of what a system does” - Jeff Patton https://www.jpattonassociates.com/the-new-backlog/ https://www.jpattonassociates.com/wp-content/uploads/2015/01/how_you_slice_it.pdf
8. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Benefits of Story Mapping • Structured way of breaking down something big • Always clear how the parts fit into the whole • Always clear how what we do relates to the user’s needs • Done together, creates common understanding • Focused on creating small deliverable increments • Brings more structure and meaning to the portfolio
9. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Structure, relations and overview
10. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Structure, relations and overview
11. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Elements of a Story Map
12. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Elements of a Story Map
13. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Process
14. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Getting ready for work Write down everything you have/had to do to to get out the door on your way to work.... “Shut off alarm” “Get into the shower” “Wash hair” “Make coffee” ...
15. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Big feature, big map
16. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Technical work can be valuable on its own
17. Lagerweij Consulting and Coaching | Wouter Lagerweij | @wouterla | wouter@lagerweij.com Value • “Business Value”, “Value for the users” ◦ Drives towards larger steps/slices/stories Better: Something is valuable when it: • Increases knowledge • Decreases risk • Generates useful feedback (Seb Rose: https://www.slideshare.net/sebrose/user-stories-from-good-intentions-to-bad-advice-lean-agile-scotland-2019)
18. Lagerweij Consulting and Coaching | Wouter Lagerweij | wouter@lagerweij.com Slicing it smaller: address
19. Lagerweij Consulting and Coaching | Wouter Lagerweij | @wouterla | wouter@lagerweij.com Slice and plan • Slice -> Sprint • Plan in slices, not stories • Stories only in Jira after refinement, right before sprint
20. Lagerweij Consulting and Coaching | Wouter Lagerweij | @wouterla | wouter@lagerweij.com Slices to allow prioritisation
21. Lagerweij Consulting and Coaching | Wouter Lagerweij | @wouterla | wouter@lagerweij.com Slices are… • Small ◦ A sprint-sized-chunk makes it easy to create a planning ◦ Deployment != Release ◦ Slice X is release ready => make that visible on the map ◦ A slice with a name gives an instant sprint goal ▪ Focus • Named ◦ Put value central ◦ Clear goal ▪ Allows for decisions by the team
22. Lagerweij Consulting and Coaching | Wouter Lagerweij | @wouterla | wouter@lagerweij.com Slice Twice Once for releases , then for planning