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. “A 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

Managment Processes. Software for Your Mind: Patterns and Anti-Patterns for Creating and Maintaining a Shared Vision. Making the Impossible Possible: Applying Heliotropic Abundance for creating Program and Project Management Processes. 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 122

Software Review 2004 2012 PMI 122

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. Here's a few comments on the Standish reporting process. If the project was over budget, was the needed budget estimate correct?

Software Review 44

Software Review 2004 Estimate Budget 44

Herding Cats

APRIL 4, 2019

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. But when some statement is made about risk, estimating, performance modeling, or the like - always ask for references. Paul Chavas, Elsevier Academic Press, 2004.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

MARCH 11, 2017

What happens if you shift focus from "accurate estimation" to "reliably shipping by a date"? . This quote demonstrates a lack of understanding of making decisions in the presence of uncertainty and the processes and events that create uncertainty. There is naturally occurring variability from uncontrolled processes.

2003 46

2003 2014 2015 2011 46

Herding Cats

APRIL 16, 2019

Management Processes (#MP). Agile Software Development (#ASD). While many of the presentations have similar titles, the content is focused on a specific set of processes and practices, while the principles are the same, since they are Immutable. . Management Processes. Project Performance Management (#PPM).

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