Delivering software with DevOps and Agile
Lately everyone’s trying to fix or replace the concept of MVP (minimum viable product) in Agile software development, but MVP ain’t broke, and doesn’t need fixing.
For anyone who’s forgotten, here’s Eric Ries’ definition of MVP: “the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.”
Continue reading “MVP Ain’t Broke”
Continuous delivery shouldn’t be a controversial subject in the world of Agile software development – the third principle behind the Agile manifesto all but requires it: “Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.” Yet as with true iteration, enterprises embracing Agile software development often balk at the idea.
Continue reading “Continuous delivery isn’t scary, it’s necessary”
The values and principles of the Agile Manifesto are explicit about the need for frequent releases of working software, which must be iterations of the product, not simply increments of a plan made prior to commencing development. Yet the iterative approach – necessarily including re-work to features that are already delivered – often faces strong opposition from within enterprises, even those that are enthusiastically embracing Agile.
Continue reading “Agile needs iteration, not just incrementation”