Remove 2002 Remove Estimate Remove Software Engineering
article thumbnail

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

Scrum.org

Why our brain is not built for software engineering. Knowledge work’ refers to tasks that take place mostly in our minds, like predicting scope, setting up plannings, considering consequences of changes to complex systems, working out test cases and estimating complexity. This will affect all estimates and predictions.

2002 208
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 ? 10 Deadly Sins of Software Estimation , Steve McConnell , Construx, 2002. Steve McConnell.

2012 48
Insiders

Sign Up for our Newsletter

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

article thumbnail

Misunderstanding Making Decisions in the Presence of Uncertainty

Herding Cats

What happens if you shift focus from "accurate estimation" to "reliably shipping by a date"? . If your project has no uncertainty, there is no need to estimate. All estimates have precision and accuracy. Deciding how much precision and accuracy is needed for a credible estimate is critical to the success of that decision.

2003 46
article thumbnail

Real Options and Decision Making for ICT Projects

Herding Cats

Estimation locks down choices early through upfront t decision making, #NoEstimates preserves options. This is the same paradigm of Agile software development where responding to change over following the plan is part of the original manifesto. Aligning Software Investment Decisions with the Markets ," Hakan Erdogmus. "

2008 32
article thumbnail

Top Solutions to Project Failure – Epicflow Research Part 2

Epicflow Blog

Victorine Ghobeira , a Senior Business Analyst and Project Manager at Dataquest, says that “preventing a lack of resource starts when defining and estimating activities and leads to creating a realistic schedule. Facts and Fallacies of Software Engineering by Robert L.

article thumbnail

Risk Management is How Adults Manage Projects

Herding Cats

So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. But when some statement is made about risk, estimating, performance modeling, or the like - always ask for references. I'm not expecting anyone to read all these books.

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