Scrum.org

OCTOBER 19, 2022

2001 ) and proactive behavior ( LePine, Erez & Johnson, 2002 ). “So Another approach is to track many organizations over time as they adopt Agile methodologies, while also measuring anything else that could influence their results other than agility itself. So we went to Google Scholar and searched for review articles.

Agile 211

Agile 2010 2013 2008 211

Scrum.org

FEBRUARY 3, 2020

Developing a new product requires understanding of the users, of the technologies involved and what makes something valuable (or not). Why our brain is not built for software engineering. It is a mental process and a limited mental resource (Ashcraft, 2002). Limitations of attention. Limitations of thinking.

2002 205

2002 SCRUM 2007 2003 205

Herding Cats

MAY 10, 2019

Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. 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.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

Let's start with a critical understanding of the purpose of managing risk on software development projects. Information about key project cost, (technical) performance and schedule attributes is often uncertain or unknown until late in the program. IEEE Transactions on Software Engineering , Vol. 3, March 2002.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

NOVEMBER 7, 2016

“Believing is Seeing: Confirmation Bias Studies in Software Engineering, “Magne Jørgensen and Efi Papatheocharous, 41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA). 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

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. & Zein, S.,

Estimate 40

Estimate Software Review Software 2012 40

Epicflow Blog

MAY 14, 2019

Over 200 PM experts from ExxonMobil, INEOS, DXC Technology, and other companies have shared their experience and proved that it’s a super hot topic. Business drivers have to be translated into project drivers by a strong technical team, not management. Facts and Fallacies of Software Engineering by Robert L.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75