Scrum.org

OCTOBER 19, 2022

Several empirical studies have indeed found that teams with a frequent delivery strategy are more likely to deliver successful project outcomes and satisfy stakeholders than teams that do not ( Chow & Cao, 2008 , Jørgensen, 2016 ). 2014 ; Young & Jordan, 2008 ; Russo, 2021 ). Journal of systems and software , 81 (6), 961–971.

Agile 204

Agile 2010 2013 2008 204

Herding Cats

MAY 7, 2019

Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points,” Putu Linda Primandari and Sholiq, The Third Information Systems International Conference, Procedia Computer Science, 72, pp. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B.

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

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

APRIL 4, 2019

All making things smaller dos is show that you're late, over budget, and what you're building (Technical Performance Measures) doesn't work faster. Risk Analysis – A Quantitative Guide , Third Edition, David Vose, John Wiley & Sons April 2008. Risk Analysis: A Quantitative Guide , David Vose, John Wiley & Sons 2008.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

APRIL 13, 2018

Real Options can be used to address the gap found in traditional capital budgeting methods. This is the same paradigm of Agile software development where responding to change over following the plan is part of the original manifesto. Managing Requirements for Business Value," John Favaro, IEEE Software , March/April 2002.

2008 32

2008 2002 Estimate Software Engineering 32

Herding Cats

DECEMBER 3, 2017

Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. The domain for the Cone can certainly be product development, but it's origins are for Programs, where a budget, period of performance, and needed capabilities are On Contract.

2007 34

2007 2012 2009 2010 34