Scrum.org

OCTOBER 19, 2022

So we went to Google Scholar and searched for review articles. 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. A survey study of critical success factors in agile software projects. 2013, June).

Agile 206

Agile 2010 2013 2008 206

Scrum.org

NOVEMBER 24, 2021

Van Waardenburg & Van Vliet (2013) offer a case study in a large organization and conclude that “The Project Manager focuses on the ’how’ of a project, the Product Owner focuses on the ’what’”. One of the reviewers of this article, Maarten Dalmijn , noted that he missed “product discovery” as a core activity in the work by Bass (2018).

2014 213

2014 2008 Technical Review 2019 213

Herding Cats

NOVEMBER 7, 2016

The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ‒ Steve McConnell. Software quality measurement,” Magne Jørgensen, Advances in Engineering Software 30 (1999) 907–912.

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. 5, October 2013.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

MAY 10, 2019

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.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MARCH 11, 2017

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. Kirkeboen, G., &

2003 46

2003 2014 2015 2011 46

Herding Cats

MAY 11, 2019

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.

Risk Management 35

Risk Management Risk Technical Review 2002 35