Better ROI from Software Development

In this episode, I discuss my personal experience with Microsoft Certifications and their value in the IT industry.

I believe that certifications provide a wider breadth of knowledge that may not be obtained through day-to-day work - but is still no subsitute for experience when it comes to recruitment.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/166

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In this episode, I introduce the Actor Model as a Design Pattern that can offer faster and more efficient processing by managing state in memory.

I discuss potential use cases for the Actor Model, such as in online gaming and IoT sensors, but acknowledge that it is a different development model than traditional approaches.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/165

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In this podcast episode, I introduce the concept of design patterns in software development and explain their importance in improving code quality and readability.

I give examples of design patterns in everyday life and emphasize how they can speed up the development process by providing tested and proven development paradigms.

I also highlight the confusion that can arise when design patterns are not followed correctly.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/164

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

This is the first episode after a prolonged break - so firstly, an apology for the gap in recordings.

In this episode I wanted to talk about why I took a break, the lessons to learn and what I've been up to over the past few months.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/163

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

As we start the new year, its not uncommon for organisations to looks at budgets and general expenditure - and given the current financial outlook, I would have expected many organisations to be taking the time to look at how best to weather the storm.

I've found that many organisations typically react with a combination of cost cutting and putting pressure on staff for "more" in such periods.

However like many "traditional" sound managerial practices, this cause dysfunctional and negative outcomes in the Age of Software & Digital - and specifically when it comes to any form of knowledge work like Software Development.

The problem we have is that these "traditional" managerial practices have become muscle memory - so ingrained with the managerial psyche that it can be a difficult thing to re-think.

In this episode, I want to ask you to re-think about 3 things in particular:

-----

Find this episodes show notes at: https://red-folder.com/podcasts/162

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

This episode, I wanted to take a quick look at the 2022 edition of the State of DevOps Report.

I've talked a number of times about the State of DevOps report. I originally introduced it back in episode 13, and last year I devoted seven episodes, 120-126, to a deep-dive into the 2021 edition.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/161

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

I've long held the belief that Estimation is the source of much dysfunction within Software Development.

However, with a New Year, I'll like to take this as an opportunity to revisit my strong opinions on the subject - are they still valid? Are there better ways?

In this episode I recap the understandable desire for Software Development Estimations, why I feel that its a source of so much dysfunction and my plan for the coming year to test and challenge my opinions.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/160

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

I originally discussed Gantt charts back in episode 62, but I found more history behind them while researching Scientific Management and Taylorism for episode 156. I originally thought to include this additional history in that episode, but it felt out of place - thus this separate episode to revisit Gantt charts.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/159

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why of the podcast.  Over recent episodes, I've take a deeper dive into the themes of the pitch and why they made the cut.

And in this weeks episode, I want to explore the idea that there is no a one-size fits all approach to Software Development

-----

Find this episodes show notes at: https://red-folder.com/podcasts/158

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why of the podcast.  Over the coming episodes, I'll take a deeper dive into the themes of the pitch and why they made the cut.

In this episode, I look at why Software Development cannot be deterministic - why do have so many unknowns - why can't we make it as deterministic as moving pig-iron or flipped hamburgers at McDonalds.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/157

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why of the podcast.  Over the coming episodes, I'll take a deeper dive into the themes of the pitch and why they made the cut.

In this episode, I want to take a deeper dive into the management practices of yesterday - where they came from and why they gave us success yesterday but are failing us today and certainly not fit for tomorrow

-----

Find this episodes show notes at: https://red-folder.com/podcasts/156

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why the podcast.  Over the coming episodes, I'll take a deeper dive into the themes of the pitch and why they made the cut.

Over the last few episodes, I've looked at the business side of the pitch and how our organisations need to embrace changes as something they do rather than something that happens to them.

In this episode, I want to move onto the Software Development half of the pitch, and look at its age and maturity.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/155

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why the podcast.  Over the coming episodes, I'll take a deeper dive into the themes of the pitch and why they made the cut. 

In this episode, I follow on from last weeks introduction of change, brought on by the current Age of Software and Digital, by providing more evidence of change - along with why change shouldn't be something that happens to an organisation - change should be something that an organisation "does".

-----

Find this episodes show notes at: https://red-folder.com/podcasts/154

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why the podcast.  Over the coming episodes, I'll take a deeper dive into the themes of the pitch and why they made the cut.

In this episode, I wanted to talk about why I led with "Welcome to the Age of Software and Digital".

-----

Find this episodes show notes at: https://red-folder.com/podcasts/153

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why the podcast.  Over the coming episodes, I'll take a deeper dive into the themes of the pitch and why they made the cut.

If you listen back to the pitch, you will notice that it is almost half way through the 5 minutes and 21 seconds before I actually mention "software development" - which might seem odd for a podcast entitles "Better ROI from Software Development".

In this episode, I explain why I devote pretty much the entire first half of the pitch to talking about the business context we find ourselves in.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/152

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

On the 23rd September, the UK Chancellor announces a series of change during a "mini-budget".

The mini-budget, and its contents, have been the subject of much debate ever since.

What might have been missed by many people where the changes to the IR35 off-payroll rules - which, as I discuss in this episode, could have material impact on both the contractor AND permanent recruitment markets

Note: Since the original recording and release of this episode, the proposed reversal of the "Off-Payroll" rules has been dropped.  This episode does still however provide some value with a description of IR35 and the Off-Payroll rules.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/151

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Welcome to the 150th episode of the podcast.

In this episode, I take a moment of introspection to revisit the "pitch" for this series.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/150

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Over the last few episodes, I've focused on legacy software - what it is, how it occurs, and various strategies to deal with it.

Alongside that legacy software is the legacy data - which is arguably more important than the data.

