Agile Principles -- Continuous Delivery

April 16, 2012 · 1 min read

Probably the most important principle in all of agile development reads like this... 

Our highest priority is to satisfy the customer 

through early and continuous delivery of valuable software. 

I like to sum this up in one succinct statement, software that is sitting in QA is not providing value to anyone. 

The most important thing an agile practitioner can do is identify valuble pieces of software and get them to production as fast as posible. Notice that this principle does not specify a timebox, or iteration length or any other such thing. The key is in the term continuously. As soon as you have something that could be providing value, get it out the door.

This article is part of the GWB Archives. Original Author: Jonathan Mills

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.