estimation

Calculate PERT estimates and adjust for risk in software engineering.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/chavangorakh1999/sde-skills --skill estimation-chavangorakh1999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: estimation
Source: https://github.com/chavangorakh1999/sde-skills/tree/main/sde-execution/skills/estimation
Command: npx skills add https://github.com/chavangorakh1999/sde-skills --skill estimation-chavangorakh1999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps software teams overcome the inherent uncertainty in estimating engineering effort, providing structured methods to arrive at more reliable estimates and communicate risks effectively.

Core Features & Use Cases

  • Three-Point Estimation (PERT): Calculate optimistic, expected, and pessimistic estimates to derive a weighted average and confidence interval.
  • Risk Factor Adjustment: Incorporates common risks like new technology or unclear requirements to adjust estimates.
  • Cone of Uncertainty: Illustrates how estimate accuracy improves with project clarity.
  • Story Point Calibration: Provides guidance on using story points and relating them to time.
  • Velocity Tracking: Uses "yesterday's weather" to predict future team capacity.
  • Use Case: When planning a new feature, use this Skill to get a PERT estimate, identify potential risks, and determine a realistic sprint commitment based on historical team velocity.

Quick Start

Use the estimation skill to estimate the effort for implementing Redis caching for the product catalog, with optimistic=2 days, expected=4 days, and pessimistic=8 days.

Frequently Asked Questions about estimation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I estimate software engineering effort when project requirements are uncertain?

Software engineering effort estimation uses the Cone of Uncertainty to illustrate how accuracy improves with project clarity, combining PERT analysis and risk factor adjustments to help teams make better decisions on scope and timelines as details emerge.

How do I calculate a PERT estimate for a new software feature?

Story point calibration provides guidance on using story points and relating them to time, while velocity tracking uses historical team capacity, or yesterday's weather, to predict future sprints and determine realistic sprint commitments.

Can I use story points and velocity tracking to determine realistic sprint commitments?

Yes, you can use story point calibration to relate story points to time, and apply velocity tracking using yesterday's weather to predict future team capacity and set realistic sprint commitments for software development.

How do I adjust project estimates for risks like new technology or unclear requirements?

To adjust project estimates for risks like new technology or unclear requirements, apply risk factor adjustments to your baseline calculation, modifying the expected effort to account for specific project uncertainties and improve timeline reliability.