June 05, 2015

Carl Sagan's BS Detector

There are several BS detector paradigms. One of my favorites is Carl Sagan's. This one has been adapted from Reality Charting the book that goes along with the Apollo Method Root Cause Analysis process we use in our governance process in our domain. Any outage, any hard break, and disruption to the weekly release process is cause for Root Cause Analysis.

Here's Carl's checklist applied to the #NoEstimates conjecture that decisions can be made in the absence of estimates

Seek independent facts. Remember, a fact is a cause supported by sensed evidence and should be independently verified by you before it can be deemed legitimate. If you cannot find sensed evidence of causal relationships you should be skeptical.

Writing software for money is based on making decisions in the presence of uncertainty.

a primary process for making those decisions is Microeconomics and Opportunity costs. What's the lost opportunity for one decision over another?

To do this we need to estimate both the cost that results from choosing one decision over another and the benefits, opportunity, from that decision.

Welcome open debate on all points of view. Suspend judgment about the event or claim until all cause paths have been pursued to your satisfaction using RealityCharting®.

The notion that #NoEstimates is exploring and seeking conversation is not evidenced.

Any challenge questions are labeled as trolling, harassing, and unwanted.

You'd think is #NoEstimates is the next big thing responding to any and all challenges would be a terrific marketing opportunity. It's basic sales strategy, find all objections to your products value proposition, overcome them, and the deal is closed.

Always challenge authority. Ask to be educated. Ask the expert how they came to know what they know. If they cannot explain it to your satisfaction using evidence-based causal relationships then be very skeptical.

This is not the same as challenge everything.

This is when you hear something that is not backed b tangible evidence challenge it.

Ask the person making the claim how they know it will work outside their personal anecdotal experience?

Consider more than one hypothesis. The difference between a genius and a normal person is that when asked to solve a problem the genius doesn’t look for the right answer, he or she looks for how many possible solutions he or she can find. A genius fundamentally understands that there is always another possibility, limited by our fundamental ignorance of what is really happening.

The self-proclaimed thought leaders, agile leaders were challenged, I've been challenged, I must be an agile thought leader, needs to be tested with actual evidence.

Don’t defend a position because it is yours. All ideas are prototypical because there is no way we can really know all the causes. Seek to understand before seeking to be understood.

Use this on both sides of the conversation.

Where can no estimates be applied?

Where is it not applicable

Provide evidence on both sides.

Try to quantify what you think you know. Can you put numbers to it?

Show the numbers

Do the math

If there is a chain of causes presented, every link must work. Use RealityCharting® to verify that the chain of causes meets the advanced logic checks defined above and that the causes are sufficient in and of themselves.

If estimating is the smell of dysfunction, show the causal chain of the dysfunction.

Confirm that estimating is actually the root cause of management dysfunction.

Is misuse and abuse of estimates caused by the estimating process?

Use Occam’s razor to decide between two hypothesis; If two explanations appear to be equally viable, choose the simpler one if you must. Nature loves simplicity.

When conjecturing that stopping estimates fixed the dysfunction, is this the simplest solution?

How about stopping Bad Management practices

In the upcoming #NoEstimates book, Chapter 1 opens with a blatant Bad Management process of assigning a project to an inexperienced PM that is 100's of times bigger than she has ever seen.

Then blaming the estimating process for her failure.

This notion is continued on with references to other failed projects, without ever seeking the actual root cause of the failure.

No evidence is ever presented to show that stopping estimates will have to make the project successful.

Try to prove your hypothesis wrong. Every truth is prototypical and the purpose of science is to disprove that which we think we know.

This notion is lost on those conjecturing #NoEstimates is applicable their personal anecdotal experience.

Testing the idea in an external domain, not finding a CEO that supports the notion.

The null hypothesis test H0, is basic High School statistics.

Missing entirely there

Use carefully designed experiments to test all hypotheses.

No such thing in the #NoEstimates paradigm

So it's becoming clear #NoEstimates does pass the smell test of the basic BS meter

The Big Questions

What's the answer to how can we make a decision in the presence of uncertainty and not estimate and NOT violate the core principles of Microeconomics

It's not about the developers like or dislike of estimates. When I was a developer - radar, real-time controls, flight avionics, enterprise IT - I never liked estimates. It's about business. It's not our money. This notion appears to be completely lost. It's the millennials view of the world. We have two millennials (25 and 26) It's all about ME. Even if those suggesting are millennials, the message appears to be it's all about me. Go talk to the CFO.

The End

The rhetoric on #NoEstimates has now reached a fever pitch, paid conferences, books, blatant misrepresentations. Time to call BS and move on. This is the last post. I've met many interesting people in both good and bad ways. And will stay in touch. So long and thanks for the Fish. As Douglas Adams says. Those with the money will have the final say on this idea.

