Estimaciones (2)

Luego de un primer post sobre el tema, sigo desarrollando.

En el libro Software Estimation (Demystifying the black art), Steve McConnell plantea una distinción crucial que de hecho ha despertado discusión con algunos colegas en Google Plus:

“Here is a dictionary definition of estimate: 1. A tentative evaluation or rough calculation. 2. A preliminary calculation of the cost of a project. 3. A judgment based upon one’s impressions; opinion. (Source: The American Heritage Dictionary, Second College Edition, 1985.)”

…

“Strictly speaking, the dictionary definition of estimate is correct: an estimate is a prediction of how long a project will take or how much it will cost. But estimation on software projects interplays with business targets, commitments, and control.”

Según el autor un objetivo es

“..a statement of a desirable business objective.”

Y respecto a un compromiso:

“While a target is a description of a desirable business objective, a commitment is a promise to deliver defined functionality at a specific level of quality by a certain date. A commitment can be the same as the estimate, or it can be more aggressive or more conservative than the estimate. In other words, do not assume that the commitment has to be the same as the estimate; it doesn’t.”

La estimación como los objetivos de negocio son elementos necesarios para poder establecer compromisos.

Seguimos pensando..

Update: Podes seguir leyendo sobre estimaciones aquí.