Remove 2011 Remove Analysis Remove Software Developers Remove Software Engineering
article thumbnail

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

Scrum.org

For this analysis, we use the evaluations of 857 stakeholders for 241 teams. For this, we used a simple statistical technique called multiple regression analysis. Each dot represents a team: A scatterplot and the results from a regression analysis may not be intuitive for many readers, especially those not familiar with statistics.

Agile 201
article thumbnail

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

Herding Cats

This first post is a follow-on from the posts Root Cause of Project Failure , Root Cause Analysis , Discovering the Root Cause - The 5 Whys , T urning Editorials into Root Cause Analysis , Observation Issues and Root Cause Analysis , Without a Root Cause Analysis, No Suggested Fix Can Be Effective. References .

2014 45
Insiders

Sign Up for our Newsletter

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

article thumbnail

Microeconomics and Risk Management in Decision Making for Software Development

Herding Cats

Economics is a social science concerned chiefly with description and analysis of the production, distribution, and consumption of goods and services. If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers.

article thumbnail

Software Estimating Resources

Herding Cats

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. Monte Carlo Schedule Risk Analysis,” Intaver Institute, Inc. 61, September 2004. & Zein, S.,

article thumbnail

Estimating is a Learned Skill

Herding Cats

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. The Future of Systems-and Software Development. Springer International Publishing, 2016.

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. 5, September/October 2011. México, 1 al 3 de Febrero de 2006. De Meyer, C.

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.