agile

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)

Day	Ceremony	Duration	Attendees
Mon	Sprint Planning	2h	Full team
Daily	Standup	15min	Full team
Thu	Design Review	1h	PM, Design, Eng
Fri	Sprint Review	1h	Full team + stakeholders
Fri	Retrospective	30min	Full team

Sprint Planning Template

Sprint 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)

As 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

Points	Complexity	Example
1	Trivial	Config change
2	Small	Minor UI tweak
3	Medium	New simple feature
5	Large	Complex feature
8	XL	Multiple components
13	Epic	Should be broken down

Kanban