Good quote from today

During an iteration kickoff meeting–


“Guys, I know you’re just becoming familiar with XYZ, but could you tell us when every un-scheduled downtime event is going to be this year?”


Promptly followed by:


“Can you go ahead and estimate the time to fix the bugs we haven’t found yet?”


He was kidding.  I think.

About Jeremy Miller

Jeremy is the Chief Software Architect at Dovetail Software, the coolest ISV in Austin. Jeremy began his IT career writing "Shadow IT" applications to automate his engineering documentation, then wandered into software development because it looked like more fun. Jeremy is the author of the open source StructureMap tool for Dependency Injection with .Net, StoryTeller for supercharged acceptance testing in .Net, and one of the principal developers behind FubuMVC. Jeremy's thoughts on all things software can be found at The Shade Tree Developer at http://codebetter.com/jeremymiller.
This entry was posted in Uncategorized. Bookmark the permalink. Follow any comments here with the RSS feed for this post.
  • Gary Williams

    I think your estimate is too complex and I suspect that you are using some imaginary facts to make it. Get Real, baby! I need a rational answer.

    ;-)

  • http://codebetter.com/blogs/jeremy.miller jmiller

    Here you go “Mr. I was a Mathmatics Major”, I think it’ll be 5 + 3i.

  • Gary Williams

    Yes, I was kidding — still waiting for that estimate though.

  • http://codebetter.com/blogs/jeremy.miller jmiller

    Hence “previous employer.” That poor lady is still there though.

  • Carlton

    “I had a business analyst who would routinely use very snide remarks and inside jokes in her requirements documents just to see how closely people were reading the documents.”

    Without knowing all the actors or context, but on the surface that sounds like a cry for help…seriously. If the best way to get feedback on your work is to write provocative things, maybe one might be better off doing something else?

  • http://codebetter.com/blogs/jeremy.miller jmiller

    Harry,

    I hear what you’re saying, but we’re down to a bare handful of purely exceptional cases. Purposely introducing bugs?!? I had a business analyst who would routinely use very snide remarks and inside jokes in her requirements documents just to see how closely people were reading the documents.

  • http://blogs.infosupport.com/harryn HarryNieboer

    Actually, you can estimate the time to fix the bugs that you have not found yet when
    - you have an idea about the time you need to fix an average bug
    - you have an idea about the number of bugs to come.
    I leave the first metric up to your experience, the second can be estimated if you deliberately INSERTED some bugs into your application.
    Say you inserted 20 bugs of all sorts, and until now people found 150 bugs, 5 of which were yours. Than you can estimate another 450 bugs to come to you, as around a quarter of the bugs are found up till now.

    In a project where we developed and another party tested, we inserted bugs to get an idea on how good the other party did their testing work …

    Greetings
    Harry