Agile as a way of tackling IT development came out of a frustration with the high failure rate of traditional waterfall methods. There’s a parallel with strategy; conventional strategy fails the vast majority of the time and to some extent, it fails for the same reasons that waterfall tended to. Like traditional IT projects, traditional strategy assumes that we can set requirements at the start, follow a linear path without deviating, and that the world will stay stable for us until we’ve finished delivering. Of course, for strategy that is almost never true, which is why it almost never works.
This webinar talks about some of the principles that underpin both “Agile” and “Agile strategy,” what some genuinely Agile strategy approaches look like and how they work.