Remove 2007 Remove Estimate Remove Software Engineering
article thumbnail

Five reasons why Scrum is not helping in getting twice the work done in half the time

Scrum.org

I worked as a product owner for my first product in 2007–08 to manage the insurance lifecycle for a major insurance company in America. Do you measure estimated time for a task vs. actual time spent? Just processes will not improve speed on the road, and we also need a better car with a newer engine. Complete harmony at work.

article thumbnail

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

Scrum.org

A while ago, I received an interesting scientific article from Gunther Verheyen titled “Getting Things Done: The Science Behind Stress-Free Productivity” (Heylighen & Vidal, 2007). Why our brain is not built for software engineering. This will affect all estimates and predictions. Limitations of attention.

2002 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

Basis of Estimating Software Development

Herding Cats

The estimating of software development is both straightforward and complex. When it is suggested that estimating is hard, of no value, and unnecessary, always ask what principle is used to support that claim? Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991. Don't hear one?

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
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

Microeconomics and Risk Management in Decision Making for Software Development

Herding Cats

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. Software engineering economics." IEEE Transactions of Software Engineering, 1 (1984): 4-21.

article thumbnail

Resources for Cone of Uncertainty

Herding Cats

Some feel that the cone does not provide any value for the work they do and does not match the reducing uncertainty in their estimates. First, the Cone of Uncertainty is a Principle used to define the needed reduction in the variances of estimates on Programs. Remember Risk Management is How Adults Manage Projects - Tim Lister.

2007 34