I have a fundamental problem when teaching Story Mapping in a class or workshop. That is, participants never have enough time to build a complete enough backlog to explore all the different release and development strategies that having a full backlog gives you. That sucks. But, I have a simple solution.
This question recently came from Douglas Ferguson (but I get asked a lot)
[In User Story Mapping], how do you typically handling multi-user processes that create branches?
Do you create different maps for different users and different flows?
My take on Garrett’s popular Elements of User Experience model coupled with tactical advice for: creating models to better understand your users, improving your software’s usability, and improving your applications’ visual design.
Garrett’s Elements of User Experience
Jeff Patton’s Tactical Advice
User Interface Design, User Centered Design, Interaction Design, Information Architecture, Visual Design, Human Computer Interaction, and Usability Engineering – what do all these terms mean? And exactly what do you need to do to improve your users’ experience with your software? Now more than ever the quality of user experience separates the successful software products from the failures.
Effectively leveraging advanced user interactions such as Ajax requires a fundamental knowledge of user experience processes and techniques.
In this tutorial you’ll learn what User Experience specialists do and how you can leverage Ux approaches to improve the quality of user interface in your software.
Other Useful Information
Jeff Patton and Dave Gray discuss agile design, lean startups, design thinking, teams of teams and much more.
“For me, an agile process turns good people into order takers.” – Jeff Patton
What is valuable out of agile development? Learn that answer, what’s missing in agile development and Jeff’s ideas on where to go from here.
Streamed live on Jan 21, 2014 | Video Length 53:16
View this video on YouTube.
There’s more on this topic, check out Jeff’s blog posts.
Understanding and communicating requirements in an Agile environment is a very different way of thinking and working.
In this talk, Jeff will explain where the idea of the agile story came from, and how best to write and use them. You’ll learn how stories help you manage the flow of discussion and work from big ideas all the way through to delivery. You’ll learn how to break big ideas down into organized backlogs using story mapping. You’ll learn how stories fit into a discovery process that you’ll use to better understand the challenges of your customers and users, imagine solutions, and continuously learn if you’re building things they truly value.
Jeff Patton gave this talk at Agile 2013 on August 6.