Better ROI from Software Development

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 ste...

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 m...

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...

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 a...

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 sha...

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 in...

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...

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 in...

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,...

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 so...

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 conf...

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...

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...

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 epis...

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...

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.