Elixion

Sprints Overview

Understanding agile sprint management in Elixion

Sprints Overview

Sprints are time-boxed iterations that help teams deliver work incrementally. Elixion provides comprehensive sprint management tools for agile teams.

What is a Sprint?

A sprint is a fixed time period (typically 1-4 weeks) during which a team commits to completing a set of work. At the end of each sprint, the team delivers potentially shippable work.

Sprint Lifecycle

Planning → Active → Review → Retrospective → Complete
    ↑                                            │
    └────────── Next Sprint ←────────────────────┘

Phases

1. Planning

  • Review and refine backlog
  • Estimate stories
  • Commit to sprint scope
  • Define sprint goal

2. Active

  • Daily standups
  • Work on committed items
  • Track progress
  • Address blockers

3. Review

  • Demo completed work
  • Gather feedback
  • Accept/reject items

4. Retrospective

  • Discuss what went well
  • Identify improvements
  • Create action items

5. Complete

  • Close sprint
  • Move incomplete items
  • Calculate velocity

Sprint Structure

Sprint: Sprint 15 (Jan 8-19)
├── Goal: Complete user authentication
├── Status: Active
├── Duration: 2 weeks
├── Capacity: 40 points
└── Issues:
    ├── Story: AUTH-100 (5 pts) - Done
    ├── Story: AUTH-101 (8 pts) - In Progress
    ├── Story: AUTH-102 (5 pts) - In Progress
    ├── Task: AUTH-103 (3 pts) - To Do
    └── Bug: AUTH-104 (2 pts) - To Do

Key Concepts

Sprint Goal

A single objective that describes the sprint's purpose:

Good goals:

  • "Complete core authentication flow"
  • "Launch MVP to beta users"
  • "Resolve all critical bugs"

Avoid:

  • "Complete all stories" (not specific)
  • Too many objectives
  • Vague outcomes

Sprint Capacity

Total effort the team can commit to:

Team Capacity Calculation:

Team Members: 5
Sprint Length: 2 weeks (10 days)
Hours per day: 6 (accounting for meetings, etc.)

Base Capacity: 5 × 10 × 6 = 300 hours

Adjustments:
- Alice: Vacation 2 days (-12 hours)
- Bob: Training 1 day (-6 hours)

Final Capacity: 282 hours

Velocity

Average story points completed per sprint:

Last 5 Sprints:
Sprint 10: 32 points
Sprint 11: 28 points
Sprint 12: 35 points
Sprint 13: 30 points
Sprint 14: 32 points

Average Velocity: 31.4 points

Sprint Backlog

Issues committed to the current sprint:

| Item | Points | Assignee | Status | |------|--------|----------|--------| | AUTH-100 | 5 | Alice | Done | | AUTH-101 | 8 | Bob | In Progress | | AUTH-102 | 5 | Carol | To Do |

Sprint Views

Sprint Board

Visual kanban board for the sprint:

┌─────────────┬─────────────┬─────────────┬─────────────┐
│   To Do     │ In Progress │  In Review  │    Done     │
├─────────────┼─────────────┼─────────────┼─────────────┤
│ AUTH-103    │ AUTH-101    │             │ AUTH-100    │
│ AUTH-104    │ AUTH-102    │             │             │
└─────────────┴─────────────┴─────────────┴─────────────┘

Burndown Chart

Track progress over time:

Points
  40 ┤
  30 ┤  ●─●
  20 ┤      ╲─●─●
  10 ┤            ╲─●─●
   0 ┼────────────────────●
     Day 1  3   5   7   9  10

Sprint Calendar

Timeline view of sprint activities:

Week 1: Jan 8-12
├── Mon: Sprint Planning
├── Tue-Thu: Development
└── Fri: Mid-sprint review

Week 2: Jan 15-19
├── Mon-Wed: Development
├── Thu: Sprint Review
└── Fri: Retrospective

Sprint Ceremonies

Sprint Planning

Duration: 1-2 hours per week of sprint

Agenda:

  1. Review sprint goal
  2. Discuss capacity
  3. Select backlog items
  4. Break down stories
  5. Commit to sprint

Daily Standup

Duration: 15 minutes

Questions:

  1. What did I complete?
  2. What will I work on?
  3. Any blockers?

Sprint Review

Duration: 1 hour per week of sprint

Agenda:

  1. Demo completed work
  2. Gather stakeholder feedback
  3. Discuss incomplete items
  4. Update product backlog

Sprint Retrospective

Duration: 1-1.5 hours

Format:

  1. What went well?
  2. What could improve?
  3. Action items

Sprint Metrics

Key Metrics

| Metric | Description | Target | |--------|-------------|--------| | Velocity | Points completed | Consistent | | Commitment Rate | Committed vs. completed | > 85% | | Burndown | Progress trend | On track | | Scope Change | Items added/removed | < 10% |

Health Indicators

Healthy Sprint:

  • ✅ Burndown tracking to goal
  • ✅ No blocking issues
  • ✅ Team engaged
  • ✅ Daily progress

Warning Signs:

  • ⚠️ Flat burndown
  • ⚠️ Many blocked items
  • ⚠️ Scope creep
  • ⚠️ Team stress

Best Practices

Planning

  • Don't over-commit
  • Leave buffer (10-20%)
  • Include bugs and tech debt
  • Get team buy-in

Execution

  • Focus on sprint goal
  • Limit work in progress
  • Address blockers quickly
  • Communicate daily

Completion

  • Don't extend sprints
  • Move incomplete items
  • Celebrate successes
  • Learn from misses

Continuous Improvement

  • Track velocity trends
  • Review commitment accuracy
  • Implement retro actions
  • Experiment with process

Next: Sprint Planning - Deep dive into planning sprints