@TotherAlistair @KentBeck I'll commit heresy. I don't even view SCRUM as being that agile. Scrum + mvp + kanban + all those other artefacts are great ways of building a product once you have an idea (an MVP) of where you are going. For me, that's more the Lean space, all about learning and reducing waste.
@TotherAlistair @KentBeck To put it simply, this is the approach I've used (fig 1) from software to heavy engineering and it's best implemented with a map (fig 2) because any system contains many evolving components ... 
@TotherAlistair @KentBeck ... and to give you my background, this is because I directed my company to go "All Agile" around 2002 (PS. loved the manifesto btw) but by 2004, I started to discover that going "all agile" doesn't work. By 2005, I had maps and was on the path to mixed methods.
@TotherAlistair @KentBeck Btw ... I'm not saying there's anything wrong with the manifesto, I can't fault it, IMHO it's fabulous and always was. The problem for me was way too many things are calling themselves "agile" when they really aren't that - they're more lean / product development processes.
