Herding Cats

DECEMBER 16, 2017

Software Sizing, Estimation, and Risk Management: When Performance is Measured Performance Improves , Daniel Galaorath and Michael Evans , Auerbach, 2006. Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991. Agile Estimating and Planning , Mike Cohn, Prentice Hall, 2006.

Software Developers 46

Software Developers Software Development Estimate 2006 46

Herding Cats

MAY 10, 2019

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. Pich, Working Paper, 21/2006, Cambridge University, Judge Business School. “A De Meyer, C.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

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. Pich, Working Paper, 21/2006, Cambridge University, Judge Business School. “A De Meyer, C.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MARCH 11, 2017

Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L. Kirkeboen, G., &

2003 46

2003 2014 2015 2011 46

Herding Cats

MAY 7, 2019

Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. COSMIC Software Estimation Approach,” Alain Abran, ICEAA Workshop, Portland Oregon, June 6?9, Patnail, International Journal of Software Engineering, IJSE, 8.1,

Estimate 40

Estimate Software Review Software 2012 40

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

FEBRUARY 9, 2019

This also meant developing software systems to support this effort. We were one of the first users of eXtreme Programming, long before Scrum was around and presented that early work in 2003, " Making Agile Development Work in a Government Contracting Environment, Measuring velocity with Earned Value." . Let's start with the obvious.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42