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.

2012 48

2012 2007 2011 2010 48

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.

2003 46

2003 2014 2015 2011 46

Herding Cats

SEPTEMBER 22, 2017

The #NoEstimates Manifesto - Actually restates Best Practice for estimating and making decisions with those estimates. . Deterministic estimates are point estimates and Point estimates without a Variance are of little value in the presence of uncertainty. Delivery Time over Development Time.

Estimate 50

Estimate 2017 Governance Government 50

nTask

AUGUST 8, 2019

Its simplicity and ease of implementation has made it the most popular version of the systems development life cycle (SDLC) for software engineering and IT projects. What Dr. Royce was describing was a flawed model for software development as he argued for a model with multiple iterations or runs.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

Herding Cats

APRIL 14, 2018

Software development is a Value Creaton activity, but Value cannot be determined unless we know the cost to produce that value and when that value will be available for use by those who of paid for that Value. For software development, those scarce resources are people, time, and money. Microeconomics .

Process 45

Process Estimate Software Developers Software Development 45

Herding Cats

FEBRUARY 9, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. This also meant developing software systems to support this effort. 40 - Estimation is a Problematic Practice of Companies Doing Dangerous Things. Is this normal?

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

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. Software Engineering Institute, January 1996.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

JANUARY 23, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. This also meant developing software systems to support this effort. Rarely are software engineers working on science experiments. Almost impossible?

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

SEPTEMBER 27, 2017

"Managing the Development of Large-Scale Software: Concepts and Techniques," Winston Royce, Proceedings, Wescon, August 1970. Iterative Enhancement: A Practical Technique for Software Development," Victor Basil and Albert Turner, IEEE Transactions on Software Engineering , Vol. 4, December 1975.

2003 38

2003 Software Engineering Manufacturing Engineering 38

Herding Cats

JUNE 9, 2018

There is always lots of complaining about the biases introduced into managing projects and making the estimates needed to make project decisions. With these business principles of software development and projects in general, we can ask and answer five principles of project success. A final Thought . Palacios, Cristina Casado?Lumbreras,

Transportation 39

Transportation Software Engineering Finance 2011 39

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) ? De Meyer, C.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

FEBRUARY 9, 2018

I've seen estimates abused by bad managers, so let's NOT estimate and that will fix the behavior of Bad Managers." While the human behaviors are real and observable, conjecturing that decisions can be made in the presence of uncertainty without estimating the outcome of those decisions, there is no principle to support that conjecture.

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

Herding Cats

JUNE 9, 2018

There is always lots of complaining about the biases introduced into managing projects and making the estimates needed to make project decisions. With these business principles of software development and projects in general, we can ask and answer five principles of project success. A final Thought . Palacios, Cristina Casado?Lumbreras,

Transportation 28

Transportation Software Engineering Finance 2011 28

Herding Cats

JANUARY 13, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates or any other project attribute. Estimates of cost, schedule, technical performance on the left have a lower probability of being precise and accurate than estimates on the right.

Technical Review 28

Technical Review Software Review Estimate Software Engineering 28

Teamweek

NOVEMBER 9, 2022

Project tracking software helps you: Understand if you’re on track to meet task, milestone, and project deadlines Time tracking Compare estimated vs. actual efforts and costs Adjust plans quickly if you’re not on schedule or within the budget. And almost all such tools are built for software project teams.

Software Review 52

Software Review Software Technical Review Construction 52

MPUG

MAY 14, 2021

By education and training, I’m actually a software developer. Having spent half my life in the commercial space and half in the government space, the questions are always there. And then I came back and started using it in larger government programs. Again, my name is Fletcher Hearns. What’s happening now.

Performance Measurement 59

Performance Measurement Underperforming Technical Team Software Engineering Engineering 59

Herding Cats

FEBRUARY 23, 2016

The conjecture that we can make decisions in the presence of uncertainty without estimating the impacts of those decisions is without any principles that can be tested beyond personal anecdotes of I know people who spend other peoples money without providing estimates. Not a group that likes to get questions, by the way.

Estimate 39

Estimate Risk Management Finance Software Developers 39

MPUG

MAY 6, 2021

We are a consulting company in the DC Baltimore area that specializes in project and portfolio management for about 80% of our customers in the government space, the other 20 in the commercial space. I actually got my degree in software engineering and moved up into project management like a lot of us did back in the day.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). The BLUE bars are the probabilistic ranges of the current estimate date.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). The BLUE bars are the probabilistic ranges of the current estimate date.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). Estimates are needed but are subject to large level of uncertainty.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

JANUARY 14, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates or any other project attribute (in this post, cost, schedule, and technical performance parameters). Economics of Software Development. Prentice-Hall, 1981.

Technical Review 28

Technical Review Software Review Underperforming Technical Team Risk Management 28

Herding Cats

JUNE 7, 2018

This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's . In the presence of uncertainty, estimates is needed to make decisions. There is no way out of this for any non-trivial software development project. This information comes from the Paul G.

Underperforming Technical Team 32

Underperforming Technical Team SCRUM Software Engineering Risk Management 32

Herding Cats

JUNE 19, 2017

The Cone of Uncertainty is a framing assumption used to model the needed reduction in some parameter of interest in domains ranging from software development to hurricane forecasting. Of late, Cone of Uncertainty has become the mantra of No Estimates advocates claiming that data is needed BEFORE the Cone is of any use.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Herding Cats

JUNE 7, 2018

This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's . In the presence of uncertainty, estimates is needed to make decisions. There is no way out of this for any non-trivial software development project. This information comes from the Paul G.

Underperforming Technical Team 28

Underperforming Technical Team SCRUM Software Engineering Risk Management 28

Leading Agile

AUGUST 20, 2018

They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. The same rule of thumb applies to other governance reviews, as well. It’s not okay, for instance, for an individual to perform both the programming and the testing of a software feature.

Software Review 55

Software Review Software Technical Review Development Team Review 55