Scrum
An Agile framework for managing software development work through fixed-length iterations called sprints, with defined roles, ceremonies, and artifacts.
Detailed Explanation
Scrum is the most widely used Agile framework. It defines three roles: Product Owner (manages backlog), Scrum Master (facilitates process), and Developers (build the product). Work is organized into sprints (1-4 weeks), with ceremonies: Sprint Planning, Daily Standup, Sprint Review, and Sprint Retrospective.
Scrum artifacts include: Product Backlog (prioritized work), Sprint Backlog (work for current sprint), and Increment (working software at end of sprint). The goal is to produce a potentially shippable increment at the end of each sprint, enabling continuous delivery and adaptation.
Why It Matters
Scrum provides structure for Agile development. It is the most common framework in software teams and is widely understood across the industry.
Real-World Example
A development team uses 2-week sprints. On Monday, they plan the sprint (pick 20 story points of work). Each day, they have a 15-minute standup. On Friday, they demo completed work. After two weeks, they retrospective and plan the next sprint.
When to Use
For teams of 3-9 developers working on complex products with evolving requirements. Scrum provides enough structure to be predictable while remaining flexible.
Advantages
- Clear roles and responsibilities
- Regular delivery of working software
- Continuous improvement through retrospectives
- Transparent progress through artifacts
- Adaptable to changing requirements
Disadvantages
- Ceremonies can feel heavy for small teams
- Requires commitment from all team members
- Sprint interruptions can disrupt planning
- Velocity-based planning can be misleading
- Difficult for distributed teams without adaptation
Frequently Asked Questions
What is the difference between Scrum and Kanban?
Scrum uses fixed-length sprints with planning at the start. Kanban is continuous flow with no fixed iterations. Scrum is better for feature development; Kanban is better for operations and support.
What is a story point?
Story points estimate the relative effort of a task (complexity, uncertainty, work). They are not hours—1 point might be 2 hours, 8 points might be 3 days. The team calibrates over time using velocity.
What is a sprint goal?
The sprint goal is a concise statement of what the team plans to achieve in the sprint. It provides focus and alignment. The sprint backlog should support the sprint goal.
Can Scrum work with remote teams?
Yes, with adaptations. Use video for all ceremonies, async communication tools (Slack, Teams), digital boards (Jira, Linear), and overlapping work hours. Many successful Scrum teams are fully remote.
What is velocity in Scrum?
Velocity is the total story points completed in a sprint. It helps with sprint planning (predict how much work fits in a sprint) and release planning. Velocity varies by team and should not be used to compare teams.