Scrum.org

FEBRUARY 4, 2022

References in academic papers are also a good source. Academic authors usually explicitly reference where their ideas or claims come from. It is often helpful to identify and follow these references if you’re interested in them. Some authors are merely proposing an idea and may reference only supporting evidence, or not at all.

Agile 201

Agile Software Review Underperforming Technical Team Technical Review 201

Scrum.org

OCTOBER 19, 2022

But adherence to a framework or prescribed process does not guarantee agility. Adherence to a framework or prescribed process does not guarantee agility.”. I prefer a process-based definition of agility. Although we used Scrum teams for our investigation, these processes are generic enough to apply to Agile teams in general.

Agile 215

Agile 2010 2013 2008 215

Herding Cats

APRIL 4, 2019

But when some statement is made about risk, estimating, performance modeling, or the like - always ask for references. No References? Henry Montgomery (Editor), Universitetsforlaget; UK Edition, November 28, 2011. 3421, Second Edition, December 2011. I'm not expecting anyone to read all these books.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

MAY 7, 2019

So start here to build your academic foundation, that can be put to work to build a foundation of validated experience of making estimates in the presence of uncertainty and protect yourself from fallacious claims that estimates are a waste, not needed, and produce bad resulting in the decision making process for those paying you to produce value.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

The same process for estimating is applied to multi-billion dollar projects we work. And the same process is applied to the Scrum development processes on those projects. . Here's some materials that provide the tools and processes needed to learn how to estimate. Laplante, ACM SIGSOFT Software Engineering Notes , Vol.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

OCTOBER 24, 2018

Root Cause is the fundamental initiating cause on a causal chain leading to a failure of a process which results in a recurrence of the problem. Root Cause Analysis is a systematic documented approach to arrive at the true Root Cause of the process problem. References . What Are Problem Causes of Software Projects?

2014 45

2014 Aerospace 2011 2013 45

Herding Cats

MARCH 11, 2018

If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Software engineering economics." IEEE Transactions of Software Engineering, 1 (1984): 4-21.

Software Developers 34

Software Developers Software Development Risk Management Risk 34