Herding Cats

MAY 7, 2019

The reason for this resource page is the lack of understanding of how to estimate, the urban myths about software estimating, and the fallacies that estimating is not needed, when developing software, in the presence of uncertainty, when spending other peoples money. Monte Carlo Schedule Risk Analysis,” Intaver Institute, Inc.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

Estimating is a learned skill, used for any purpose from every-day life to management of projects. Believing is Seeing: Confirmation Bias Studies in Software Engineering, “Magne Jørgensen and Efi Papatheocharous, 41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA). Better Sure than Safe?

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

OCTOBER 24, 2018

But before going further, let's establish the definitions we need to understand and apply Root Cause Analysis needed to discover the corrective and preventive actions to increase the probability of project success - especially Software Project Success. Australian Government, Department of Defence, Defence Material Organization, Version 2.0

2014 45

2014 Aerospace 2011 2013 45

Herding Cats

MARCH 11, 2017

Uncertainty is related to three aspects of the management of projects: The external world - the activities of the project itself. The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. One starting point is the value at risk.

2003 46

2003 2014 2015 2011 46

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 ? The program management processes should seek to reduce uncertainty in the variable of the project. IT Risk Management.

2012 48

2012 2007 2011 2010 48

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). Prentice-Hall, 1981. Here's a simple definition of the Cone of Uncertainty: .

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). Prentice-Hall, 1981. Here's a simple definition of the Cone of Uncertainty: .

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). This is done by active risk management, through probabalistic decision-making.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

FEBRUARY 23, 2016

This list starts with the earliest posts, beginning in 2009. . It has many good concepts, one serious math error, and connects well with how we manage and work billion dollar programs. Software Estimating - Pawel commented on the previous post about the difficulties in making estimates of duration and cost of software.

Estimate 39

Estimate Risk Management Finance Software Developers 39