Remove 2002 Remove Software Engineering Remove Software Review
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). So, answering your mail and writing some code at the same time is going to decrease productiveness. Limitations of attention.

2002 225
article thumbnail

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

Scrum.org

2001 ) and proactive behavior ( LePine, Erez & Johnson, 2002 ). “So So we went to Google Scholar and searched for review articles. 2010) reviewed 28 scientific studies that investigated how Scrum is associated with overall business outcomes. SCRUM and productivity in software projects: a systematic literature review.

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

Defensive Programming Grows Up

Leading Agile

Defensive programming consists of learning and using guidelines for software design and coding that tend to minimize the frequency and severity of problems in production. The day came when the software community more-or-less forgot about defensive programming. The Age of the Mainframe. And sleep, too. The Age of the Webapp.

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 ? This variation can be explained by the fact that initial concepts do not describe the final software system accurate enough.

2012 48
article thumbnail

Misunderstanding Making Decisions in the Presence of Uncertainty

Herding Cats

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp.

2003 46
article thumbnail

Top Solutions to Project Failure – Epicflow Research Part 2

Epicflow Blog

Give due consideration to the power of effective communication and take the necessary measures to improve its quality. Facts and Fallacies of Software Engineering by Robert L. Glass ( Addison-Wesley Professional, 2002), also recommended by Giorgio Locatelli. Step one to effective communication is active listening.”.

article thumbnail

Software Estimating Resources

Herding Cats

This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. Performance Evaluation of non?Markovian