Remove 2002 Remove Software Developers Remove Software Engineering
article thumbnail

Thinking By Sprinting: What Cognitive Science Tells Us About Why Scrum Works

Scrum.org

Software development is (generally speaking) very complex. Why our brain is not built for software engineering. It is a mental process and a limited mental resource (Ashcraft, 2002). In fact, simple heuristics can actually lead to better, quicker decisions than theoretical optimal procedures (Gigerenzer, 2002).

2002 225
article thumbnail

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

Scrum.org

2001 ) and proactive behavior ( LePine, Erez & Johnson, 2002 ). “So SCRUM and productivity in software projects: a systematic literature review. In 14th International Conference on Evaluation and Assessment in Software Engineering (EASE) (pp. A survey study of critical success factors in agile software projects.

Agile 225
Insiders

Sign Up for our Newsletter

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

Trending Sources

article thumbnail

Reading List for the Cone of Uncertainty

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 ? A Probabilistic Method for Predicting Software Code Growth," Michael Ross, Journal of Cost Analysis and Parametrics 4:127-147, 2011. "10

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

Defensive Programming Grows Up

Leading Agile

People who specialize in testing software will need technical skills more-or-less on par with competent software engineers. In a 2002 piece entitled The Law of Leaky Abstractions , Joel Spolsky observed that abstractions over any implementation can leak details of that implementation. Contracts vs. Promises.

article thumbnail

Top Solutions to Project Failure – Epicflow Research Part 2

Epicflow Blog

Facts and Fallacies of Software Engineering by Robert L. Glass ( Addison-Wesley Professional, 2002), also recommended by Giorgio Locatelli. Great Planning Disasters by Peter Hall (University of California Press, 1982), recommended by Sean Doull-Connolly , a Senior Process Engineer at TIAA.

article thumbnail

Real Options and Decision Making for ICT Projects

Herding Cats

This is the same paradigm of Agile software development where responding to change over following the plan is part of the original manifesto. If you google "Real Options software development" or "real options ICT" you'll find these and many dozens more. Here's a sample. 72, 2nd Quarter, 2008, pp. 744-758. "A

2008 32