Comments on: The Gut Instinct Equation http://www.codesqueeze.com/the-gut-instinct-equation/ Ideas for building efficient developers and software Thu, 11 Mar 2010 22:07:34 -0500 hourly 1 By: Mihai http://www.codesqueeze.com/the-gut-instinct-equation/#comment-2839 Mihai Sun, 28 Sep 2008 18:53:55 +0000 http://www.codesqueeze.com/the-gut-instinct-equation/#comment-2839 You really have it in for charts :D. It's just an observation, the truth is that as long as you offer a model for the readers that they can understand it's not bad. Keep up the postings and charting ;). Thank so much, it's growing into a nice place for Agile resource references. You really have it in for charts :D.
It’s just an observation, the truth is that as long as you offer a model for the readers that they can understand it’s not bad.

Keep up the postings and charting ;). Thank so much, it’s growing into a nice place for Agile resource references.

]]> By: Max Pool http://www.codesqueeze.com/the-gut-instinct-equation/#comment-174 Max Pool Wed, 22 Aug 2007 23:10:57 +0000 http://www.codesqueeze.com/the-gut-instinct-equation/#comment-174 @Bruce - Leon's chart recently gave me an idea of how to handle that situation. Stay tuned and I will write a post on that soon. @Bruce –

Leon’s chart recently gave me an idea of how to handle that situation. Stay tuned and I will write a post on that soon.

]]> By: Bruce http://www.codesqueeze.com/the-gut-instinct-equation/#comment-173 Bruce Wed, 22 Aug 2007 23:03:39 +0000 http://www.codesqueeze.com/the-gut-instinct-equation/#comment-173 Hi Max, Nice to meet you. I totally agree that people stink at estimating anything. I really like the recalibration chart. The other part of estimating is before you have started the project and have only high-level customer requirements. Then the customer goes to you: So how long will it take and how much will it cost me?!? Even worse, they demand a fixed price/fixed outcome proposal, but are not willing to get down into the detail of the requirements until they have signed off on the project. (Pretending Leon wrote it) Hi Max,

Nice to meet you. I totally agree that people stink at estimating anything. I really like the recalibration chart.

The other part of estimating is before you have started the project and have only high-level customer requirements. Then the customer goes to you: So how long will it take and how much will it cost me?!?

Even worse, they demand a fixed price/fixed outcome proposal, but are not willing to get down into the detail of the requirements until they have signed off on the project.

(Pretending Leon wrote it)

]]> By: lb http://www.codesqueeze.com/the-gut-instinct-equation/#comment-172 lb Wed, 22 Aug 2007 22:59:28 +0000 http://www.codesqueeze.com/the-gut-instinct-equation/#comment-172 @Bruce + Max Yep I'm subscribed.... but i don't have much of an answer. I like Max's response. So just pretend I said that, OK ;-) @Bruce + Max
Yep I’m subscribed…. but i don’t have much of an answer.

I like Max’s response. So just pretend I said that, OK ;-)

]]> By: Max Pool http://www.codesqueeze.com/the-gut-instinct-equation/#comment-171 Max Pool Wed, 22 Aug 2007 22:54:28 +0000 http://www.codesqueeze.com/the-gut-instinct-equation/#comment-171 @Bruce - I don't know if Leon is subscribed to the comments, so let me take a crack at this (if you are Leon, feel free to jump in). I agree that in a SCRUM/Agile project where sprints are explicitly mapped out, this chart melts away as you will not need to speculate on progress - true progress will be seen in burn down/up charts. However, we are currently viewing this at the project level which does not make sense when SCRUM is applied. If we get more granular, we could apply this to the time or estimation of a single feature. Long story short, people stink at estimating anything and I found this a clever way of recalibrating perceived progress. @Bruce –

I don’t know if Leon is subscribed to the comments, so let me take a crack at this (if you are Leon, feel free to jump in).

I agree that in a SCRUM/Agile project where sprints are explicitly mapped out, this chart melts away as you will not need to speculate on progress – true progress will be seen in burn down/up charts.

However, we are currently viewing this at the project level which does not make sense when SCRUM is applied. If we get more granular, we could apply this to the time or estimation of a single feature.

Long story short, people stink at estimating anything and I found this a clever way of recalibrating perceived progress.

]]> By: Bruce http://www.codesqueeze.com/the-gut-instinct-equation/#comment-170 Bruce Wed, 22 Aug 2007 22:36:54 +0000 http://www.codesqueeze.com/the-gut-instinct-equation/#comment-170 Hi Leon, How do you think this is affected by an agile approach? Especially in the case where the customer is highly involved with setting the priorities on (back-log) requirements. In this case the feature creep will be much more visible to that customer, but also the end functionality will be more in line with the customer's expectations, rather than containing a whole lot of wizz-bang with little business benefit. The other side of the coin is of course making sure that the requirements that do make it into coding is documented sufficiently in order for the test team to effectively test the system. This is especially important when doing regression testing after refactoring. Hi Leon,
How do you think this is affected by an agile approach? Especially in the case where the customer is highly involved with setting the priorities on (back-log) requirements. In this case the feature creep will be much more visible to that customer, but also the end functionality will be more in line with the customer’s expectations, rather than containing a whole lot of wizz-bang with little business benefit.
The other side of the coin is of course making sure that the requirements that do make it into coding is documented sufficiently in order for the test team to effectively test the system. This is especially important when doing regression testing after refactoring.

]]> By: Justin Deltener http://www.codesqueeze.com/the-gut-instinct-equation/#comment-162 Justin Deltener Tue, 21 Aug 2007 13:50:27 +0000 http://www.codesqueeze.com/the-gut-instinct-equation/#comment-162 I'm constantly amazed at how utterly horrible developers are at estimating time. Developers think in terms of features left instead of actual time remaining. In the past it was a constant struggle to get devs to turn features remaining into somewhat accurate quantifiable hours left to deployment. This graph really supports this sad fact LOL I’m constantly amazed at how utterly horrible developers are at estimating time. Developers think in terms of features left instead of actual time remaining. In the past it was a constant struggle to get devs to turn features remaining into somewhat accurate quantifiable hours left to deployment. This graph really supports this sad fact LOL

]]> By: Max Pool http://www.codesqueeze.com/the-gut-instinct-equation/#comment-160 Max Pool Tue, 21 Aug 2007 10:38:15 +0000 http://www.codesqueeze.com/the-gut-instinct-equation/#comment-160 Thanks Leon! I found it a unique way of looking at things, so keep up the out-of-box thinking =) Thanks Leon! I found it a unique way of looking at things, so keep up the out-of-box thinking =)

]]> By: lb http://www.codesqueeze.com/the-gut-instinct-equation/#comment-159 lb Tue, 21 Aug 2007 04:03:46 +0000 http://www.codesqueeze.com/the-gut-instinct-equation/#comment-159 thanks for writing this up. You made it make a lot more sense than i did! cheers lb thanks for writing this up. You made it make a lot more sense than i did!
cheers
lb

]]>