A
AiTechWorlds
AiTechWorlds
Scrum roles, ceremonies, sprint structure, story points, Kanban WIP limits, velocity calculation, and Scrum vs Kanban.
Agile is an iterative approach to software development and project management. Instead of planning everything upfront (waterfall), Agile delivers working software in small increments and adapts based on feedback.
Values:
| Feature | Scrum | Kanban | SAFe | XP |
|---|---|---|---|---|
| Focus | Sprints + ceremonies | Flow visualization | Enterprise scale | Engineering practices |
| Iterations | Fixed sprints (1–4 weeks) | Continuous flow | Program Increments | 1–2 week iterations |
| Roles | SM, PO, Dev Team | No specific roles | Many | Coach, Customer |
| Best for | Feature development | Ops, support, maintenance | Large enterprises | Small teams, technical debt |
| Pillar | Meaning |
|---|---|
| Transparency | Everyone can see the work and its status |
| Inspection | Regular checkpoints to inspect progress |
| Adaptation | Adjust process/product when inspection reveals problems |
| Role | Responsibilities |
|---|---|
| Product Owner (PO) | Owns the product backlog, prioritizes features, represents stakeholders |
| Scrum Master (SM) | Facilitates ceremonies, removes blockers, coaches team on Scrum |
| Development Team | Cross-functional, self-organizing, delivers the product increment |
| Artifact | Description |
|---|---|
| Product Backlog | Prioritized list of all work (user stories, features, bugs) |
| Sprint Backlog | Items selected for the current sprint + sprint plan |
| Increment | Working, potentially shippable product at sprint end |
| Definition of Done (DoD) | Criteria all items must meet to be "done" |
As a [user type],
I want to [action]
so that [benefit/outcome].
Acceptance Criteria:
- Given [context], when [action], then [expected result]
- Given [context], when [action], then [expected result]
Story Points: 3
Priority: High| Points | Complexity / Effort |
|---|---|
| 1 | Trivial — a few minutes |
| 2 | Simple — clear scope |
| 3 | Small — some complexity |
| 5 | Medium — some unknowns |
| 8 | Large — significant complexity |
| 13 | Very large — consider splitting |
| 21+ | Too large — must split |
1. Visualize the workflow — every step of work made visible
2. Limit Work in Progress (WIP) — cap items per column to prevent overload
3. Manage flow — optimize for smooth progression, not individual busyness
4. Make policies explicit — clear rules for how work moves between stages
5. Improve collaboratively — use data to drive improvements
| Metric | Description | Why It Matters |
|---|---|---|
| Lead time | Request to delivery | Customer experience |
| Cycle time | Start of work to delivery | Team efficiency |
| Throughput | Items completed per week | Capacity |
| WIP | Items in progress at once | Flow efficiency |
| Flow efficiency | Active time / Lead time × 100 | Waste identification |
| Aspect | Scrum | Kanban |
|---|---|---|
| Iteration | Fixed sprints | Continuous flow |
| Change during work | No (sprint is locked) | Yes (anytime) |
| WIP limits | Per sprint | Per column |
| Roles | PO, SM, Team | None required |
| Metrics | Velocity, burndown | Lead time, cycle time |
| Best for | Feature development | Ongoing support, ops |
| Ceremonies | Required | Optional |
Team members simultaneously reveal cards (Fibonacci). Discuss outliers, re-estimate.
XS, S, M, L, XL for quick relative sizing before breaking into stories.
Estimate = (Optimistic + 4×Most Likely + Pessimistic) / 6Velocity = Story points completed per sprint (average over last 3–5 sprints)
Sprint capacity = Velocity × (available hours / typical hours)
Example:
Team velocity = 40 points/sprint
One member on vacation = 80% availability
Sprint capacity = 40 × 0.8 = 32 pointsDownload Agile, Scrum & Kanban: Complete Guide
Get this note + 100s more free on Telegram
Join AiTechWorlds on Telegram and get daily AI tips, prompt engineering templates, coding resources, and exclusive content — 100% free!
No spam. Leave anytime.