Learn to Estimate - Revision history

Kevlin at 20:53, 11 July 2009

Kevlin — Sat, 11 Jul 2009 20:53:19 GMT

←Older revision		Revision as of 20:53, 11 July 2009
Line 1:		Line 1:
	As a programmer you need to be able to provide estimates to your managers, colleagues, and users for the tasks you need to perform, so that they will have a reasonably accurate idea of the time, costs, technology, and other resources needed to achieve their goals.		As a programmer you need to be able to provide estimates to your managers, colleagues, and users for the tasks you need to perform, so that they will have a reasonably accurate idea of the time, costs, technology, and other resources needed to achieve their goals.

-	To ~~learn how~~ to estimate it is obviously important to learn some estimation techniques. First of all, however, it is fundamental to learn what estimates are, and what they should be used for — as strange as it may seem, many developers and managers don't really know this.	+	To be able to estimate well it is obviously important to learn some estimation techniques. First of all, however, it is fundamental to learn what estimates are, and what they should be used for — as strange as it may seem, many developers and managers don't really know this.

	The following exchange between a project manager and a programmer is not untypical:		The following exchange between a project manager and a programmer is not untypical:
Line 12:		Line 12:
	:''Programmer:'' Deal!		:''Programmer:'' Deal!

-	The programmer, at the end, comes up with an "estimate" that matches what is acceptable for the manager. But since it is seen to be the programmer's estimate, the manager will hold ~~him~~ accountable to it. To understand what is wrong with this conversation we need three definitions — estimate, target, and commitment:	+	The programmer, at the end, comes up with an "estimate" that matches what is acceptable for the manager. But since it is seen to be the programmer's estimate, the manager will hold the programmer accountable to it. To understand what is wrong with this conversation we need three definitions — estimate, target, and commitment:

-	* An ''estimate'' is an approximate calculation or judgement of the value, number, quantity, or extent of something. This definition implies that an estimate is a factual measure based on hard data and previous experience — hopes and wishes must be ignored when calculating it. The definition also implies that, being approximate, an estimate cannot be precise, e.g., a task cannot be estimated to last 234.14 days.	+	* An ''estimate'' is an approximate calculation or judgement of the value, number, quantity, or extent of something. This definition implies that an estimate is a factual measure based on hard data and previous experience — hopes and wishes must be ignored when calculating it. The definition also implies that, being approximate, an estimate cannot be precise, e.g., a development task cannot be estimated to last 234.14 days.
	* A ''target'' is a statement of a desirable business objective, e.g., "The system must support at least 400 concurrent users."		* A ''target'' is a statement of a desirable business objective, e.g., "The system must support at least 400 concurrent users."
	* A ''commitment'' is a promise to deliver specified functionality at a certain level of quality by a certain date or event. One example could be "The search functionality will be available in the next release of the product."		* A ''commitment'' is a promise to deliver specified functionality at a certain level of quality by a certain date or event. One example could be "The search functionality will be available in the next release of the product."

-	Estimates, targets, and commitments are independent from each other, but targets and commitments should be based on sound estimates. As Steve McConnell notes: "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." Thus, the purpose of estimation is to make proper project management and planning possible, allowing the project stakeholders to make commitments based on realistic targets.	+	Estimates, targets, and commitments are independent from each other, but targets and commitments should be based on sound estimates. As Steve McConnell notes, "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." Thus, the purpose of estimation is to make proper project management and planning possible, allowing the project stakeholders to make commitments based on realistic targets.

	What the manager in the conversation above was really asking the programmer was to make a commitment based on an unstated target that the manager had in mind, ''not'' to provide an estimate. The next time you are asked to provide an estimate make sure everybody involved knows what they are talking about, and your projects will have a better chance of succeeding. Now it's time to learn some techniques....		What the manager in the conversation above was really asking the programmer was to make a commitment based on an unstated target that the manager had in mind, ''not'' to provide an estimate. The next time you are asked to provide an estimate make sure everybody involved knows what they are talking about, and your projects will have a better chance of succeeding. Now it's time to learn some techniques....

Kevlin at 18:04, 4 February 2009

