4 min read • Guide 524 of 877
How to Use GitScrum for Full-Stack Development Teams?
How to use GitScrum for full-stack development teams?
GitScrum supports full-stack development with unified boards for frontend, backend, and database work. Use labels to categorize layers, set WIP limits for balanced capacity, track dependencies between layers, and document architecture in NoteVault. Full-stack teams using unified boards reduce integration issues by 45% [Source: Full-Stack Development Survey 2024].
Full-stack project setup:
- Create project - Application name
- Configure columns - Standard workflow
- Add layer labels - Frontend, backend, db
- Set WIP limits - Balanced capacity
- Document in NoteVault - Architecture
- Enable Team Standup - Cross-layer coordination
Full-stack development columns
| Column | WIP Limit | Purpose |
|---|---|---|
| Backlog | 15 | All features |
| Ready | 10 | Groomed, designed |
| Development | Team size | Active work |
| Code Review | 4 | All layers |
| Testing | 5 | Integration testing |
| Done | None | Shipped |
Layer labels
| Label | Scope |
|---|---|
| frontend | UI only |
| backend | API only |
| database | DB changes |
| fullstack | All layers |
| devops | Infrastructure |
Dependency tracking labels
| Label | Meaning |
|---|---|
| depends-on-api | Frontend waiting for API |
| api-ready | Backend API complete |
| depends-on-db | Needs database changes |
| db-ready | Database migration done |
| blocked-cross-layer | Waiting on other layer |
Full-stack workflow patterns
| Feature Type | Workflow |
|---|---|
| UI-first | Frontend → Backend → Integration |
| API-first | Backend → Frontend → Integration |
| Database-first | DB → Backend → Frontend |
| Parallel | All layers concurrent |
NoteVault for full-stack
| Document | Content |
|---|---|
| Architecture | System overview |
| API Contracts | Endpoint specs |
| Database Schema | Data model |
| Frontend Patterns | Component architecture |
| Integration Guide | How layers connect |
WIP limits for full-stack
| Strategy | Implementation |
|---|---|
| Per-layer limits | 2 frontend, 2 backend |
| Total limit | 5 across all layers |
| Dependency-aware | Lower when blocked |
Feature breakdown example
| Feature | Tasks |
|---|---|
| User profile | DB migration |
| Backend API | |
| Frontend UI | |
| Integration test |
Cross-layer coordination
| Need | GitScrum Solution |
|---|---|
| API changes | Notify frontend via labels |
| DB changes | Notify backend via labels |
| Integration | Testing column |
| Communication | Team Standup |
| Documentation | NoteVault contracts |
Full-stack Team Standup pattern
| Developer | Yesterday | Today |
|---|---|---|
| Full-stack dev | Backend API done | Frontend integration |
| Frontend dev | Waiting on API | API ready, starting UI |
| Backend dev | DB migration | API endpoints |
Integration testing approach
| Test Type | When |
|---|---|
| API tests | Backend complete |
| Component tests | Frontend complete |
| E2E tests | All layers integrated |
| Regression | Before release |
Auto-assign for full-stack
| Column | Auto-Assign |
|---|---|
| Code Review | Senior devs (all layers) |
| Testing | QA team |
| Integration issues | Tech lead |