An empirical approach through customer journeys in web projects
One of the keys questions facing teams developing customer facing application is how to avoid developing something only to find that it isn't needed. A 'traditional' backlog often fails in this regard as it is a list and as such is: Hard to visualise individual features not related to a customer journey or goal. Can lead to a waterfall style analysis with little testing of ideas Leads to the highest paid person in the room dominating what should be done next Does not engage with people effectively A training exercise to build an ecommerce site - Could we use this approach in the 'real world' Recently I was asked to help with a project as a Product Owner and I wanted to use a new, rapid and iterative approach to design. I had experimented with Customer Centred Design for some time and wanted to run a follow up experiment. My hypothesis was base on some training I did with teams unfamiliar with developing a product in an iterative way. The trainin