@cloudkinetix/bmad-enhanced/expansion-packs/ck-jira-integration/checklists/sprint-readiness-checklist.md

Cloud-Kinetix enhanced fork of BMAD-METHOD - Breakthrough Method of Agile AI-driven Development with robust versioning and unified validation.

# Sprint Readiness Checklist

## Purpose

Comprehensive validation to ensure the team is fully prepared to begin a new sprint with all necessary planning, technical setup, and team alignment in place.

## Required Artifacts

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

1. Product backlog (JIRA and/or BMAD stories)
2. Team capacity information
3. Previous sprint retrospective notes
4. Technical dependencies list
5. Definition of Done (DoD)
6. Sprint goal draft
   ]]

## Checklist Sections

### 1. Backlog Readiness (Basic Level)

[[LLM: Validate that stories are ready for sprint planning]]

- [ ] **Stories Estimated**: All candidate stories have story points
- [ ] **Acceptance Criteria**: Each story has clear AC
- [ ] **Priority Order**: Backlog is properly prioritized
- [ ] **Dependencies Identified**: Technical/business dependencies noted
- [ ] **Epic Association**: Stories linked to appropriate epics

**Backlog Quality**: ⭐⭐⭐⭐⭐ (minimum 4/5 stars required)

### 2. Team Readiness (Comprehensive Level)

[[LLM: Ensure team is prepared for the sprint]]

#### Capacity Assessment

- [ ] **Team Availability**: All members' availability confirmed
- [ ] **Vacation/Time Off**: PTO accounted for in capacity
- [ ] **Meeting Overhead**: Time allocated for ceremonies
- [ ] **Support/Maintenance**: Buffer for unplanned work

**Available Capacity**: \_\_\_ story points (based on velocity)

#### Role Coverage

- [ ] **Product Owner**: Available for clarifications
- [ ] **Scrum Master**: Ready to facilitate
- [ ] **Developers**: Full team coverage
- [ ] **QA**: Testing capacity confirmed
- [ ] **Specialists**: Any needed experts available

**Team Health**:

- ⭐⭐⭐⭐⭐ Fully staffed and ready
- ⭐⭐⭐⭐ Minor gaps with mitigation
- ⭐⭐⭐ Significant gaps needing attention
- ⭐⭐ Major concerns
- ⭐ Not ready for sprint

### 3. Technical Readiness (Expert Level)

[[LLM: Validate technical environment and dependencies]]

#### Environment Status

- [ ] **Development**: Environments stable and accessible
- [ ] **Testing**: Test environments prepared
- [ ] **CI/CD**: Build pipeline healthy
- [ ] **JIRA Integration**: Sync working properly
- [ ] **Version Control**: Branches prepared

#### Technical Debt

- [ ] **Critical Fixes**: From previous sprint addressed
- [ ] **Known Issues**: Documented and prioritized
- [ ] **Performance**: No blocking performance issues
- [ ] **Security**: No unaddressed vulnerabilities
- [ ] **Documentation**: Critical docs updated

**Technical Health Score**: \_\_\_% ready

### 4. Sprint Goal Validation

[[LLM: Ensure clear, achievable sprint goal]]

- [ ] **Goal Defined**: Clear, concise sprint goal exists
- [ ] **Measurable**: Success criteria defined
- [ ] **Achievable**: Realistic given capacity
- [ ] **Valuable**: Delivers business value
- [ ] **Focused**: Not trying to do everything

**Goal Quality Assessment**:

- ✅ **EXCELLENT**: Clear, focused, achievable
- ⚠️ **NEEDS WORK**: Requires refinement
- ❌ **NOT READY**: Too vague or unrealistic

### 5. Story Deep Dive (Top 5 Stories)

[[LLM: Detailed validation of highest priority stories]]

For each of the top 5 stories:

**Story 1: {{story_title}}**

- [ ] Requirements clear
- [ ] Design completed/approved
- [ ] Technical approach defined
- [ ] Test scenarios identified
- [ ] No blocking dependencies

**Story 2-5**: [Repeat pattern]

**Story Readiness**: \_\_\_/5 stories fully ready

### 6. Risk Assessment

[[LLM: Identify and evaluate sprint risks]]

#### Risk Categories

- [ ] **Technical Risks**: Identified and mitigation planned
- [ ] **Resource Risks**: Team availability concerns addressed
- [ ] **Dependency Risks**: External dependencies managed
- [ ] **Scope Risks**: Scope creep prevention planned
- [ ] **Quality Risks**: Testing approach defined

**Overall Risk Level**:

- 🟢 Low Risk - Normal sprint
- 🟡 Medium Risk - Proceed with caution
- 🔴 High Risk - Consider replanning

### 7. Communication & Alignment

[[LLM: Verify team alignment and communication]]

- [ ] **Stakeholder Briefed**: Key stakeholders informed
- [ ] **Team Aligned**: Everyone understands goal
- [ ] **Calendar Clear**: No major conflicts
- [ ] **Communication Plan**: How to handle issues
- [ ] **Success Metrics**: How we'll measure success

**Alignment Score**: Excellent | Good | Fair | Poor

## Sprint Readiness Decision

[[LLM: Synthesize all sections into go/no-go recommendation]]

### Summary Assessment

- Backlog Quality: \_\_\_/5 stars
- Team Readiness: \_\_\_/5 stars
- Technical Health: \_\_\_% ready
- Sprint Goal: EXCELLENT/NEEDS WORK/NOT READY
- Story Readiness: \_\_\_/5 ready
- Risk Level: 🟢/🟡/🔴
- Team Alignment: \_\_\_ rating

### Sprint Start Recommendation

- [ ] ✅ **GO**: Team is ready to start sprint
- [ ] ⚠️ **CONDITIONAL GO**: Start with specific adjustments
- [ ] ❌ **NO GO**: Critical issues must be resolved first

### Required Actions Before Sprint Start

[[LLM: List specific actions needed based on gaps identified:

1. Highest priority items to address
2. Who needs to do what
3. Timeline for completion
4. How to verify readiness
   ]]

### Sprint Success Factors

[[LLM: Based on assessment, highlight:

- Key strengths to leverage
- Main risks to monitor
- Success metrics to track
- Team agreements needed
  ]]

---

_This checklist ensures teams start sprints with confidence and clarity, setting up for success from day one._