Highlights

None

Agile might seem perfectly suited for when a company is developing a product or service that doesn’t exist and is looking to move quickly

None

The fundamental problem with agile, as many companies use it, is that its relentless pace biases developers. They want to get out a minimum viable product in only a few weeks, so they skimp on scoping out just what the product should accomplish.

None

rather than take the time and uncertainty to develop a new capability, they go with the skills they currently have. They accept their existing constraints, which automatically limits the potential for a high-growth offering.

None

they curtail their ambitions on the product. Instead of a major breakthrough, they tend toward only incremental improvements on existing offerings. Or if they do go bold, their minimum viable product isn’t really viable at all, so customers can’t give realistic feedback. The developers haven’t had time to do their homework and prepare something that’s sustainable.

None

Amazon, for example, has learned to use the working backwards process for idea development, but then follow agile to build and ship the product.