Calculate three-point task duration estimates

Convert optimistic, most likely, and pessimistic day estimates into PERT weighted averages and standard deviations. Use it for project planning.

You getA Markdown calculation table with columns, total Estimated Duration and estimation Confidence Commentary

Prompt

Prompt
Act as a project estimation expert. Calculate three-point PERT estimates for the list of tasks provided below.

Follow these rules:
- Calculate the Expected Duration (E) for each task using the standard formula: E = (Optimistic + 4 * Most Likely + Pessimistic) / 6.
- Calculate the Task Standard Deviation (SD) using: SD = (Pessimistic - Optimistic) / 6.
- Round all calculated values to one decimal place.
- Sum the expected durations to show the total expected timeline for the entire batch.

Output format:
1. A Markdown calculation table with columns: Task Name, Optimistic (O), Most Likely (M), Pessimistic (P), Expected Duration (E), Standard Deviation (SD)
2. Total Estimated Duration (sum of E values in days)
3. Estimation Confidence Commentary (noting which task carries the widest variance and highest delivery risk)

My raw tasks with their three time estimates are below:

Example output

Example for: five core tasks for a database migration sprint

1. Task Duration Calculation Table
Task NameOptimistic (O)Most Likely (M)Pessimistic (P)Expected Duration (E)Standard Deviation (SD)
Database schema backup and validation1.02.04.02.2 days0.5 days
ETL script data transformation3.06.014.06.8 days1.8 days
User data migration run2.03.08.03.7 days1.0 days
Integration smoke tests & sanity check1.02.03.02.0 days0.3 days
DNS cutover & production switch0.51.03.01.3 days0.4 days
2. Total Estimated Duration
  • Total Expected Project Duration: 16.0 working days
3. Estimation Confidence Commentary
  • Highest Uncertainty: 'ETL script data transformation' exhibits the highest standard deviation (1.8 days) with a range spread of 11 days between optimistic and pessimistic inputs. This task represents 42% of the overall schedule risk.
  • High-Confidence Tasks: 'Integration smoke tests' and 'DNS cutover' show narrow distributions (SD 0.3-0.4 days), indicating predictable execution with low exposure to unexpected delays.
  • Recommended Action: Focus technical spiking and pre-migration testing on data transformation scripts prior to cutover to compress the pessimistic bound.
Written by AI from this prompt. Your results will vary.

In ChatGPT, Claude, or Gemini, paste the prompt followed by your tasks and their 3 estimate numbers (e.g., Task 1: 3, 5, 12 days). Ask as a follow-up: 'What is the 95% confidence interval for this overall project timeline?'

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Project Management
Project Management

Diplomatic pushback against scope creep

Draft a polite, professional response that acknowledges an out-of-scope request, explains project tradeoffs, and offers clear paths forward.

Project Management

Audit a RACI chart for split accountability

Identify dangerous governance flaws, duplicate owners, and delivery bottlenecks in an existing RACI matrix. Use this before launching high-stakes projects.