Herding Cats

MAY 10, 2019

requires making estimates) ? This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. IEEE Transactions on Software Engineering , Vol. 920, November 2004. reducible and irreducible ?

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MARCH 17, 2019

Here are my collected works, presentations, briefings, journal papers, articles, white papers, and essays, used to increase the Probability of Project Success (PoPS) I've developed and applied over my career in the software-intensive system of systems domain. An Introduction to IMP/IMS , 17 Oct 2004. Basis of Estimate Process.

2003 54

2003 2011 2008 Performance Measurement 54

Herding Cats

MAY 11, 2019

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. requires making estimates) ? 920, November 2004.

Risk Management 35

Risk Management Risk Technical Review 2002 35

The IIL Blog

APRIL 27, 2018

First let’s keep the concept of ROI basic, which is in this context: Applying this equation to a real-life example, if the cost for rolling out a SMILE activity = $10,000 and the estimated value of the program is $100,000 (considering quantitative and/or qualitative factors such as listed above): This number is not exaggerated.

Software Review 121

Software Review 2004 2012 PMI 121

Herding Cats

APRIL 4, 2019

Research shows that for projects, especially software projects Aleatory uncertainty is the predominant source of risk. So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. Software Risk Management , Barry W.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

JUNE 24, 2016

This graph is from old 2004 numbers. Many times the books uses 12, 16, even 25 year old reports as the basis of the suggestion that Not Estimating fixes the problems in the reports. If the project was over budget, was the needed budget estimate correct? The No Estimates book does a poor job of keeping the references straight.

Software Review 44

Software Review 2004 Estimate Budget 44

Herding Cats

MARCH 11, 2017

What happens if you shift focus from "accurate estimation" to "reliably shipping by a date"? . If your project has no uncertainty, there is no need to estimate. The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty.

2003 46

2003 2014 2015 2011 46

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Agile Software Development (#ASD). Enterprise IT and Embedded Systems (#EIT).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

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. Of late, Cone of Uncertainty has become the mantra of No Estimates advocates claiming that data is needed BEFORE the Cone is of any use.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35