I’m a full time agile coach, and a part time Kiwi trouble maker. I love roaming around taking photos of my home city , Berlin, and complaining that it doesn’t snow enough. The thing I love MOST though is agile, and the fun and culture that can be built by using it! For my personal credentials; I have been involved with the IT sector for 15 years.. UI and UX design for 12 of those, and a scrum (CSM, CSP, CSPO) and advanced kanban specialist for 8… though i would officially describe myself as a recovering business analyst.
Likes it’s older and more broad sister, Story Mapping; Flow mapping is a way to get a big picture view over a tiny chunk of your backlog. Flowmapping seeks to bridge the gap between the unfashionable (but totally necessary) world of architectural system or process modeling, and agile teams. Flow charts are still the first go to to figure out what needs to be developed if your product has processes that get turned into functional chunks. When used in tandem with other agile techniques like the Strawman, Flow mapping can help to plan and de risk the unsexy back end parts of product.
Its fast, analog and easy for any team of any level to implement.