Comments on: The Perfect Estimate http://blog.slickedit.com/2007/08/the-perfect-estimate/ "Hello World" - The SlickEdit Developer Blog Wed, 08 Feb 2012 10:18:34 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Mohd Amjed http://blog.slickedit.com/2007/08/the-perfect-estimate/comment-page-1/#comment-296 Mohd Amjed Tue, 01 Jan 2008 08:03:31 +0000 http://blog.slickedit.com/?p=94#comment-296 It was rather a fun reading this, keep it up, gd work. It was rather a fun reading this, keep it up, gd work.

]]> By: RFB http://blog.slickedit.com/2007/08/the-perfect-estimate/comment-page-1/#comment-108 RFB Thu, 23 Aug 2007 13:18:29 +0000 http://blog.slickedit.com/?p=94#comment-108 You’ve probably heard that when making estimates you should take your best guess and double it. You missed the step of changing to the next highest unit of measure :) A one hour job inevitably takes two days, and a week task two months! You’ve probably heard that when making estimates you should take your best guess and double it.

You missed the step of changing to the next highest unit of measure :)

A one hour job inevitably takes two days, and a week task two months!

]]> By: Scott Westfall http://blog.slickedit.com/2007/08/the-perfect-estimate/comment-page-1/#comment-107 Scott Westfall Wed, 22 Aug 2007 18:37:22 +0000 http://blog.slickedit.com/?p=94#comment-107 Phileosophos, SlickEdit is committed to an annual release cycle, which works very well for us and our customers. As a mature product, most of our changes are incremental and fit well within this framework. Our customers know that each year they will receive a release with new features and bug fixes. We also release smaller updates as needed to address issues that don’t fit this schedule. I agree that this model doesn’t work for all products, particularly those in their first release or ones making major overhauls. However, setting a release date is always a part of the business of software development. As much as we’d like to have this date set solely based on when the software will be ready, the reality of the business must be factored in. For new products, you have to factor in market windows, capital burn rates, annual sales cycles, etc. It’s no good to release a product after the company has already gone broke or someone has beaten you to the market. For existing products, there are also business pressures. As developers, it’s our job to work with the business team and discuss what can be built in the available time. Where more time leads to a better product, we need to show them that and provide them with the ability to choose what makes sense for the business. That’s why I believe estimates are so important. Effective estimates enable a company to plan releases and commit to release dates far in advance. This allows all of the business functions, like production and marketing, to work toward the same date, culminating in a successful release. This article didn’t really touch on these subjects, but I hope to write more on this in the future. Phileosophos,
SlickEdit is committed to an annual release cycle, which works very well for us and our customers. As a mature product, most of our changes are incremental and fit well within this framework. Our customers know that each year they will receive a release with new features and bug fixes. We also release smaller updates as needed to address issues that don’t fit this schedule.
I agree that this model doesn’t work for all products, particularly those in their first release or ones making major overhauls. However, setting a release date is always a part of the business of software development. As much as we’d like to have this date set solely based on when the software will be ready, the reality of the business must be factored in.
For new products, you have to factor in market windows, capital burn rates, annual sales cycles, etc. It’s no good to release a product after the company has already gone broke or someone has beaten you to the market. For existing products, there are also business pressures.
As developers, it’s our job to work with the business team and discuss what can be built in the available time. Where more time leads to a better product, we need to show them that and provide them with the ability to choose what makes sense for the business. That’s why I believe estimates are so important.
Effective estimates enable a company to plan releases and commit to release dates far in advance. This allows all of the business functions, like production and marketing, to work toward the same date, culminating in a successful release.
This article didn’t really touch on these subjects, but I hope to write more on this in the future.

]]> By: Phil http://blog.slickedit.com/2007/08/the-perfect-estimate/comment-page-1/#comment-104 Phil Wed, 22 Aug 2007 16:35:02 +0000 http://blog.slickedit.com/?p=94#comment-104 When I picked up the SWAG acronym, the S meant Scientific. :-) When I picked up the SWAG acronym, the S meant Scientific. :-)

]]> By: Phileosophos http://blog.slickedit.com/2007/08/the-perfect-estimate/comment-page-1/#comment-103 Phileosophos Wed, 22 Aug 2007 15:36:49 +0000 http://blog.slickedit.com/?p=94#comment-103 So I see management at SlickEdit are also wedded to the incredibly stupid method (ISM) of doing software? That is, (1) pick a ship date, (2) pick a product name, and (3) only then figure out what you need to build? Yuck. I pity you. I've done enough of that. So I see management at SlickEdit are also wedded to the incredibly stupid method (ISM) of doing software? That is, (1) pick a ship date, (2) pick a product name, and (3) only then figure out what you need to build? Yuck. I pity you. I’ve done enough of that.

]]>