0:00
Have you ever had to estimate the
0:01
duration or cost of a project activity
0:04
and wondered what if things go wrong or
0:06
what if they go better than expected?
0:09
How do I factor in that uncertainty?
0:12
Hi, I'm Andrew from PM Aspirant. If
0:16
you're new to the channel, welcome and
0:17
don't forget to subscribe for more
0:19
project management tips. Today, we're
0:22
going to cover an essential project
0:24
management tool, threepoint estimating.
0:27
Whether you're estimating costs,
0:29
durations, or resources, this technique
0:31
allows you to account for uncertainty by
0:34
considering multiple scenarios. At its
0:37
core, threepoint estimating provides
0:39
more realistic estimates by accounting
0:41
for three possible outcomes. One,
0:44
optimistic, the best case scenario where
0:47
everything goes smoothly without any
0:49
delays or issues. Two, pessimistic, the
0:53
worst case scenario where significant
0:55
challenges arise causing delays or
1:00
Three, most likely the scenario that's
1:03
most probable, assuming normal
1:04
conditions with minor variations.
1:07
By considering these three
1:09
possibilities, you develop a more
1:11
complete picture of what could happen,
1:13
which helps in managing uncertainty and
1:15
preparing more accurate estimates. You
1:18
might be thinking, why bother with three
1:20
estimates when I can just pick one?
1:22
While singleoint estimates are quicker,
1:25
they don't account for the
1:26
unpredictability of real world projects.
1:29
Threepoint estimating ensures you
1:31
consider different potential outcomes.
1:34
Reducing the risk of under or
1:36
overestimating your project's needs. For
1:39
instance, relying solely on an
1:41
optimistic estimate could lead to a too
1:43
tight schedule or budget, while focusing
1:45
only on the pessimistic side may lead to
1:48
unnecessary buffers that impact
1:50
efficiency. Threepoint estimating helps
1:54
you strike a balance. Now, let's talk
1:57
about how to calculate threepoint
1:59
estimates. There are two commonly used
2:01
methods, the simple average and the per
2:04
method. Both of these help you arrive at
2:07
an expected estimate, but they weigh the
2:09
different scenarios slightly
2:11
differently. The simple average, also
2:14
known as the triangular distribution
2:16
method, gives equal weight to all three
2:18
estimates: optimistic, most likely, and
2:21
pessimistic. You simply add them up and
2:24
divide by three. This method assumes
2:26
that each outcome, whether optimistic,
2:29
most likely, or pessimistic, has an
2:31
equal chance of happening. It's
2:33
straightforward and works well when you
2:35
don't want to favor any particular
2:37
scenario over the others. Now, let's
2:40
dive into the per method. PER stands for
2:42
program evaluation and review technique
2:45
and it's a bit more refined. In this
2:48
method, we recognize that the most
2:50
likely estimate is usually more reliable
2:53
and therefore should carry more weight.
2:56
So instead of giving all three estimates
2:58
equal weight, the per method gives the
3:00
most likely estimate four times the
3:03
weight of the other two. In this
3:05
formula, the most likely estimate has a
3:08
higher influence on the final result
3:10
because it's assumed that it's the
3:12
outcome that will happen most
3:13
frequently. This approach leads to a
3:15
more balanced estimate that's closer to
3:18
what is expected in reality. So why use
3:21
the per formula? The per method is
3:23
especially helpful when there's more
3:25
confidence in the most likely scenario,
3:27
but you still want to account for risk
3:29
and uncertainty on either end. You can
3:32
apply threepoint estimating in various
3:34
aspects of project management, such as
3:38
cost estimating. Use it when you need to
3:40
estimate how much a project will cost
3:43
while accounting for potential
3:45
fluctuations in price or scope. Schedule
3:48
estimating is also useful for estimating
3:50
activity durations where there could be
3:53
delays or faster than expected progress.
3:56
Risk management. Since this technique
3:59
inherently considers uncertainty, it's
4:01
great for managing risks by providing a
4:03
range of potential outcomes. You'll
4:06
typically use threepoint estimating
4:08
during processes like estimate activity
4:10
durations, estimate costs, and estimate
4:13
activity resources. So once you have
4:16
your threepoint estimate, how do you
4:18
interpret it? The key lies in the range
4:22
between your optimistic and pessimistic
4:24
estimates. This range tells you a lot
4:26
about the level of uncertainty or risk
4:29
involved in the task or activity. A wide
4:32
range between the optimistic and
4:34
pessimistic values indicates high
4:36
uncertainty. This means you should be
4:38
cautious as there is a greater chance
4:40
that things could go wrong or there are
4:42
unknown factors at play. A narrow range
4:45
suggests that you have higher confidence
4:47
in the estimate. The smaller gap between
4:49
the best and worst case scenarios means
4:51
there's less variability and less risk.
4:54
This range is critical for project
4:56
managers because it helps in decisionm.
4:59
For example, if you see a wide range in
5:01
your estimates, you might want to plan
5:03
for additional contingency or
5:05
investigate the risks further. Why is
5:07
this technique so valuable? Let's cover
5:10
a few of its main benefits. One,
5:12
improved accuracy. By considering
5:15
optimistic, pessimistic, and most likely
5:17
outcomes, you get a more realistic
5:19
estimate that's better suited for
5:21
dealing with uncertainty. Two, risk
5:24
identification. The range between the
5:26
optimistic and pessimistic values gives
5:29
insight into the level of risk. The
5:31
wider the range, the more uncertain the
5:33
task is likely to be. Three, reduce
5:36
bias. This method forces you to think
5:39
about both the best and worst case
5:41
scenarios, reducing the likelihood of
5:44
overly optimistic or pessimistic
5:46
estimates. It helps in creating more
5:49
balanced, unbiased project forecasts. As
5:52
a project manager, your role in this
5:54
process is critical. You're responsible
5:57
for guiding the team in providing
5:59
realistic estimates for all three
6:01
scenarios: optimistic, pessimistic, and
6:05
most likely. You also need to ensure
6:07
that team members consider all relevant
6:09
risks, assumptions, and constraints.
6:12
This prevents the team from creating
6:14
overly optimistic or unrealistic
6:16
estimates, which can lead to project
6:18
delays or budget overrun. Finally,
6:21
you'll use these estimates to create a
6:23
more reliable project schedule and
6:25
budget, helping ensure that your project
6:28
stays on track. As helpful as it is,
6:30
threepoint estimating isn't perfect.
6:33
One, subjectivity. The estimates for
6:35
optimistic, pessimistic, and most likely
6:38
scenarios can be subjective, relying
6:40
heavily on the experience and judgment
6:42
of the estimators. This can sometimes
6:45
lead to inaccuracies.
6:47
Two, time consuming since it requires
6:49
the team to create three estimates for
6:52
every task or activity. Threepoint
6:54
estimating can be more timeconuming than
6:57
simpler estimation methods. For large or
6:59
complex projects, this added complexity
7:02
might not always be practical. Let's
7:04
take a look at an example. Here is the
7:07
scenario. A project manager is
7:10
estimating the duration of a task. The
7:13
optimistic duration is 4 days. The
7:15
pessimistic duration is 10 days and the
7:18
most likely duration is 7 days. What is
7:22
the expected duration using the per
7:25
formula? Using the per method, the
7:28
estimate is equal to 4 the optimistic
7:31
duration plus 4 * 7 the likely duration
7:34
+ 10 the pessimistic duration / 6. This
7:39
becomes 4 + 28 + 10 / 6. This is equal
7:45
to 42 / 6 and the result is 7 days. In
7:51
summary, threepoint estimating is a
7:53
powerful tool for project managers to
7:55
account for uncertainty, improve
7:58
accuracy, and manage risk in project
8:00
estimates. Mastering this technique will
8:03
help you create more reliable project
8:06
plans. If you find this video helpful,
8:09
make sure to give it a thumbs up and
8:11
don't forget to subscribe to PM Aspirant
8:14
for more project management insights so
8:16
you will be updated when we release new
8:18
videos. Thanks for watching and I'll see
8:21
you in the next video.