Kevlin — Wed, 04 Feb 2009 18:04:20 GMT

←Older revision		Revision as of 18:04, 4 February 2009
Line 7:		Line 7:
	:''Project Manager:'' Can you give me an estimate of the time necessary to develop feature ''xyz''?		:''Project Manager:'' Can you give me an estimate of the time necessary to develop feature ''xyz''?
	:''Programmer:'' One month.		:''Programmer:'' One month.
-	:''Project Manager:'' That's far too long~~, we~~'ve only got one week!	+	:''Project Manager:'' That's far too long! We've only got one week.
	:''Programmer:'' I need at least three.		:''Programmer:'' I need at least three.
	:''Project Manager:'' I can give you two at most.		:''Project Manager:'' I can give you two at most.

Gasproni at 16:58, 4 February 2009

Gasproni — Wed, 04 Feb 2009 16:58:07 GMT

←Older revision		Revision as of 16:58, 4 February 2009
Line 14:		Line 14:
	The programmer, at the end, comes up with an "estimate" that matches what is acceptable for the manager. But since it is seen to be the programmer's estimate, the manager will hold him accountable to it. To understand what is wrong with this conversation we need three definitions — estimate, target, and commitment:		The programmer, at the end, comes up with an "estimate" that matches what is acceptable for the manager. But since it is seen to be the programmer's estimate, the manager will hold him accountable to it. To understand what is wrong with this conversation we need three definitions — estimate, target, and commitment:

-	* An ''estimate'' is an approximate calculation or judgement of the value, number, quantity, or extent of something. This definition implies that an estimate is a factual measure based on hard data and previous experience — hopes and wishes must be ignored when calculating it. It also implies that, being approximate, an estimate cannot be precise, e.g., a task cannot be estimated to last 234.14 days.	+	* An ''estimate'' is an approximate calculation or judgement of the value, number, quantity, or extent of something. This definition implies that an estimate is a factual measure based on hard data and previous experience — hopes and wishes must be ignored when calculating it. The definition also implies that, being approximate, an estimate cannot be precise, e.g., a task cannot be estimated to last 234.14 days.
	* A ''target'' is a statement of a desirable business objective, e.g., "The system must support at least 400 concurrent users."		* A ''target'' is a statement of a desirable business objective, e.g., "The system must support at least 400 concurrent users."
	* A ''commitment'' is a promise to deliver specified functionality at a certain level of quality by a certain date or event. One example could be "The search functionality will be available in the next release of the product."		* A ''commitment'' is a promise to deliver specified functionality at a certain level of quality by a certain date or event. One example could be "The search functionality will be available in the next release of the product."

Gasproni at 16:56, 4 February 2009

Gasproni — Wed, 04 Feb 2009 16:56:58 GMT

←Older revision		Revision as of 16:56, 4 February 2009
Line 14:		Line 14:
	The programmer, at the end, comes up with an "estimate" that matches what is acceptable for the manager. But since it is seen to be the programmer's estimate, the manager will hold him accountable to it. To understand what is wrong with this conversation we need three definitions — estimate, target, and commitment:		The programmer, at the end, comes up with an "estimate" that matches what is acceptable for the manager. But since it is seen to be the programmer's estimate, the manager will hold him accountable to it. To understand what is wrong with this conversation we need three definitions — estimate, target, and commitment:

-	* An ''estimate'' is an approximate calculation or judgement of the value, number, quantity, or extent of something. This definition implies that an estimate is a factual measure based on hard data and previous experience — hopes and wishes ~~have no place in~~ calculating it. It also implies that, being approximate, an estimate cannot be precise, e.g., a task cannot be estimated to last 234.14 days.	+	* An ''estimate'' is an approximate calculation or judgement of the value, number, quantity, or extent of something. This definition implies that an estimate is a factual measure based on hard data and previous experience — hopes and wishes must be ignored when calculating it. It also implies that, being approximate, an estimate cannot be precise, e.g., a task cannot be estimated to last 234.14 days.
	* A ''target'' is a statement of a desirable business objective, e.g., "The system must support at least 400 concurrent users."		* A ''target'' is a statement of a desirable business objective, e.g., "The system must support at least 400 concurrent users."
	* A ''commitment'' is a promise to deliver specified functionality at a certain level of quality by a certain date or event. One example could be "The search functionality will be available in the next release of the product."		* A ''commitment'' is a promise to deliver specified functionality at a certain level of quality by a certain date or event. One example could be "The search functionality will be available in the next release of the product."