In last week's episode, I talked about why thinking about that legacy data is so important.

In this week's, I will provide advice for dealing with it.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/149

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Over the last few episodes, I've focused on legacy software - what it is, how it occurs, and various strategies to deal with it.

Alongside that legacy software is the legacy data - which is arguably more important than the data.

In this episode, I want to talk about why thinking about that legacy data is so important

-----

Find this episodes show notes at: https://red-folder.com/podcasts/148

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen as a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software.

A few weeks ago, I introduced three methods to address legacy software:

In this episode, I take a deeper dive into Outsourcing

-----

Find this episodes show notes at: https://red-folder.com/podcasts/147

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen as a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software. 

Two weeks ago, I introduced three methods to address legacy software: 

-----

Find this episodes show notes at: https://red-folder.com/podcasts/146 

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen as a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software.

In last week's episode, I introduced three methods to address legacy software:

In this episode, I take a deeper dive into Evolution

-----

Find this episodes show notes at: https://red-folder.com/podcasts/145

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen as a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software.

In this episode, I'll introduce three methods to address legacy software:

I briefly compare the three options and will dig further into each in future episodes.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/144

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software.

In this episode, I'll describe a simply risk matrix that can be used to monitor and highlight how legacy your software products are.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/143

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software.

In this episode, I'll talk about some of the causes behind how our software can become "legacy".

-----

Find this episodes show notes at: https://red-folder.com/podcasts/142

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software.

In this episode, I'll talk about the impact of Legacy software and why the software industry invests so much effort into addressing.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/141

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

This is the start of a new mini-series looking at Legacy software.

The term "legacy" is often seen as positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software.

In this episode, I'll give you an introduction to Legacy software.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/140

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

I've talked many times about the productivity benefits from automation.

In this episode, I talk about the higher value benefits we get from automation - something you could describe as a side-effect.

Automation gives us productivity - but not just to do more, but to do better.  Automation gives us the opportunity to elevate the work carried out by our teams - ultimately leading to better, cheaper, more reliable, more secure software.

I look at common automation techniques and how they helps to free up our teams:

-----

Find this episodes show notes at: https://red-folder.com/podcasts/139

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

I've talked many times about the productivity benefits from automation.

In this episode, I talk about the knowledge sharing benefits we get from automation - something you could describe as a side-effect.

I discuss how, to be effective, any new software developer needs to learn not just the technical tools and practices, but also the domain - the environment in which the software will operate.

I then look at how automation practices like Continuous Integration, Deployment & Delivery, Infrastructure-as-Code and Automated Testing can help provide that knowledge.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/138

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

I've talked many times about the productivity benefits from automation.

In this episode, I talk about the auditability benefits we get from automation - something you could describe as a side-effect.

I discuss:

-----

Find this episodes show notes at: https://red-folder.com/podcasts/137

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

I've talked many times about the productivity benefits from automation.

In this episode, I talk about the security benefits we get from automation - something you could describe as a side-effect.

I discuss:

-----

Find this episodes show notes at: https://red-folder.com/podcasts/136

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In this episode I introduce Infrastructure-as-Code - a way of defining your Operation's infrastructure as code - an example of DevOps in practice with our Ops teams learning from our Dev teams.

Why you may be interested in this episode:

-----

Find this episodes show notes at: https://red-folder.com/podcasts/135

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In this episode I want to continue the talk about the team structures discussed on https://web.devopstopologies.com/ - with a focus this week on the topologies are shown to work.

The devopstopologies.com website is based on the work by Matthew Skelton & Manuel Pais. I introduced Matthew and Manual as authors of the Team Topologies book in the last episode.  The work is a pre-cursor to the Team Topologies book - and work that I feel stands on its own two feet - with a specific look into how teams should work together to gain benefits from DevOps.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/134

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In this episode I want to talk about the team structures discussed on https://web.devopstopologies.com/ - with a focus this week on the anti-types.

The devopstopologies.com website is based on the work by Matthew Skelton & Manuel Pais. I introduced Matthew and Manual as authors of the Team Topologies book in the last episode.  The work is a pre-cursor to the Team Topologies book - and work that I feel stands on its own two feet - with a specific look into how teams should work together to gain benefits from DevOps.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/133

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In the last episode, I introduced "Conway's Law" - an observation of how our organisational structures influence our software structures.

In this episode, I want to talk about how we can utilise this law when we want to improve problems in our software structures - commonly referred to as the "Inverse Conway Maneuver".

Why you might be interested in this episode:

-----

Find this episodes show notes at: https://red-folder.com/podcasts/132

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In this episode, I introduce Conway's Law, which talks about how our software structures will reflect the structures of the organisations that create them.

Why you might be Interested in this episode:

-----

Find this episodes show notes at: https://red-folder.com/podcasts/131

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

This episode, I want to take a look at Checklists - when to use and when not to.

Much of this episode is inspired by the Sight Reliability Engineering practices that come out of Google.

Why you might be interested in this episode

CORRECTION: During the episode I refer to "The Manifest Checklist" - this should have been "The Checklist Manifesto: How To Get Things Right" by Atul Gawande

-----

Find this episodes show notes at: https://red-folder.com/podcasts/130

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Failure in our software systems is inevitable - be it a failing hard drive, broken network cable, power outage, virus, or simply a bug in the code.

"Hope is not a strategy" - thus we need to think about how we handle that failure.

Why you might be interesting in this episode:

-----

Find this episodes show notes at: https://red-folder.com/podcasts/129

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In this episode, I take a look at "Error Budgets"

Much of this episode is inspired by the Sight Reliability Engineering practices that come out of Google

Why you might be interested in this episode:

-----

Find this episodes show notes at: https://red-folder.com/podcasts/128

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In this episode, I take a look at how to measure the availability of our systems.

