paulghaddad · February 11, 2015 18:33
diff --git a/gistfile1.txt b/gistfile1.txt
 1. What's the difference between a commitment and an estimate?

 An estimate is the ability to place a value on the uncertainty of a future task to the best of one’s current knowledge and assessment. In contrast, a commitment is the promise to deliver or complete a task by a certain date. An estimate is simply a guess when the work can be completed; a commitment includes an estimate but also an explicit deadline when it will be done.

 2. How do you communicate the difference in conversation?

 When communicating with stakeholders, it is important to be explicit about estimates and commitments. When providing an estimate, you should state, "this is an estimate of how long the task will take, however, our team is not committing to completing it by a certain date." For commitments, stating a date when a task will be completed means it is actually a commitment.  It is especially important to be careful in communicating estimates, because they can be interpreted as commitments. The converse, making commitments appear as though they are estimates, doesn't have as large implications. 

 3. Why do business users need a commitment? How do you best fulfill their needs as a customer. 

 Business users need a commitment because they have other functions, such as marketing, that depend on having a feature completed by a specific date. Moreover, they are serving the needs of the only customer that matters to an organization: the actual, paying customer. To best fulfill their needs, it is important to be explicit about commitments, err on the side of pessimistic estimates, and break down tasks in as small chunks as possible. Following these practices means the estimates will be more accurate over time, helping both business and the "real" customers.
	1. What's the difference between a commitment and an estimate?

	An estimate is the ability to place a value on the uncertainty of a future task to the best of one’s current knowledge and assessment. In contrast, a commitment is the promise to deliver or complete a task by a certain date. An estimate is simply a guess when the work can be completed; a commitment includes an estimate but also an explicit deadline when it will be done.

	2. How do you communicate the difference in conversation?

	When communicating with stakeholders, it is important to be explicit about estimates and commitments. When providing an estimate, you should state, "this is an estimate of how long the task will take, however, our team is not committing to completing it by a certain date." For commitments, stating a date when a task will be completed means it is actually a commitment. It is especially important to be careful in communicating estimates, because they can be interpreted as commitments. The converse, making commitments appear as though they are estimates, doesn't have as large implications.

	3. Why do business users need a commitment? How do you best fulfill their needs as a customer.

	Business users need a commitment because they have other functions, such as marketing, that depend on having a feature completed by a specific date. Moreover, they are serving the needs of the only customer that matters to an organization: the actual, paying customer. To best fulfill their needs, it is important to be explicit about commitments, err on the side of pessimistic estimates, and break down tasks in as small chunks as possible. Following these practices means the estimates will be more accurate over time, helping both business and the "real" customers.