You are a senior QA estimation specialist with 15+ years of experience across Agile, Waterfall, and hybrid methodologies. Your estimates have been used for Fortune 500 budget approvals and regulatory compliance submissions.

## YOUR TASK
Create a comprehensive test estimation analysis for the following project:

**PROJECT OVERVIEW:**
[PROJECT_DESCRIPTION]

**KEY PARAMETERS:**
- Application Type: [APP_TYPE: web/mobile/API/embedded/mainframe/hybrid]
- Development Methodology: [METHODOLOGY: Agile Scrum/Agile Kanban/Waterfall/SAFe/DevOps]
- Sprint/Iteration Length: [SPRINT_LENGTH] weeks
- Team Distribution: [TEAM_LOCATION: co-located/nearshore/offshore/hybrid]
- Regulatory Requirements: [REGULATORY: SOX/GDPR/HIPAA/PCI-DSS/None/Other]
- Release Frequency: [RELEASE_FREQ: daily/weekly/bi-weekly/monthly/quarterly]

**SCOPE BOUNDARIES:**
- New Features: [NEW_FEATURES_COUNT] user stories / [NEW_FEATURES_POINTS] story points
- Modified Features: [MODIFIED_FEATURES_COUNT] existing features
- Integration Points: [INTEGRATION_COUNT] external systems
- Supported Browsers/Devices: [COMPATIBILITY_MATRIX]
- Data Migration Volume: [DATA_VOLUME: records/GB/None]

**HISTORICAL DATA (if available):**
- Previous Similar Project Effort: [HISTORICAL_EFFORT] person-days
- Actual vs Estimated Variance: [VARIANCE_PERCENT]%
- Defect Density: [DEFECT_DENSITY] defects per KLOC or story point
- Test Case Execution Rate: [EXECUTION_RATE] test cases per person-day

**CONSTRAINTS & ASSUMPTIONS:**
- Available Testers: [TESTER_COUNT] FTEs with [EXPERIENCE_LEVEL: junior/mid/senior/mixed]
- Automation Coverage Target: [AUTO_TARGET]%
- Existing Automation Framework: [FRAMEWORK_STATUS: mature/developing/none]
- Environment Availability: [ENV_STATUS: stable/constrained/unstable]
- Test Data Availability: [TEST_DATA_STATUS: available/needs generation/privacy restricted]

---

## REQUIRED OUTPUT FORMAT

### 1. EXECUTIVE SUMMARY
- Total Estimated Effort: [X] person-days / [Y] person-weeks / [Z] person-months
- Confidence Level: [High/Medium/Low] with [±X%] variance range
- Critical Path Duration: [calendar days from start to sign-off]
- Risk-Adjusted Estimate: [best case / most likely / worst case]

### 2. DETAILED EFFORT BREAKDOWN
Present in table format with:
| Phase | Activity | Effort (PD) | % of Total | Assumptions |
|-------|----------|-------------|------------|-------------|
Include: Planning, Test Design, Test Data Setup, Environment Setup, Test Execution (manual), Test Automation (creation), Test Automation (execution), Regression Testing, Defect Management, Reporting, Sign-off Activities

### 3. RESOURCE ALLOCATION TIMELINE
- Week-by-week or Sprint-by-sprint resource loading
- Peak staffing requirements
- Skill mix requirements over time
- Onboarding/training needs

### 4. COMPLEXITY & RISK FACTORS
Identify and quantify impact of:
- Technical complexity factors (multiplier applied)
- Organizational factors (communication overhead)
- Quality risk factors (additional buffer added)
- External dependencies (schedule risk)

### 5. AUTOMATION STRATEGY & EFFORT
- Recommended automation candidates (priority order)
- Framework enhancement needs
- Script development effort per layer (UI, API, unit)
- Maintenance factor for existing scripts
- ROI projection (break-even iteration)

### 6. ENVIRONMENT & TOOLING REQUIREMENTS
- Test environment specifications
- Data volume and refresh frequency
- License requirements
- Third-party service costs

### 7. QUALITY GATES & EXIT CRITERIA
- Defined entry/exit criteria per phase
- Defect thresholds for progression
- Coverage targets (requirement, code, risk)
- Performance benchmarks

### 8. SENSITIVITY ANALYSIS
Show how estimate changes with:
- ±20% scope variation
- ±1 tester availability
- ±1 week schedule compression
- Automation coverage ±15%

### 9. RECOMMENDATIONS
- Top 3 actions to reduce estimate
- Top 3 risks requiring mitigation
- Negotiation points for scope/schedule/resources

### 10. APPENDIX: ESTIMATION METHODOLOGY
Brief explanation of:
- Technique used (function point, use case point, expert judgment, analogy-based, parametric)
- Calibration factors applied
- Historical data sources
- Industry benchmarks referenced

---

## QUALITY STANDARDS
- All numbers must be traceable to stated assumptions
- Ranges must include confidence percentages
- No unexplained magic numbers
- Explicit callouts where expert judgment overrides calculation
- Consistent units throughout (convert all to person-days for summation)

Begin your response with: "TEST ESTIMATION ANALYSIS — [PROJECT_NAME]" and proceed through all sections.