Gasproni at 16:55, 4 February 2009

Gasproni — Wed, 04 Feb 2009 16:55:09 GMT

←Older revision		Revision as of 16:55, 4 February 2009
Line 14:		Line 14:
	The programmer, at the end, comes up with an "estimate" that matches what is acceptable for the manager. But since it is seen to be the programmer's estimate, the manager will hold him accountable to it. To understand what is wrong with this conversation we need three definitions — estimate, target, and commitment:		The programmer, at the end, comes up with an "estimate" that matches what is acceptable for the manager. But since it is seen to be the programmer's estimate, the manager will hold him accountable to it. To understand what is wrong with this conversation we need three definitions — estimate, target, and commitment:

-	* An ''estimate'' is an approximate calculation or judgement of the value, number, quantity, or extent of something. This definition implies that an estimate is ~~an objective~~ measure. It also implies that, being approximate, an estimate cannot be precise, e.g., a task cannot be estimated to last 234.14 days.	+	* An ''estimate'' is an approximate calculation or judgement of the value, number, quantity, or extent of something. This definition implies that an estimate is a factual measure based on hard data and previous experience — hopes and wishes have no place in calculating it. It also implies that, being approximate, an estimate cannot be precise, e.g., a task cannot be estimated to last 234.14 days.
	* A ''target'' is a statement of a desirable business objective, e.g., "The system must support at least 400 concurrent users."		* A ''target'' is a statement of a desirable business objective, e.g., "The system must support at least 400 concurrent users."
	* A ''commitment'' is a promise to deliver specified functionality at a certain level of quality by a certain date or event. One example could be "The search functionality will be available in the next release of the product."		* A ''commitment'' is a promise to deliver specified functionality at a certain level of quality by a certain date or event. One example could be "The search functionality will be available in the next release of the product."

Gasproni at 16:46, 4 February 2009

Gasproni — Wed, 04 Feb 2009 16:46:54 GMT

←Older revision		Revision as of 16:46, 4 February 2009
Line 20:		Line 20:
	Estimates, targets, and commitments are independent from each other, but targets and commitments should be based on sound estimates. As Steve McConnell notes: "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." Thus, the purpose of estimation is to make proper project management and planning possible, allowing the project stakeholders to make commitments based on realistic targets.		Estimates, targets, and commitments are independent from each other, but targets and commitments should be based on sound estimates. As Steve McConnell notes: "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." Thus, the purpose of estimation is to make proper project management and planning possible, allowing the project stakeholders to make commitments based on realistic targets.

-	What the manager in the conversation above was really asking the programmer was to make a commitment based on an unstated target that the manager had in mind, ''not'' to provide an estimate. The next time you are asked to provide an estimate make sure everybody involved knows what they are talking about, and ~~you may discover that~~ your projects ~~won't be late any more~~. Now it's time to learn some techniques....	+	What the manager in the conversation above was really asking the programmer was to make a commitment based on an unstated target that the manager had in mind, ''not'' to provide an estimate. The next time you are asked to provide an estimate make sure everybody involved knows what they are talking about, and your projects will have a better chance of succeeding. Now it's time to learn some techniques....

	By [[Giovanni Asproni]]		By [[Giovanni Asproni]]

Kevlin: Learn to estimate moved to Learn to Estimate

Kevlin — Tue, 03 Feb 2009 21:31:49 GMT

Learn to estimate moved to Learn to Estimate

←Older revision

Revision as of 21:31, 3 February 2009

Kevlin at 21:31, 3 February 2009

Kevlin — Tue, 03 Feb 2009 21:31:33 GMT

