article thumbnail

Cone of Uncertainty Bibliography

Herding Cats

It can be the needed performance of a measure - Effectiveness, Performance, Key Performance Parameter, or a Technical Performance Measures. The specifics of the Technical Performance Measures applied to inform Physical Percent Complete and the Cone of Uncertainty around the TPM are shown here.

article thumbnail

Biases in Project Management and How to Remove Them

Herding Cats

What are the measures of physical percent complete needed to inform the decision makers of progress to plan in order to take corrective or preventive actions to stay on plan? Software engineering economics is about making decisions related to software engineering in a business context. A final Thought .

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Biases in Project Management and How to Remove Them

Herding Cats

What are the measures of physical percent complete needed to inform the decision makers of progress to plan in order to take corrective or preventive actions to stay on plan? Software engineering economics is about making decisions related to software engineering in a business context. A final Thought .

article thumbnail

Risk Management is How Adults Manage Projects

Herding Cats

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. Complete Guide to the Basics of Project Risk Management: Improve Your Chances for Success, Dmitry Nizhebetskiy, Project Management Basics, 2017. It just closed the loop faster.

article thumbnail

Microeconomics and Risk Management in Decision Making for Software Development

Herding Cats

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.