Scrum.org

FEBRUARY 3, 2020

Why our brain is not built for software engineering. It is a mental process and a limited mental resource (Ashcraft, 2002). In fact, simple heuristics can actually lead to better, quicker decisions than theoretical optimal procedures (Gigerenzer, 2002). Limitations of attention. Limitations of thinking. References.

2002 196

2002 SCRUM 2007 2003 196

Scrum.org

OCTOBER 19, 2022

2001 ) and proactive behavior ( LePine, Erez & Johnson, 2002 ). “So SCRUM and productivity in software projects: a systematic literature review. In 14th International Conference on Evaluation and Assessment in Software Engineering (EASE) (pp. A survey study of critical success factors in agile software projects.

Agile 203

Agile 2010 2013 2008 203

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. 3, March 2002. 11 November 2002. México, 1 al 3 de Febrero de 2006.

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. 3, March 2002. 11 November 2002. México, 1 al 3 de Febrero de 2006.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

OCTOBER 5, 2018

"A Quick Estimation Approach to Software Cost Estimation," Leckraj Nagowah, Hajrah BibiBenazir, and Bachun, African Conference on Software Engineering and Applied Computing , . "A A Probabilistic Method for Predicting Software Code Growth," Michael Ross, Journal of Cost Analysis and Parametrics 4:127-147, 2011. "10

2012 48

2012 2007 2011 2010 48

Herding Cats

NOVEMBER 7, 2016

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. Planning and Executing Time-Bound Projects,” Eduardo Miranda, IEEE Computer , March 2002, pp. 5 Oct 1990, Page 21.

Estimate 64

Estimate 2006 2005 2013 64

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. 8, August 2002 pp.

2003 46

2003 2014 2015 2011 46