Mostrar mensagens com a etiqueta PERT. Mostrar todas as mensagens
Mostrar mensagens com a etiqueta PERT. Mostrar todas as mensagens

quarta-feira, 21 de junho de 2017

Estimation: PERT / Three Point Estimation Technique

The estimation technique in Agile is Planning Poker.
As for Waterfall, a combination of decomposition (WBS), PERT / 3 point estimation (weights sum up 6) and iterative reevaluation could be used.
What is exactly the 3 point estimation and PERT? Google says:
Quoting Tech Republic:
"PERT is an estimating technique that uses a weighted average of three numbers (see below) to come up with a final estimate.

  • The most pessimistic (P) case when everything goes wrong [also called "Worst Case Scenario"]
  • The most optimistic (O) case where everything goes right [also called "Best Case Scenario"]
  • The most likely (M) case given normal problems and opportunities [also called "Expected Case Scenario"]

The resulting PERT estimate is calculated as (O + 4M + P)/6. This is called a "weighted average" since the most likely estimate is weighted four times as much as the other two values. You'll notice that the final PERT estimate is moved slightly toward either the optimistic or pessimistic value - depending on which one is furthest from the most likely. Generally this ends up moving the final estimate toward the worst case, since the worst case value tends to be further out from the most likely that the optimistic number."

Some tools (like MS Project) will allow you to do some What If scenarios, by defining different weights  (above the weights are 1, 4, 1, and all weights should sum up to 6). What if it is most probable that mostly everything goes wrong (could be tested with weights like 1, 1, 4). What if mostly everything goes right (4, 1, 1)?


quinta-feira, 28 de julho de 2016

Estimation Process and related artifacts

Your QMS could include a process on estimation (that presents the estimation techniques and the associated activities to be executed in order to produce the final estimation sheets that are input for ROMs, Proposals, Change Requests, ...).

One example (INTERNAL):


Some common artifacts include templates and models to help you estimating (INTERNAL, use the QMS Portal with the doc id enclosed in double quotes):

  • Estimation form (template): CSW-QMS-2011-TPL-02102-estimation-sum-up.xls (now a xltx)
  • Planning Poker form (template): CSW-QMS-2015-TPL-02398-planning-poker-estimation.xltx
  • Effort Per Phase Model: CSW-QMS-2009-DOC-04974-effort-model-2014-baseline-data4all.xlsx
  • Safety Critical Estimation Model: CSW-QMS-2014-DOC-01296-asd-estimation-model.xlsx
  • Estimation @ CRITICAL Software - Study on the Estimation Process for CRITICAL Software Projects: CSW-ESTIMATE-2009-PCS-00707-estimation-process.doc
PS. If you're interested in estimation models, google for them. They are very dependent on the business you're working on although there are some attempts to generalize them.