Definition Estimate Governance Software Engineering 
Herding Cats
AUGUST 27, 2017
There's a recent post titled Four Fallacious Reasons to Estimate. It lists the usual suspects for why those spending the money think they don't have to estimate how much they plan to spend when they'll be done producing the value they've been assigned to produce for that expenditure. Let's look at each one in more detail.
Herding Cats
MAY 8, 2016
ways to make decisions with No Estimates. can we make a decision in the presence of Uncertainty without making an estimate of the impact or outcome of that decision? What would be the evidence that we could make decisions in the presence of uncertanty without estimating the impacts and outcomes of those decisions? . Start here.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
OCTOBER 5, 2018
The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ? This variation can be explained by the fact that initial concepts do not describe the final software system accurate enough.
Herding Cats
FEBRUARY 9, 2018
I've seen estimates abused by bad managers, so let's NOT estimate and that will fix the behavior of Bad Managers." While the human behaviors are real and observable, conjecturing that decisions can be made in the presence of uncertainty without estimating the outcome of those decisions, there is no principle to support that conjecture.
MPUG
MAY 14, 2021
Having spent half my life in the commercial space and half in the government space, the questions are always there. And then I came back and started using it in larger government programs. I got junior software engineers, software engineers, senior software engineers. Is it Fletcher?
Herding Cats
MAY 10, 2019
requires making estimates) ? This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996.
Herding Cats
MAY 11, 2019
requires making estimates) ? Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996.
Expert insights. Personalized for you.
46 
Let's personalize your content