Remove 2014 Remove Case Study Remove Software Developers Remove Software Development
article thumbnail

In-Depth: The Science On Sustainable Pace, Stress, And Motivation

Scrum.org

It is very similar to work engagement (Schaufeli & Salanova, 2014), which we also measure in both the Scrum Team Survey and TeamMetrics (as “team morale”). It has been thoroughly tested and verified through experiments, case studies, and field research (Deci & Ryan, 2020). In Achieving Quality in Software (pp.

article thumbnail

Top 10 Lean/ Kanban Books for IT, Software and Knowledge Work!

Digite

hours, Published 2014 by Blue Hole Press). This is the original book where David Anderson first laid down the definition of and guidance to the Kanban Method for software and knowledge work. Principle of Product Development Flow. 290 pages, Published 8 May 2014 by Celeritas Publishing). Kanban from the Inside.

Lean 79
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

In-Depth: The Evidence-Based Business Case For Agile

Scrum.org

2014 ; Young & Jordan, 2008 ; Russo, 2021 ). Journal of systems and software , 81 (6), 961–971. In International Conference on Agile Software Development (pp. Information and Software Technology , 78 , 83–94. Interpretative case studies on agile team productivity and management. 2013, June).

Agile 214
article thumbnail

Risk Management Resources

Herding Cats

“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. 1, March 2014. 5, September/October 2011. 255, April 2010.

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

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.

article thumbnail

Without a Root Cause Analysis, No Corrective or Preventive Action is Credible - Part 1

Herding Cats

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
article thumbnail

Misunderstanding Making Decisions in the Presence of Uncertainty

Herding Cats

Mazzuchi, and Shahram Sarkani, Systems Engineering , Volume 17, Issue 4, Winter 2014, Pages: 375–391. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L.

2003 46