Herding Cats

MAY 10, 2019

Risk Management is essential for development and production programs. Risk issues that can be identified early in the program, which will potentially impact the program later, termed Known Unknowns and can be alleviated with good risk management. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003.

Risk Management 38

Risk Management Risk Technical Review 2002 38

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

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MARCH 11, 2017

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. The risk is created when we have not accounted for this natural variances in our management plan for the project. An aleatory risk is expressed as a relation to a value.

2003 46

2003 2014 2015 2011 46

Herding Cats

OCTOBER 5, 2018

"A Quick Estimation Approach to Software Cost Estimation," Leckraj Nagowah, Hajrah BibiBenazir, and Bachun, African Conference on Software Engineering and Applied Computing , . "A A Probabilistic Method for Predicting Software Code Growth," Michael Ross, Journal of Cost Analysis and Parametrics 4:127-147, 2011. "10

2012 48

2012 2007 2011 2010 48

Herding Cats

MAY 7, 2019

Monte Carlo Schedule Risk Analysis,” Intaver Institute, Inc. Effort Estimation of Use Cases for Incremental Large-Scale Software Development,” Pareastoo Mohagheghi, Bente Anda, and Reidat Conradi, Proceedings of the 27th international conference on Software engineering. 61, September 2004. Chakraborty and K.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ‒ Steve McConnell. Planning and Executing Time-Bound Projects,” Eduardo Miranda, IEEE Computer , March 2002, pp. 5 Oct 1990, Page 21.

Estimate 64

Estimate 2006 2005 2013 64

Leading Agile

AUGUST 20, 2018

But there’s a risk that people will get excited about automation and get ahead of themselves. Including appropriate tooling in the automated CI process covers most of the remaining risks in this area. No one can check for unknown issues, even using manual methods, so no risk is introduced by automating this step.

Software Review 78

Software Review Software Technical Review Development Team Review 78