npx skills add https://github.com/borghei/claude-skills --skill agile-coach为团队和组织转型提供专家级敏捷辅导。
| 方面 | Scrum | Kanban | SAFe | LeSS |
|---|---|---|---|---|
| 角色 | SM, PO, Dev | 灵活 | 定义了许多 | SM, PO, Dev |
| 节奏 | 固定冲刺 | 持续 | PI 规划 | 冲刺 |
| 规划 | 冲刺规划 | 按需 | PI 规划 | 冲刺规划 |
| 最适合 | 产品开发 |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 运维 |
| 企业 |
| 多团队 |
| 变更 | 冲刺结束时 | 随时 | PI 边界 | 冲刺 |
TEAM SIZE & COMPLEXITY MATRIX
Simple Complex
Small (1-2 teams) Kanban Scrum
XP Scrumban
Medium (3-8 teams) Scrum@Scale SAFe Essential
Nexus LeSS
Large (9+ teams) SAFe Portfolio SAFe Full
Enterprise Custom Hybrid
Kanban
DIRECTIVE ←────────────────────────────→ NON-DIRECTIVE
Teaching Advising Coaching Mentoring Facilitating
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
"Do this" "Consider" "What do "In my "What does
"this..." you think?" experience" the team
think?"
GROW 模型:
G - GOAL
├── 你想要实现什么?
├── 成功会是什么样子?
└── 你希望在何时实现?
R - REALITY
├── 现在的情况如何?
├── 你已经尝试了什么?
└── 存在哪些障碍?
O - OPTIONS
├── 你可以做什么?
├── 还有其他选择吗?
├── 如果没有限制会怎样?
└── 你对哪些选项最感兴趣?
W - WAY FORWARD
├── 你将会做什么?
├── 你将在何时做?
├── 你需要什么支持?
└── 你如何知道你已经成功了?
TUCKMAN'S MODEL + COACHING APPROACH
FORMING
├── 行为:礼貌,试探性
├── 需求:方向,清晰度
└── 教练:指导,设定期望
STORMING
├── 行为:冲突,抗拒
├── 需求:支持,引导
└── 教练:调解,使其正常化
NORMING
├── 行为:协作出现
├── 需求:强化
└── 教练:观察,强化
PERFORMING
├── 行为:高生产力
├── 需求:拓展性挑战
└── 教练:退后一步,咨询
ADJOURNING
├── 行为:完成
├── 需求:庆祝,收尾
└── 教练:引导回顾会
# Agile Transformation Roadmap
## Phase 1: Foundation (Months 1-3)
### Goals
- 建立领导层支持
- 创建转型团队
- 评估当前状态
### Activities
- [ ] 高管对齐研讨会
- [ ] 当前状态评估
- [ ] 试点团队选择
- [ ] 教练入职
- [ ] 培训方案设计
### Success Criteria
- 领导层承诺
- 试点团队确定
- 基线度量指标建立
## Phase 2: Pilot (Months 4-6)
### Goals
- 启动试点团队
- 学习与适应
- 建立内部能力
### Activities
- [ ] 试点团队启动
- [ ] 框架培训
- [ ] 辅导会议
- [ ] 回顾会
- [ ] 成功故事记录
### Success Criteria
- 试点团队正常运行
- 初步改进可见
- 经验教训被捕获
## Phase 3: Expand (Months 7-12)
### Goals
- 扩展成功模式
- 建立社区
- 嵌入实践
### Activities
- [ ] 启动更多团队
- [ ] 实践社区
- [ ] 教练发展
- [ ] 流程优化
- [ ] 工具改进
### Success Criteria
- 多个团队实现敏捷
- 内部教练活跃
- 可持续的实践
## Phase 4: Optimize (Months 13+)
### Goals
- 持续改进
- 组织敏捷性
- 业务成果
### Activities
- [ ] 组合层面的敏捷性
- [ ] 跨团队协调
- [ ] 基于度量的改进
- [ ] 创新赋能
### Success Criteria
- 实现业务敏捷性
- 自我维持的改进
AGILE MATURITY MODEL
Level 1: Initial
├── 临时流程
├── 依赖英雄
└── 有限的可视性
Level 2: Repeatable
├── 基础的 Scrum/Kanban
├── 团队层面的实践
└── 一些度量指标
Level 3: Defined
├── 一致的实践
├── 跨团队协调
└── 持续改进
Level 4: Managed
├── 量化管理
├── 可预测的结果
└── 业务对齐
Level 5: Optimizing
├── 创新文化
├── 市场响应能力
└── 组织学习
| 维度 | 分数 (1-5) | 证据 |
|---|---|---|
| 价值观与思维模式 | ||
| 团队实践 | ||
| 技术卓越 | ||
| 产品负责人 | ||
| 领导支持 | ||
| 持续改进 |
回顾会格式:
FORMAT 1: Start-Stop-Continue
┌─────────────┬─────────────┬─────────────┐
│ START │ STOP │ CONTINUE │
│ │ │ │
│ What should │ What should │ What's │
│ we begin │ we stop │ working │
│ doing? │ doing? │ well? │
└─────────────┴─────────────┴─────────────┘
FORMAT 2: 4Ls
┌─────────────┬─────────────┐
│ LIKED │ LEARNED │
├─────────────┼─────────────┤
│ LACKED │ LONGED FOR │
└─────────────┴─────────────┘
FORMAT 3: Sailboat
☀️ Sun (Goals)
│
💨 Wind ←──⛵──→ ⚓ Anchor
(Helpers) │ (Impediments)
🪨 Rocks (Risks)
研讨会引导:
WORKSHOP STRUCTURE
1. OPENING (10%)
├── 欢迎,目的
├── 议程概述
└── 工作协议
2. DIVERGE (30%)
├── 产生想法
├── 个人思考
└── 捕获所有输入
3. EXPLORE (20%)
├── 分享观点
├── 讨论模式
└── 深化理解
4. CONVERGE (30%)
├── 优先级排序
├── 决策
└── 行动计划
5. CLOSE (10%)
├── 总结成果
├── 分配行动
└── 收集反馈
CONFLICT RESOLUTION STEPS
1. ACKNOWLEDGE
├── 承认冲突存在
├── 创造安全空间
└── 设定基本规则
2. UNDERSTAND
├── 听取各方观点
├── 识别潜在需求
├── 区分立场与利益
3. EXPLORE
├── 生成选项
├── 寻找共同点
└── 基于共同利益构建
4. AGREE
├── 定义可接受的解决方案
├── 记录协议
└── 设定后续计划
OUTCOME METRICS (Business Value)
├── 客户满意度
├── 上市时间
├── 交付的收入/价值
└── 市场响应能力
PROCESS METRICS (Flow)
├── 前置时间
├── 周期时间
├── 吞吐量
└── 在制品
QUALITY METRICS (Technical)
├── 缺陷率
├── 技术债务
├── 测试覆盖率
└── 部署频率
TEAM METRICS (Health)
├── 团队幸福感
├── 心理安全
├── 参与度
└── 可持续性
┌─────────────────────────────────────────────────────────────┐
│ AGILE TEAM DASHBOARD │
├─────────────────────────────────────────────────────────────┤
│ Velocity Cycle Time Lead Time Throughput │
│ 42 pts 3.2 days 8.5 days 12 items │
│ vs Avg: +5% vs Avg: -10% vs Avg: -15% vs Avg: +8% │
├─────────────────────────────────────────────────────────────┤
│ FLOW METRICS │
│ WIP: 8 items Blocked: 2 Queue Time: 1.2 days │
├─────────────────────────────────────────────────────────────┤
│ QUALITY │
│ Escaped Defects: 3 Tech Debt: 12 items Coverage: 82% │
├─────────────────────────────────────────────────────────────┤
│ TEAM HEALTH │
│ Happiness: 4.2/5 Safety: 4.0/5 Engagement: High │
└─────────────────────────────────────────────────────────────┘
ADKAR 模型:
A - AWARENESS
├── 为什么需要变革?
└── 不变革的风险是什么?
D - DESIRE
├── 对我有什么好处?
└── 有什么益处?
K - KNOWLEDGE
├── 我们如何变革?
└── 需要什么技能?
A - ABILITY
├── 我们能实施吗?
└── 我们有资源吗?
R - REINFORCEMENT
├── 我们如何维持?
└── 什么会阻止倒退?
| 利益相关者 | 影响力 | 兴趣度 | 策略 |
|---|---|---|---|
| 高管 | 高 | 可变 | 与业务目标对齐 |
| 中层管理者 | 高 | 中 | 解决顾虑 |
| 团队 | 中 | 高 | 赋能成功 |
| 客户 | 中 | 高 | 展示价值 |
# Community of Practice Charter
## Purpose
[为什么这个社区存在]
## Scope
- In scope: [Topics]
- Out of scope: [Not covered]
## Membership
- Open to: [Criteria]
- Expected participation: [Level]
## Activities
- 月度聚会
- 知识分享会
- 技能发展
- 问题解决研讨会
## Leadership
- Facilitator: [Name]
- 轮值主持人
- 沟通负责人
## Success Metrics
- 参与率
- 知识共享
- 问题解决
- 成员满意度
形式:
references/frameworks.md - 敏捷框架详情references/coaching_techniques.md - 辅导方法references/facilitation.md - 会议引导references/transformation.md - 转型手册# Maturity assessment scorer
python scripts/maturity_scorer.py --assessment assessment.yaml
# Metrics dashboard generator
python scripts/metrics_dashboard.py --team "Team Alpha"
# Retrospective idea generator
python scripts/retro_format.py --format sailboat
# Transformation tracker
python scripts/transformation_tracker.py --phase pilot
每周安装
86
仓库
GitHub 星标
30
首次出现
Jan 24, 2026
安全审计
安装于
opencode61
claude-code60
gemini-cli59
codex55
cursor52
github-copilot51
Expert-level agile coaching for team and organizational transformation.
| Aspect | Scrum | Kanban | SAFe | LeSS |
|---|---|---|---|---|
| Roles | SM, PO, Dev | Flexible | Many defined | SM, PO, Dev |
| Cadence | Fixed sprints | Continuous | PI Planning | Sprints |
| Planning | Sprint Planning | On-demand | PI Planning | Sprint Planning |
| Best For | Product dev | Operations | Enterprise | Multi-team |
| Change | End of sprint | Anytime | PI boundaries | Sprint |
TEAM SIZE & COMPLEXITY MATRIX
Simple Complex
Small (1-2 teams) Kanban Scrum
XP Scrumban
Medium (3-8 teams) Scrum@Scale SAFe Essential
Nexus LeSS
Large (9+ teams) SAFe Portfolio SAFe Full
Enterprise Custom Hybrid
Kanban
DIRECTIVE ←────────────────────────────→ NON-DIRECTIVE
Teaching Advising Coaching Mentoring Facilitating
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
"Do this" "Consider" "What do "In my "What does
"this..." you think?" experience" the team
think?"
GROW Model:
G - GOAL
├── What do you want to achieve?
├── What would success look like?
└── By when do you want this?
R - REALITY
├── What is happening now?
├── What have you tried?
└── What obstacles exist?
O - OPTIONS
├── What could you do?
├── What else?
├── What if there were no constraints?
└── Which options interest you most?
W - WAY FORWARD
├── What will you do?
├── When will you do it?
├── What support do you need?
└── How will you know you've succeeded?
TUCKMAN'S MODEL + COACHING APPROACH
FORMING
├── Behavior: Polite, tentative
├── Need: Direction, clarity
└── Coach: Guide, set expectations
STORMING
├── Behavior: Conflict, resistance
├── Need: Support, facilitation
└── Coach: Mediate, normalize
NORMING
├── Behavior: Collaboration emerging
├── Need: Reinforcement
└── Coach: Observe, reinforce
PERFORMING
├── Behavior: High productivity
├── Need: Stretch challenges
└── Coach: Step back, consult
ADJOURNING
├── Behavior: Completion
├── Need: Celebration, closure
└── Coach: Facilitate retrospective
# Agile Transformation Roadmap
## Phase 1: Foundation (Months 1-3)
### Goals
- Establish leadership buy-in
- Create transformation team
- Assess current state
### Activities
- [ ] Executive alignment workshop
- [ ] Current state assessment
- [ ] Pilot team selection
- [ ] Coach onboarding
- [ ] Training program design
### Success Criteria
- Leadership committed
- Pilot teams identified
- Baseline metrics established
## Phase 2: Pilot (Months 4-6)
### Goals
- Launch pilot teams
- Learn and adapt
- Build internal capability
### Activities
- [ ] Pilot team launch
- [ ] Framework training
- [ ] Coaching sessions
- [ ] Retrospectives
- [ ] Success story documentation
### Success Criteria
- Pilot teams functioning
- Initial improvements visible
- Lessons learned captured
## Phase 3: Expand (Months 7-12)
### Goals
- Scale successful patterns
- Build communities
- Embed practices
### Activities
- [ ] Additional team launches
- [ ] Community of practice
- [ ] Coach development
- [ ] Process optimization
- [ ] Tool refinement
### Success Criteria
- Multiple teams agile
- Internal coaches active
- Sustainable practices
## Phase 4: Optimize (Months 13+)
### Goals
- Continuous improvement
- Organizational agility
- Business outcomes
### Activities
- [ ] Portfolio-level agility
- [ ] Cross-team coordination
- [ ] Metrics-driven improvement
- [ ] Innovation enablement
### Success Criteria
- Business agility achieved
- Self-sustaining improvement
AGILE MATURITY MODEL
Level 1: Initial
├── Ad-hoc processes
├── Hero-dependent
└── Limited visibility
Level 2: Repeatable
├── Basic Scrum/Kanban
├── Team-level practices
└── Some metrics
Level 3: Defined
├── Consistent practices
├── Cross-team coordination
└── Continuous improvement
Level 4: Managed
├── Quantitative management
├── Predictable outcomes
└── Business alignment
Level 5: Optimizing
├── Innovation culture
├── Market responsiveness
└── Organizational learning
| Dimension | Score (1-5) | Evidence |
|---|---|---|
| Values & Mindset | ||
| Team Practices | ||
| Technical Excellence | ||
| Product Ownership | ||
| Leadership Support | ||
| Continuous Improvement |
Retrospective Formats:
FORMAT 1: Start-Stop-Continue
┌─────────────┬─────────────┬─────────────┐
│ START │ STOP │ CONTINUE │
│ │ │ │
│ What should │ What should │ What's │
│ we begin │ we stop │ working │
│ doing? │ doing? │ well? │
└─────────────┴─────────────┴─────────────┘
FORMAT 2: 4Ls
┌─────────────┬─────────────┐
│ LIKED │ LEARNED │
├─────────────┼─────────────┤
│ LACKED │ LONGED FOR │
└─────────────┴─────────────┘
FORMAT 3: Sailboat
☀️ Sun (Goals)
│
💨 Wind ←──⛵──→ ⚓ Anchor
(Helpers) │ (Impediments)
🪨 Rocks (Risks)
Workshop Facilitation:
WORKSHOP STRUCTURE
1. OPENING (10%)
├── Welcome, purpose
├── Agenda overview
└── Working agreements
2. DIVERGE (30%)
├── Generate ideas
├── Individual thinking
└── Capture all input
3. EXPLORE (20%)
├── Share perspectives
├── Discuss patterns
└── Deepen understanding
4. CONVERGE (30%)
├── Prioritize
├── Decide
└── Plan actions
5. CLOSE (10%)
├── Summarize outcomes
├── Assign actions
└── Gather feedback
CONFLICT RESOLUTION STEPS
1. ACKNOWLEDGE
├── Recognize the conflict exists
├── Create safe space
└── Set ground rules
2. UNDERSTAND
├── Hear all perspectives
├── Identify underlying needs
├── Separate positions from interests
3. EXPLORE
├── Generate options
├── Find common ground
└── Build on shared interests
4. AGREE
├── Define acceptable solution
├── Document agreements
└── Set follow-up plan
OUTCOME METRICS (Business Value)
├── Customer satisfaction
├── Time to market
├── Revenue/value delivered
└── Market responsiveness
PROCESS METRICS (Flow)
├── Lead time
├── Cycle time
├── Throughput
└── Work in progress
QUALITY METRICS (Technical)
├── Defect rate
├── Technical debt
├── Test coverage
└── Deployment frequency
TEAM METRICS (Health)
├── Team happiness
├── Psychological safety
├── Engagement
└── Sustainability
┌─────────────────────────────────────────────────────────────┐
│ AGILE TEAM DASHBOARD │
├─────────────────────────────────────────────────────────────┤
│ Velocity Cycle Time Lead Time Throughput │
│ 42 pts 3.2 days 8.5 days 12 items │
│ vs Avg: +5% vs Avg: -10% vs Avg: -15% vs Avg: +8% │
├─────────────────────────────────────────────────────────────┤
│ FLOW METRICS │
│ WIP: 8 items Blocked: 2 Queue Time: 1.2 days │
├─────────────────────────────────────────────────────────────┤
│ QUALITY │
│ Escaped Defects: 3 Tech Debt: 12 items Coverage: 82% │
├─────────────────────────────────────────────────────────────┤
│ TEAM HEALTH │
│ Happiness: 4.2/5 Safety: 4.0/5 Engagement: High │
└─────────────────────────────────────────────────────────────┘
ADKAR Model:
A - AWARENESS
├── Why is change needed?
└── What are the risks of not changing?
D - DESIRE
├── What's in it for me?
└── What are the benefits?
K - KNOWLEDGE
├── How do we change?
└── What skills are needed?
A - ABILITY
├── Can we implement?
└── Do we have resources?
R - REINFORCEMENT
├── How do we sustain?
└── What prevents regression?
| Stakeholder | Influence | Interest | Strategy |
|---|---|---|---|
| Executives | High | Variable | Align to business goals |
| Middle Mgmt | High | Medium | Address concerns |
| Teams | Medium | High | Enable success |
| Customers | Medium | High | Show value |
# Community of Practice Charter
## Purpose
[Why this community exists]
## Scope
- In scope: [Topics]
- Out of scope: [Not covered]
## Membership
- Open to: [Criteria]
- Expected participation: [Level]
## Activities
- Monthly meetups
- Knowledge sharing sessions
- Skill development
- Problem-solving workshops
## Leadership
- Facilitator: [Name]
- Rotating host
- Communication owner
## Success Metrics
- Participation rate
- Knowledge shared
- Problems solved
- Member satisfaction
Formats:
references/frameworks.md - Agile framework detailsreferences/coaching_techniques.md - Coaching methodsreferences/facilitation.md - Meeting facilitationreferences/transformation.md - Transformation playbook# Maturity assessment scorer
python scripts/maturity_scorer.py --assessment assessment.yaml
# Metrics dashboard generator
python scripts/metrics_dashboard.py --team "Team Alpha"
# Retrospective idea generator
python scripts/retro_format.py --format sailboat
# Transformation tracker
python scripts/transformation_tracker.py --phase pilot
Weekly Installs
86
Repository
GitHub Stars
30
First Seen
Jan 24, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode61
claude-code60
gemini-cli59
codex55
cursor52
github-copilot51
BMAD工作流编排与SSD结构化系统设计 - 多代理AI开发流程自动化
10,600 周安装