Time to Rethink Agile in Enterprise Startups
Interesting interview in First Round Review with Ogi Kavazovic from Flatiron Health:
“In Kavazovic’s experience, the two pitfalls described above boil down to a key misunderstanding: agile development and longer-term planning are NOT actually the mutually exclusive modus operandi the tech world has portrayed them to be.”
I think saying that the 'tech world' has claimed that long-term planning does not fit with agile development is a bit of a straw man. It's true that you should not make detailed plans many months or years into the future: they'll invariably be wrong and you'll have to change course. But what Kavazovic really means by "longer-term planning" is that you need to have a vision of the future that you're trying to get to, and it seems to me that that is wholly within the scope of agile development. The long term vision is especially important in Enterprise companies because, as Kavazovic succinctly states:
“There’s still a vital difference between consumer and enterprise sales: Selling to users vs. selling to buyers”
This is the classic problem faced by all software companies trying to sell to business. To persuade the software buyer to sign a multi-year contract, you need excite them with future developments that will justify their long-term contract. However in order to delight the software user, you need to iterate quickly through solutions to find what will meet their needs. Giving the buyer what they need requires certainty. Giving the end-user what they need requires experimentation, i.e. an absence of certainty.
“Agile is really good for making sure that you create a successful user experience. But it’s important to separate that from the overall product roadmap, which requires meeting the needs of your buyer.” The key is to take a two-pronged approach: 1) articulate a long-term product vision, but 2) establish a culture of flexibility when it comes to the details.”
Kavazovic's proposed solution to this tension is not so radical - it's essentially a rehash of the 'roadmap based on problems' framework - but it does present a neat way to meet the contradictory needs of the buyer and end-user.