estimation-sizing-thinking

Generate directional QA sizing and timelines with PERT estimation.

Updated Aug 27, 2026

Search Tags:#planning #qa #governance #sizing #rfp #estimate #pert

Ready to run

npx skills add https://github.com/sandeep-singh-79/QE_RFP_OS_Agents_Skills --skill estimation-sizing-thinking

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: estimation-sizing-thinking
Source: https://github.com/sandeep-singh-79/QE_RFP_OS_Agents_Skills/tree/main/.claude/skills/estimation-sizing-thinking
Command: npx skills add https://github.com/sandeep-singh-79/QE_RFP_OS_Agents_Skills --skill estimation-sizing-thinking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides directional, defensible sizing and timelines for QA initiatives by accounting for enablement effort, execution effort, test complexity, scale, ramp-up, and uncertainty. This helps governance and procurement processes ensure estimates are credible and avoid post-award credibility loss.

Core Features & Use Cases

Separate Enablement vs Execution: Always differentiate enablement (front-loaded) from execution (post enablement) to maintain credibility and avoid optimistic schedules.
Apply Test Complexity Matrix: Classify major test groups and adjust for high-complexity items to reflect true effort and maintenance risk.
Ramp-Up and Scale Adjustments: Include onboarding, domain learning, tool familiarization, and cross-system dependencies; adjust for pilot vs enterprise scope.
Guardrails and Sub-Skills: Use Scope Completeness Validator, PERT estimation, and KPI baseline processes to ensure defensible sizing.

Quick Start

Start by separating enablement from execution, classify test complexity, and run a PERT-based sizing pass to produce a defensible estimate.

Frequently Asked Questions about estimation-sizing-thinking

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

FAQPage Schema

How do I create defensible QA sizing and timelines for an RFP response?▼

Defensible QA sizing separates enablement effort from execution, applies a test complexity matrix, and uses PERT estimation to produce credible timelines that withstand governance and procurement scrutiny.

What is the best way to estimate QA effort for enterprise scale versus a pilot project?▼

Estimating QA effort for enterprise scale requires adjusting for ramp-up, domain learning, tool familiarization, and cross-system dependencies, ensuring pilot sizing does not unrealistically dictate full enterprise timelines.

Why does my QA transformation roadmap lose credibility after project award?▼

QA transformation roadmaps lose credibility when estimates fail to account for front-loaded enablement effort, test complexity, and ramp-up uncertainty, leading to overly optimistic schedules that collapse during execution.

How do I apply PERT estimation to QA planning?▼

Applying PERT estimation to QA planning involves running a sizing pass that evaluates scope completeness and uncertainty, producing directional timelines that remain defensible under governance review.

When do I need to separate enablement effort from execution effort in QA estimates?▼

You must separate enablement from execution effort whenever producing QA estimates for feasibility assessments or RFPs, preventing optimistic schedules and maintaining credibility throughout the project lifecycle.

Can I use KPI baselines to validate QA sizing for governance processes?▼

Yes, using KPI baselines as a guardrail validates QA sizing by mapping scope completeness and execution estimates against historical performance, ensuring directional timelines remain defensible during governance reviews.