Herding Cats

JUNE 18, 2017

There is a posted question at an agile conference. Can you make a decision without an estimate? There are NO means of making a credible decision in the presence of uncertainty without estimating the outcome of that decision. Don't assume, Estimate. This type of fallacy is common. . First a principle. Don't guess.

Estimate 37

Estimate Risk Management Finance Risk 37

Leading Agile

DECEMBER 1, 2023

Let alone how many can regularly meet a sprint commitment or a release commitment with defect-free, potentially shippable software. Maybe it’s a function of what I write about, the people that call us, or the people that show up to Agile conferences, but my sense is that it’s not many. Workgroups are made of collections of Agile teams.

2023 128

2023 Underperforming Technical Team Agile 2024 128

Herding Cats

MAY 8, 2016

ways to make decisions with No Estimates. Uncertainty of course is present in all software development work both reducible and irreducible uncertainty. can we make a decision in the presence of Uncertainty without making an estimate of the impact or outcome of that decision? An estimate is. It's a fallacy.

Estimate 28

Estimate Underperforming Technical Team Software Governance 28

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Product Development (#ProdDev). Governance (#Governance). Strategy (#Strategy).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

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 24, 2017

Then let's look at the actual description of how iterative and incremental development took place in “Managing the Development of Reliable Software,” R. Williams, Proceedings of the International Conference on Reliable Software, April 21-23, 1975. The VAX is my favorite real-time computer, by the way.

2003 56

2003 Process Governance Government 56

Leading Agile

DECEMBER 1, 2023

Let alone how many can regularly meet a sprint commitment or a release commitment with defect-free, potentially shippable software. Maybe it’s a function of what I write about, the people that call us, or the people that show up to Agile conferences, but my sense is that it’s not many. Workgroups are made of collections of Agile teams.

2023 62

2023 Underperforming Technical Team Agile 2024 62

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

JANUARY 11, 2018

This is the basis of all Closed Loop Control systems, from the speed control of the car, to the flight controls for an aircraft, to the temperature controls for your home, and of course the business controls for software development. Right and wrong cease to be useful concepts when you’re talking about software development.

Agile 39

Agile Software Developers Software Development Estimate 39

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. Turof, IOP Conference Series: Materials Science and Engineering , 400, 2018. “A reducible and irreducible ?

Risk Management 38

Risk Management Risk Technical Review 2002 38

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) ? 255, April 2010.

Risk Management 35

Risk Management Risk Technical Review 2002 35

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

NOVEMBER 5, 2018

In a previous post, Why Johnny Can't Estimate , mentioned some resources for estimating, the principles of business and technical management that demand estimates be made to make decisions, and background on the sources of uncertainty, that create risk, that require estimating to increase the probability of project success.

Software Review 34

Software Review Technical Review Estimate Software Developers 34

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. For software development starts with. This solution is called Software Engineering.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

JUNE 2, 2017

This is a chart from an agile conference where #Noestimates was a topic. So the first part is following standard estimating principles. So let's look at this manifesto : Probabilistic over Deterministic - there is no deterministic process in software development. From large construction to software development.

Estimate 35

Estimate Software Developers Software Development Risk Management 35

Herding Cats

AUGUST 22, 2018

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. And, my customer is equally as clueless about the need to estimate as I am. Probably not. .

Estimate 35

Estimate Underperforming Technical Team Technical Review Software Review 35

Herding Cats

FEBRUARY 20, 2018

Every once in awhile a reasonably intelligent No Estimates advocate shows up in a Twitter discussion. They often say you should be open-minded and try the concepts of No Estimates first. . A Pseudo-Open Minded person would say Sasquatch exists because the Federal Government is suppressing the evidence.

Estimate 48

Estimate Software Review Finance Closing 48

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

JANUARY 22, 2017

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 beginning of a project, comparatively little is known about the product or work results, and so estimates are subject to large uncertainty.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

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 beginning of a project, comparatively little is known about the product or work results, and so estimates are subject to large uncertainty.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

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. The BLUE bars are the probabilistic ranges of the current estimate date.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

AUGUST 25, 2017

Can All This Formality Have Any Use in Modern Software Development? The notion that agile development is a free-for-all development of what ever the customer wants to produce next, with the customer identifying the next important thing to develop works just fine for de minimus projects. Related articles.

2014 38

2014 2013 2012 Engineering 38

Leading Agile

AUGUST 19, 2020

And so, from how we do governance and how we do project planning and how we do organizational structure, all those kinds of things, right, so there’s this big hop. Because those are the things that fundamentally get in the way how we govern, right, how we deal with cross cutting concerns. We are building an internal tool.

Agile 89

Agile SCRUM Governance Government 89

MPUG

JUNE 1, 2022

Melanie: Jeff is currently the Training and Development Manager for Edwards Performance Solutions. As such, he oversees the production and maintenance of courses on project management, systems engineering, software development, business process improvement, and cyber security. Jeff, a big MPUG welcome back. The planning.

PMI 59

PMI Software Review Estimate Risk Management 59

MPUG

MARCH 18, 2021

Jeff is currently the lead course developer for Edward’s Performance Solution and oversees the production and maintenance of courses on project management, systems engineering, software development, business process improvement, and cybersecurity. Or whoever’s governing this. You ask the question.

Risk Management 52

Risk Management Software Review Underperforming Technical Team Governance 52