GitScrum for Dev Teams | GitHub Integration
Configure GitScrum for software teams with GitHub integration, sprint management, keyboard shortcuts, and markdown support. Built for developers.
7 min read
GitScrum is built for software teams, with deep GitHub integration, developer-focused workflows, and sprint management that doesn't get in the way of coding. This guide covers optimal setup for development teams of all sizes.
Developer-Focused Features
| Feature | Benefit |
|---|---|
| GitHub integration | Commits link to tasks |
| Keyboard shortcuts | Stay in flow |
| Markdown support | Code-friendly formatting |
| API access | Automation capability |
| Minimal ceremony | Focus on shipping |
Team Setup
Board Configuration
DEVELOPMENT TEAM BOARD SETUP
════════════════════════════
COLUMNS:
─────────────────────────────────────
Backlog → Prioritized work not yet started
Ready → Refined, ready to pull
In Progress → Currently being developed
Review → Code review / PR open
QA → Testing (optional)
Done → Merged and deployed
WIP LIMITS:
├── Ready: ∞ (or 2× team size)
├── In Progress: 2 per developer
├── Review: 3 total
├── QA: 5 total
└── Done: No limit
LABELS:
├── Type: feature, bug, chore, spike
├── Priority: P1, P2, P3
├── Size: S, M, L (optional)
├── Component: frontend, backend, infra
└── Status: blocked, needs-review
AUTOMATION:
├── PR opened → Move to Review
├── PR merged → Move to Done
├── In Review > 48h → Alert
└── Blocked label → Notify lead
GitHub Integration
GITHUB INTEGRATION SETUP
════════════════════════
CONNECT REPOSITORY:
1. Settings → Integrations → GitHub
2. Authorize GitScrum
3. Select organization
4. Select repository(ies)
5. Configure linking rules
COMMIT LINKING:
─────────────────────────────────────
# Mention task ID in commit message
git commit -m "Add login validation [GS-123]"
# GitScrum automatically:
├── Links commit to task
├── Shows in task activity
├── Updates progress
└── Notifies assignee
BRANCH NAMING:
─────────────────────────────────────
# From GitScrum:
Click "Create Branch" on task
→ Creates: feature/GS-123-login-validation
# Branch naming pattern configurable:
├── feature/[ID]-[slug]
├── [ID]/[title]
├── [type]/[ID]
└── Custom pattern
PR SYNC:
─────────────────────────────────────
When PR opened mentioning GS-123:
├── Task moves to "Review"
├── PR link shown on task
├── Status badge on task
└── Reviewers visible
When PR merged:
├── Task moves to "Done"
├── Merge info recorded
├── Cycle time calculated
└── Deploy tracking (optional)
Sprint Management
Sprint Configuration
SPRINT SETUP
════════════
SPRINT SETTINGS:
├── Duration: 2 weeks (configurable)
├── Start: Monday
├── End: Friday week 2
├── Planning: Monday morning
├── Review: Friday afternoon
├── Retro: After review
SPRINT BOARD VIEW:
┌─────────────────────────────────────────────────────────┐
│ Sprint 24: Jan 15 - Jan 26 │
│ ████████████░░░░░░ 67% complete | 7 days left │
├─────────────────────────────────────────────────────────┤
│ Ready │ In Progress │ Review │ Done │
│ ──────────│─────────────│─────────│────────────── │
│ [GS-130] │ [GS-123] S │ [GS-125]│ [GS-126] ✓ │
│ [GS-131] │ [GS-124] M │ │ [GS-127] ✓ │
│ │ │ │ [GS-128] ✓ │
│ │ │ │ [GS-129] ✓ │
├─────────────────────────────────────────────────────────┤
│ Committed: 34 pts | Done: 23 pts | Remaining: 11 pts │
└─────────────────────────────────────────────────────────┘
VELOCITY TRACKING:
├── Points per sprint (trend)
├── Comparison to average
├── Forecast for future
└── Calibration alerts
Sprint Metrics
SPRINT METRICS DASHBOARD
════════════════════════
┌─────────────────────────────────────────────────────────┐
│ Sprint 24 Metrics │
├─────────────────────────────────────────────────────────┤
│ │
│ VELOCITY │
│ ───────────────────────────────── │
│ Current: 34 pts (committed) │
│ Average: 32 pts (last 6 sprints) │
│ Trend: ↗ +6% improving │
│ │
│ BURNDOWN │
│ ───────────────────────────────── │
│ Day 3: 28 pts remaining │
│ Ideal: 26 pts │
│ Status: Slightly behind (1 blocked item) │
│ │
│ CYCLE TIME │
│ ───────────────────────────────── │
│ Average: 3.2 days │
│ Dev: 1.8 days | Review: 0.9 days | QA: 0.5 days │
│ │
│ COMPLETION │
│ ───────────────────────────────── │
│ Features: 4/6 complete │
│ Bugs: 3/3 complete ✓ │
│ Chores: 1/2 complete │
│ │
└─────────────────────────────────────────────────────────┘
Developer Workflow
Daily Workflow
DEVELOPER DAILY WORKFLOW
════════════════════════
MORNING:
─────────────────────────────────────
1. Check board for assignment
→ Filter: Assigned to me
2. Post async standup (or attend)
→ What I did / What I'll do / Blockers
3. Pull latest code
git pull origin main
4. Start task
→ Click "Start Work" (if configured)
→ Branch created automatically
CODING:
─────────────────────────────────────
5. Develop feature
→ Reference task in commits
git commit -m "Add feature [GS-123]"
6. When ready for review
→ Push branch
→ Create PR (auto-linked to task)
→ Task moves to Review automatically
7. Address feedback
→ Update code
→ PR updated
→ Task stays in Review
8. When merged
→ Task moves to Done
→ Celebrate! 🎉
END OF DAY:
─────────────────────────────────────
9. Update any task status
→ If not auto-synced
10. Note any blockers
→ Add label, comment, notify
Keyboard Shortcuts
GITSCRUM KEYBOARD SHORTCUTS
═══════════════════════════
NAVIGATION:
├── G B → Go to Board
├── G L → Go to Backlog
├── G S → Go to Sprint
├── G D → Go to Dashboard
└── / → Open search
TASK ACTIONS:
├── C → Create new task
├── E → Edit selected task
├── A → Assign selected task
├── L → Add label
├── M → Move to column
└── Delete → Archive task
QUICK CREATE:
├── Shift+C → Create task with details
├── Cmd+Enter → Save task
├── Escape → Cancel
FILTERING:
├── F → Open filter panel
├── Cmd+K → Command palette
└── Q → Quick filters
Team Collaboration
Code Review Integration
CODE REVIEW WORKFLOW
════════════════════
PR CREATED:
├── Task auto-moves to Review
├── PR link on task card
├── Status badge visible
└── Assignee notified
REVIEW SLA:
├── Target: 4 hours first review
├── GitScrum shows PR age
├── Alert if exceeding SLA
└── Track in metrics
REVIEW COMPLETE:
├── PR approved
├── Merge button available
├── On merge → Task to Done
└── Deploy tracking triggered
REVIEW DASHBOARD:
┌─────────────────────────────────────────────────────────┐
│ PRs Awaiting Review │
├─────────────────────────────────────────────────────────┤
│ #234 Login validation (GS-123) 2h ago Sarah │
│ #235 Password reset (GS-124) 5h ago Mike ⚠️ │
│ #236 Session mgmt (GS-125) 1h ago Alex │
└─────────────────────────────────────────────────────────┘
Best Practices
For Dev Teams
Anti-Patterns
DEVELOPMENT TEAM MISTAKES:
✗ Manual status updates (use integration)
✗ Large tasks (too big to track)
✗ No commit references (lost context)
✗ Ignoring WIP limits (too much in progress)
✗ Story point inflation
✗ Not using board filter
✗ Skipping retros