forked from steipete/agent-rules
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathazdo-sprint-management.mdc
More file actions
133 lines (105 loc) · 4.93 KB
/
azdo-sprint-management.mdc
File metadata and controls
133 lines (105 loc) · 4.93 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
---
description: "Manage Azure DevOps Sprints including planning, tracking, and retrospectives"
globs: ["**/*"]
alwaysApply: true
---
# Azure DevOps Sprint Management
Comprehensive sprint management including planning, daily tracking, and retrospectives.
## Sprint Planning:
### Before Sprint Planning:
1. **Backlog Refinement**: Ensure Product Backlog Items (PBIs) are ready
2. **Capacity Planning**: Calculate team capacity for the sprint
3. **Definition of Ready**: Verify work items meet DoR criteria
4. **Dependencies**: Identify and resolve cross-team dependencies
### During Sprint Planning:
1. **Sprint Goal**: Define clear, measurable sprint objective
2. **Work Item Selection**: Choose PBIs based on priority and capacity
3. **Task Breakdown**: Break PBIs into specific development tasks
4. **Estimation**: Size work items using story points or hours
5. **Commitment**: Team commits to sprint backlog
### Sprint Planning Process:
1. Review sprint capacity: `az boards iteration team list`
2. Query high-priority backlog items: `az boards query --wiql "SELECT * FROM WorkItems WHERE [System.WorkItemType] = 'User Story' AND [System.State] = 'New' ORDER BY [Microsoft.VSTS.Common.Priority]"`
3. Create sprint: `az boards iteration project create --name "Sprint 1"`
4. Assign work items to sprint: `az boards work-item update --id <work-item-id> --iteration "ProjectName\\Sprint 1"`
### Project Configuration Template
- **Current Iteration**: `ProjectName\\Sprint 1`
- **Project**: `ProjectName`
- **Primary Assignee**: `user@company.com`
- **Sprint Format**: `ProjectName\\SprintName`
## Daily Sprint Tracking:
### Daily Standup Support:
- **Yesterday**: What work items were completed?
- **Today**: What work items will be worked on?
- **Blockers**: Any impediments preventing progress?
- **Sprint Progress**: Burndown chart analysis
### Work Item State Management:
- Move work items through states: New → Active → Resolved → Closed
- Update remaining work on tasks daily
- Log time spent on work items
- Update work item discussions with progress notes
### Daily Commands:
```bash
# Check current sprint progress
az boards query --wiql "SELECT * FROM WorkItems WHERE [System.IterationPath] = 'ProjectName\\Sprint 1'"
# List active work items assigned to you
az boards work-item list --iteration "ProjectName\\Sprint 1" --assigned-to "user@company.com" --output table
# Update work item state
az boards work-item update --id 12345 --state "Active"
# Update remaining work
az boards work-item update --id 12345 --fields "Microsoft.VSTS.Scheduling.RemainingWork=4"
# Add daily progress comment
az boards work-item update --id 12345 --discussion "Completed API integration. Starting UI tests tomorrow."
```
## Sprint Review:
### Demo Preparation:
1. **Completed Work**: Identify all completed PBIs
2. **Demo Script**: Prepare user-focused demonstrations
3. **Metrics**: Gather velocity, burndown, and quality metrics
4. **Stakeholder Feedback**: Collect and document feedback
### Review Process:
1. Query completed work items: `az boards query --wiql "SELECT * FROM WorkItems WHERE [System.IterationPath] = 'ProjectName\\Sprint 1' AND [System.State] = 'Closed'"`
2. Calculate sprint velocity
3. Update product backlog based on feedback
4. Document lessons learned
```bash
# Generate sprint completion report
az boards query --wiql "SELECT [System.Id], [System.Title], [System.WorkItemType], [System.State] FROM WorkItems WHERE [System.IterationPath] = 'ProjectName\\Sprint 1'" --output table
# List work items by state
az boards query --wiql "SELECT * FROM WorkItems WHERE [System.IterationPath] = 'ProjectName\\Sprint 1' AND [System.State] IN ('Active', 'Resolved', 'Closed')" --output table
```
## Sprint Retrospective:
### Retrospective Categories:
- **What Went Well**: Positive aspects to continue
- **What Could Improve**: Areas needing attention
- **Action Items**: Specific improvements for next sprint
- **Experiments**: New practices to try
### Metrics to Review:
- Sprint velocity and consistency
- Work item cycle time
- Defect rates and escape rates
- Team satisfaction and engagement
- Sprint goal achievement
### Process Improvements:
1. Create improvement work items for significant issues
2. Update team processes and definitions
3. Adjust estimation practices if needed
4. Plan capacity more accurately
## Azure DevOps Integration:
### Queries and Dashboards:
- Create custom queries for sprint tracking
- Set up burndown and velocity charts
- Configure team dashboards for visibility
- Use sprint overview widgets
### Automation:
- Set up work item state transitions
- Configure notifications for key events
- Use PR policies to enforce work item linking
- Automate sprint reports generation
### Best Practices:
- Keep sprint backlog stable after commitment
- Update work items daily with actual progress
- Use consistent work item types and states
- Maintain clear Definition of Done
- Regular backlog refinement between sprints
- Focus on sprint goal achievement over individual tasks