←Older revision		Revision as of 21:31, 3 February 2009
Line 1:		Line 1:
-	As a ~~developer~~ you need to be able to provide estimates to your managers, colleagues, and users for the tasks you need to perform, so that they will have a reasonably accurate idea of ~~what is necessary in terms of~~ time, costs, technology, and other resources, to achieve ~~the project~~ goals.	+	As a programmer you need to be able to provide estimates to your managers, colleagues, and users for the tasks you need to perform, so that they will have a reasonably accurate idea of the time, costs, technology, and other resources needed to achieve their goals.

-	~~In order to~~ learn how to estimate, it is obviously important to learn some estimation techniques. ~~However, first~~ of all, it is fundamental to learn what estimates are, and what they should be used ~~for—as~~ strange as it may seem, many developers and managers ~~don’t~~ really know this.	+	To learn how to estimate it is obviously important to learn some estimation techniques. First of all, however, it is fundamental to learn what estimates are, and what they should be used for — as strange as it may seem, many developers and managers don't really know this.

-	~~In fact, a typical conversation~~ between a project manager and a programmer ~~talking about estimates usually goes along the following lines~~	+	The following exchange between a project manager and a programmer is not untypical:
-	* PM: "Can you give me an estimate of the time necessary to develop feature xyz?"	+
-	* Programmer: "One month"	+
-	* PM: "That's far too long, we've got only one week!"	+
-	* Programmer: "I need at least three"	+
-	* PM: "I can give you two at most"	+
-	* Programmer: ~~"Deal!"~~	+

-	~~The programmer, at the end, comes up with~~ an ~~“estimate” that matches what is acceptable for the manager, but, since it is his~~ estimate, the ~~manager will hold him accountable for that~~. ~~To understand what is wrong with this conversation~~ we need three ~~definitions—estimate, target, and commitment~~.	+	:''Project Manager:'' Can you give me an estimate of the time necessary to develop feature ''xyz''?
		+	:''Programmer:'' One month.
		+	:''Project Manager:'' That's far too long, we've only got one week!
		+	:''Programmer:'' I need at least three.
		+	:''Project Manager:'' I can give you two at most.
		+	:''Programmer:'' Deal!

-	~~An estimate is an approximate calculation or judgement of~~ the ~~value~~, ~~number, quantity, or extent of something. This definition implies that~~ an estimate is ~~an objective measure~~. ~~It also implies that, being approximate, an~~ estimate ~~cannot be precise~~, ~~e.g~~., ~~a task cannot be estimated to last 234.14 days.~~	+	The programmer, at the end, comes up with an "estimate" that matches what is acceptable for the manager. But since it is seen to be the programmer's estimate, the manager will hold him accountable to it. To understand what is wrong with this conversation we need three definitions — estimate, target, and commitment:

-	A target is a statement of a desirable business objective, e.g.	+	* An ''estimate'' is an approximate calculation or judgement of the value, number, quantity, or extent of something. This definition implies that an estimate is an objective measure. It also implies that, being approximate, an estimate cannot be precise, e.g., a task cannot be estimated to last 234.14 days.
-	* The system must support at least 400 concurrent users	+	* A ''target'' is a statement of a desirable business objective, e.g., "The system must support at least 400 concurrent users."
		+	* A ''commitment'' is a promise to deliver specified functionality at a certain level of quality by a certain date or event. One example could be "The search functionality will be available in the next release of the product."

-	~~A commitment~~ is a ~~promise~~ to ~~deliver specified functionality at~~ a ~~certain level of quality by a certain date. One example could~~ be	+	Estimates, targets, and commitments are independent from each other, but targets and commitments should be based on sound estimates. As Steve McConnell notes: "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." Thus, the purpose of estimation is to make proper project management and planning possible, allowing the project stakeholders to make commitments based on realistic targets.
-	* The search functionality will be available in the ~~next release~~ of the ~~product~~.	+

