Agile Scrum - 1 - Introduction

Welcome to this introduction to Scrum, the most popular Agile project management methodology. Scrum is a framework designed to solve problems and deliver value. It is also an iterative approach, meaning work happens in short, repeated cycles where you build, learn, and improve continuously. A central concept of Scrum is the sprint, a short time-box (typically 2 weeks) during which the team focuses on delivering a usable increment of the product.

Scrum emphasizes continuous improvement, value-focused delivery, and high adaptability. You don't need the complete solution defined upfront — you start with what you have and iterate. This flexibility is one of its biggest advantages over traditional approaches.

Scrum vs traditional methodology

  • Delivery focus: Scrum emphasizes value; traditional methods emphasize activities and deliverables
  • Feedback loop: Scrum offers continuous feedback and improvement; traditional waits until project end
  • Planning: Scrum plans dynamically and continuously; traditional plans upfront in detail
  • Roles: Scrum defines clear, focused roles (Product Owner, Scrum Master, Dev Team)

An analogy: in traditional methods, building a car means designing the full car upfront. In Agile/Scrum, you might start with a skateboard, then a scooter, a bicycle, a motorbike — and finally a car. At each stage, the user has something usable and gives feedback.

The origin of Scrum traces back to the 1980s when two Japanese researchers used the term — borrowed from rugby (players grouping heads-down on the field) — for software development. It was later formalized by two Americans in the 1990s, and the official Scrum Guide has been refined ever since. Today, Scrum is the dominant Agile methodology worldwide.

Summary

This introductory lesson covers Agile Scrum as a framework for iterative project management, emphasizing continuous improvement and value delivery. Scrum is presented as the most popular Agile methodology, enabling teams to adapt quickly without requiring the complete solution upfront. The lesson contrasts Agile's approach to traditional methods, highlighting key differences in delivery philosophy, planning dynamics, and team roles, while tracing Scrum's origins from rugby terminology to its adoption in software development.

Key points

  • Scrum is an iterative framework that delivers value incrementally through regular cycles, making it highly adaptable to changing requirements
  • The methodology emphasizes continuous improvement and progressive enhancement, allowing teams to start with initial capabilities and refine over time
  • Agile prioritizes value delivery and team flexibility over detailed upfront planning and comprehensive documentation
  • Sprints (typically two-week cycles) structure the work into manageable periods with clear feedback loops
  • Core difference from traditional methods: Agile focuses on delivering working solutions with continuous refinement, whereas Waterfall emphasizes upfront planning and end-stage validation
  • Scrum originated from rugby terminology (scrum formation) in Japanese manufacturing (1980s) and was later formalized by American practitioners, becoming the standard Agile methodology

FAQ

What is Scrum and how does it differ from traditional project management?

Scrum is an iterative Agile framework for managing projects with emphasis on delivering value incrementally through short cycles called Sprints. Unlike traditional methods that plan everything upfront and validate at the end, Scrum enables continuous improvement, faster feedback, and adaptation to changing requirements throughout the project.

What is a Sprint in Scrum?

A Sprint is a fixed time-box (typically two weeks) during which the team works on delivering a portion of the project's value. Sprints allow for iterative development, regular progress assessment, and the ability to adjust approach based on feedback and lessons learned.

Why is Agile/Scrum valuable for teams?

Agile Scrum provides adaptability, speed, and the ability to deliver value without requiring the complete solution at the project's start. Teams can progressively improve their work, remain flexible to changes, and maintain focus on delivering tangible business value rather than just completing planned activities.