Herding Cats

NOVEMBER 7, 2016

Estimating is a learned skill, used for any purpose from every-day life to management of projects. When I left for the airport this morning to catch my flight to a customer site I estimated, given the conditions, how much time I need to get to my favorite parking spot at DIA. Google will find these when there is no URL provided.

Estimate 64

Estimate 2006 2005 2013 64

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

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

MAY 10, 2019

Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. requires making estimates) ? Kadane, and Anthony O’Hagan, Carnegie Mellon University, Statistics & Data Science, January 5, 2005. Estimation of Long?Term

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

Let's start with a critical understanding of the purpose of managing risk on software development projects. Information about key project cost, (technical) performance and schedule attributes is often uncertain or unknown until late in the program. requires making estimates) ? Estimation of Long?Term

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

FEBRUARY 9, 2019

40 - Estimation is a Problematic Practice of Companies Doing Dangerous Things. A #Noestimates advocate makes the claim that having a ±10% accuracy for estimates of cost and duration is a dangerous thing. Define the probabilistic ranges of the work in a single point estimate manner. Is this normal?

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Herding Cats

APRIL 16, 2019

, Cost and schedule growth for federal programs is created by unrealistic technical performance expectations, unrealistic cost and schedule estimates, inadequate risk assessments, unanticipated technical issues, and poorly performed and ineffective risk management, all contributing to program technical and programmatic shortfalls.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42