Herding Cats

JUNE 19, 2017

The Cone of Uncertainty is a framing assumption used to model the needed reduction in some parameter of interest in domains ranging from software development to hurricane forecasting. The Cone of Uncertainty as a Technical Performance Measure. The Cone of Uncertainty as a Technical Performance Measure.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

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 Risk Management 28

Herding Cats

JUNE 4, 2016

Technical Performance Measures. Software Engineering is a Verb. Related articles. Assessing Value Produced By Investments. Who's Budget is it Anyway? Architecture -Center ERP Systems in the Manufacturing Domain. IT Risk Management. Why Guessing is not Estimating and Estimating is not Guessing. Deadlines Always Matter.

Software Engineering 28

Software Engineering Performance Measurement Finance Manufacturing 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.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

AUGUST 27, 2017

That's why I strive to create an environment with mutual trust between the engineers and the different stakeholders. We engineers should always keep in mind that software development is usually one part of many others inside the company. Root Cause: Productivity is the efficacy of the investment of time, talent, and money.

Estimate 46

Estimate Software Review Underperforming Technical Team Technical Review 46

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

FEBRUARY 9, 2018

In the project domain, an estimate is a calculated approximation of some desired measurement. This is usually a cost, a completion date, a performance measure used in a closed loop control system to keep the project GREEN while delivering the needed Capabilities to produce the Value for the customer at the needed time for the needed cost.

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

Herding Cats

APRIL 4, 2019

All making things smaller dos is show that you're late, over budget, and what you're building (Technical Performance Measures) doesn't work faster. Probabilistic Risk Assessment and Management for Engineers and Scientist 2nd Edition , Ernest J. This is good, but it doesn't reduce risk. It just closed the loop faster.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

MARCH 11, 2018

If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Software engineering economics." IEEE Transactions of Software Engineering, 1 (1984): 4-21.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Herding Cats

JUNE 7, 2018

This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's . There is no way out of this for any non-trivial software development project. Allen School of Computer Science Software Engineering Course . This information comes from the Paul G.

Underperforming Technical Team 32

Underperforming Technical Team SCRUM Software Engineering Risk Management 32

Herding Cats

JUNE 7, 2018

This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's . There is no way out of this for any non-trivial software development project. Allen School of Computer Science Software Engineering Course . This information comes from the Paul G.

Underperforming Technical Team 28

Underperforming Technical Team SCRUM Software Engineering Risk Management 28