2002 Estimate Software Development Software Engineering 
Herding Cats
OCTOBER 5, 2018
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 ? As more details get developed, the Cone converges to the actual value. Steve McConnell.
Herding Cats
MAY 10, 2019
requires making estimates) ? This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. IEEE Transactions on Software Engineering , Vol. 3, March 2002. 11 November 2002.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
MAY 11, 2019
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. requires making estimates) ? 3, March 2002.
Herding Cats
MARCH 11, 2017
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.
Herding Cats
APRIL 13, 2018
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. "
Epicflow Blog
MAY 14, 2019
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. Discussion in PMI Project, Program and Portfolio Management.
Scrum.org
FEBRUARY 3, 2020
Software development is (generally speaking) very complex. Why our brain is not built for software engineering. This will affect all estimates and predictions. It is a mental process and a limited mental resource (Ashcraft, 2002). This will affect all estimates and predictions.
Expert insights. Personalized for you.
48 
Let's personalize your content