Better ROI from Software Development

This episode is a wrap-up for a mini-series looking at estimation in software development - recapping the guidelines I provided in Episode 189 and providing some additional tips that didn't have a home elsewhere in the series. ----- Find this episodes show notes at: https://red-folder.com/podcasts/205 Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podca...

In this episode, the penultimate episode in the Software Estimation mini-series, I want to discuss how Software Estimation works in terms of professionalism - and in many cases, surprisingly, the professional response is not to provide an estimate. ----- Find this episodes show notes at: https://red-folder.com/podcasts/204 Have an idea for an episode topic, or want to see what is coming up: https:...

This episode is part of a wider mini-series looking at Estimation in Software Development. In this episode, I ask the question, is AI the answer? Following on from the episodes on Qualitative and Quantitative approaches, it's easy to see there are pros and cons to individual practices. And realistically, it feels like you will need a blend of various approaches to create truly valuable estimates....

This episode is part of a wider mini-series looking at Estimation in Software Development. In the last couple of episodes, I've looked at a number of methods that fall under the Qualitative approach to software estimation. Qualitative estimation is predominantly based on expert judgment, some think based on subjective thought process. In this week's episode, I want to move on to discuss some Quant...

This episode is part of a wider mini-series looking at Estimation in Software Development. In last week's episode, I looked at a number of methods that fall under the Qualitative approach to software estimation. Qualitative estimation is predominantly based on expert judgment, something based on subjective thought process. In this episode I wanted to take a specific look at another method I person...

This episode is part of a wider mini-series looking at Estimation in Software Development. In last week's episode, I introduced two approaches to software estimation, Qualitative and Quantitative estimation. Qualitative estimation is predominantly based on expert judgment, something based on subjective thought process. Whereas Quantitative is based on something we count or calculate. A use of stat...

This episode is part of a wider mini-series looking at Estimation in Software Development. In this episode, I wanted to look at practical methods to help develop the team's estimation skills. We cannot expect valuable estimation without investment. It's like any skill, it has to be practiced and refined to obtain a good level of proficiency. So in this episode, I want to take a look at two approac...

This episode is part of a wider mini-series looking at Estimation in Software Development. In this episode, I wanted to highlight the emotional baggage that you developers may associate with estimation, and through no fault of your own, will carry that baggage into future estimation work. In the episode, I look at the psychological scarring left behind from decades of using estimates as punitive t...

This episode is part of a wider mini-series looking at Estimation in Software Development. In this episode, I wanted to look at the impact that dependencies have on software estimation. This episode was inspired by a blog post on scrum.org entitled "Eliminate Dependencies, Don't Manage Them", which I read while preparing this series. In brief, the article talks about how you're better off eliminat...

This episode is part of a wider mini-series looking at Estimation in Software Development. In this episode, I want to encourage you to mentally separate estimation and planning. They are often conflated, which leads to confusion, distrust and dysfunctional behavior. An estimate is generally part of a plan, and a plan can be the outcome of the act of planning. Software development can't be delivere...

This episode is part of a wider mini-series looking at Estimation in Software Development. In last week's episode, I asked you to think about what the term "estimate" means to you, your team and your organisation. In the episode I talked about different definitions that could easily be conflated - the amount of effort, a target, and a commitment. In this week's episode I want to continue the discu...

This episode is part of a wider mini-series looking at Estimation in Software Development. In this week's episode, I want to discuss what the term "estimate" may mean to you and the colleagues that you work with. The term 'estimate' is often used interchangeably to mean the effort required, the target completion date, or even a commitment to complete the work by a specific date. Often the meaning...

This episode is part of a wider mini-series looking at Estimation in Software Development. In this episode I want to take a deeper dive into the cost of achieving that - what is the correct cost for the perceived value of the estimate to you and your organisation. This episode continue on from 190 where I asked "Don't invest in estimates unless there are clear demonstrable value in having them" --...

This episode is part of a wider mini-series looking at Estimation in Software Development. In the last episode, I talk about the short hand of a "valuable estimate" -  an estimate that is desirable for the organisation asking for it. While what constitutes "valuable" will differ from organisations to organisation, team to team, and maybe even piece of work to piece of work, I feel that it will mos...

This episode is part of a wider mini-series looking at Estimation in Software Development. So for this episode I want to introduce the idea of a "valuable estimate" and what that may mean for you. As I go through this series I will use the term "valuable estimate" as a short hand for some value that is desirable by the organisation asking for it. This may seem a little vague … and to be honest, by...

I started the mini-series in episode 189 by providing the following guidelines: Don't invest in estimates unless there are clear demonstrable value in having them Agree what a "valuable" estimate looks like - this will likely be a desirable level of accuracy and precision for an estimate Provide the team with training & time to develop their estimation skills Collect data on points 1-3 and reg...

Back in January 2023, in episode  #160, "Revisiting Software Development Estimation," I made the commitment to revisit and potentially revise my views on software development estimation. While I acknowledged the desirability of estimations for reasons like cost, risk, and planning, the episode recognized that these desires don't always make estimations attainable or accurate, particularly in compl...

Following on from the last two episodes that look at the dysfunctional and unexpected results that can from the seemly well intentioned call for "more planning", this week's episode takes a look at a similar paradox - the call for "more developers". We look at why "more developers" does not generally equal "greater output" - the unexpected operational ov...

In this episode, the second of two, I conclude the exploration of the dysfunctions and unexpected results that can occur from the seeming well intentioned call for "more planning". In last week's episode, I looking at the historical context of why the request for "more planning", and explored the high cost and dysfunctions that can arise from over-planning. And this week&#3...

In this episode, the first of two, I start to explore the dysfunctions and unexpected results that can occur from the seeming well intentioned call for "more planning". In this episode, I will start by looking at the historical context of why the request for "more planning", and an exploration of the high cost and dysfunctions that can arise from over-planning. And in next week...

In the last episode I the dysfunctions and unexpected results of a "feature factory" within Software Development. This week I look at what happens if the pendulum swings too far the other way - where an overemphasis on perfection leads again to dysfunction and unexpected results. ----- Find this episodes show notes at: https://red-folder.com/podcasts/185 Have an idea for an episode topic...

In the fast-paced world of software development, the “feature factory” model, with its promise of rapid growth and high ROI, can easily captivate businesses. This episode takes a dive into why the the feature factory is so alluring - and why beneath the allure, lies a multitude of hidden dysfunctions and potential for long-term damage. ----- Find this episodes show notes at: https://red-folder.com...

In this episode I look at another practice that can be bad for ROI - a practice that may commonly be considered good or common practice, but is actually causing dysfunctional, and unexpected, results. In this episode I want to explore the dangers of performance measurements in modern software development - how, while they are a useful and powerful tool, they are so commonly used incorrectly to dis...

We all know that a heft bonus improves productivity. Its a management stable - dangle the carrot and good results just roll it. But is that really true? In this episode, I look at the negative consequences of using bonuses for motivation - once again, leaning heavily on the work of Daniel Pink and his book "Drive" to explore the idea of extrinsic and intrinsic motivators - and what works...

Occasionally I record an episode exploring something that may commonly be considered good, or common practice, but is actually causing dysfunctional, and unexpected, results in modern software development - and thus would be bad for ROI. This week I look at the RAG (Red Amber Green) status reporting and its impact on modern software development. ----- Find this episodes show notes at: https://red-...