We often talk a lot about various initiatives and the resulting technical solutions in detail. But we often do so without keeping in mind the specific business objective and the desired impact we want to achieve. This is where Impact Mapping comes in.
This question often comes up in agile teams. In this blog post, we look for the answer to this question in the context of the various agile and organisational frameworks like Scrum, LeSS, SAFe, Disciplined Agile and draw a conclusion.
While preparing for my guest lecture on technology decisions, I stumbled across a slide with the 12 principles from the agile manifesto. It made me realise again how apt these principles from the agile manifesto from 2001 (!), which are often forgotten in practise, are for product development.