Remove 2012 Remove Closing Remove Software Development Remove Software Engineering
article thumbnail

Risk Management Resources

Herding Cats

Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996. De Meyer, C. Loch, and M.

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

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. IEEE Transactions on Software Engineering , Vol.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Misunderstanding Making Decisions in the Presence of Uncertainty

Herding Cats

Accuracy - how close is the estimate to the actual value? So in the end, if we are to make a decision in the presence of uncertainty, we MUST make estimates to develop a reliable shipping date while producing an accurate and precise estimate of the cost, schedule, and technical performance of the product shipped on that date.

2003 46
article thumbnail

Misinterpretations of the Cone of Uncertainty

Herding Cats

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. Closed Loop Stochastic Adaptive control in the presence of Evolving Uncertainty. Thesis, University of Southern California, August 2012.

article thumbnail

Managing in Presence of Uncertainty

Herding Cats

Software development project schedule estimation has long been a difficult problem. Instead, it suggests the Cone of Uncertainty is not the proper model for software estimating, with no evidence other than anecdotal examples from observed projects. This approach ignores the core principle of closed loop control.

2010 28
article thumbnail

Assume a Spherical Cow

Leading Agile

” I was reminded of the old joke by a recent article by John Regehr, Professor of Computer Science at the University of Utah, entitled “Closing the Loop: The Importance of External Engagement in Computer Science Research.” In 2012, I wrote a blog post entitled “Delivering provably-correct code.”

article thumbnail

Risk Management is How Adults Manage Projects

Herding Cats

It just closed the loop faster. 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. Foundations of Risk Management, 2nd Edition, Terje Aven, John Wiley & Sons, 2012. This is good, but it doesn't reduce risk.