---

name: agile version: "2.0.0" description: Agile product management, Scrum practices, and team collaboration for iterative product development. sasmp_version: "1.3.0" bonded_agent: 08-product-operations bond_type: PRIMARY_BOND parameters:

• name: methodology type: string enum: [scrum, kanban, safe, hybrid] required: true
• name: team_size type: number default: 5 retry_logic: max_attempts: 3 backoff: exponential logging: level: info hooks: [start, complete, error]

---

Agile Product Management Skill

Apply agile methodologies to product development and team collaboration. Master sprint planning, backlog management, and continuous improvement.

Scrum Framework

Sprint Cycle (2-week)

Sprint Planning Template

CopySprint Goal: [One sentence describing sprint outcome]

Capacity:
- Team size: 5 engineers
- Working days: 10
- Available points: 40

Selected Stories:
1. [Story A] - 8 points - Owner: Dev1
2. [Story B] - 5 points - Owner: Dev2
3. [Story C] - 13 points - Owner: Dev3
...

Risks:
- [Risk 1]: Mitigation plan
- [Risk 2]: Mitigation plan

Definition of Done:
[ ] Code reviewed
[ ] Tests written
[ ] Documentation updated
[ ] PM accepted

PM in Agile

User Story Format (INVEST)

CopyAs a [user type]
I want [action/capability]
So that [benefit/outcome]

Acceptance Criteria:
Given [context]
When [action]
Then [result]

Backlog Grooming

Weekly Grooming (1 hour):

1. Review upcoming sprint stories
2. Clarify acceptance criteria
3. Size/estimate stories
4. Identify dependencies
5. Reorder by priority

Story Points Guide

Kanban

Board Structure

Copy| Backlog | To Do | In Progress | Review | Done |
|---------|-------|-------------|--------|------|
|         |       |             |        |      |
|  WIP: - | WIP:3 |   WIP: 3    | WIP: 2 |  -   |

Flow Metrics

• Lead Time: Request → Done
• Cycle Time: In Progress → Done
• Throughput: Items completed per week
• WIP: Work in progress items

Scaling Agile

SAFe Basics

• Team Level: Scrum teams (5-9 people)
• Program Level: Multiple teams (50-125 people)
• Large Solution: Multiple programs
• Portfolio: Business strategy

Cross-Team Coordination

• Scrum of Scrums: Daily sync between teams
• PI Planning: Quarterly planning event
• System Demo: Integration showcase
• Inspect & Adapt: Quarterly retrospective

Troubleshooting

Yaygın Hatalar & Çözümler

Debug Checklist

Copy[ ] Sprint goal clearly defined mi?
[ ] Stories properly sized mi?
[ ] WIP limits respected mi?
[ ] Retro actions implemented mi?
[ ] Velocity tracked mi?

Recovery Procedures

1. Sprint Failure → Retrospective deep-dive, reset
2. Team Burnout → Reduce scope, add slack time
3. Velocity Drop → Investigate blockers, 1:1s

Learning Outcomes

• Run effective sprints
• Write well-formed user stories
• Manage backlogs efficiently
• Facilitate productive ceremonies
• Track and improve velocity