@cloudkinetix/bmad-enhanced
Version:
Cloud-Kinetix enhanced fork of BMAD-METHOD - Breakthrough Method of Agile AI-driven Development with robust versioning and unified validation.
214 lines (193 loc) • 4.58 kB
YAML
name: jira-sprint-planning
title: JIRA Sprint Planning Workflow
description: Structured workflow for sprint planning with full JIRA integration and three-way sync
type: planning
category: agile
estimated_time: 2-4 hours
agents:
- jira
- pm
- sm
- architect
- dev
prerequisites:
- JIRA project configured
- MCP connection established
- Team velocity data available
- Product backlog groomed
startup_sequence:
- agent: jira
task: backlog
message: "Analyzing backlog health and story readiness"
planning_phase:
- id: 1.1
agent: jira
task: backlog
outputs:
- Backlog health report
- Story readiness assessment
- Missing estimate identification
- Technical debt items
- id: 1.2
agent: pm
task: prioritize-sprint-candidates
inputs:
- Backlog health report
- Business priorities
- Team capacity
outputs:
- Prioritized story list
- Sprint goal proposal
- Risk assessment
decision_points:
- id: D1
name: Sprint Goal Definition
description: Define primary sprint objective
- id: 1.3
agent: architect
task: technical-feasibility-review
inputs:
- Sprint candidates
- System architecture
outputs:
- Technical dependencies
- Architecture impacts
- Risk mitigation plan
- id: 1.4
agent: sm
task: capacity-planning
inputs:
- Team availability
- Historical velocity
- Sprint candidates
outputs:
- Capacity allocation
- Sprint backlog proposal
- Contingency planning
sprint_setup_phase:
- id: 2.1
agent: jira
task: jira-operations
inputs:
mode: create-sprint
- Sprint name
- Sprint dates
- Sprint goal
outputs:
- Sprint created in JIRA
- Sprint ID for tracking
- id: 2.2
agent: jira
task: jira-operations
inputs:
mode: assign-to-sprint
- Selected story list
- Sprint ID
outputs:
- Stories assigned to sprint
- Updated sprint backlog
- Capacity metrics
- id: 2.3
agent: pm
task: create-sprint-plan-doc
outputs:
- Sprint plan document
- Success criteria
- Risk register
implementation_kickoff:
- id: 3.1
agent: dev
task: technical-planning-session
inputs:
- Sprint backlog
- Technical dependencies
outputs:
- Implementation approach
- Task breakdown
- Pairing assignments
- id: 3.2
agent: jira
task: setup
inputs:
mode: sprint-board
outputs:
- Configured board filters
- Swim lanes setup
- Quick filters created
- id: 3.3
agent: jira
task: sync
inputs:
mode: initialize
outputs:
- Daily sync schedule
- Standup templates
- Progress tracking setup
validation_phase:
- id: 4.1
agent: jira
task: sync
inputs:
mode: validate
scope: sprint
outputs:
- JIRA-BMAD-Git alignment check
- Sync discrepancies identified
- Remediation actions
- id: 4.2
agent: sm
task: sprint-kickoff-preparation
outputs:
- Kickoff meeting agenda
- Team commitments documented
- Communication plan
decision_points:
- id: D1
step: 1.2
description: Define sprint goal and theme
impacts:
- Story selection criteria
- Success metrics
- Team focus
- id: D2
step: 1.4
description: Commit to sprint scope
options:
- Full proposed backlog
- Reduced scope with buffer
- Include stretch goals
impacts:
- Team stress level
- Delivery confidence
- Stakeholder expectations
- id: D3
step: 3.1
description: Choose implementation strategy
options:
- Sequential story completion
- Parallel development tracks
- Risk-first approach
impacts:
- Resource allocation
- Integration complexity
- Early value delivery
outputs:
- Sprint created and configured in JIRA
- Sprint backlog with estimates
- Sprint plan document
- Technical approach documentation
- Daily sync process initialized
- Three-way sync validated
success_criteria:
- All stories properly estimated and assigned
- Sprint capacity not exceeded
- Technical dependencies identified
- Team commitment obtained
- Stakeholders informed
- Sync processes operational
monitoring:
- Daily standup updates
- Burndown chart tracking
- Blocker identification
- Sync health monitoring
- Velocity tracking