DevOps Project Management | Incidents & Infrastructure
Manage DevOps workflows for incidents, infrastructure, and platform requests. GitScrum provides severity labels, incident columns, and NoteVault runbooks.
4 min read
DevOps and platform teams work differently than feature teams—infrastructure projects, incident response, and platform improvements require different workflows. GitScrum adapts to these needs with flexible boards, incident labels, and visibility into both project work and operational tasks.
Platform Team Challenges
What Makes DevOps Different
DEVOPS/PLATFORM WORK PATTERNS:
┌─────────────────────────────────────────────────────────────┐
│ UNIQUE PLATFORM TEAM NEEDS │
├─────────────────────────────────────────────────────────────┤
│ │
│ INTERRUPT-DRIVEN: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ • Incidents interrupt planned work ││
│ │ • On-call rotations ││
│ │ • Support requests from dev teams ││
│ │ • Can't predict weekly capacity ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ INFRASTRUCTURE PROJECTS: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ • Long-running migrations ││
│ │ • Security improvements ││
│ │ • Cost optimization ││
│ │ • Tooling and automation ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ CROSS-TEAM SERVICE: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ • Support multiple development teams ││
│ │ • Platform requests and prioritization ││
│ │ • Documentation and training ││
│ │ • SLAs and service levels ││
│ └─────────────────────────────────────────────────────────┘│
│ │
└─────────────────────────────────────────────────────────────┘
Board Structure
DevOps Workflow
| Column | Purpose |
|---|---|
| Requests | Incoming from teams |
| Triage | Priority assessment |
| Backlog | Prioritized work |
| In Progress | Active work |
| Blocked | Waiting on external |
| Review | Peer review |
| Done | Completed |
| Incidents | Active incidents |
Label System
Platform Team Labels
DEVOPS PROJECT LABELS:
┌─────────────────────────────────────────────────────────────┐
│ ORGANIZING PLATFORM WORK │
├─────────────────────────────────────────────────────────────┤
│ │
│ TYPE LABELS: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ type:incident ││
│ │ type:infrastructure ││
│ │ type:security ││
│ │ type:automation ││
│ │ type:support-request ││
│ │ type:documentation ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ AREA LABELS: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ area:kubernetes ││
│ │ area:ci-cd ││
│ │ area:monitoring ││
│ │ area:databases ││
│ │ area:networking ││
│ │ area:security ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ URGENCY LABELS: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ sev:1-critical → Production down ││
│ │ sev:2-high → Major impact ││
│ │ sev:3-medium → Degraded service ││
│ │ sev:4-low → Minor issue ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ REQUESTING TEAM: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ team:frontend ││
│ │ team:backend ││
│ │ team:mobile ││
│ │ team:data ││
│ └─────────────────────────────────────────────────────────┘│
│ │
└─────────────────────────────────────────────────────────────┘
Incident Management
Incident Workflow
INCIDENT PROCESS:
┌─────────────────────────────────────────────────────────────┐
│ INCIDENT RESPONSE WORKFLOW │
├─────────────────────────────────────────────────────────────┤
│ │
│ DETECTION: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ • Alert fires or report received ││
│ │ • Create task: "[INC-123] Service X down" ││
│ │ • Add labels: type:incident, sev:1-critical ││
│ │ • Move to Incidents column ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ RESPONSE: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ • Assign on-call engineer ││
│ │ • Document in task comments (timeline) ││
│ │ • Update status regularly ││
│ │ • Coordinate in communication channel ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ RESOLUTION: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ • Document fix applied ││
│ │ • Move to Done when resolved ││
│ │ • Create follow-up tasks for root cause ││
│ │ • Schedule post-mortem ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ POST-MORTEM: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ • Document in NoteVault ││
│ │ • Create improvement tasks ││
│ │ • Link to incident task ││
│ │ • Track action items ││
│ └─────────────────────────────────────────────────────────┘│
│ │
└─────────────────────────────────────────────────────────────┘
Documentation
NoteVault for DevOps
| Note | Content |
|---|---|
| Runbooks | Incident response procedures |
| Architecture | Infrastructure diagrams |
| On-call guide | Rotation and escalation |
| Post-mortems | Incident learnings |