mcpField
E
estimating-work

estimating-work

github.com/dralgorhythmDevelopment12859 installsUpdated 14w ago
Repository

About estimating-work

estimating-work is a skill for teams estimating software work. It outlines relative sizing, estimation methods, calibration, and common pitfalls.

Key features

  1. 01Story point and T-shirt sizing
  2. 02Planning Poker steps
  3. 03Three-point estimate formula
  4. 04Reference-story calibration
  5. 05Common estimation pitfalls

Use cases

  1. 01Sizing a backlog item
  2. 02Comparing estimates across a team
  3. 03Revising estimates after scope changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dralgorhythm/claude-agentic-framework --skill estimating-work

After installing, type/estimating-workin Claude Code to confirm it loaded.

Details

From the project README

Estimating Work

Estimation Approaches

Story Points

Relative complexity, not time.

PointsComplexity
1Trivial, well understood
2Simple, minor unknowns
3Moderate complexity
5Complex, some unknowns
8Very complex, significant unknowns
13Extremely complex, many unknowns
21+Too big, needs decomposition
T-Shirt Sizing

For high-level estimates.

SizeRelative Effort
XSHours
S1-2 days
M3-5 days
L1-2 weeks
XL2-4 weeks

Estimation Factors

Consider:

  • Complexity: How difficult is the problem?
  • Uncertainty: How much is unknown?
  • Effort: How much work is involved?
  • Risk: What could go wrong?

Estimation Techniques

Planning Poker
  1. Present the task
  2. Everyone selects estimate privately
  3. Reveal simultaneously
  4. Discuss outliers
  5. Re-estimate if needed
Three-Point Estimation
Expected = (Optimistic + 4×Likely + Pessimistic) / 6
Reference Stories

Keep calibration stories:

  • "This 3-point story took 2 days"
  • "This 8-point story took a week"

Common Pitfalls

  • Anchoring: First estimate biases others
  • Optimism: Underestimating unknowns
  • Scope Creep: Original estimate doesn't match final scope
  • Ignoring Overhead: Code review, testing, deployment

Tips

  1. Estimate in ranges, not points
  2. Include buffer for unknowns
  3. Track actual vs. estimated
  4. Re-estimate when scope changes
  5. Don't estimate in hours (use relative sizing)

Comments

Markdown supported