Herding Cats

AUGUST 27, 2017

There's a recent post titled Four Fallacious Reasons to Estimate. It lists the usual suspects for why those spending the money think they don't have to estimate how much they plan to spend when they'll be done producing the value they've been assigned to produce for that expenditure. Let's look at each one in more detail.

Estimate 46

Estimate Software Review Underperforming Technical Team Technical Review 46

Herding Cats

NOVEMBER 3, 2016

Since all risk comes from uncertainty - reducible (Epistemic) and irreducible (Aleatory), estimating is a foundation of all we do. There is no discussion of the conjecture that estimates are a waste, estimates can't be done, estimates are evil, estimates must be stopped immediately. illities are a waste.

Estimate 28

Estimate Software Engineering Engineering Risk Management 28

Herding Cats

JUNE 9, 2017

The classic paper “ Software Engineering Economics,” Barry Boehm, IEEE Transactions on Software Engineering , Vol SE-10(1), 1984, pp. For software development, there are many decisions to be made. What Feature to develop next ? Why Guessing is not Estimating and Estimating is not Guessing.

Software 51

Software Software Engineering Estimate Manufacturing 51

Herding Cats

DECEMBER 3, 2017

Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. 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.

2007 34

2007 2012 2009 2010 34

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

JUNE 12, 2018

Then conjecture that NOT estimating will fix that symptom. Then conjecturing (here) that Not Estimating will somehow fix the problem of when you are DSTOP. The supposed evidence in the presentation, that estimating "does not work" starts with the Chaos Report. Principle #2 - Shorten the Feedback Cycle .

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

Herding Cats

APRIL 13, 2018

Estimation locks down choices early through upfront t decision making, #NoEstimates preserves options. Real Options can be used to address the gap found in traditional capital budgeting methods. If you google "Real Options software development" or "real options ICT" you'll find these and many dozens more. Here's a sample.

2008 32

2008 2002 Estimate Software Engineering 32

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. What Resources will be needed to reach Done?

Transportation 39

Transportation Software Engineering Finance 2011 39

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. 40 - Estimation is a Problematic Practice of Companies Doing Dangerous Things. We develop these reference classes using Agile Function Points.

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. In all engineering worlds, from software engineering to bending metal for money, there is really nothing new under the sun. For software development starts with.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

JUNE 12, 2018

Then conjecture that NOT estimating will fix that symptom. The notion of waterfall development on slide 9 as actually prohibited in our domain. The notion of waterfall development on slide 9 as actually prohibited in our domain. This is called Doing Stupid Things on Purpose (DSTOP). Not likely.

Underperforming Technical Team 28

Underperforming Technical Team Software Engineering Estimate Development Team Review 28

Herding Cats

APRIL 4, 2019

All making things smaller dos is show that you're late, over budget, and what you're building (Technical Performance Measures) doesn't work faster. 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. No References?

Risk Management 43

Risk Management Risk 2003 2011 43

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

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

Workzone

JANUARY 18, 2023

Favro Gamers or rather game developers, you may want to check out Favro. It’s specifically built for technicl creatives—such as game developers, UX designers and software engineers. Their Kanban board stretches horizontally across to help you visualize what’s next in the product development cycle.

2023 52

2023 Software Review Lean Estimate 52

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. What Resources will be needed to reach Done?

Transportation 28

Transportation Software Engineering Finance 2011 28

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

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

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

Herding Cats

MARCH 4, 2017

This is an immutable principle that impacts planning, execution, performance measures, decision making, risk, budgeting, and overall business and technical management of the project and the business funding the project no matter the domain, context, technology or any methods. All project work operates in the presence of uncertainty.

2010 28

2010 2007 Estimate Aerospace 28

Teamweek

OCTOBER 20, 2022

You probably already know—Agile isn’t just for software developers anymore. After all, Agile projects deliver proven value in software projects: Higher profit More meaningful projects and client relationships Greater productivity Clearer communication. They also assign estimates to each task. “We’re an Agile agency ??.”.

Agile 52

Agile Technical Review SCRUM Executing 52

MPUG

MAY 14, 2021

By education and training, I’m actually a software developer. Well, because according to PMI, the Project Management Institute, 45% of projects experience scope expansion, 32% failed on their budgeting, and 16% were deemed complete failures. I got junior software engineers, software engineers, senior software engineers.

Performance Measurement 59

Performance Measurement Underperforming Technical Team Software Engineering Engineering 59

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

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

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

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

MPUG

MAY 6, 2021

I actually got my degree in software engineering and moved up into project management like a lot of us did back in the day. Individual contributor team, lead section, lead project manager, program manager, director of engineering. Fletcher Hearns: Does the project meet schedule and budget? By education and training.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

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. You probably remember the case of the Volkswagen software engineer who was sentenced to prison for writing code that enabled vehicles to pass emissions tests fraudulently. It is not true.

Software Review 55

Software Review Software Technical Review Development Team Review 55