# Integration Health Checklist

## Purpose

Regular health assessment of the JIRA-BMAD-Git integration to ensure optimal performance, data accuracy, and team productivity. Run weekly or when issues arise.

## Required Artifacts

[[LLM: To execute this checklist, you need:

1. Integration configuration files
2. Recent sync logs and reports
3. Access to JIRA, Git repositories, and BMAD workspace
4. Performance metrics from last 7 days
5. Team feedback or issue reports
   ]]

## Checklist Sections

### 1. Configuration Health (Basic Level)

[[LLM: Verify all configuration is valid and up-to-date]]

- [ ] **Config Files Exist**: All required configs present
- [ ] **Project Mapping Valid**: JIRA project key correct
- [ ] **Git Repos Accessible**: All configured repos reachable
- [ ] **Team Data Current**: Team members still accurate
- [ ] **MCP Tools Working**: Atlassian MCP responding

**Config Status**:

- ⭐⭐⭐⭐⭐ Perfect configuration
- ⭐⭐⭐⭐ Minor updates needed
- ⭐⭐⭐ Several issues
- ⭐⭐ Major problems
- ⭐ Critical failures

### 2. Sync Performance Analysis (Comprehensive Level)

[[LLM: Analyze sync operation performance over past week]]

#### Sync Metrics

- [ ] **Success Rate**: \_\_\_% of syncs completed successfully
- [ ] **Average Duration**: \_\_\_ seconds per sync
- [ ] **Error Frequency**: \_\_\_ errors per 100 syncs
- [ ] **Data Volume**: \_\_\_ stories/issues synced daily

#### Performance Trends

- [ ] **Speed**: Improving / Stable / Degrading
- [ ] **Reliability**: Improving / Stable / Degrading
- [ ] **Error Rate**: Decreasing / Stable / Increasing
- [ ] **User Satisfaction**: High / Medium / Low

**Performance Grade**: A+ | A | B | C | D | F

### 3. Data Integrity Verification (Expert Level)

[[LLM: Deep validation of data consistency across systems]]

#### Cross-System Validation

- [ ] **JIRA → BMAD**: Updates reflected accurately
- [ ] **BMAD → JIRA**: Changes sync correctly
- [ ] **Git → Both**: Commits linked properly
- [ ] **Field Mapping**: All fields sync as expected
- [ ] **Status Sync**: Workflow states align

#### Data Quality Checks

- [ ] **No Orphaned Issues**: All issues have proper links
- [ ] **No Duplicates**: No duplicate issues created
- [ ] **Formatting Preserved**: Wiki markup correct
- [ ] **Attachments Intact**: Files transfer properly
- [ ] **History Maintained**: Audit trail complete

**Integrity Score**: \_\_\_% (issues passed / total checked × 100)

### 4. Team Adoption & Usage

[[LLM: Assess how well the team is using the integration]]

#### Usage Patterns

- [ ] **Daily Active Users**: \_\_\_% of team
- [ ] **Feature Utilization**: Using \_\_\_% of features
- [ ] **Command Frequency**: \_\_\_ commands/day average
- [ ] **Error Recovery**: Users handle errors well

#### Adoption Indicators

- [ ] **Sync Frequency**: Regular / Sporadic / Rare
- [ ] **Feature Discovery**: Team exploring new features
- [ ] **Process Integration**: Part of daily workflow
- [ ] **Satisfaction Level**: High / Medium / Low

**Adoption Health**:

- ✅ **THRIVING**: Full adoption and satisfaction
- ⚠️ **GROWING**: Increasing usage with some gaps
- ❌ **STRUGGLING**: Low adoption or satisfaction

### 5. Error Analysis & Resolution

[[LLM: Review and categorize recent errors]]

#### Error Categories (Last 7 Days)

- [ ] **Configuration Errors**: \_\_\_ occurrences
- [ ] **Network/Timeout**: \_\_\_ occurrences
- [ ] **Permission Issues**: \_\_\_ occurrences
- [ ] **Data Format**: \_\_\_ occurrences
- [ ] **User Errors**: \_\_\_ occurrences

#### Resolution Status

- [ ] **Auto-Resolved**: \_\_\_% handled automatically
- [ ] **User-Resolved**: \_\_\_% fixed by users
- [ ] **Escalated**: \_\_\_% needed support
- [ ] **Unresolved**: \_\_\_% still pending

**Error Management**: Excellent | Good | Needs Improvement | Poor

### 6. Integration Dependencies

[[LLM: Check health of dependent systems]]

- [ ] **JIRA API**: Response time < 2s
- [ ] **Git Operations**: No performance issues
- [ ] **File System**: Adequate space available
- [ ] **Network**: Stable connectivity
- [ ] **MCP Services**: All tools operational

**Dependency Status**:

- 🟢 All systems healthy
- 🟡 Minor issues detected
- 🔴 Critical dependency problems

### 7. Security & Compliance

[[LLM: Verify security posture and compliance]]

- [ ] **Access Control**: Permissions appropriate
- [ ] **Data Privacy**: No sensitive data exposed
- [ ] **Audit Logging**: All operations logged
- [ ] **Token Security**: API tokens secure
- [ ] **Compliance**: Meeting requirements

**Security Rating**: Secure | Minor Concerns | Major Issues

## Overall Integration Health

[[LLM: Synthesize comprehensive health assessment]]

### Health Dashboard

```
Configuration:    ⭐⭐⭐⭐⭐ [___/5]
Performance:      _________ [Grade: ___]
Data Integrity:   _________ [___% ]
Team Adoption:    _________ [Status: _______]
Error Rate:       _________ [___ per day]
Dependencies:     _________ [🟢/🟡/🔴]
Security:         _________ [Status: _______]
```

### Overall Health Score: \_\_\_/100

### Health Status:

- [ ] 💚 **HEALTHY** (90-100): Operating optimally
- [ ] 💛 **GOOD** (70-89): Minor improvements needed
- [ ] 🧡 **FAIR** (50-69): Several issues to address
- [ ] ❤️ **POOR** (<50): Significant problems requiring attention

## Improvement Recommendations

[[LLM: Based on the health check, provide prioritized recommendations]]

### Immediate Actions (This Week)

1. **Highest Priority**: {{specific action}}
2. **Quick Wins**: {{easy improvements}}
3. **Risk Mitigation**: {{prevent problems}}

### Medium-term Improvements (This Month)

1. **Process Optimization**: {{workflow improvements}}
2. **Team Training**: {{adoption improvements}}
3. **Technical Debt**: {{cleanup needed}}

### Long-term Enhancements (This Quarter)

1. **Feature Additions**: {{new capabilities}}
2. **Automation**: {{reduce manual work}}
3. **Scaling Preparation**: {{growth readiness}}

## Trending Analysis

[[LLM: Compare to previous health checks if available]]

### Trends:

- **Improving**: {{areas getting better}}
- **Stable**: {{areas holding steady}}
- **Declining**: {{areas needing attention}}

### Predicted Issues:

Based on trends, watch for:

1. {{potential problem 1}}
2. {{potential problem 2}}

---

_Regular health checks ensure your JIRA integration remains a productivity accelerator, not a bottleneck._