12 Tips for Accurate Project Estimating
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:
- The presence of hidden or unknown variables that are difficult or impossible to anticipate, and sometimes even more difficult to resolve.
- Our often-idealistic views of our own capabilities. We frequently believe that we can achieve much more than is possible in the available time.
- 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:
- 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.
- Create and use planning documents, such as specifications and project plans.
- Perform a detailed task analysis of the work to be performed.
- Use a "complexity factor" as a multiplier to determine whether a pending project is more or less complex than a previous one.
- Use more than one method to arrive at an estimate, and look for a midpoint among all of them.
- 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.)
- 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.
- Consider simpler or more efficient ways to organise and perform the work.
- 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.
- In really nebulous situations, consider a phase-based approach, where the first phase focuses primarily on requirements gathering and estimating.
- Develop contingency plans by prioritising the deliverables right from the start into "must-have" and "nice-to-have" categories.
- 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的更多相关文章
- .NET 5学习笔记(12)——WinUI 3 Project Reunion 0.5
2021年3月的时候,Win UI 3终于来到了第一个稳定的支持版本,可用于创建发布到Micosoft Store的应用.据某软的说法,这个叫WinUI 3 Project Reunion 0.5的版 ...
- 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 ...
- 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 ...
- maven build时报错Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test
[INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ ...
- maven install时报错 Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test)
今天在一个maven项目上执行maven install命令的时候一直报错,错误信息如下: [INFO] ----------------------------------------------- ...
- 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- ...
- 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 ...
- usbip install
# README for usbip-utils## Copyright (C) 2011 matt mooney <mfm@muteddisk.com># 2 ...
- elasticsearch容量规划
https://docs.bonsai.io/article/123-capacity-planning Capacity Planning Capacity planning is the proc ...
随机推荐
- Java中的HashTable详解
Hashtables提供了一个很有用的方法可以使应用程序的性能达到最佳. Hashtables(哈 希表)在计算机领域中已不 是一个新概念了.它们是用来加快计算机的处理速度的,用当今的标准来处理,速度 ...
- Vim 学习资料
VIM中文手册 简明 Vim 练级攻略 所需即所获:像 IDE 一样使用 vim
- 冒泡排序:一百以内十个随机数放入数组排序并打印<
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/ ...
- ThinkPHP添加模板时,犯的三个错
错误一:低级错误,将n打成看m,如图1 图1 这个找错,花了我将近2小时.扫了好几遍与之相关的代码,上网查了好些. 错误二:这个算是个低能的高级错误了.具体模板显示的效果如图2 图2 只要将相对地址及 ...
- javascript中的function
function / 对象 所有的变量和方法名的:以字母,$ _开头其他随便,尽量使用英文字母命名,见名知意注意点:不允许使用关键字定义变量和方法的名称====函数即方法,方法即函数====百度:ja ...
- SqlParameter 基本用法
因为通过SQL 语句的方式,有时候存在脚本注入的危险,所以在大多数情况下不建议用拼接SQL语句字符串方式,希望通过SqlParameter实现来实现对数据的操 作,针对SqlParameter的方式我 ...
- VSS错误自动修复
公司项目开发源代码管理一直用vss,从vss6.0用到vss8.0(vss2005),在近两年的试用中碰到一些大大小小的问题:1:vss服务迁移,这个比较好办,直接将整个vss目录拷贝过去,加上相应的 ...
- 序列化各个类型成JSON XML实例
LitJson组件序列化请参考http://www.cnblogs.com/leee/p/4437230.html XML序列化请参考http://www.cnblogs.com/leee/p/424 ...
- thrift
环境准备: 1.下载window版本的thrift编译器 2.下载idea的thirft插件 3.设置thrift编译工具为:步骤1下载的编译器 4.编写thrift文件 namespace java ...
- Nginx 配置 Basic 认证
/* * 环境:LNMP(CentOS 6.6 + Nginx 1.8.0) */ 在 Nginx 下配置 Basic 认证需要依靠 Nginx 的 http_auth_basic_module 模块 ...