Implement Scrum with GitScrum | Sprints, Ceremonies, Artifacts
Master Scrum implementation with GitScrum: sprint planning, daily standups, reviews, and retrospectives. Set up roles, artifacts, and ceremonies for effective delivery.
8 min read
Scrum provides a proven framework for iterative development with clear roles, ceremonies, and artifacts. GitScrum supports Scrum implementation with sprint boards, backlog management, burndown charts, and ceremony facilitation tools.
Scrum Framework
Core Elements
SCRUM FRAMEWORK OVERVIEW:
┌─────────────────────────────────────────────────────────────┐
│ │
│ ROLES: │
│ • Product Owner: Owns backlog, prioritizes work │
│ • Scrum Master: Facilitates process, removes blockers │
│ • Development Team: Self-organizing, delivers increment │
│ │
│ EVENTS (Ceremonies): │
│ • Sprint: Time-box for delivering increment (1-4 weeks) │
│ • Sprint Planning: Define sprint goal and backlog │
│ • Daily Scrum: 15-min sync, identify blockers │
│ • Sprint Review: Demo increment, gather feedback │
│ • Sprint Retrospective: Process improvement │
│ │
│ ARTIFACTS: │
│ • Product Backlog: Ordered list of all work │
│ • Sprint Backlog: Work committed for current sprint │
│ • Increment: Potentially shippable product version │
│ │
│ COMMITMENTS: │
│ • Product Goal: Long-term objective │
│ • Sprint Goal: Purpose of the sprint │
│ • Definition of Done: Quality standard │
└─────────────────────────────────────────────────────────────┘
Sprint Cycle
2-WEEK SPRINT TIMELINE:
┌─────────────────────────────────────────────────────────────┐
│ │
│ WEEK 1: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ Mon │ Tue │ Wed │ Thu │ Fri ││
│ │ Planning│ │ │ │ ││
│ │ (2h) │ Dev │ Dev │ Dev │ Dev ││
│ │ Daily │ Daily │ Daily │ Daily │ Daily ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ WEEK 2: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ Mon │ Tue │ Wed │ Thu │ Fri ││
│ │ │ │ │ │ Review ││
│ │ Dev │ Dev │ Dev │ Dev │ (1h) ││
│ │ Daily │ Daily │ Daily │ Daily │ Retro ││
│ │ │ │ Refine│ │ (1h) ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ REFINEMENT: Mid-sprint, prepare next sprint's work │
└─────────────────────────────────────────────────────────────┘
Sprint Planning
Planning Meeting
SPRINT PLANNING STRUCTURE (2 hours):
┌─────────────────────────────────────────────────────────────┐
│ │
│ PART 1: WHAT (45 min) │
│ Facilitated by Product Owner │
│ │
│ 1. Review product goal and roadmap context │
│ 2. Propose sprint goal │
│ 3. Present prioritized backlog items │
│ 4. Team asks clarifying questions │
│ 5. Team assesses capacity │
│ 6. Agree on sprint goal │
│ │
│ PART 2: HOW (1 hour) │
│ Facilitated by Development Team │
│ │
│ 1. Break stories into tasks │
│ 2. Discuss technical approach │
│ 3. Identify dependencies │
│ 4. Pull items until capacity reached │
│ 5. Commit to sprint backlog │
│ │
│ OUTPUT: │
│ • Sprint goal (1 sentence) │
│ • Sprint backlog (committed items) │
│ • Team confident in commitment │
└─────────────────────────────────────────────────────────────┘
Sprint Backlog
SPRINT BACKLOG STRUCTURE:
┌─────────────────────────────────────────────────────────────┐
│ SPRINT 24 - Goal: Complete checkout redesign │
│ Capacity: 45 points | Committed: 42 points │
├─────────────────────────────────────────────────────────────┤
│ │
│ USER STORIES: │
│ │
│ #115 New checkout flow UI (8 pts) │
│ ├── Design review [✓ Done] │
│ ├── Implement cart summary [■ In Progress] │
│ ├── Implement payment form [□ To Do] │
│ └── Write tests [□ To Do] │
│ │
│ #116 Payment gateway integration (13 pts) │
│ ├── Stripe API integration [■ In Progress] │
│ ├── Error handling [□ To Do] │
│ ├── Webhook handlers [□ To Do] │
│ └── Integration tests [□ To Do] │
│ │
│ #117 Order confirmation (8 pts) │
│ ├── Email template [□ To Do] │
│ ├── Confirmation page [□ To Do] │
│ └── Analytics events [□ To Do] │
│ │
│ #118 Guest checkout option (5 pts) │
│ BUG-45 Cart total calculation (3 pts) │
│ TECH-12 Payment logging (5 pts) │
└─────────────────────────────────────────────────────────────┘
Daily Ceremonies
Daily Scrum
DAILY SCRUM FORMAT (15 min):
┌─────────────────────────────────────────────────────────────┐
│ │
│ TIME: Same time daily (recommended: morning) │
│ WHO: Development team (others may observe) │
│ │
│ EACH TEAM MEMBER: │
│ 1. What did I complete yesterday? │
│ 2. What will I work on today? │
│ 3. Any blockers? │
│ │
│ ALTERNATIVE FORMAT (Focus on Goal): │
│ 1. Are we on track for the sprint goal? │
│ 2. What work remains? │
│ 3. Any adjustments needed? │
│ │
│ SCRUM MASTER: │
│ • Keep time-boxed to 15 min │
│ • Note blockers for follow-up │
│ • Don't solve problems in standup │
│ • Schedule follow-up discussions as needed │
│ │
│ ANTI-PATTERNS: │
│ ✗ Status report to manager │
│ ✗ Problem-solving sessions │
│ ✗ Going over 15 minutes │
│ ✗ Only some people talking │
└─────────────────────────────────────────────────────────────┘
Sprint Board
SPRINT BOARD:
┌─────────────────────────────────────────────────────────────┐
│ SPRINT 24 | Day 6 of 10 | Goal: Complete checkout redesign │
├────────────┬────────────┬────────────┬────────────┬────────┤
│ TO DO │ IN PROGRESS│ IN REVIEW │ TESTING │ DONE │
│ (backlog) │ (WIP: 4) │ (WIP: 3) │ (WIP: 2) │ │
├────────────┼────────────┼────────────┼────────────┼────────┤
│ │ │ │ │ │
│ □ #117 │ ■ #115-2 │ ■ #116-1 │ ■ #115-1 │ ✓#115-0│
│ Tasks:3 │ @Alex │ @Maria │ @QA │ │
│ │ │ │ │ ✓#118 │
│ □ #116-3 │ ■ #116-2 │ │ │ │
│ │ @Jordan │ │ │ │
│ │ │ │ │ │
│ □ BUG-45 │ │ │ │ │
│ │ │ │ │ │
└────────────┴────────────┴────────────┴────────────┴────────┘
│ Burndown: ████████░░░░░░░░░░ 42% complete │
└─────────────────────────────────────────────────────────────┘
Sprint Closure
Sprint Review
SPRINT REVIEW (1 hour):
┌─────────────────────────────────────────────────────────────┐
│ │
│ ATTENDEES: │
│ Scrum team + stakeholders (business, users, leadership) │
│ │
│ AGENDA: │
│ │
│ 1. Sprint Summary (5 min) - Product Owner │
│ • Sprint goal │
│ • What was planned vs delivered │
│ │
│ 2. Demo (40 min) - Development Team │
│ • Live demonstration of completed features │
│ • Focus on user value, not technical details │
│ • Gather feedback and questions │
│ │
│ 3. Backlog Update (10 min) - Product Owner │
│ • Impact on upcoming priorities │
│ • Incorporate feedback │
│ • Preview next sprint direction │
│ │
│ 4. Q&A (5 min) │
│ │
│ OUTPUT: │
│ • Stakeholder feedback captured │
│ • Updated product backlog │
│ • Clear next priorities │
└─────────────────────────────────────────────────────────────┘
Sprint Retrospective
SPRINT RETROSPECTIVE (1 hour):
┌─────────────────────────────────────────────────────────────┐
│ │
│ ATTENDEES: Scrum team only (safe space) │
│ FACILITATOR: Scrum Master │
│ │
│ FORMAT OPTIONS: │
│ │
│ CLASSIC (Start/Stop/Continue): │
│ • What should we START doing? │
│ • What should we STOP doing? │
│ • What should we CONTINUE doing? │
│ │
│ 4L's: │
│ • LIKED: What went well? │
│ • LEARNED: What did we learn? │
│ • LACKED: What was missing? │
│ • LONGED FOR: What do we wish we had? │
│ │
│ PROCESS: │
│ 1. Set the stage (5 min) - Check-in, set tone │
│ 2. Gather data (15 min) - Individual reflection │
│ 3. Generate insights (20 min) - Group discussion │
│ 4. Decide actions (15 min) - Pick 1-3 improvements │
│ 5. Close (5 min) - Summarize, appreciate │
│ │
│ OUTPUT: │
│ • 1-3 specific action items with owners │
│ • Follow up in next retrospective │
└─────────────────────────────────────────────────────────────┘