Agile / Scrum
Also known as: Scrum Framework, Agile Methodology, Iterative Development
An iterative project management framework that delivers work in short cycles (sprints) with continuous feedback, enabling teams to adapt quickly to changing requirements and deliver value incrementally.
Quick Reference
Memory Aid
Plan → Sprint (2-4 weeks) → Demo → Retro → Repeat. Deliver working product every sprint.
TL;DR
Break work into 2-4 week sprints. The Product Owner prioritizes, the team delivers, and stakeholders review. Retrospect after each sprint to continuously improve. Embrace change through short feedback cycles.
What Is Agile / Scrum?
Instead of planning everything upfront and delivering at the end (waterfall), Scrum breaks work into 2-4 week sprints. Each sprint delivers a working increment. After each sprint, the team reviews what was built, gets feedback, and adapts the plan.
Individuals and interactions over processes and tools. Working software over comprehensive documentation. Customer collaboration over contract negotiation. Responding to change over following a plan.
— Agile Manifesto
Scrum defines three roles (Product Owner, Scrum Master, Development Team), five events (Sprint, Sprint Planning, Daily Standup, Sprint Review, Sprint Retrospective), and three artifacts (Product Backlog, Sprint Backlog, Increment). The Product Owner prioritizes work by value, the team self-organizes to deliver, and the Scrum Master removes impediments. The framework embraces change — requirements evolve through collaboration between cross-functional teams and stakeholders.
The Scrum Sprint Cycle
Work flows in iterative sprint cycles: plan, build, review, and adapt — then repeat.
Sprint Planning
Select & plan work
Sprint (2-4 wks)
Build the increment
Daily Standup
Coordinate daily
Sprint Review
Demo to stakeholders
Retrospective
Improve the process
Origin & Context
Scrum was formalized in 1995, building on ideas from the Agile Manifesto (2001) and earlier iterative approaches. The name comes from rugby — a scrum is where the whole team works together to move the ball forward.
Core Components
Sprint
A time-boxed iteration (2-4 weeks) that produces a potentially shippable increment.
Example
A two-week sprint where the team delivers three user stories: user login, password reset, and profile editing.
Product Backlog
A prioritized list of everything that might be needed in the product, managed by the Product Owner.
Example
A ranked list of 50 user stories, with the top 10 refined and ready for the next sprint.
Sprint Review
A meeting at sprint end where the team demonstrates what was built and stakeholders provide feedback.
Example
The team demos the login flow to stakeholders, who request adding social login — this goes into the backlog for prioritization.
Retrospective
A meeting where the team reflects on how they worked and identifies improvements.
Example
The team decides to start pair programming on complex features after two bugs slipped through in the sprint.
Did You Know?
The term 'Scrum' was borrowed from a 1986 Harvard Business Review article by Hirotaka Takeuchi and Ikujiro Nonaka titled 'The New New Product Development Game,' which compared high-performing cross-functional teams to the rugby formation where the whole team moves together.
When to Use Agile / Scrum
Software product development
Problem it solves: Enables teams to deliver working software frequently while adapting to changing requirements.
Real-World Application
Spotify scaled Scrum to 30+ teams using the Squad/Tribe model, maintaining agility while coordinating across hundreds of developers.
Complex projects with evolving requirements
Problem it solves: When requirements can't be fully defined upfront, Scrum allows learning and adapting.
Real-World Application
A healthcare startup used Scrum to develop an MVP in 8 sprints, pivoting the product direction twice based on user feedback gathered during Sprint Reviews.
Scrum is often adopted superficially — doing standups and sprints without embracing the underlying principles of transparency, inspection, and adaptation. This 'cargo cult Scrum' delivers the ceremonies without the benefits.
How to Apply Agile / Scrum: Step by Step
Before You Start
- →A cross-functional team of 5-9 people
- →A Product Owner with authority to prioritize
- →Organizational willingness to embrace iterative delivery
Create the Product Backlog
The Product Owner creates and prioritizes a list of features, enhancements, and fixes.
Tips
- ✓Write backlog items as user stories: 'As a [user], I want [feature] so that [benefit]'
Common Mistakes
- ✗Creating too detailed specifications upfront — keep items at the right level of detail
Sprint Planning
The team selects items from the backlog for the upcoming sprint and plans how to deliver them.
Tips
- ✓Don't overcommit — use velocity from previous sprints to guide capacity
Common Mistakes
- ✗Letting the Product Owner or management dictate sprint scope instead of the team
Execute the Sprint
The team works on the sprint backlog, holding daily standups to coordinate.
Tips
- ✓Standups should be 15 minutes max: What did I do? What will I do? What's blocking me?
Common Mistakes
- ✗Turning standups into status reports to management
Review and Retrospect
Demo the increment to stakeholders (Review) and reflect on team process (Retrospective).
Tips
- ✓Always implement at least one improvement from the Retrospective
Common Mistakes
- ✗Skipping the Retrospective — this is where the team continuously improves
Value & Outcomes
Primary Benefit
Delivers working product incrementally with continuous feedback and adaptation.
Additional Benefits
- ✓Reduces risk through short feedback cycles
- ✓Increases team ownership and morale
- ✓Makes progress visible and transparent
What You'll Learn
- →How to manage work in iterative sprints
- →How to prioritize by value and adapt to change
Typical Outcomes
Best Practices
📋 Preparation
- •Train the whole team on Scrum principles
- •Ensure the Product Owner has authority and availability
🚀 Execution
- •Protect the sprint — don't add work mid-sprint unless critical
- •Keep sprints short (2 weeks is most common)
🔄 Follow-Up
- •Act on Retrospective improvements every sprint
- •Track velocity to improve planning accuracy
💎 Pro Tips
- •The Retrospective is the most important ceremony — it's how the team continuously improves
Spotify's Squad Model
Spotify famously adapted Scrum into its own 'Squad' model, where autonomous squads of 6-12 people own specific product features end-to-end. Multiple squads form 'Tribes' around business areas, enabling coordination without sacrificing team autonomy. This approach allowed Spotify to scale from 30 to 3,000+ engineers while maintaining agile practices.
Limitations & Pitfalls
Difficult to scale beyond a single team without additional frameworks
Mitigation: Use SAFe, LeSS, or Spotify model for multi-team coordination
Requires disciplined time-boxing and commitment that some organizations resist
Mitigation: Start with one team, demonstrate success, then expand
Apply Agile / Scrum with Stratrix
Turn this framework into a professional strategy deck in under a minute. Stratrix applies Agile / Scrum automatically to your business context.
Try Stratrix Free