Better ROI from Software Development Podcast

Providing advice on how to get the best Return On Investment from your Software Development.

This series is targeted at those that fund software development in improving their return on investment.

Through a series of short weekly podcasts, we explore and explain why "traditional" management techniques will not only produce poor returns, but actively encourage it.

Listen at:


#42: Containers, Docker, Kubernetes and Serverless - explaining Container Orchestrators and Kubernetes

Published: Wed, 27 May 2020 12:40:43 GMT

Over the current few episodes I am introducing a number of technologies from modern Software Delivery.

These are:

  • Containers
  • Docker
  • Kubernetes
  • And Serverless

There are "hot" technologies within Software Development at the moment.

They are helping Software Teams:

  • Get Better ROI when spending      on Computer Servers
  • Improving the speed to market
  • Allowing for more complex and      ambitious solutions

These are technologies that your Development Team may want to use or may even be using.

In episode 40, I explained Virtualisation; a technology that makes the other possible.

In episode 41, I introduced Containers and the Docker Container format - a technology that allow us to achieve greater ROI from our physical servers, improves our developer productivity and increase simplicity to access the tools they need,

Towards the end of that episode I talked about how containers and the Microservice architecture from episode 17 are logical bed fellows and are gaining huge industry adoption.

The downside to this however is a level of complexity brought by having so many small "parts" to manage.

While it is considerably easier to think about and develop at a small scale ... Linking them together correctly brings additional overheads to the big monolith on a single server setup.

To make this practical we need a Container Orchestrator - the subject of todays episode.

Listen now  

#11: We need to talk about Culture

Published: Wed, 02 Oct 2019 15:45:57 GMT

In the last five episodes I've introduced a number of terms to help us move away from the traditional software development practices.

In episode 6, I introduced the Minimum Viable Product as a way to rethink our traditional ideas of waterfall style software projects. I recommend using MVP as a way to approach the traditional problems of unknown benefits, unknown costs and unknown risks.

In episode 7, I introduced Lean as a backup to the mind set behind Minimum Viable Product. Lean's strong manufacturing pedigree stands out as a proven method of reducing waste, delivering faster throughput and ultimately value to the customer.

In episode 8, I introduce Agile as a complementary mind set to back up Minimum Viable Product. I introduced the Agile Manifest; the commitment behind much of the work in the Agile movement since 2001. I showed how the manifestos recommendations aligned with Lean and MVP.

In episode 9, I introduced the Cloud as a key enabled to support the adoption of Minimum Viable Product, Lean and Agile. I talked about the value that the flexibility of the Cloud can provide - along with the potentially market changing opportunities made available by initiative services the Cloud makes available.

And in the last episode, episode 10, I introduced DevOps as a set of practices and process that build on a Lean & Agile heritage. I also introduced the State of DevOps report as providing evidence that DevOps is helping organisations meet and exceed their goals.

In this episode, I want to take a step back and address some of cultural issues that these episodes generate.

Listen now