Story Mapping: Putting the User Back Into the User Story – January 18th 2018


The User Story template has three important parts; however, agile development teams often have a tendency to leave off the last part (the “Why”, or outcome objective), and the first part (the “Who”, or consumer of the functionality). The remaining stripped down “User Story” leaves out the rich elements and characteristics necessary for robust development. Meanwhile, even fully-formed, 3-part User Stories are missing essential detail, especially when it comes to describing the relationships between the stories and the user’s workflow that they represent. Story mapping solves both of these problems. It keeps the user forefront, and it provides a multi-dimensional description of the product. Come learn the basics of Story Mapping, some examples, and some tips and tricks you can take back to your own workplace to put the User back into the User Story.

Jaynee Beach has been a passionate User Experience designer and advocate for over 30 years. She enjoys using an Agile mindset to help teams create valuable user experiences and bring them to market. She is the co-author of “Experience Design: Simplifying the Complex” (fall, 2017). Jaynee holds BS degrees in Math and Computer Science, and MS and PhD in Cognitive Psychology. She led the transformation of the Cobra and Huey helicopter cockpits from analog gauges to multi-function displays; and the team that created the user interface for the Autonomic Logistics Information System (ALIS) on the F-35 Joint Strike Fighter. She holds a co-patent for a graphical user interface for well treatment plans in oil and gas, and shares a patent with the research team that explored multi-modal alerting in combat aircraft cockpits. Jaynee is the CEO of Agile ITDX, a company specializing in Digital Transformations that use data science to create intelligent design.


Sponsored by:

Comments are closed