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

Scrum.org

MARCH 11, 2020

Source : Scrum Guide 2017. . Check out the complete Scrum Guide 2017 list on the Development Team by downloading the Scrum Guide Reordered.). Finally, the term Development Team seems to limit the role to technical people, for example, software engineers. Too much estimating: The Development Team estimates sub-tasks.

Development Team Review 220

Development Team Review Underperforming Technical Team Software Review Technical Review 220

Herding Cats

SEPTEMBER 22, 2017

The #NoEstimates Manifesto - Actually restates Best Practice for estimating and making decisions with those estimates. . Deterministic estimates are point estimates and Point estimates without a Variance are of little value in the presence of uncertainty. Estimates make use of a broad range of models and data .

Estimate 50

Estimate 2017 Governance Government 50

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

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

DECEMBER 8, 2017

This can be the confidence in the estimate for any variable. But is can be ANY variance for the program, including confidence in the estimates of future performance - cost, schedule, or technical performance. This usually results in a project's actual costs far outrunning the optimistic estimates and creating a large overrun.

Performance Measurement 35

Performance Measurement Technical Review 2017 2008 35

Herding Cats

MAY 11, 2019

requires making estimates) ? 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.

Risk Management 35

Risk Management Risk Technical Review 2002 35

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. I'm not expecting anyone to read all these books.

Risk Management 43

Risk Management Risk 2003 2011 43