Master iterative development, sprint ceremonies, team roles, and the frameworks that let modern teams ship value continuously.
Written in 2001 by 17 software practitioners, the Agile Manifesto defines 4 core values and 12 principles that changed how software is built. 84% of organizations now use Agile in some form.
over processes and tools
A great team with poor tools outperforms a poor team with great tools. Conway's Law: your system architecture mirrors your team structure. Build cross-functional, empowered teams first.
over comprehensive documentation
Ship something real every sprint. A demo is worth a thousand meetings. The measure of progress is working software — not burndown charts or velocity metrics.
over contract negotiation
Involve stakeholders weekly, not just at the start and end. Amazon's "working backwards" model writes the press release before writing a line of code — aligning with the customer from day one.
over following a plan
Markets change, users give feedback, requirements evolve. Teams that can pivot quickly win. Spotify rebuilt their entire backend architecture mid-growth. Flexibility > rigidity.
Scrum is the most popular Agile framework, used by 66% of Agile teams. It organizes work into fixed-length sprints (1–4 weeks) with clear roles, ceremonies, and artifacts.
Each ceremony has a specific purpose and time-box. Running them well is the difference between a high-performing Agile team and one that just goes through the motions.
Answer two questions: (1) What can we deliver this sprint? (2) How will we do it? The team pulls stories from the top of the Product Backlog, breaks them into tasks, and commits to a Sprint Goal.
# Sprint Planning Template Sprint Goal: Enable users to add and categorize expenses Stories Committed: ✓ [5 pts] Add expense form with amount + category ✓ [3 pts] Edit/delete existing expenses ✓ [2 pts] Category filter on expense list ✗ [8 pts] AI category suggestion (moved to next sprint) Team Capacity: 4 devs × 8 days × 6 hrs = 192 hrs Committed: ~40 story points (team velocity avg: 42)
Not a status report to the Scrum Master — it's a synchronization meeting for the team. Three questions only:
# Each team member answers: 1. Yesterday: "Finished the expense form UI, all tests passing" 2. Today: "Starting the category filter — pair with Ali" 3. Blockers: "Need design sign-off on the modal layout" # Anti-patterns to avoid: ✗ Detailed technical discussions (take offline) ✗ Problem-solving during standup ✗ Reporting to SM instead of team ✗ Longer than 15 minutes
The team demos working software to stakeholders and gets feedback. Only completed (done-done) stories are demoed. This is where the Product Owner formally accepts or rejects stories.
# Start/Stop/Continue format (most common) Start: "Writing tests before code (TDD)" "Using feature flags for risky changes" Stop: "Merging PRs without 2 reviews" "Picking up new tasks mid-sprint" Continue: "Daily pair programming sessions" "Documenting decisions in ADRs" # Action items: specific, assigned, and time-boxed Action: Set up branch protection rules by next Wednesday — assigned: Leyla
Both are Agile frameworks, but they solve different problems. Scrum is prescriptive and sprint-based; Kanban is flow-based and continuous.
| Aspect | Scrum | Kanban |
|---|---|---|
| Cadence | Fixed sprints (1–4 weeks) | Continuous flow |
| Roles | PO, SM, Dev Team required | No prescribed roles |
| WIP Limits | Sprint backlog limits work | Explicit WIP limits per column |
| Change mid-cycle | ❌ Sprint scope is locked | ✅ Add/remove anytime |
| Planning meetings | Sprint planning every sprint | Just-in-time planning |
| Best for | Product development, new features | Ops, support, maintenance |
| Metrics | Velocity, burndown chart | Cycle time, throughput |
| Real-world use | Spotify feature teams, most startups | GitHub ops, Trello support teams |
Real-time agile estimation tool. Create a room, invite your team, and estimate story points together — instantly see consensus and disagreements.
Launch Planning Poker →