Herding Cats

DECEMBER 16, 2017

Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991. Estimating Software Costs: Bringing Realism to Estimating , Second Edition, Capers Jones, 2007. Software Cost Estimation with COCOMO II , Barry Boehm, et. Agile Estimating and Planning , Mike Cohn, Prentice Hall, 2006. Prentice Hall, 2000.

Software Developers 46

Software Developers Software Development Estimate 2006 46

Herding Cats

NOVEMBER 7, 2016

And the same process is applied to the Scrum development processes on those projects. . 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. 5 Oct 1990, Page 21.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

MARCH 11, 2017

“Quantifying Uncertainty in Early Lifecycle Cost Estimation (QUELCE),” Robert Ferguson, Dennis Goldenson, James McCurley, Robert Stoddard, David Zubrow, and Debra Anderson, Technical Report, CMU/SEI-2011-TR-026 ESC-TR-2011-026. Mazzuchi, and Shahram Sarkani, Systems Engineering , Volume 17, Issue 4, Winter 2014, Pages: 375–391.

2003 46

2003 2014 2015 2011 46

Herding Cats

MAY 7, 2019

“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. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B. 9, Issue 3, No.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

MAY 10, 2019

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. 5, September/October 2011. Software Engineering Institute, January 1996.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

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. 5, September/October 2011. Software Engineering Institute, January 1996.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Epicflow Blog

MAY 14, 2019

Varun Maheshwari , a Scrum Master at Telstra, says to “avoid project based thinking and start product thinking, have tight & fast feedback loops, make teams really autonomous, let team members talk to real customers so that they can understand domain & customer needs better, etc. Develop Your Leadership Skills.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75