Better ROI from Software Development

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

During September, I'm running a short survey to understand UK Executive's attitudes to custom software development.  Please take the time and have your say at: https://software-survey.red-folder.com/

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

I take the sixth 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 do all that I can to keep the productivity of myself, and others, as high as possible. I will do nothing that decreases that productivity."

During September, I'm running a short survey to understand UK Executive's attitudes to custom software development.  Please take the time and have your say at: https://software-survey.red-folder.com/

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

I take the fifth 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 fearlessly and relentlessly improve my creations at every opportunity. I will never degrade them."