Listen "Delivering Working Software Frequently & Continuously"
Episode Synopsis
In episode 5 of Troubleshooting Agile we discuss the Third Agile Principle: 'Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.'
Evolution in our thinking, since the Agile Manifesto was written back in 2001, makes what was once considered 'shorter timescales' seem laughable now, but, when retrospecting, 'working software frequently' remains one of the core agile disciplines. But, as Squirrel and Jeffrey highlight through various client stories, it is far from easy to implement continuously.
We hear where, why and how so many companies fail to fully employ this principle, and Squirrel and Jeffrey discuss some interesting techniques to overcome common problems - from slicing up elephant carpaccio to employing continuous integration with nothing more than a rubber chicken.
*We apologise for a few sound difficulties at the start of the episode with Jeffrey's mic. Stick with it and they soon pass.*
***
Squirrel and Jeffrey have told us which common obstacles they regularly witness that prevent organisations from delivering working software frequently. Now we want to hear from you guys on the matter. You can leave your answers in the comments below, you can email us at [email protected], or you can find a poll on our Twitter feed @TShootingAgile.
What are the obstacle for your organisation to delivering working software frequently?
1. The tech team aren't offering to do this, or don't know how.
2. Customers (external or internal or both) don't know it's possible or how to use it if offered.
3. Both 1. and 2.
4. Neither - we already deliver frequently!
***
SHOWNOTES:
-Agile Manifesto Principles - http://agilemanifesto.org/principles.html
-Continuous Delivery, by Jez Humble and David Farley - https://martinfowler.com/books/continuousDelivery.html
-Continuous Delivery - https://continuousdelivery.com
-CITCON - https://citconf.com
-James Shore's blog: "Continuous Integration on a Dollar a Day - http://www.jamesshore.com/Blog/Continuous-Integration-on-a-Dollar-a-Day.html
-Alistair Cockburn's blog: "Elephant Carpaccio" - http://alistair.cockburn.us/Elephant+carpaccio
***
We'd love to hear any thoughts, ideas or feedback you have regarding the episode (or regarding anything else for that matter).
You can email us, here:
[email protected]
Or send us a tweet, here:
twitter.com/TShootingAgile
Or you can find our website, here:
troubleshootingagile.com/
Also, here is a link to our iTunes:
itunes.apple.com/gb/podcast/troub…d1327456890?mt=2
If you feel like liking, Sharing and/or Subscribing, we'd really appreciate it.
Evolution in our thinking, since the Agile Manifesto was written back in 2001, makes what was once considered 'shorter timescales' seem laughable now, but, when retrospecting, 'working software frequently' remains one of the core agile disciplines. But, as Squirrel and Jeffrey highlight through various client stories, it is far from easy to implement continuously.
We hear where, why and how so many companies fail to fully employ this principle, and Squirrel and Jeffrey discuss some interesting techniques to overcome common problems - from slicing up elephant carpaccio to employing continuous integration with nothing more than a rubber chicken.
*We apologise for a few sound difficulties at the start of the episode with Jeffrey's mic. Stick with it and they soon pass.*
***
Squirrel and Jeffrey have told us which common obstacles they regularly witness that prevent organisations from delivering working software frequently. Now we want to hear from you guys on the matter. You can leave your answers in the comments below, you can email us at [email protected], or you can find a poll on our Twitter feed @TShootingAgile.
What are the obstacle for your organisation to delivering working software frequently?
1. The tech team aren't offering to do this, or don't know how.
2. Customers (external or internal or both) don't know it's possible or how to use it if offered.
3. Both 1. and 2.
4. Neither - we already deliver frequently!
***
SHOWNOTES:
-Agile Manifesto Principles - http://agilemanifesto.org/principles.html
-Continuous Delivery, by Jez Humble and David Farley - https://martinfowler.com/books/continuousDelivery.html
-Continuous Delivery - https://continuousdelivery.com
-CITCON - https://citconf.com
-James Shore's blog: "Continuous Integration on a Dollar a Day - http://www.jamesshore.com/Blog/Continuous-Integration-on-a-Dollar-a-Day.html
-Alistair Cockburn's blog: "Elephant Carpaccio" - http://alistair.cockburn.us/Elephant+carpaccio
***
We'd love to hear any thoughts, ideas or feedback you have regarding the episode (or regarding anything else for that matter).
You can email us, here:
[email protected]
Or send us a tweet, here:
twitter.com/TShootingAgile
Or you can find our website, here:
troubleshootingagile.com/
Also, here is a link to our iTunes:
itunes.apple.com/gb/podcast/troub…d1327456890?mt=2
If you feel like liking, Sharing and/or Subscribing, we'd really appreciate it.
More episodes of the podcast Troubleshooting Agile
Gene Kim on Vibe Coding Part II
17/12/2025
Gene Kim on Vibe Coding Part I
10/12/2025
Montage vs Marginal
03/12/2025
Three Types of Learning Part II
26/11/2025
Three Types of Learning Part I
19/11/2025
Greatest Hits: The Systems Thinking Rant
14/11/2025
A New Boat Every Day
05/11/2025
Systems Thinking Rant Redux Part III
29/10/2025
Systems Thinking Rant Redux Part II
22/10/2025
Systems Thinking Rant Redux Part I
15/10/2025
ZARZA We are Zarza, the prestigious firm behind major projects in information technology.