Projects typically involve many dynamic aspects, yet they're often constrained by finite conditions. These contradictory forces make it very difficult to determine with pinpoint accuracy the time and effort required. By using a set of proactive estimating techniques to scope, plan, and constrain your project conditions, you can dramatically improve your estimating practices, reduce and mitigate risks, and increase your project success rate.

Do you excel at predicting the time, funding, and resources your projects will require?

Whether your company aims to develop a new product or service, update an existing system, or launch a new Web site, these undertakings will require people, schedules, funding, resources, requirements, testing, revising, implementation, evaluation, and many other elements.

You may have seen this phenomenon already: projects are risk magnets. Why is that?

The possible reasons include the fact that projects typically involve many dynamic aspects, yet they're often constrained by finite conditions. These opposing forces make it very challenging to identify with great accuracy the time and effort required, and can result in many budget and schedule "collisions" during the life of the project.

When my clients or colleagues invariably ask, "How long do you think this effort might take?" I usually experience a knee-jerk reaction. Instinctively, a part of my brain that once excelled at solving math problems on timed quizzes goes into overdrive. "I know the answer!" it screams.

Yet, unless that project or task is something I've performed many times before - under very similar conditions each time, and with good records of my actual hours spent - providing an accurate estimate can be quite elusive. As I strive to imagine all of the stages and steps of a process, as well as fathom the unknown variables or things that could go awry, it's no wonder that I hardly ever guess 100% correctly, particularly for new endeavours.

Estimating Techniques Can Help Manage Risks

Did you know that estimating is an invaluable tool for anticipating and managing these project uncertainties?

When we can identify our cost and schedule requirements with relative precision, it reduces the risk of running out of time, resources, and budget during a project.

Yet with all of the emphasis we place on creating accurate estimates and bids, we still seem to have difficulty developing realistic predictions of our time and effort. If we look carefully at the evidence, I believe we'll find three basic, underlying clues to the reasons for our challenges with estimating:

  1. The presence of hidden or unknown variables that are difficult or impossible to anticipate, and sometimes even more difficult to resolve.
  2. Our often-idealistic views of our own capabilities. We frequently believe that we can achieve much more than is possible in the available time.
  3. A strong human desire to please other people by telling them what they want to hear. (After all, who wants to be the bearer of bad news?)

12 Tips for Increasing Estimating Accuracy

To remedy these shortcomings, below are 12 ideas for boosting the accuracy of your estimates:

  1. Maintain an ongoing "actual hours" database of the recorded time spent on each aspect of your projects. Use the data to help estimate future projects and identify the historically accurate buffer time needed to realistically perform the work.
  2. Create and use planning documents, such as specifications and project plans.
  3. Perform a detailed task analysis of the work to be performed.
  4. Use a "complexity factor" as a multiplier to determine whether a pending project is more or less complex than a previous one.
  5. Use more than one method to arrive at an estimate, and look for a midpoint among all of them.
  6. Identify a set of caveats, constraints, and assumptions to accompany your calculations, which would bound the conditions under which your estimates would be meaningful. (Anything that occurs outside of those constraints would be considered out of scope.)
  7. If the proposed budget or schedule seems inadequate to do the work, propose adjusting upward or downward one or more of the four project scoping criteria: cost, schedule, quality, and features.
  8. Consider simpler or more efficient ways to organise and perform the work.
  9. Plan and estimate the project rollout from the very beginning so that the rollout won't become a chaotic scramble at the end. For instance, you could propose using a minimally disruptive approach, such as a pilot programme or a phased implementation.
  10. In really nebulous situations, consider a phase-based approach, where the first phase focuses primarily on requirements gathering and estimating.
  11. Develop contingency plans by prioritising the deliverables right from the start into "must-have" and "nice-to-have" categories.
  12. Refer to your lessons-learned database for "20:20 foresight" on new projects, and incorporate your best practices into future estimates.

In conclusion, by using a set of proactive estimating techniques to scope, plan, and constrain your project conditions, you can dramatically improve your estimating practices, reduce and mitigate risks, and greatly increase your project success rate!

