4 min lectura • Guide 361 of 877
How to Track OKRs for Development Teams with GitScrum?
How to track OKRs for development teams with GitScrum?
Track OKRs by documenting objectives in NoteVault with measurable key results, then creating labels for each objective (okr:q1-performance). Tag tasks contributing to each OKR. Use Cumulative Flow reports to track progress toward key results. Review weekly in Team Standup to ensure daily work connects to quarterly objectives.
OKR structure in NoteVault
# Q1 2025 Engineering OKRs
## Objective 1: Improve Platform Reliability
- KR1: Achieve 99.9% uptime (current: 99.5%) [Progress: 70%]
- KR2: MTTR under 15 minutes (current: 45 min) [Progress: 40%]
- KR3: Zero P1 incidents from known issues [Progress: 80%]
Related tasks label: okr:reliability
## Objective 2: Accelerate Delivery Speed
- KR1: Deploy to production 2x per day (current: 3x/week)
- KR2: Lead time under 3 days (current: 7 days)
- KR3: PR review time under 4 hours (current: 12 hours)
Related tasks label: okr:speed
## Weekly Check-in
| Week | O1 Progress | O2 Progress | Notes |
|------|-------------|-------------|-------|
| W1 | 15% | 10% | Starting work |
| W2 | 30% | 25% | On track |
Setting up OKR tracking:
- Define OKRs - Quarterly planning with team
- Create NoteVault doc - Central OKR reference
- Create OKR labels - okr:reliability, okr:speed, etc.
- Tag relevant tasks - Connect work to OKRs
- Weekly OKR review - Update progress percentages
- Filter by OKR label - See all contributing work
- End-of-quarter review - Score OKR achievement
Connecting tasks to OKRs
| OKR | Label | Example Tasks |
|---|---|---|
| Improve reliability | okr:reliability | Add monitoring, fix timeout bugs |
| Accelerate delivery | okr:speed | CI pipeline improvements, automation |
| Reduce tech debt | okr:tech-debt | Refactoring, dependency updates |
| Improve security | okr:security | Audit fixes, vulnerability patches |
OKR progress tracking methods
| Method | How It Works |
|---|---|
| Label filter | See all tasks tagged with OKR label |
| Completion rate | % of OKR-tagged tasks completed |
| KR metrics | Measure actual KR progress (uptime %, etc.) |
| Weekly check-in | Manual progress update in NoteVault |
| Cumulative Flow | Work completion trends |
Good vs bad engineering OKRs
| Bad OKR | Good OKR |
|---|---|
| Complete 50 tickets | Deploy to production 2x per day |
| Work on performance | Page load under 2 seconds |
| Reduce bugs | Zero P1 bugs in production |
| Improve code quality | Test coverage above 80% |
| Better documentation | 100% of APIs documented |