Much of this episode is inspired by the Sight Reliability Engineering practices that come out of Google

Why you might be interested in this episode

-----

Find this episodes show notes at: https://red-folder.com/podcasts/127

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

The State of DevOps report provides excellent insight through rigorous analysis of its wide reaching survey.

The research provides evidence-based guidance to help focus on the capabilities that drive performance.

One of those are Site Reliability Engineering practices that came out Google's efforts to handle massive scale.

Why you might be interesting in this episode:

-----

Find this episodes show notes at: https://red-folder.com/podcasts/126

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

The State of DevOps report provides excellent insight through rigorous analysis of its wide reaching survey.

The research provides evidence-based guidance to help focus on the capabilities that drive performance.

One of those is Culture.

Why you might be interesting in this episode:

-----

Find this episodes show notes at: https://red-folder.com/podcasts/125

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

The State of DevOps report provides excellent insight through rigorous analysis of its wide reaching survey.

The research provides evidence-based guidance to help focus on the capabilities that drive performance.

One of those is Security.

Why you might be interesting in this episode:

-----

Find this episodes show notes at: https://red-folder.com/podcasts/124

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

The State of DevOps report provides excellent insight through rigorous analysis of its wide reaching survey.

The research provides evidence-based guidance to help focus on the capabilities that drive performance.

One of those is the DevOps Technical Practices of:

Why you might be interesting in this episode:

-----

Find this episodes show notes at: https://red-folder.com/podcasts/123

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

The State of DevOps report provides excellent insight through rigorous analysis of its wide reaching survey.

The research provides evidence-based guidance to help focus on the capabilities that drive performance.

One of those is quality internal Documentation.

Why you might be interesting in this episode:

-----

Find this episodes show notes at: https://red-folder.com/podcasts/122

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

The State of DevOps report provides excellent insight through rigorous analysis of its wide reaching survey.

The research provides evidence-based guidance to help focus on the capabilities that drive performance.

One of those is Cloud computing.

Why you might be interesting in this episode:

-----

Find this episodes show notes at: https://red-folder.com/podcasts/121

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

The State of DevOps report provides excellent insight through rigorous analysis of its wide reaching survey.

I introduced the State of DevOps report back in episode 13 and in this episode I take a look at the 2021 edition.

Listen to this episode if you are looking for the justification "why" you invest in the effort and disruption that DevOps requires.  Or listen to this episode to understand "how" the practices can help you produce better outcomes from software development.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/120

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Long term listeners will have heard me use the term "Shift Left" - but what does that mean?

In this episode, I take a deeper dive into the "Shift Left" principal, why modern software development advocates it, and common places to find it happening.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/119

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Many of my episode talk about an experimental mindset - have a hypnosis, try something, act on the feedback.

The timeliness and quality of the feedback has real impact on our outcomes.  And I illustrate this in this episode through the act of providing our customer the perfect bath.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/118

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

What is Robotic Process Automation (RPA)?

