Scrum

In modern software development, teams need structured yet flexible approaches to deliver quality products efficiently. One of the most widely adopted agile frameworks for managing product development is Scrum, which emphasizes iterative progress, collaboration, and adaptability. Instead of imposing rigid rules, Scrum offers guiding principles and lightweight practices that help organizations adapt quickly to change while keeping customer value at the center.

This glossary page addresses the most common questions about Scrum in a clear, question–answer format.

What is the purpose of Scrum?

The main purpose of Scrum is to maximize product value through incremental delivery. By breaking complex work into manageable pieces, it allows teams to detect problems early, adapt to changes, and continuously improve. The approach also fosters collaboration across business and technical teams.

What are the Scrum Values?

Scrum is guided by five core values that shape how teams collaborate and deliver work:

• Commitment – each member commits to achieving the goals of the Scrum Team.

• Courage – team members have the courage to tackle challenges and do the right thing.

• Focus – the team focuses on the work of the sprint and the goals ahead.

• Openness – stakeholders and team members are open about progress, challenges, and feedback.

• Respect – team members respect each other’s skills, perspectives, and contributions.

These values foster trust and accountability, making Scrum more than just a set of practices.

What is Scrum vs Agile?

Agile is the overarching philosophy or mindset that promotes adaptability, collaboration, and customer focus. Scrum is a specific framework under the agile umbrella, with defined roles, events, and artifacts. In short, agile describes the principles, while Scrum provides a practical way to implement them.

What are the key components of Scrum?

Scrum is made up of several core elements:

• Framework – lightweight and adaptable, offering guidance without rigid rules.

• Sprints – short, fixed cycles (1–4 weeks, often 2) that deliver usable outcomes.

• Agile roots – built on principles of adaptability, feedback, and collaboration.

• Roles – Product Owner (value), Scrum Master (facilitation), Developers (delivery).

• Artifacts – Product Backlog, Sprint Backlog, and Increment for transparency.

• Events – Sprint, Planning, Daily Scrum, Review, Retrospective.

• Values – commitment, courage, focus, openness, respect.

These components ensure Scrum teams stay aligned, adaptable, and value-driven.

What are the three pillars of Scrum?

Scrum is built on three pillars: Transparency, Inspection, and Adaptation. Transparency ensures that all stakeholders share a common understanding of work and progress. Inspection means regularly reviewing deliverables and processes. Adaptation enables teams to make adjustments quickly when issues or opportunities arise.

What are the three roles in Scrum?

The Scrum Team is made up of three key roles, each with unique responsibilities:

• Developers – professionals who build the product increment during each sprint. They handle coding, testing, and all technical tasks needed to deliver value.

• Product Owner – owns the Product Backlog and prioritizes work based on business value. They act as the bridge between stakeholders and the development team.

• Scrum Master – a facilitator and coach who ensures the team follows Scrum principles, removes blockers, and fosters an environment of collaboration and continuous improvement.

These roles collectively ensure accountability for delivery, value maximization, and adherence to Scrum practices.

What are the 5 main events in Scrum?

Scrum has five key events (sometimes called ceremonies) that bring structure and rhythm to the framework:

1. The Sprint – a fixed time-box (1–4 weeks) where a usable product increment is developed.

2. Sprint Planning – the team plans what work will be done in the sprint and how it will be achieved.

3. Daily Scrum – a 15-minute daily meeting for the team to inspect progress and adjust plans.

4. Sprint Review – stakeholders review the increment and provide feedback for future work.

5. Sprint Retrospective – the team reflects on the sprint process and identifies improvements for the next cycle.

Together, these events ensure alignment, transparency, and continuous improvement.

What is a Sprint in Scrum and why is it often 2 weeks?

A sprint is a time-boxed cycle in Scrum, usually lasting between 1 and 4 weeks, where the team delivers a usable product increment. It establishes a steady rhythm that encourages progress, collaboration, and continuous feedback — often described as the “heartbeat” of Scrum.

Why 2 weeks is common:

• Balances adaptability with productivity.

• Short enough for quick feedback and reduced risk.

• Long enough for meaningful work without excess overhead.

• Keeps teams aligned while avoiding wasted effort from overly frequent planning.

Why is Daily Scrum 15 minutes?

The Daily Scrum is designed to be a quick, focused event. Limiting it to 15 minutes encourages concise updates and prevents it from becoming a full problem-solving meeting. This ensures that the team stays aligned without wasting valuable development time.

What are the key Scrum artifacts?

There are three main artifacts: Product Backlog, Sprint Backlog, and Increment. The Product Backlog is an ordered list of all work needed for the product. The Sprint Backlog is a subset of items chosen for a sprint. The Increment is the actual working product delivered at the end of each sprint.

How does Scrum work?

Scrum operates through a cycle of structured events that repeat each sprint:

1. Sprint Planning – the team defines what to deliver and how to approach the work.

2. Execution – developers collaborate to complete backlog items.

3. Daily Scrum – quick daily check-ins to align and adapt.

4. Sprint Review – the increment is demonstrated to stakeholders for feedback.

5. Retrospective – the team reflects and identifies improvements for the next sprint.

This sequence ensures transparency, regular inspection, and continuous adaptation — the core strengths of agile Scrum.

Conclusion

Scrum remains one of the most effective frameworks for software development teams seeking agility, adaptability, and collaboration. By combining structured roles, events, and artifacts with an iterative mindset, Scrum enables continuous value delivery while minimizing risk. For organizations embracing agile scrum, it provides a proven path toward building better products and stronger teams.

Frequently Asked Questions

1. What are the 5 principles of Scrum?

The principles are: Empirical Process Control, Self-organization, Collaboration, Value-based prioritization, and Iterative development. These principles guide how Scrum teams plan, execute, and adapt. They reinforce agility, teamwork, and customer-centric delivery.

2. What is the 3-5-3 rule in Scrum?

The 3-5-3 rule summarizes Scrum: 3 roles, 5 events, and 3 artifacts. This simple formula helps newcomers remember the framework’s structure. It reflects the lightweight nature of Scrum while covering its essentials.

3. What is an example of a Scrum?

An example would be a software team planning a 2-week sprint to build a new login feature. They hold daily Scrums to sync, present the working feature at Sprint Review, and discuss improvements in the Retrospective. This cycle repeats until the product is complete.

4. What are some common Scrum mistakes?

Common mistakes include: turning daily scrums into long status meetings, skipping retrospectives, overloading the sprint backlog, or failing to empower the Product Owner. Teams also err by treating Scrum as rigid rules instead of a flexible framework.

5. Which tool is used for Scrum?

Popular tools include Jira, Trello, Asana, and Azure DevOps. These tools help manage backlogs, track sprint progress, and provide transparency across the team. The choice depends on team size, complexity, and integration needs.