# Agile Scrum Framework & Sprint Playbook

> **Category**: Iterative & Incremental | **Badge**: Agile Core

## Overview
The Agile Scrum framework splits complex roadmaps into bite-sized, 1 to 4 week Sprints. This playbook details ceremony rituals, sprint velocity tracking, and Definition of Done (DoD) benchmarks.

### Best Suited For
E-commerce, SaaS products, mobile apps, and rapidly evolving market requirements with cross-functional teams.

### Not Recommended For
Hard-contract projects with zero change allowance or strict physical hardware deadlines.

## Key Roles & Responsibilities
- **Product Owner (PO)**: Defines the vision, manages and prioritizes the Product Backlog, accepts user stories.
- **Scrum Master (SM)**: Removes blockers, facilitates sprint ceremonies, shields team from external friction.
- **Developers & QA**: Cross-functional engineering team delivering shippable increments each sprint.

## Core Ceremonies & Rhythms
### Sprint Planning (2 Hours (for 2-wk sprint))
Select backlog items, agree on sprint goal, decompose stories into tasks.

### Daily Standup (15 Minutes)
Yesterday's wins, today's commitment, active blockers.

### Sprint Review / Demo (1 Hour)
Live demonstration of working software to stakeholders and client team.

### Sprint Retrospective (45 Minutes)
Inspect & Adapt: What went well? What slowed us down? Action items for next sprint.

## Phases & Execution Stepper
1. **Backlog Refinement** (01): Regularly estimate story points (Fibonacci sequence: 1, 2, 3, 5, 8) and refine acceptance criteria.
1. **Sprint Commitment** (02): Lock in scope based on historical team velocity. No mid-sprint scope creep allowed.
1. **Iterative Execution** (03): Move cards on ThinkNCollab Kanban board from In Progress to Code Review and QA Verification.
1. **Increment Release** (04): Deploy audited code to staging/production and update sprint burn-down telemetry.

## Default Board Workflow Blueprint
Columns: Sprint Backlog ➔ In Progress ➔ Code Review ➔ QA & Acceptance ➔ Done (Deployed)