Even with over 30 years experience, it was a new term to me when I same across it in the Tech Pro Unicorn episode (#114).  Thus I wanted to investigate and share my understanding - and indeed, unexpected personal history.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/117

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

What is Low Code?  What is No Code?  How can they help us?

I touched on this subject during the Tech Pro Unicorn episode (#114), but had a lot more notes than could be covered - thus in this episode, I take a deeper dive.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/116

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Should you build or buy your software?

I touched on this subject during the Tech Pro Unicorn episode (#114), but had a lot more notes than could be covered - thus in this episode, I take a deeper dive.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/115

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Back in October I had the pleasure of appearing on the Tech Pro Unicorn podcast - the first time that I appears as a guest.

The host, Michael Grace, and I covered a number of topics - such as build vs buy, low-code/ no-code and generally tried to put the world to rights'.

And with Michael's kind permission, I am re-playing the interview in in full.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/114

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

The OWASP Top 10 is the most critical security concerns for web application security as defined by the Open Web Application Security Project®

In the last two episode, I introduce OWASP, their Top 10, why it matters and who it affects - as well as introducing the first seven on the list.

In this episode, I talk about eight to ten of the list.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/113

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

The OWASP Top 10 is the most critical security concerns for web application security as defined by the Open Web Application Security Project®

In the last episode, I introduce OWASP, their Top 10, why it matters and who it affects - as well as introducing the first three on the list.

In this episode, I talk about four to seven of the list.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/112

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

The OWASP Top 10 is the most critical security concerns for web application security as defined by the Open Web Application Security Project®

In this episode, I introduce OWASP, their Top 10, why it matters and who it affects - as well as introducing the first three on the list.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/111

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Continuing my mini-series on security, I discuss Supply Chain Attacks.

No conversation on cyber-security in 2021 would be complete without talking about Supply Chain Attacks.  They are on the increase, with many high profile examples - such as SolarWinds.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/110

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Continuing my mini-series on security, I discuss why you would paid to be hacked.

When you are spending so much time and money putting security in place, it seem counter-intuitive to then pay someone to try and break it.  But without that, how will you know if your defenses work?

I also introduce three ways of validating those defenses - penetration testing, bug bounties and red team/ blue team exercises.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/109

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Continuing my mini-series on security, I introduce Social Engineering.

Social Engineering is a direct attempt to manipulate us into doing something that we otherwise would not.  Its not a new technique, but the modern connected world gives social engineers more tools to work with.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/108

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Continuing my mini-series on security, I introduce Zero Trust.

The traditional approach of security at the border is not longer enough in the modern IT world.  Unlike the good citizens of Troy, you should "never trust, always verify" - you should have Zero Trust.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/107

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Continuing my mini-series on security, I want to follow on from last week's episode, taking a look beyond passwords.

We are rapidly moving to additional forms of proving our identity - be it something we KNOW, something we HAVE or something we ARE - and, possible more importantly, using multiple when doing so (MFA/ 2FA).

-----

Find this episodes show notes at: https://red-folder.com/podcasts/106

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Continuing my mini-series on security, I want to talk about passwords.

Passwords are historically our ubiquitous method of proving our identity.  In the episode I talk about what happens when you lose control of those passwords ... and how prevalent it is.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/105

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

If you're new to thinking about cyber security, in this episode I give you my top 5 recommendations to address in your organisation:

-----

Find this episodes show notes at: https://red-folder.com/podcasts/104

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In this first of a mini-series on security, I look at why cyber security is so critical.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/103

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In this episode, I discuss the Theory of Constraints as introduced in the book The Goal by Eliyahu M. Goldratt.

Modern software development methodologies (Agile, Lean, DevOps) place a heavy focus on the flow of quality work through the development process - and the continual improvement of that flow.

The Theory of Constraints helps us to identify areas of improvement within that flow.

Note: I originally recorded this as one episode, but have subsequently split into two parts during the edit.  Part 1, last week, introduces the ideas of flow and the Theory of Constraints using a simplified manufacturing line example.  Part 2, this episode, applies those thoughts to our traditional software development practices and look at how we may traditional have tried, unsuccessfully, to resolve those constraints.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/102

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In this episode, I discuss the Theory of Constraints as introduced in the book The Goal by Eliyahu M. Goldratt.

Modern software development methodologies (Agile, Lean, DevOps) place a heavy focus on the flow of quality work through the development process - and the continual improvement of that flow.

The Theory of Constraints helps us to identify areas of improvement within that flow.

Note: I originally recorded this as one episode, but have subsequently split into two parts during the edit.  Part 1, this episode, introduces the ideas of flow and the Theory of Constraints using a simplified manufacturing line example.  Part 2, next week, applies those thoughts to our traditional software development practices and look at how we may traditional have tried, unsuccessfully, to resolve those constraints.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/101

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Welcome to the 100th episode of the Better ROI from Software Development podcast.

In this episode, I introduce the second book that I would recommend to any non-technical CxO.

Project to Product by Mik Kersten joins War and Peace and IT by Mark Schwartz on the mandatory reading list for any business leader navigating the modern digital age.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/100

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In this episode, I introduce Value Streams and Value Stream Mapping.

Value Streams and Value Stream Mapping, I believe, are exceptionally useful tools to help us understand what we're doing, how we are doing it, and where we can find sources for improvement.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/99

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Continuing the conversation on Open Source, in this episode I look at common licences.

There are a variety of licences in Open Source - covering legal use and commitments you must abide by.  Like any legal contract, its important that you understand what you're committing too.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/98

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Continuing the conversation on Open Source, in this episode I look at the motivation behind why it exists.

Why would individuals, groups and even organisations give up their time, their work, and their intellectual property for free? 

-----

Find this episodes show notes at: https://red-folder.com/podcasts/97

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Open Source is everywhere - in our software, in our servers, and in the services we use every day - and its here to stay.

In this episode, I give an introduction to what Open Source is, why its incorrect to think of it as free, and why there needs to be governance to protect your organisation.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/96

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Continuing the conversation on Software Application Speed, I look at one of the means of improvement - using a Content Delivery Network (CDN).

In this episode I introduce the Content Delivery Network (CDN); how it works, why you would consider it, and the concerns that may come with it.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/95

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Continuing the conversation on Software Application Speed, I look at one of the means of improvement - Caching.

In this episode I introduce Caching - how prevalent it is within modern computing, why we use it in software development, the pros and cons, the dangers of staleness, and why its an important business decision.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/94

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Continuing the conversation on Software Application Speed, I look at one of the means of improvement - Website Performance Optimisation.

In this episode I introduce Website Performance Optimisation - what it is, why we do it and how to make a start.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/93

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Continuing the conversation on Software Application Speed, I look at one of the means of improvement - User Experience Design.

In this episode I introduce User Experience Design, its subset User Interface Design and how they can help your users get things done easier, with less frustration, and greater efficiency. 

-----

Find this episodes show notes at: https://red-folder.com/podcasts/92

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Speed of our software applications is rarely considered until it becomes a problem.  In this episode I talk about why speed it important in all of our software application - not just the consumer facing ones.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/91

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Following on from last week's introduction into Search Engine Optimisation (SEO), I wanted to provide my advice how to avoid the bad and the ugly of the industry.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/90

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Search Engine Optimization (SEO) is seen as highly desirable for driving traffic to your website.

In this episode I address the myth of SEO being "free traffic" and provide my thoughts on avoiding the bad and the ugly of SEO advice.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/89

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Have you ever come across a website or mobile app that occasionally takes time to reflect changes?

This maybe due to Eventual Consistency - a side-effect of decisions being made by technologists over the CAP Theorem.

Import decisions that the business must be, but often aren't, aware of.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/88

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In episode 83, I had a long chat with Trevor Ewen about how he provides software service to non-technical clients.

If you've not listened to it, it was an excellent interview full of wonderful insights.

So much so that I want to pull a number of topics from that podcast and look at them in more depth.

In this episode, I want to look at the value of meeting agendas.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/87

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In episode 83, I had a long chat with Trevor Ewen about how he provides software service to non-technical clients.

If you've not listened to it, it was an excellent interview full of wonderful insights.

So much so that I want to pull a number of topics from that podcast and look at them in more depth.

In this episode, I want to look at using Video for Rapid Feedback

-----

Find this episodes show notes at: https://red-folder.com/podcasts/86

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In episode 83, I had a long chat with Trevor Ewen about how he provides software service to non-technical clients.

If you've not listened to it, it was an excellent interview full of wonderful insights.

So much so that I want to pull a number of topics from that podcast and look at them in more depth.

In this episode, I want to look at the regular software releases.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/85

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In episode 83, I had a long chat with Trevor Ewen about how he provides software service to non-technical clients.

If you've not listened to it, it was an excellent interview full of wonderful insights.

So much so that I want to pull a number of topics from that podcast and look at them in more depth.

In this episode, I want to look at the SLA

-----

Find this episodes show notes at: https://red-folder.com/podcasts/84

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

In this episode I talk to Trevor Ewen about providing software solutions to the non-technical buyer.

Trevor shares with us his experience on who a non-technical buyer is, why he enjoys working with them, how they differ from the technical buyer, along with advice on how to get the best out of the relationship.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/83

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

This episode is based on LinkedIn poll which asked the question: "Will you be judging jobseekers on whether or not they were furloughed during the pandemic?"

I talk about my own response to the question and explore reasons why a "yes" response may be provided.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/82

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Completing my mini-series on the Scrum Framework, I wanted to talk about the dangers of misunderstanding Scrum.

Scrum is deceptively simple to understand - but difficult to implement.  It can be too easy to misunderstand or mis-implement Scrum; only to be left wondering why it is so recommended.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/81

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Continuing my mini-series on the Scrum Framework, I look at stopping a sprint.

Should you ever stop a sprint?  And if you do, under what circumstances?

-----

Find this episodes show notes at: https://red-folder.com/podcasts/80

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Continuing my mini-series on the Scrum Framework, I look at Problems.

We commonly struggle to raise and discuss Problems in our Organisations; but in this episode, I talk about how Scrum drags those problems into the light and actively encourages us to resolved them.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/79

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Continuing my mini-series on the Scrum Framework, I take a look at the potential warning flag of the team asking for more.

While the team asking for more maybe a good thing, it can also be a sign of a problem in the team - and maybe in the management team.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/78

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Continuing my mini-series on the Scrum Framework, I look at conflict.

We commonly have negative contentions about conflict; but in this episode, I talk about why healthy conflict is so important for our teams to produce the best work.

-----

Find this episodes show notes at: https://red-folder.com/podcasts/77

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Over the last few episodes, I've been talking about Scrum, an agile framework.

In this episode, I want to talk about the Definition of Done. The Definition of Done comes from the Increment description - the Increment being one of the Artifacts produced by Scrum.

The Definition of Done is a way of coordinating the team and the entire organisation on what completed work looks like.

Continuing my mini-series on the Scrum Framework, I look at some of the common problems I see with its adoption.

I discuss problems with transitioning the traditional Project Manager and Business Analysis role into Scrum, and dangers of using pick 'n' mix Scrum.

Following on from last week's primer of the Scrum, I take a look at some of the theories and values behind the Agile Framework.

In this episode I introduce Scrum - an Agile Framework popular within Software Development.

This episode serves as a primer for future episodes - in which I will dig deeper.

Is a bonus the best form of employee motivation?

In this podcast I talk about the dangers of a bonus culture and how to think about it differently.

In this week's episode I talk about meetings as they relate to Software Development - I introduce you to the good, the bad and the ugly.

In this episode I ask if we are making enough time for focused work.

Focused work is critical to us to allow us to solve problems and do the most valuable work.

Do we need to think about the time we are providing for ourselves, our teams, and our organisations?

In this episode I talk about the similarities between our New Year resolutions and major business initiatives; why we set them, why they are attractive and why they often fail.

In this episode, I talk about a recent software project and how I've used many of the processes I have introduced in prior podcasts.

I talk about how I applied them.

And how they fit together to allow me to develop software with confidence - minimizing risk and maximizing the ability to adapt.

Having your team working at 100% utilisation is a good thing for ROI, right?

Software Developers are expensive, surely maximizing their available time is the best way to achieve ROI?

In this episode, I discuss why maximizing time is not as important as value to the end customer - and that focus on 100% utilisation is bad for ROI.

Doing "Big Bang" releases may seem like an effective use of time and people.  They may carry huge prestige and bragging rights for their leadership.  But are they good for ROI?

In this episode, I talk about the dangers they bring - from dangerously high levels of risk to reduced agility to respond to market pressures. 

We think we want to employ the "Rockstar" developer.  We want the superstar.

We actively recruit for it - we even put it into the job adverts.

But is the "Rockstar" good for ROI?

In this episode, I discuss why I believe they are actually the reverse - they are "Bad for ROI".

Gantt Charts are a popular tool for visualising dependencies for complex activities. 

In this episode I discuss why the use of Gantt Charts are bad for ROI in Software Development.

Through September I ran a survey to establish UK Executive's attitudes towards custom Software Development.

Unfortunately the survey failed to obtain enough respondents to be useful, but I want to share my experience.

So in this podcast, I largely cover how the survey was designed, how I promoted it and the lessons learnt.

In this episode I continue to look at professionalism in software development.

I take a look at the ninth oath from the Programmer's Oath by Uncle Bob Martin, introduced in episode #51, to explore further:

"I Promise that, to the best of my ability and judgement: I will never stop learning and improving my craft.".

I also close out this mini-series looking at the Programmer's Oath with some final thoughts.

In this episode I continue to look at professionalism in software development.

I take a look at the eighth oath from the Programmer's Oath by Uncle Bob Martin, introduced in episode #51, to explore further:

"I Promise that, to the best of my ability and judgement: I will produce estimates that are honest both in magnitude and precision. I will not make promises without certainty."

In this episode I continue to look at professionalism in software development.

I take the seventh oath from the Programmer's Oath by Uncle Bob Martin, introduced in episode #51, to explore further:

"I Promise that, to the best of my ability and judgement: I will continuously ensure that others can cover for me, and that I can cover for them."

In this episode I continue to look at professionalism in software development.

I take the second oath from the Programmer's Oath by Uncle Bob Martin, introduced in episode #51, to explore further:

"I Promise that, to the best of my ability and judgement: The code that I produce will always be my best work. I will not knowingly allow code that is defective either in behavior or structure to accumulate."

In this episode I continue to look at professionalism in software development.

I take the first oath from the Programmer's Oath by Uncle Bob Martin, introduced in the last episode, to explore further:

I Promise that, to the best of my ability and judgement: I will not produce harmful code.

In this episode I start to look at professionalism in software development.

Software development doesn't have the same level of professionalism & accountability found in Doctors, Lawyers or Architects.

In this episode I talk about why it is desirable, but unlikely to happen.

And I introduce the Programmers Oath - an attempt to start the conversation 

In this episode I provide a recap of the episodes since the last recap show (episode #25).

This episode is both a recap of the series since episode #25 and a good entry point for new listeners.

During this episode, I'll be summarising the key takeaways - and which episodes to listen to if you want more.

In this episode I want to discuss how dangerous it can be to assume another persons intent purely from their actions.

This is a message I am seeing come up quite a bit lately.

And the more I think about it, the more I see it in everyday business work.

Both in how we perceive our teams and how our teams perceive us.

Over the last few episodes I've talked about learning to improve our individuals, teams and entire organisations to handle change.

In this episode I want to explore why it is so important to that we are learning to build our Software right.

Often the focus of our teams is to build the right thing - which is certainly important. But we also need to think about building the thing right.

In this episode I wanted to continue the conversation on Learning.

In the last few episodes, I talked about;

In this episode I want to looks at how the Software Development team can learn through a number of deliberate practices.

In this episode I wanted to continue the conversation on Learning.

In the last two episodes I talked about why Learning is so important to me personally and Organisational Learning.

In this episode, I want to move onto talking helping Individual Learning.

In this episode I wanted to continue the conversation on Learning.

In my last episode I talked about why Learning is so important to me personally.

In this episode, I want to move onto talking about Organisational Learning.

In this episode I wanted to start talking about learning. Learning is one of the singularly overlooked concepts in running a business. 

I believe every business is a technology business.  For a business to thrive in the modern world it must be able to adapt and change rapidly. 

That ability for a business to adapt and change quickly, comes down to how well the organisation learns

And when I say organisation, I actually mean every part of that organisation - be that an individual right the way through the organisation as a whole. 

So in this episode I'm going to talk abut why learning is so important to me.

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

These are:

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

They are helping Software Teams:

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 access to the tools they need.

In episode 42, I introduced Container Orchestrators and Kubernetes; a technology for running complex containers based solutions; helping us to:

In this episode I will move onto the Serverless technology.

I will also close out this little series on "hot" technologies, by talking about them in the Cloud and the future of these technologies as I foresee it.

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

These are:

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

They are helping Software Teams:

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.

Over the next few episodes I want to introduce a number of technologies from modern Software Delivery.

These are:

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

They are helping Software Teams:

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

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

In this episode I will introduce Containers and the Docker Container format - possibly one of the most useful advancements in recent years in providing repeatable and reliable software distribution.

Over the next few episodes I want to introduce a number of technologies from modern Software Delivery.

These are:

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

They are helping Software Teams:

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

Over the next few episodes I will be giving an overview of what the technology is, how they help with ROI and why your Development Team maybe trying to convince you that they are a good idea.

In this first episode, I want to explain Virtualisation.

A technology that makes those others possible.

I find that quite often business owners and leaders desire a level of predictability that isn't being achieved by their software development teams.

The want reliable costs and timelines for the delivery of software. But the software development teams fail to achieve them.

In this episode I will discuss that, to improve that predictability, you need to ask your teams to do less.

I will also question if that desire for predictability is even an appropriate goal when talking about getting better ROI from your software development.

I'm recording this on Tuesday the 21st May 2020.

At this point, in the UK, we have been under lock down for 4 weeks.

UK rules discourage person to person interactions as much as possible.

While we are able to leave our homes for work, shopping and daily exercise, we are encourage to minimise this as much as possible.

Where they can, businesses are being encouraged to work from home.

In this episode I wanted to talk about helping your staff with phycological safety and motivation.

This episode will mostly focus on supporting those that have suddenly found themselves unexpectedly working from home.

Most of the of the advice however is universally.

I find that many organisations have a myopic over focus on the immediate term.

This over focus drives poor return on investment over the longer term.

In this episode I revisit the analogy of technical debt and how this is related to an over focus on the immediate.

I will also pull from the three horizons example from the book The Alchemy of Growth on a way of avoiding that over focus.

Over the last 10 episodes I've been focused on recruitment.

I had originally planned to finish that mini-series two episodes back; but then I gave you a bonus episode last week on the best hire you can make.

I recently came across a question online, and it fitted so perfectly with the recruitment series that I couldn't resist adding another episode to the mini-series.

In this episode, I look at feedback.

Last week I completed a mini-series of 9 episodes looking at various aspects of recruitment.

As I went through the series I decided I wanted to give you a bonus episode on recruitment.

I wanted to tell you about the best hire you can make.

This episode is the final part of a recruitment mini-series; where I have been focusing on various characteristics that I believe are important in recruitment. And while I think many of these themes are universal, I have, of course, been focusing on software development.

In this episode, I will close out this recruitment mini-series, with a discussion on getting the most from your new employee and keeping them engaged.

This episode is part of a recruitment mini-series; where I am focusing on various characteristics that I believe are important in recruitment.

And while I believe many of these themes are universal, I will, of course, be focusing on software development.

In this episode, I talk about the need to act quickly.

This episode is part of a recruitment mini-series; where I will be focusing on various characteristics that I believe are important in recruitment. And while I believe many of these themes are universal, I will, of course, be focusing on software development.

In this episode, I talk about the actual interview.

Interviewing an individual to gauging future performance is far from a fool-proof means of recruitment.

Unfortunately, it is commonly the only option available to us.

I'll provide advice, from my personal experience, on what works well and a few things that don't.

This episode is part of a recruitment mini-series; where I will be focusing on various characteristics that I believe are important in recruitment. And while I believe many of these themes are universal, I will, of course, be focusing on software development.

In this episode, I talk about working with recruitment agencies.

For better or worse, most software development recruitment is undertaken through agencies. While it is possible, and desirable, to attract potential employees directly, most organisations are not appropriately placed for this.

In this episode, I talk about how I engage with agencies for best effect - as well as touch on some longer-term activities that can help to reduce your reliance on them.

This episode is part of a recruitment mini-series; where I will be focusing on various characteristics that I believe are important in recruitment. And while I believe many of these themes are universal, I will of course be focusing on software development.

In this episode I talk about getting a good understanding of the market before you go into it.

Software Development remuneration has risen steadily for quite some time.

Dependent on the skills and experience your role requires, you may find that previous recruitment may not be an accurate guide to current market rates.

Blindly going into the market with a figure based on historical recruitment can quickly affect you ability to attract the best people.

Also, given that many organisations has a recruitment sign off process, having a eye on the market before getting any rates signed off can avoid recruitment stalling for lack of enough approved funds.

This episode is part of a recruitment mini-series; where I will be focusing on various characteristics that I believe are important in recruitment. And while I believe many of these themes are universal, I will of course be focusing on software development.

In this episode I talk about the importance of defining the role.

This episode is part of a recruitment mini-series; where I will be focusing on various characteristics that I believe are important in recruitment. And while I believe many of these themes are universal, I will of course be focusing on software development.

In this episode I ask the question if traditional recruitment, a permanent employee, is the right thing for you?

While the first inclination maybe to advertise and recruit for a permanent employee, it may not be the right way of getting that extra help.

And with the rise of the gig-economy and a shortage of skilled software developers on the market, sometimes you may have to look at alternatives.

I'll also talk about the alternative options such as using contractors or outsourcing.

This episode is part of a recruitment mini-series; where I will be focusing on various characteristics that I believe are important in recruitment. And while I believe many of these themes are universal, I will of course be focusing on software development.

Somewhat at odds with the title of the mini-series, I first ask the question: "should you be recruiting at all?"

I find many organisations are recruiting when they shouldn't be ... Along with more than a few that should be recruiting and aren't.

I believe our traditional management techniques would have us recruit to solve the wrong types of problems - which can often produce the opposite of the desired outcome.

In this episode, I will be looking at some of the reasons why recruitment may not be solving the right problem.

Over the coming episodes I'm going to take a deep dive into recruitment.

Recruitment is singularly one of the most important roles of management.

Our businesses are run and operated by people.

Yes processes, tools and a hundred other things can help, but ultimately it is the people that make the business.

So over the coming few episodes I want to talk about various characteristics that I believe are important in recruitment. And while I believe many of these themes are universal, I will of course be focusing on software development.

In this episode, I will be summarising the themes that I plan to look at over the coming weeks.

Welcome to the 25th episode.

I decide I wanted to use this episode as both a recap to the series so far and as a good entry point for new listeners.

During this episode, I'll be summarising the key takeaways so far - and which episodes to listen to if you want more.

In last week's episode I introduced the idea of Pair Programming.

A software development practice that has two developers working on the same thing on the same computer. One acting as the driver - the other as a navigator - with regular role reversal.

I talked about, while there is an increase to the developer-hours spent on a problem, the benefits of faster delivery, better quality, knowledge sharing and better team communications soon outweighs the cost.

In this episode, I want to talk about a similar software development practice - but much more amped up - mob programming.

In this weeks episode, I want to introduce the practise of Pair Programming.

At first, Pair Programming can seem completely at odds with achieving returns from your software development investment.

Though this episode, I will look at the common misconceptions and why this is a valuable practice for ROI.

In the last few episodes I've started a mini-series introducing some of the tools and practices that allow for the fast delivery of software and ultimately delivery of value to our customer.

In episode 18, I introduced Source Control, what it was, why your developers will be using it and the value it brings.

Following your development team saved their software code to the Source Control, I then introduced Continuous Integration in episode 19. I described how Continuous Integration allows us to find problems faster - allowing us to address them much more cost effectively and making Software Development much more productive.

In episode 20, I introduced Continuous Delivery. It builds on Continuous Integration and make the releasing of our of software as easy as a button press. Through automation we make our release process a repeatable, reliable, easy, non-event.

And then in the last episode I introduced Continuous Deployment which builds upon Continuous Delivery by removing the manual button press - automating the entire process from developer to customer many times a day.

In this, the final episode of this mini-series, I want to talk about how to handle incomplete work.

In the last few episodes I've started a mini-series introducing some of the tools and practices that allow for the fast delivery of software ... and ultimately delivery of value to our customer.

In episode 18, I introduced Source Control, what it was, why your developers will be using it and the value it brings.

Once your development team has saved their software code to the Source Control, I then introduced Continuous Integration in episode 19. I described how Continuous Integration allowed us to find problems faster - allowing us to address them much more cost effectively and making Software Development much more productive.

Then, in the last episode, I introduced Continuous Delivery. It builds on Continuous Integration and make the releasing of our of software as easy as a button press. Through automation we make our release process a repeatable, reliable, easy, non-event process.

In this episode, I introduce Continuous Deployment.

In the last few episodes I've started a mini-series introducing some of the tools and practices that allow for the fast delivery of software, and ultimately delivery of value to our customer.

In episode 18, I introduced Source Control, what it was, why your developers will be using it and the value it brings.

Once your development team has saved their software code to the Source Control, I then introduced Continuous Integration in the last episode, episode 19. I described how Continuous Integration allowed us to find problems faster - allowing us to address them much more cost effectively and making Software Development much more productive.

In this episode I introduce the next step in the process of getting that software into the hands of your customer - Continuous Delivery

UPDATE: I noticed after initial publish the order of the clips in this episode where very incorrect.  I've now updated - apologies for any confusion.

In last week's episode I started a mini-series introducing some of the tools and practices that allow for the fast delivery of software and ultimately delivery of value to our customer.

In that episode, I introduced Source Control, what it was, why your developers will be using it and the value it brings.

Once your development team has saved their software code to the Source Control, what happens next?

In this episode I introduce Continuous Integration.

In this episode, I want to talk about Source Control.

Source Control is a tool that should be available to your Software Development and at the heart of everything they do.

The aim of this episode is to introduce to you what it is, why they should be using it and ultimately why your are probably spending money on it.

This is part of a mini-series which takes us up to Christmas. I will introduce some of the tools and practices that allow for the fast delivery of software and ultimately delivery of value to our customer.

We start with Source Control in this episode, then move through a number of closely related topics to getting our software investment in front of our customer as quickly as possible.

In this weeks podcast, I wanted to talk about how the size and complexity of a deployable piece of software matters to the ability to deliver value to the customer - and thus ROI on our Software Development.

In this episode I want to introduce the term Technical Debt.

The term Technical debt was coined in 1992 by Ward Cunningham to describe what happens when we fail to adequately maintain what he calls “immature” code.

I find technical debt a great way to express choices we make in prioritising our software development investment.

In last weeks episode I talked about software testing - predominantly around automation to aid in flow of delivering value to your customer.

One point I touched on in the episode is that you cannot, and indeed should not, aim or expect to test everything.

While I can understand an expectation or a desire to test everything 100% - it simply isn't feasible.

Pre-release testing is to gain enough confidence to put it live.

The second half of that is post-release Monitoring.

And it is Monitoring that I want to cover in this episode.

In this episode I want to talk about testing, why it is important for ROI and what types of testing can be done.

Back in episode 10, I briefly mentioned the State of DevOps reports as part of the introduction to DevOps.

In this episode I want to spend more time reviewing the 2019 report

In this short episode, I want to introduce a book that I feel that every executive should read.

I started writing about how to get better ROI from Software Development back in 2016.

This was as a direct aim to educate the executive level on how to interact, with better results, with IT - and predominately software development.

Like many, I've felt that the relationship between IT and the Business had become dysfunctional - with neither party happy with what the other brings to the table. Both parties becoming frustrated with the other.

I've spent many years researching, writing and speaking on how to address this dysfunction.

And I really wish I'd had this book.

... To be honest, I wish I'd written this book.

I'm finding it a great companion piece to my own work and recommend it highly to any listener to this podcast.

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.

Over the last couple of episodes;

I've introduced the concepts of Minimum Viable Product as a way to think about software development to improve your return on investment.

I've then introduced Lean and Agile to provide background and backup for why that Minimum Viable Product mind set works.

And in last weeks, I introduced the Cloud as an enabler to Minimum Viable Product in practice.

In this episode I want to introduce one last term in this set of episodes - DevOps

In the last couple of episodes I've introduced the concepts of Minimum Viable Product, Lean and Agile.

I believe these help us to adjust our mind-set to one more conducive to getting Better ROI from Software Development.

In this episode, I introduce the Cloud; which I believe enables some core practicalities that our new mind-set requires.

In the last couple of episodes I've introduced the concepts of Minimum Viable Product and Lean Software Development.

In this episode I want to introduce Agile.

Along with Minimum Viable Product & Lean Software Development - Agile - along with Cloud & DevOps which I'll pick up in the coming weeks - provides a great introduction on how to get the Better Return from your Software Development Investment.

In the last episode I introduced the Minimum Viable Product.

I personally see Minimum Viable Products being related to Lean Principals.

I'll give you an introduction to Lean in this podcast - and where appropriate, tie it back to the Minimum Viable Product.

In my last podcast I talked about how you should be considering investment in software development as volatile experiments – and that they should be managed as such.

In this podcast, I’ll introduce the concept of Minimal Viable Product (MVP) a tool that can help you manage that volatility in an experimental manner.

 In this episode I want to talk about how to think about investing in software development.

I see too many people thinking that software development is an activity with one outcome – success.

And with that I see funding being made to that software development with the expectation that it will deliver specific anticipated benefits.

I want to take you through why I think that mindset is incorrect and how you should be thinking when investing in software development.

Software Development is complex.

The problems it solves will always have a level of complexity.

In this podcast I talk about why.

Projects are not the best way to get great return on your software development.
And in this podcast I'll tell you why.

In the last podcast I told you that focusing on 100% utilization is the wrong thing for return on investment.
But how can that be?
Are we not taught that utilization means productivity?
Are we not encourage to stretch our staff?
To get the most out of the staff salary?
Are we not even told its a good thing to sweat the asset? 

Why is it difficult to get great return on your software development investment?

Why is it that software development isn't keeping pace with your business?

You’ve tried to resolve it yourself; you’ve set targets, you’ve encouraged, you’ve cajoled, you’ve been driven half insane with techno-babble – but your tried and tested management techniques aren’t working – if anything they are producing negative effects.

So why is it so difficult?

Episode 0 - a brief summary of why I am creating this podcast series.