-	~~Estimates, targets and commitments are independent from each other, but targets and commitments should be based on sound estimates, or, as Steve McConnell puts it:~~	+	What the manager in the conversation above was really asking the programmer was to make a commitment based on an unstated target that the manager had in mind, ''not'' to provide an estimate. The next time you are asked to provide an estimate make sure everybody involved knows what they are talking about, and you may discover that your projects won't be late any more. Now it's time to learn some techniques....
-	"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".	+
-	~~In other terms, the purpose of estimation is to make proper project management and planning possible, and allow the project stakeholders to make commitments based on realistic targets.~~	+
-		+
-	What the manager in the conversation above was really asking the programmer was to make a commitment based on an unstated target that the manager had in mind, not to provide an estimate. The next time you are asked to provide an estimate make sure everybody involved knows what they are talking about, and you may discover that your projects ~~won’t~~ be late ~~anymore~~. Now ~~it’s~~ time to learn some ~~techniques…~~	+

	By [[Giovanni Asproni]]		By [[Giovanni Asproni]]

Gasproni at 22:51, 28 January 2009

Gasproni — Wed, 28 Jan 2009 22:51:00 GMT

←Older revision		Revision as of 22:51, 28 January 2009
Line 26:		Line 26:

	What the manager in the conversation above was really asking the programmer was to make a commitment based on an unstated target that the manager had in mind, not to provide an estimate. The next time you are asked to provide an estimate make sure everybody involved knows what they are talking about, and you may discover that your projects won’t be late anymore. Now it’s time to learn some techniques…		What the manager in the conversation above was really asking the programmer was to make a commitment based on an unstated target that the manager had in mind, not to provide an estimate. The next time you are asked to provide an estimate make sure everybody involved knows what they are talking about, and you may discover that your projects won’t be late anymore. Now it’s time to learn some techniques…
		+
		+	By [[Giovanni Asproni]]
		+
		+
		+	This work is licensed under a [http://creativecommons.org/licenses/by/3.0/us/ Creative Commons Attribution 3]
		+
		+	Back to [[97 Things Every Programmer Should Know]] home page

Gasproni: New page: As a developer you need to be able to provide estimates to your managers, colleagues, and users for the tasks you need to perform, so that they will have a reasonably accurate idea of what...

Gasproni — Wed, 28 Jan 2009 22:49:37 GMT

New page: As a developer you need to be able to provide estimates to your managers, colleagues, and users for the tasks you need to perform, so that they will have a reasonably accurate idea of what...

New page

As a developer you need to be able to provide estimates to your managers, colleagues, and users for the tasks you need to perform, so that they will have a reasonably accurate idea of what is necessary in terms of time, costs, technology, and other resources, to achieve the project goals.

In order to learn how to estimate, it is obviously important to learn some estimation techniques. However, first of all, it is fundamental to learn what estimates are, and what they should be used for—as strange as it may seem, many developers and managers don’t really know this.

In fact, a typical conversation between a project manager and a programmer talking about estimates usually goes along the following lines
* PM: "Can you give me an estimate of the time necessary to develop feature xyz?"
* Programmer: "One month"
* PM: "That's far too long, we've got only one week!"
* Programmer: "I need at least three"
* PM: "I can give you two at most"
* Programmer: "Deal!"

The programmer, at the end, comes up with an “estimate” that matches what is acceptable for the manager, but, since it is his estimate, the manager will hold him accountable for that. To understand what is wrong with this conversation we need three definitions—estimate, target, and commitment.

An estimate is an approximate calculation or judgement of the value, number, quantity, or extent of something. This definition implies that an estimate is an objective measure. It also implies that, being approximate, an estimate cannot be precise, e.g., a task cannot be estimated to last 234.14 days.

A target is a statement of a desirable business objective, e.g.
* The system must support at least 400 concurrent users

A commitment is a promise to deliver specified functionality at a certain level of quality by a certain date. One example could be
* The search functionality will be available in the next release of the product.

Estimates, targets and commitments are independent from each other, but targets and commitments should be based on sound estimates, or, as Steve McConnell puts it:
"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".
In other terms, the purpose of estimation is to make proper project management and planning possible, and allow the project stakeholders to make commitments based on realistic targets.

What the manager in the conversation above was really asking the programmer was to make a commitment based on an unstated target that the manager had in mind, not to provide an estimate. The next time you are asked to provide an estimate make sure everybody involved knows what they are talking about, and you may discover that your projects won’t be late anymore. Now it’s time to learn some techniques…