Comments

Carl Sagan's BS Detector

There are several BS detector paradigms. One of my favorites is Carl Sagan's. This one has been adapted from Reality Charting the book that goes along with the Apollo Method Root Cause Analysis process we use in our governance process in our domain. Any outage, any hard break, and disruption to the weekly release process is cause for Root Cause Analysis.

Here's Carl's checklist applied to the #NoEstimates conjecture that decisions can be made in the absence of estimates

Seek independent facts. Remember, a fact is a cause supported by sensed evidence and should be independently verified by you before it can be deemed legitimate. If you cannot find sensed evidence of causal relationships you should be skeptical.

Writing software for money is based on making decisions in the presence of uncertainty.

a primary process for making those decisions is Microeconomics and Opportunity costs. What's the lost opportunity for one decision over another?

To do this we need to estimate both the cost that results from choosing one decision over another and the benefits, opportunity, from that decision.

Welcome open debate on all points of view. Suspend judgment about the event or claim until all cause paths have been pursued to your satisfaction using RealityCharting®.

The notion that #NoEstimates is exploring and seeking conversation is not evidenced.

Any challenge questions are labeled as trolling, harassing, and unwanted.

You'd think is #NoEstimates is the next big thing responding to any and all challenges would be a terrific marketing opportunity. It's basic sales strategy, find all objections to your products value proposition, overcome them, and the deal is closed.

Always challenge authority. Ask to be educated. Ask the expert how they came to know what they know. If they cannot explain it to your satisfaction using evidence-based causal relationships then be very skeptical.

This is not the same as challenge everything.

This is when you hear something that is not backed b tangible evidence challenge it.

Ask the person making the claim how they know it will work outside their personal anecdotal experience?

Consider more than one hypothesis. The difference between a genius and a normal person is that when asked to solve a problem the genius doesn’t look for the right answer, he or she looks for how many possible solutions he or she can find. A genius fundamentally understands that there is always another possibility, limited by our fundamental ignorance of what is really happening.

The self-proclaimed thought leaders, agile leaders were challenged, I've been challenged, I must be an agile thought leader, needs to be tested with actual evidence.

Don’t defend a position because it is yours. All ideas are prototypical because there is no way we can really know all the causes. Seek to understand before seeking to be understood.

Use this on both sides of the conversation.

Where can no estimates be applied?

Where is it not applicable

Provide evidence on both sides.

Try to quantify what you think you know. Can you put numbers to it?

Show the numbers

Do the math

If there is a chain of causes presented, every link must work. Use RealityCharting® to verify that the chain of causes meets the advanced logic checks defined above and that the causes are sufficient in and of themselves.

If estimating is the smell of dysfunction, show the causal chain of the dysfunction.

Confirm that estimating is actually the root cause of management dysfunction.

Is misuse and abuse of estimates caused by the estimating process?

Use Occam’s razor to decide between two hypothesis; If two explanations appear to be equally viable, choose the simpler one if you must. Nature loves simplicity.

When conjecturing that stopping estimates fixed the dysfunction, is this the simplest solution?

How about stopping Bad Management practices

In the upcoming #NoEstimates book, Chapter 1 opens with a blatant Bad Management process of assigning a project to an inexperienced PM that is 100's of times bigger than she has ever seen.

Then blaming the estimating process for her failure.

This notion is continued on with references to other failed projects, without ever seeking the actual root cause of the failure.

No evidence is ever presented to show that stopping estimates will have to make the project successful.

Try to prove your hypothesis wrong. Every truth is prototypical and the purpose of science is to disprove that which we think we know.

This notion is lost on those conjecturing #NoEstimates is applicable their personal anecdotal experience.

Testing the idea in an external domain, not finding a CEO that supports the notion.

The null hypothesis test H0, is basic High School statistics.

Missing entirely there

Use carefully designed experiments to test all hypotheses.

No such thing in the #NoEstimates paradigm

So it's becoming clear #NoEstimates does pass the smell test of the basic BS meter

The Big Questions

What's the answer to how can we make a decision in the presence of uncertainty and not estimate and NOT violate the core principles of Microeconomics

It's not about the developers like or dislike of estimates. When I was a developer - radar, real-time controls, flight avionics, enterprise IT - I never liked estimates. It's about business. It's not our money. This notion appears to be completely lost. It's the millennials view of the world. We have two millennials (25 and 26) It's all about ME. Even if those suggesting are millennials, the message appears to be it's all about me. Go talk to the CFO.

The End

The rhetoric on #NoEstimates has now reached a fever pitch, paid conferences, books, blatant misrepresentations. Time to call BS and move on. This is the last post. I've met many interesting people in both good and bad ways. And will stay in touch. So long and thanks for the Fish. As Douglas Adams says. Those with the money will have the final say on this idea.