On delivering software

More than ten years ago, some visionaries got together in the mountains of Utah to relax, ski and discuss on the challenges of their profession. That was the very moment when the Agile movement cristallized. They wrote a manifest and 12 principles. The first gem goes like:

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

And only now we all are understanding what they mean. Even them.

In Software G Forces: the effects of acceleration, Kent Beck discusses the technological and business challenges of making your releases shorter. And why that matters (see also a good summary of Beck ideas by Mary Poppendieck).

On the other hand, Jeff Humble and David Farley have published a (jolt-award wining) book called Continuous delivery, which goes (technological) deeper on the value proposal done by Beck. I highly recommend this talk by Jeff at DevOps Hamburg and the introductory article.

Seems that it takes 10 years for the new ideas to mature and emerge in other shapes and wrappings. Nice to see that we, (“software deliverers”) as a profesion, are continuously improving.


3 responses to “On delivering software”

  1. […] Software G Forces: the effects of acceleration was one of my favorite talks this year, which together with the book Continuous delivery bring to life again the big theme of agile movement: how to better build software. […]

  2. […] Alguien tan experimentada como Jocely Goldfein (VMWare, Facebook) dice que no existe the one true way to ship software. Que nos acostumbremos a tener trade-offs y pensar desde nuestro contexto. Como complemento a este artículo, recomiendo oir a Beck hablando de qué variables determinan el contexto de uno: tiempos de release, negocio y prácticas de ingeniería. […]

  3. […] ¿Qué tienen en común la dieta japonesa, los métodos de entrenamento de Mouriño y las técnicas ágiles de creación de software? […]

Leave a Reply

Your email address will not be published. Required fields are marked *