12 Tips for Accurate Project Estimating的更多相关文章

  1. .NET 5学习笔记(12)——WinUI 3 Project Reunion 0.5

    2021年3月的时候,Win UI 3终于来到了第一个稳定的支持版本,可用于创建发布到Micosoft Store的应用.据某软的说法,这个叫WinUI 3 Project Reunion 0.5的版 ...

  2. A Guide to Creating a Quality Project Schedule

    Successful projects start with a good quality project schedule. Creating a schedule is one of the fi ...

  3. Deploy .Net project automatically with MsBuild and MsDeploy (1)

    Q: How to change parameter values in configuration files dynamically In the first section http://www ...

  4. maven build时报错Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test

    [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ ...

  5. maven install时报错 Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test)

    今天在一个maven项目上执行maven install命令的时候一直报错,错误信息如下: [INFO] ----------------------------------------------- ...

  6. git 打包报错:Maven Build时提示:Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test

    1.使用git 升级 服务命令 mvn  deploy -e 之后报错: Failed to execute goal org.apache.maven.plugins:maven-surefire- ...

  7. P6 Professional Installation and Configuration Guide (Microsoft SQL Server Database) 16 R1

    P6 Professional Installation and Configuration Guide (Microsoft SQL Server Database) 16 R1       May ...

  8. usbip install

    # README for usbip-utils## Copyright (C) 2011 matt mooney <mfm@muteddisk.com>#               2 ...

  9. elasticsearch容量规划

    https://docs.bonsai.io/article/123-capacity-planning Capacity Planning Capacity planning is the proc ...

随机推荐

  1. 密码等级:至少包含字母、大小写数字、字符中的两种 JS实现方案

    前言 密码,如果设置的太简单,很容易就被攻破,所以很多网站将密码设置的要求设置的挺严格,一般是字母.数字.字符3选2,区分大小写.对于设置得太简单的密码,予以错误提示.或者予以密码等级(低中高)显示, ...

  2. 解决Windows Server 2003不认U盘或移动硬盘的问题

    1.进入命令提示符环境(也就是DOS) 2.进入DISKPART程序 3.输入AUTOMOUNT ENABLE指令 4.OK,下次USB硬盘接入后就可以像XP 一样自动装载了.

  3. TYVJ P1073 加分二叉树 Label:区间dp

    背景 NOIP2003 提高组 第三道 描述 设一个n个节点的二叉树tree的中序遍历为(l,2,3,…,n),其中数字1,2,3,…,n为节点编号.每个节点都有一个分数(均为正整数),记第j个节点的 ...

  4. HDU 4604 Deque(最长上升子序)

    题目链接 本来就对N*log(N)算法不大会....然后各种跪了,求出最长不下降+最长不上升-最少相同元素.求相同元素,用二分求上界搞的.代码里4个二分.... #include <cstdio ...

  5. 连接access的语句

    using System;using System.Collections.Generic;using System.ComponentModel;using System.Data;using Sy ...

  6. Windows下PHPUnit安装

    收藏的介绍地址 1.手动方式安装示例:http://blog.sina.com.cn/s/blog_5d3dc0110100ghlo.html2.通过Pear安装示例:blog.sina.com.cn ...

  7. appSetting 在单独文件的读写

    #region appSetting /// <summary> /// 设定 appSetting /// </summary> /// <param name=&qu ...

  8. Html - 图片

    千图网 http://www.58pic.com/ 图标宝 http://ico.58pic.com/ 瓢城Web俱乐部 http://www.ycku.com/demo/

  9. [转]超详细图解:自己架设NuGet服务器

    本文转自:http://diaosbook.com/Post/2012/12/15/setup-private-nuget-server 超详细图解:自己架设NuGet服务器 汪宇杰          ...

  10. java数据类型定义与输出

    JAVA数据类型分基本数据类型和引用数据类型. 一.基本数据类型 Java里面包含8个基本数据类型,分别是: boolean.byte.char.short.int.float.douboe.long ...