Source: Jeff Patton on User Story Mapping and Product Management

• Art school dropout to software developer to early Extreme Programming
• “Extreme Programming Explained” by Kent Beck (and we agree the first edition was the better version!)
• One of the secrets to success is having a great relationship with customers
• Early Agile colleagues included Eric Evans (“Domain-Driven Design“), Joshua Kerievsky (“Refactoring to Patterns” and Industrial Logic), Rob Mee (Pivotal Labs)
• The product decisions on what to build matter most
• YOW! Talk “User Story Mapping: Discover the Whole Story“
• Story Mapping addressed the problem of losing sight of the big picture when building very small things
• Larry Constantine and Lucy Lockwood “Software For Use” – task modelling was the inspiration for Story Mapping
• Impact Mapping was inspired by Effect Mapping
• There is no way to build a story map and not stand in the shoes of someone using your product
• They were initially called “stories” not “user stories”, because of the way we use them – it’s not a change in the way we write documents, its a change in the way we work
• As a… I want… So that… is just a conversation starter, and they need titles!
• Dependencies in story mapping – the map helps you see in slices, using stories helps you build the thing you need now
• Passionate Product Owner course
• The hope of the User Story Mapping book is that people think differently about stories
• Your job in software development is not to build more crap faster, your job is to change the world
• Jez Humble “Lean Enterprise” – output and impact
• What we do now builds on an Agile foundation – but it is more than Agile – we are missing an umbrella term for product centricity
• Raccoon! – Jeff likes it, but it doesn’t work in mountain states as they knock over garbage cans!

  TheAgileRevolution-95 (43 minutes)