What is Scrum?
Answer
Overview
Scrum is an agile framework for managing and completing complex work. It organizes teams around short, fixed-length development cycles called Sprints (usually 1–4 weeks), with regular planning, review, and retrospective meetings.
Scrum Roles
| Role | Responsibilities |
|---|---|
| Product Owner | Prioritizes the backlog, defines what to build, represents business |
| Scrum Master | Facilitates the process, removes blockers, coaches the team |
| Development Team | Self-organizing team that does the actual work (design, code, test) |
Scrum Artifacts
| Artifact | Description |
|---|---|
| Product Backlog | Ordered list of all features/requirements for the product |
| Sprint Backlog | Items selected for the current Sprint from the product backlog |
| Increment | The working, shippable product at end of each Sprint |
Scrum Events (Ceremonies)
| Event | Duration | Purpose |
|---|---|---|
| Sprint | 1–4 weeks | The development cycle |
| Sprint Planning | 2–4 hours | Plan what to build this sprint |
| Daily Standup | 15 min | What did I do? What will I do? Blockers? |
| Sprint Review | 1–2 hours | Demo completed work to stakeholders |
| Sprint Retrospective | 1 hour | What went well? What to improve? |
Daily Standup (3 Questions)
text1. What did I work on yesterday? 2. What will I work on today? 3. Are there any blockers/impediments?
Scrum in a Flutter Team
textSprint 1 (2 weeks) ├── Sprint Planning: │ ├── Select user stories from backlog │ └── Break into tasks: "Build login screen", "Integrate auth API", "Write tests" ├── Daily Standup (every morning, 15 min) ├── Development (Flutter coding, PR reviews) ├── Sprint Review: │ └── Demo: "Login, registration, and profile screens completed" └── Retrospective: ├── Went well: "Great collaboration on UI" └── Improve: "Need better API mocking for offline testing" Sprint 2 → Next set of features...
Story Points & Velocity
- Story Points — relative measure of effort for a task (1, 2, 3, 5, 8, 13...)
- Velocity — total story points completed per sprint (used for forecasting)
- Burndown Chart — tracks remaining work in a sprint over time
Scrum vs Kanban
| Feature | Scrum | Kanban |
|---|---|---|
| Structure | Fixed sprints (timeboxed) | Continuous flow |
| Roles | Defined (PO, SM, Dev) | No formal roles |
| Best for | Product teams with planned releases | Support/maintenance teams |
Real-world Note: Most Flutter teams use a hybrid — Scrum ceremonies with a Kanban board (Jira, Trello, Linear). Sprints are 1–2 weeks with daily standups.