Remove 2013 Remove Software Developers Remove Software Engineering Remove Sustainability
article thumbnail

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

Scrum.org

Many studies have identified high autonomy as an important prerequisite for Agile teams ( Moe, Dingsøyr & Dybå, 2010 ; Donmez & Gudela, 2013 ; Tripp & Armstrong, 2018 ; Melo et. Ultimately, the role of (top) management is to keep their business healthy and economically sustainable. Journal of systems and software , 81 (6), 961–971.

Agile 204
article thumbnail

Misunderstanding Making Decisions in the Presence of Uncertainty

Herding Cats

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.

2003 46
Insiders

Sign Up for our Newsletter

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

article thumbnail

Risk Management Resources

Herding Cats

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. Software Engineering Institute, January 1996. De Meyer, C. Loch, and M.

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

Limits of a Self-Organizing Team

Leading Agile

But ultimately we’ll see how the idea ties back to self-organizing teams in the context of Agile software development. I can imagine some software engineers taking umbrage at that comment. In 2013 I described a conference session Pelrine facilitated in which we explored this concept in 2009.

Agile 92