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

MARCH 4, 2017

Let's say you're the project or program manager of a large complex system. We cannot escape these two uncertainties - reducible and irreducible - and must learn how to manage in the presence of these uncertainties. Are we being effective with our budget - that is are we earning our budget. Abstracted from [3].

2010 28

2010 2007 Estimate Aerospace 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

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. Uncertainty creates Risk. Risk management requires active reduction of risk. This extended post covers.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Herding Cats

APRIL 4, 2019

In a recent exchange in social media, it was clear the notion of risk and the sources of risk, the consequences or risks and managing in the presence of risk was in very unclear, when it was conjectured , we can simply slice the work into small bits and REDUCE risk. . Software Risk Management , Barry W.

Risk Management 43

Risk Management Risk 2003 2011 43

Epicflow Blog

JANUARY 12, 2021

The need for specialists in the field of project management is growing annually because businesses are getting bigger and most companies are becoming project-based. According to the research by Project Management Institute , 87.7 million project management-oriented experts will be required by 2027 by different companies worldwide.

PMO 82

PMO 2007 Controlling Construction 82

Herding Cats

APRIL 16, 2019

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Management Processes (#MP). Project Performance Management (#PPM). Agile Project Management (#APM). Risk Management (#RM). Cost, Schedule, and Technical Performance Management (#CSTPM). Management Processes.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

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

MPUG

OCTOBER 9, 2019

Kyle: Hello everyone and welcome to today’s MPUG training series, part one, Understanding and Incorporating Agile Project Management. He’s an accomplished speaker, consultant and educator supporting the project management community for over 25 years. But it is clearly not limited to just software.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

MPUG

OCTOBER 24, 2019

He’s an accomplished speaker, consultant and educator, supporting the project management community for over 25 years. But at the same time, there’s an important step, program managers, portfolio managers, people who are working on multiple projects may have to see the big picture. They’re iterative.

Agile 40

Agile Technical Review Software Review Underperforming Technical Team 40