2003 Estimate Risk Software Engineering 
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. requires making estimates) ? Risk Management Papers. “A
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) ? De Meyer, C. “A
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.
Herding Cats
SEPTEMBER 27, 2017
"Iterative and Incremental Development: A Brief History," Craig Larman and Victor Basili, IEEE Computer , June 2003. Managing the Development of Large-Scale Software: Concepts and Techniques," Winston Royce, Proceedings, Wescon, August 1970. IT Risk Management. Why Guessing is not Estimating and Estimating is not Guessing.
Herding Cats
FEBRUARY 9, 2018
I've seen estimates abused by bad managers, so let's NOT estimate and that will fix the behavior of Bad Managers." While the human behaviors are real and observable, conjecturing that decisions can be made in the presence of uncertainty without estimating the outcome of those decisions, there is no principle to support that conjecture.
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. . This is good, but it doesn't reduce risk.
Herding Cats
MAY 7, 2019
This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. Performance Evaluation of non?Markovian
Expert insights. Personalized for you.
38 
Let's personalize your content