Story maps andjust in time analysisTeamGunFire                 @benmathews80
Product Backlog    @benmathews80
Product BacklogHard to prioritise                One dimensional                        Can lack                         c...
Story mapsWhat are those then?                       @benmathews80
@benmathews80
Story mapsActivity     Sign inTask        Register         Log in       Log out           Can create a    Can accessStorie...
Story mapsMVPRelease   2Release   3          @benmathews80
Story maps@benmathews80
Story maps@benmathews80
Story mapsReveal            Helps slicing questions         User focusedVisual                   Aids                     ...
Story mapsGet the activity and task level right                   Explain to the team      Work from the map              ...
Just in time analysis(or how we’re coping with a big team)                               @benmathews80
JIT analysis      I try to do no work…      (but fail!)                      Team pulls                        analysisSim...
JIT analysis     Daily stand up                            StoryPO catch                      huddles up            Ad-hoc...
JIT analysisLo-fi artefacts                  @benmathews80
JIT analysis@benmathews80
@benmathews80
Upcoming SlideShare
Loading in …5
×

Story Mapping and JIT Analysis

941 views
793 views

Published on

A presentation on story mapping and just in time analysis.

Presented at the London Scrum User Group 15/02/2012

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
941
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Huge array of stories of different sizesLittle traceability of stories that have been decomposedToo detailed to get an overview – lacks context - Hard to see gapsHard to prioritise “log in is just as important as register new user”
  • Asking a product owner to prioritise some stories is meaningless to them. E.g. register vs log inAs we break large stories down, the resulting workable stories can lose context and obscure the bigger picture (smell – lots of stories with the same value statement)Hard to spot gaps where the stories meet, assumptions about where one story ends and another begins
  • Tolkien produced a detailed map of Middle Earth to give readers context and to help visualise the journey the fellowship took.Story maps aim to do something similar for a project.Jeff Patton (circa 2005 although used before)
  • Start with main activities – do this for all the activities in the systemIdentify the tasks the user does as part of that activityGenerate stories for those activitiesIdentify what stories are releasable and those that aren’tI’m never asking my PO to prioritise log in vs log out.
  • Produced high level estimates based on the tasksStarted to build up a list of questions and risks
  • Started to get estimates on the first release of storiesQuestions answered visibleString indicates MVP
  • Our usual team size is 4 devs plus QA, PO, BA, SMThis project has 8 devs, bigger than recommended scrum size (12 people)Several apps, CRM, eCommerce, Fulfilment, Job Management, FinanceAcceptance criteria usually created in backlog session, too many people to manage that effectivelyProblems to solveHow do I know what people need to know? How do we share that information without making peoples heads explode?When do we capture acceptance criteria and who needs to know them?
  • Touch points previously mentioned are opportunities to request informationFocus on simple documentation at the point at which it’s neededSpend more time making sure we have conversations. My mornings blocked out for huddles and sitting with pairs to see if they need anything.
  • Backlog sessions now just about high level understanding of scope and sizing. Some technical discussion.PO catch ups make sure I’m in sync with the PORetrospectives (I didn’t understand…)Conversation during the day (co-location for the win)Story huddles – as story starts, dev pair, QA and BA discuss and write acceptance criteria.
  • Story Mapping and JIT Analysis

    1. 1. Story maps andjust in time analysisTeamGunFire @benmathews80
    2. 2. Product Backlog @benmathews80
    3. 3. Product BacklogHard to prioritise One dimensional Can lack contextProne to gaps @benmathews80
    4. 4. Story mapsWhat are those then? @benmathews80
    5. 5. @benmathews80
    6. 6. Story mapsActivity Sign inTask Register Log in Log out Can create a Can accessStories basic account secure page Can log out Email Can reset confirmation password Capture company Can see Capture Can see welcome name confirmation message @benmathews80
    7. 7. Story mapsMVPRelease 2Release 3 @benmathews80
    8. 8. Story maps@benmathews80
    9. 9. Story maps@benmathews80
    10. 10. Story mapsReveal Helps slicing questions User focusedVisual Aids prioritisation Show MVP clearly @benmathews80
    11. 11. Story mapsGet the activity and task level right Explain to the team Work from the map @benmathews80
    12. 12. Just in time analysis(or how we’re coping with a big team) @benmathews80
    13. 13. JIT analysis I try to do no work… (but fail!) Team pulls analysisSimple artefacts are better A conversation is better still @benmathews80
    14. 14. JIT analysis Daily stand up StoryPO catch huddles up Ad-hoc conversation Retrospective Backlog sessions @benmathews80
    15. 15. JIT analysisLo-fi artefacts @benmathews80
    16. 16. JIT analysis@benmathews80
    17. 17. @benmathews80

    ×