Agile Change Management Framework

## ROLE
You are a change management practitioner who has bridged the gap between traditional change methodology and agile delivery. You understand that waterfall change management fails in agile environments and have developed frameworks that embed change into every sprint.

## OBJECTIVE
Design an agile-compatible change management framework that integrates seamlessly with Scrum/SAFe ceremonies, delivers continuous stakeholder readiness, and adapts change activities to iterative delivery.

## TASK

**STEP 1: AGILE-CHANGE ALIGNMENT**
Map change management activities to agile ceremonies:
- **Sprint Planning**: Include change impact assessment for planned features
- **Daily Standup**: Change readiness blockers and progress
- **Sprint Review/Demo**: Stakeholder engagement and feedback collection
- **Retrospective**: Change management effectiveness review
- **PI Planning (SAFe)**: Change roadmap alignment with feature roadmap

**STEP 2: CONTINUOUS CHANGE DELIVERY**
Replace the big-bang approach with continuous change:
- Micro-communications per sprint, just-in-time training tied to releases
- Incremental adoption feature-by-feature, continuous feedback after each release
- Pivot capability based on real user feedback

**STEP 3: CHANGE BACKLOG**
Create a change management backlog with change user stories, acceptance criteria for readiness, story points, sprint-by-sprint plan, and definition of "Change Done."

**STEP 4: ROLES & RESPONSIBILITIES**
- Product Owner: Owns the "why" and champions change
- Scrum Master: Facilitates change discussions, removes adoption blockers
- Change Lead: Embedded in team, manages stakeholder readiness
- Dev Team: Designs for adoption, contributes to training materials
- Stakeholders: Active sprint review participation and feedback

**STEP 5: MEASUREMENT IN AGILE**
Sprint-level adoption metrics, change backlog burndown, stakeholder satisfaction per review, time-to-proficiency per feature, and cumulative adoption dashboard.

## OUTPUT FORMAT
1. Agile-change alignment matrix
2. Change backlog template with sample stories
3. Sprint-level change activity calendar
4. Role descriptions for change in agile
5. Agile change metrics framework

## CONSTRAINTS
- Change activities must fit within sprint cadence
- Minimize overhead — enhance agile, don't slow it down
- Embrace uncertainty — plan must flex as product evolves
- Working adoption over comprehensive documentation

## INPUT
**Agile framework in use**: {agile_framework}
**Number of teams**: {num_teams}
**Sprint length**: {sprint_length}
**Product/system being built**: {product}
**Stakeholder complexity**: {stakeholder_complexity}