Customer Centric Product Development - Applying Story Mapping TechniquePadma Satyamurthy
schedule 3 months agoSold Out!
Every product development essentially starts with requirements collection of what product should do and what user wants. However this becomes the most difficult part to focus on what and where to start the development from. For years, the product development requirements have become inundated with requirements templates and word documents. The traditional 100-500 page requirements document that was widely practiced a few years ago was having its own limitations. The teams particularly started feeling difficult to consume and manage these large documents and deliver value incrementally.
With more and more organizations moving to agile, the product development teams started going for leaner structures that represent crisply what customer / user wants from the product.
The teams are have done away with multi-page requirements documents and have adopted backlog as a source of managing requirements. The backlogs also started helping teams to break the large product expectations into multiple layers of epics, features/enablers and user stories.
But, at times, during this breakdown, there are chances of losing the big picture and prioritization and hence impacts the value delivered to customer as early as possible. Story mapping techniques, created by Jeff Patton is one of the most popular way to help carve out the MVP from the big picture that helps the organization to realize value at the earliest.