Scrum.org

AUGUST 25, 2022

Many studies have shown that stressed developers make more mistakes (Furuyama, Arai & Lio, 1996, Sonnentag et. High-stress environments are also more likely to burn developers out (Sonnentag et. The neurological processes for this are also well-understood. In Achieving Quality in Software (pp. Furuyama, T.,

Sustainability 180

Sustainability 2015 2014 2013 180

Digite

JANUARY 7, 2018

Several good books have been written on Kanban and its application to various business processes, especially to Scrum, since David Anderson published his original Kanban “blue book”. hours, Published 2014 by Blue Hole Press). 290 pages, Published 8 May 2014 by Celeritas Publishing). Kanban from the Inside. By Mike Burrows.

Lean 79

Lean Software Review 2010 2014 79

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 206

Agile 2010 2013 2008 206

Herding Cats

MAY 10, 2019

“A Taxonomy of Threats for Complex Risk Management,” Centre for Risk Studies, Research Programme of the Cambridge Centre for Risk Studies, University of Cambridge, Judge Business School, June 2014. “A IEEE Transactions on Software Engineering , Vol. 5, September/October 2011. 3, March 2002. 255, April 2010. 24, 2010. “A

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. IEEE Transactions on Software Engineering , Vol.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

OCTOBER 24, 2018

But before going further, let's establish the definitions we need to understand and apply Root Cause Analysis needed to discover the corrective and preventive actions to increase the probability of project success - especially Software Project Success. A Case Study in Root Cause Defect Analysis,” Marek Leszak, Dewayne E.

2014 45

2014 Aerospace 2011 2013 45

Herding Cats

MARCH 11, 2017

This quote demonstrates a lack of understanding of making decisions in the presence of uncertainty and the processes and events that create uncertainty. There is naturally occurring variability from uncontrolled processes. Aleatory uncertainty is expressed as a process variability. First, let's establish a principle.

2003 46

2003 2014 2015 2011 46