Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). The BLUE bars are the probabilistic ranges of the current estimate date.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 23, 2019

In all engineering worlds, from software engineering to bending metal for money, there is really nothing new under the sun. Rarely are software engineers working on science experiments. maybe a read of the resources of Estimating Agile Software Development may help. Almost impossible?

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

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. There are databases for Function Points .

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). Estimates are needed but are subject to large level of uncertainty.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

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. Stewart, ACTEX Publications, 2006. No References?

Risk Management 43

Risk Management Risk 2003 2011 43

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

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. So when you hear we can't estimate you'll know better.

Estimate 64

Estimate 2006 2005 2012 64

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. México, 1 al 3 de Febrero de 2006. Pich, Working Paper, 21/2006, Cambridge University, Judge Business School. “A

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

requires making estimates) ? México, 1 al 3 de Febrero de 2006. 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.

Risk Management 35

Risk Management Risk Technical Review 2002 35