Getting Started with Scrum | Sprints & Roles
Implement Scrum with 2-week sprints, defined roles, and ceremonies. GitScrum provides sprint planning, backlog management, and burndown charts.
5 min read
Scrum provides a structured framework for iterative development with defined roles, ceremonies, and artifacts. GitScrum supports complete Scrum implementation with sprint planning, backlog management, burndown charts, and retrospective tools that help teams embrace the framework effectively.
Scrum Framework Overview
| Element | Purpose | Frequency |
|---|---|---|
| Sprint | Time-boxed iteration | 1-4 weeks |
| Sprint Planning | Plan sprint work | Start of sprint |
| Daily Standup | Sync & blockers | Daily (15 min) |
| Sprint Review | Demo to stakeholders | End of sprint |
| Retrospective | Team improvement | End of sprint |
Scrum Roles
SCRUM TEAM STRUCTURE
┌─────────────────────────────────────────────────┐
│ │
│ PRODUCT OWNER │
│ ├── Owns the product backlog │
│ ├── Prioritizes by business value │
│ ├── Defines acceptance criteria │
│ └── Makes scope decisions │
│ │
├─────────────────────────────────────────────────┤
│ │
│ SCRUM MASTER │
│ ├── Facilitates ceremonies │
│ ├── Removes impediments │
│ ├── Coaches agile practices │
│ └── Protects team from distractions │
│ │
├─────────────────────────────────────────────────┤
│ │
│ DEVELOPMENT TEAM (3-9 members) │
│ ├── Self-organizing │
│ ├── Cross-functional │
│ ├── Commits to sprint goals │
│ └── Delivers working increment │
│ │
└─────────────────────────────────────────────────┘
Sprint Cycle
TWO-WEEK SPRINT STRUCTURE
┌─────────────────────────────────────────────────┐
│ DAY 1 (Monday AM) │
│ ┌─────────────────────────────────────────┐ │
│ │ SPRINT PLANNING (2-4 hours) │ │
│ │ • Review sprint goal │ │
│ │ • Select backlog items │ │
│ │ • Break into tasks │ │
│ │ • Commit as team │ │
│ └─────────────────────────────────────────┘ │
│ │
│ DAYS 1-9 (Daily) │
│ ┌─────────────────────────────────────────┐ │
│ │ DAILY STANDUP (15 minutes) │ │
│ │ • What did I do yesterday? │ │
│ │ • What will I do today? │ │
│ │ • Any blockers? │ │
│ └─────────────────────────────────────────┘ │
│ │
│ MID-SPRINT │
│ ┌─────────────────────────────────────────┐ │
│ │ BACKLOG REFINEMENT (1 hour) │ │
│ │ • Refine upcoming items │ │
│ │ • Estimate │ │
│ │ • Clarify requirements │ │
│ └─────────────────────────────────────────┘ │
│ │
│ DAY 10 (Friday PM) │
│ ┌─────────────────────────────────────────┐ │
│ │ SPRINT REVIEW (1-2 hours) │ │
│ │ • Demo completed work │ │
│ │ • Gather stakeholder feedback │ │
│ │ • Update backlog │ │
│ └─────────────────────────────────────────┘ │
│ ┌─────────────────────────────────────────┐ │
│ │ RETROSPECTIVE (1-1.5 hours) │ │
│ │ • What went well? │ │
│ │ • What to improve? │ │
│ │ • Action items │ │
│ └─────────────────────────────────────────┘ │
└─────────────────────────────────────────────────┘
Scrum Artifacts
PRODUCT BACKLOG
┌─────────────────────────────────────────────────┐
│ Ordered list of everything needed │
│ • Prioritized by Product Owner │
│ • Top items refined and ready │
│ • Always evolving │
│ │
│ 1. [Ready] User login - 5 pts │
│ 2. [Ready] Dashboard view - 8 pts │
│ 3. [Ready] Settings page - 3 pts │
│ 4. [Draft] Export feature - ? │
│ 5. [Idea] Mobile app - ? │
└─────────────────────────────────────────────────┘
SPRINT BACKLOG
┌─────────────────────────────────────────────────┐
│ Work committed for current sprint │
│ • Selected from product backlog │
│ • Team commits to completing │
│ • Supports sprint goal │
│ │
│ Sprint 12 Goal: "Users can manage profiles" │
│ ├── User login (5 pts) │
│ │ ├── API endpoint │
│ │ ├── UI component │
│ │ └── Tests │
│ └── Dashboard view (8 pts) │
│ ├── Layout │
│ ├── Data fetch │
│ └── Error states │
└─────────────────────────────────────────────────┘
INCREMENT
┌─────────────────────────────────────────────────┐
│ Potentially shippable product at sprint end │
│ • Meets Definition of Done │
│ • Adds to previous increments │
│ • Inspectable by stakeholders │
└─────────────────────────────────────────────────┘
Best Practices
Anti-Patterns
✗ Sprint planning without refined backlog
✗ Standups becoming status reports to manager
✗ Skipping retrospectives when busy
✗ Adding work mid-sprint routinely
✗ No Definition of Done
✗ Sprint Review without stakeholders