Overview of Agile Frameworks

Overview

• What you’ll learn: The major Agile frameworks — Scrum, Kanban, XP, and SAFe — their core ideas, differences, and when to use each.
• Prerequisites: Lesson 2 — Waterfall vs Agile
• Estimated reading time: 14 minutes

Introduction

Agile is a mindset. Frameworks are how you put that mindset into practice. Think of Agile as the philosophy of martial arts; the frameworks are the individual schools — each with its own style, techniques, and strengths. No single framework is “the best.” The best one is the one that fits your team, your product, and your organizational context.

Scrum

Scrum is the most widely adopted Agile framework. It is lightweight, simple to understand, but difficult to master.

• Core idea: Work in fixed-length iterations called Sprints (1-4 weeks). Each Sprint produces a potentially releasable Increment.
• Three roles: Product Owner, Scrum Master, Developers.
• Five events: Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective.
• Three artifacts: Product Backlog, Sprint Backlog, Increment — each with a commitment (Product Goal, Sprint Goal, Definition of Done).
• Best for: Teams building complex products where requirements evolve and regular feedback is essential.

Kanban

Kanban focuses on visualizing workflow, limiting work in progress (WIP), and optimizing the flow of work through the system.

• Core idea: Make work visible on a board. Limit how much work is active at any time. Measure and improve flow.
• No prescribed roles or iterations. Work flows continuously.
• Key metrics: WIP, Cycle Time, Throughput, Work Item Age.
• Best for: Support teams, operations, and any context where work arrives unpredictably and needs to flow continuously.

Extreme Programming (XP)

XP emphasizes technical practices that enable Agile development — it focuses on engineering excellence.

• Core practices: Test-Driven Development (TDD), Pair Programming, Continuous Integration, Refactoring, Simple Design.
• Short iterations: Typically 1-2 week cycles.
• Best for: Teams that want rigorous engineering discipline alongside Agile values. Often combined with Scrum.

SAFe (Scaled Agile Framework)

SAFe is a framework for applying Agile at scale — across multiple teams and the entire enterprise.

• Core idea: Coordinate multiple Agile teams around a shared mission using Agile Release Trains (ARTs).
• Program Increment (PI) Planning: Large-scale planning events that align teams every 8-12 weeks.
• Best for: Large organizations (50+ developers) that need coordination across many teams.
• Criticism: Often considered too bureaucratic, earning it the nickname “Shiny Agile For Enterprises” among critics.

Comparison

Key Takeaways

• Agile frameworks are tools, not religions. Choose based on context, not popularity.
• Scrum is the most popular starting point — structured enough to guide teams, light enough to adapt.
• Kanban complements Scrum well (they can be combined — “Scrumban”).
• XP’s technical practices benefit any team regardless of the framework used.
• SAFe addresses scaling but adds complexity — use only when you genuinely have a scaling problem.

What’s Next

In Lesson 4, you will learn about empiricism — the philosophical foundation of Scrum — and its three pillars: Transparency, Inspection, and Adaptation.