Skip to main content

Why is success measured by estimates?

http://blog.cutter.com/2008/11/04/software-estimation-a-tough-beast-to-control/

This article was posted under a quoted title "“a tough beast to control”. I agree with the title but 100% disagree with the survey. Meeting estimates IS all about "control." If you want to meet an estimate you have to give the customer exactly what you agreed and control (Deny) any changes they want.

Here is an analogy which is similar to one Robert Martin used. You go to your doctor and they say you have a tumor in your liver.(arbitrary organ). They schedule the surgery and open you up. While removing the tumor they find another one in your pancreas .(arbitrary organ).
Using estimates as a measure of success would encourage the doctor to sow you back up, let you heal and then say, we did not estimate the pancreas tumor so we could not remove it because we would exceeded our estimate by 10%. Also, I will not get my bonus if we do that and you might not pay for it.

The doctor is more successful by removing the additional tumor. It cost less to do it while the patient is already under and is open at the table. He is also more successful because he helped the patient more than originally planned.

I am not saying estimates are not important. They are important to create a schedule but success should be driven by the value to the customer not random numbers.

As leaders we must work to set customer expectations regarding success. I would like the survey to review how well the customer expectations were defined and managed.

Comments

Popular posts from this blog

2020 State of DevSecOps by Accurics

 This is an excellent report for all IT Pros and Engineers.   Highlights: Storage is most impacted solution Open security groups or network configuration Secrets are not so secret Unused resources are not secure. Take a look at these.  Look again.  These are not highly skilled problems.  They just need guidelines and proactive management.  The article uses policy as code as a solution for many of the problems.  I will drill into each of these more in the future.  I wanted to get the awareness out first and then, come back to solutions.  

Learn Anti-Leadership from Basecamp

 There are many different articles out there and Twitter comments about the Basecamp drama.  I am not going to post any here because it might seem biased depending on the article.  Google them yourself.  In short, Basecamp made a policy to not allow political discussions at work.  Coinbase did this previously too and applauded Basecamp for it.   Apparently, for years there has been a list of funny customer names at floating around Basecamp.  This list or even the knowledge that Basecamp had a list, was disturbing to some employees.  Also, some employees tried to start a Diversity and Inclusion practice.  Despite how much the founders of Basecamp promoted DI, they didn't feel they were being taken serious.  They felt the company was only about the founders and not about employees.    If this isn't enough, the founders debated and even called out employees for their comments regarding the topics, publicly.  This is my s...

Cloud Ops: The New IT for the Cloud Era

Over the past few months of interviewing and researching dozens of companies—particularly small to mid-sized SaaS businesses—one pattern keeps emerging: the desire to stand up a Cloud Operations (Cloud Ops) organization. It makes sense on the surface. Cloud is now the infrastructure of choice, so naturally, someone needs to “own” it. But what’s unfolding in practice often misses the mark. Many companies are attempting to solve growing cloud complexity by taking all their DevOps, SRE, and platform engineering talent and consolidating them into a Cloud Ops team. The idea? Share them across product teams so no one gets overwhelmed. If that sounds familiar, it should. It’s the same centralization tactic used by traditional IT for decades. And it's creating the same problems. When Cloud Ops Becomes Old IT in Disguise Here’s the playbook we’re seeing: Move DevOps, SRE, and Ops into a central Cloud Ops team. Let them handle infrastructure, CI/CD, monitoring, and cloud securit...