Herding Cats

FEBRUARY 9, 2018

Drawing Unsupported Conclusions from Incomplete and Inconclusive Data, it is not only natural but also laudable, to seek evidence that confirms something that we hold to be true. In the project domain, an estimate is a calculated approximation of some desired measurement. Let's look at what an estimate is. Then as we say in our domain.

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

Herding Cats

JUNE 7, 2018

That would mine all the User Stories are standalone pieces of software. That means the system architecture, the process flow, the data flow architecture components all how NO dependencies on other. Actual software process flows contain loops. Enterprise Software process and data flows always contain loops.

Underperforming Technical Team 32

Underperforming Technical Team SCRUM Software Engineering Risk Management 32

Herding Cats

AUGUST 1, 2018

Since there has been some confusion around the CoU in the past, about whether it can be reduced, whether there is credible data showing it is valid or not, whether those claiming it can't be reduced have any Root Cause Analysis as to why it wasn;t reduced, I thought I'd included the references we're using. So here's the outcome.

2012 29

2012 2007 2010 2006 29

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. This is the paradigm of the Cone of Uncertainty - it's a planned development compliance engineering tool, not an after the fact data collection tool. The Cone is NOT the result of the project's past performance. Prentice-Hall, 1981. When you hear. .

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JUNE 9, 2018

System One is an unconscious system that is automatic, fast, efficient at using the data or experience it already knows. The business draws upon microeconomic data to make a variety of critical choices – any one of which could mean the success or failure of their enterprise. System One - automatic. System Two - deliberative .

Transportation 28

Transportation Software Engineering Finance 2011 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). The Cone is NOT the result of the project's past performance.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

JANUARY 14, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates or any other project attribute (in this post, cost, schedule, and technical performance parameters). There can be cost and schedule performance measures as well.

Technical Review 28

Technical Review Software Review Underperforming Technical Team Estimate 28

Herding Cats

MARCH 4, 2017

This is an immutable principle that impacts planning, execution, performance measures, decision making, risk, budgeting, and overall business and technical management of the project and the business funding the project no matter the domain, context, technology or any methods. Bauman, Industrial & Engineering Chemistry , April 1958.

2010 28

2010 2007 Estimate Aerospace 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. This is the paradigm of the Cone of Uncertainty - it's a planned development compliance engineering tool, not an after the fact data collection tool. The Cone is NOT the result of the project's past performance. Prentice-Hall, 1981. When you hear. .

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JUNE 7, 2018

That would mine all the User Stories are standalone pieces of software. That means the system architecture, the process flow, the data flow architecture components all how NO dependencies on other. Actual software process flows contain loops. Enterprise Software process and data flows always contain loops.

Underperforming Technical Team 28

Underperforming Technical Team SCRUM Software Engineering Risk Management 28