4 min lectura • Guide 508 of 877
How to Use GitScrum for DevOps and SRE Teams?
How to use GitScrum for DevOps and SRE teams?
GitScrum supports DevOps/SRE teams with columns for infrastructure work, incident tracking, and operational improvements. Configure columns for incidents, infrastructure tasks, and automation projects. Use labels for severity, systems affected, and work type. NoteVault stores runbooks and postmortems. Structured SRE management reduces MTTR by 30% [Source: SRE State Report 2024].
DevOps/SRE project setup:
- Create project - DevOps or SRE team
- Configure incident columns - Incident workflow
- Add infra columns - Planned work
- Set severity labels - P1, P2, P3, P4
- Configure auto-assign - On-call routing
- Create NoteVault docs - Runbooks
DevOps/SRE columns
| Column | WIP Limit | Purpose |
|---|---|---|
| Incident Triage | 5 | New incidents |
| Active Incident | 3 | Being investigated |
| Mitigated | 2 | Stable, needs fix |
| Resolved | None | Incident closed |
| Infra Backlog | 15 | Planned work |
| In Progress | 3 | Active infra work |
| Done | None | Completed |
Incident severity labels
| Severity | Description | Response |
|---|---|---|
| P1 - Critical | Service down | Immediate |
| P2 - High | Degraded service | <1 hour |
| P3 - Medium | Minor impact | <4 hours |
| P4 - Low | No impact | Next sprint |
System labels
| Label | System |
|---|---|
| aws | AWS infrastructure |
| gcp | Google Cloud |
| k8s | Kubernetes |
| terraform | IaC |
| ci-cd | Pipelines |
| monitoring | Observability |
Incident workflow
| Stage | Actions |
|---|---|
| Triage | Assess severity, assign |
| Active | Investigate, communicate |
| Mitigated | Stable, plan fix |
| Resolved | Fix deployed |
| Postmortem | Review, learn |
Runbooks in NoteVault
| Runbook | Content |
|---|---|
| Service X Outage | Steps to diagnose, fix |
| Database Failover | Failover procedure |
| Deployment Rollback | Rollback steps |
| On-Call Handoff | Rotation process |
| Escalation | When and how |
Balancing incidents vs planned work
| Approach | Implementation |
|---|---|
| WIP limits | Limit active incidents |
| Separate columns | Visual separation |
| Priority labels | Clear priority |
| Time allocation | 70% planned, 30% incidents |
| Rotation | On-call rotation |
DevOps/SRE Team Standup
| Tab | Content |
|---|---|
| Yesterday | Incidents resolved, work done |
| Today | On-call status, planned work |
| Blockers | Dependencies, waiting |
| Weekly | Incident trends, SLO status |
Postmortem workflow
| Step | GitScrum Action |
|---|---|
| Incident resolved | Move to Resolved |
| Schedule postmortem | Create task, assign |
| Write postmortem | Document in NoteVault |
| Action items | Create tasks from postmortem |
| Track actions | Regular tasks in Infra Backlog |
Automation tracking
| Automation Type | Label |
|---|---|
| Toil reduction | toil |
| Monitoring | monitoring |
| Deployment | ci-cd |
| Security | security |
| Cost optimization | cost |
SRE metrics to track
| Metric | GitScrum Tracking |
|---|---|
| MTTR | Incident cycle time |
| Incident count | Resolved column |
| Toil reduction | Automation tasks |
| Error budget | NoteVault SLO doc |