Table of Contents
01. What is Scrum?
Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems.
Created by Ken Schwaber and Jeff Sutherland in the early 1990s, Scrum has become the most widely used Agile framework worldwide. At its core, Scrum is simple: it's a framework for getting work done. But don't let that simplicity fool you. Scrum provides structure, discipline, and a clear path to continuous adaptation. It's not a methodology with rigid rules. It's a framework that guides teams toward better ways of working.
Key Takeaway
Scrum is a framework, not a methodology. As a framework, it is intentionally incomplete. It provides structure and guidance but allows teams to adapt it to their specific context and needs. This flexibility is one of Scrum's greatest strengths, but also its greatest weakness if implemented incorrectly.
Research shows that 47% of Agile transformations fail (Scrum Inc., 2024), with common causes including leadership disconnect, lack of product vision, and cultural resistance. Additionally, 44% of teams struggle to transition from traditional methods to Scrum (Go Beyond, 2024), often because they don't fully understand or follow Scrum's core principles. Proper training and commitment to Scrum's values are essential for success.
Stats in Singapore
In Singapore, where businesses face rapid change, global competition, and the need for innovation, Scrum has become increasingly popular. According to recent data, 81% of businesses in Singapore have implemented Agile frameworks and methodologies at scale, with Scrum being the most common framework used.
02. Scrum vs Agile: Understanding the Difference
Many people confuse Scrum and Agile, but they're not the same thing. Understanding the difference is crucial for anyone looking to implement these practices.
What is Agile?
Agile is a mindset and set of values and principles outlined in the Agile Manifesto. It's a philosophy that emphasizes:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
What is Scrum?
Scrum is a specific framework that implements Agile principles. Think of Agile as the philosophy and Scrum as one way to practice that philosophy. Other Agile frameworks include Kanban, Extreme Programming (XP), and Lean.
Agile vs Scrum: Quick Comparison
| Aspect | Agile | Scrum |
|---|---|---|
| Nature | Mindset, philosophy, set of principles | Specific framework with defined accountabilities, events, and artifacts |
| Flexibility | Very flexible, adaptable to any context | Structured but adaptable within its framework |
| Roles | No specific roles defined | Three defined accountabilities: Product Owner, Scrum Master, Developers |
| Events | No specific events required | Five defined events: Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective |
| Best For | Any team or organization seeking agility | Teams working on complex products, especially software development but Scrum has been successfully used in marketing, HR, education, and many other fields |
Key Takeaway
Agile is the "what" (the philosophy), Scrum is the "how" (the framework). You can be Agile without Scrum, but you can't do Scrum without being Agile. If so, then you are not doing Scrum properly.
03. The Scrum Framework: An Overview
The Scrum framework consists of three essential components:
Accountabilities
Three accountabilities define who does what in Scrum: the Product Owner, the Scrum Master, and the Developers.
Scrum Events
Five events create regularity and minimize the need for meetings not defined in Scrum: Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
Scrum Artifacts
Three artifacts represent work or value: the Product Backlog, the Sprint Backlog, and the Increment.
These components work together to create a framework for delivering value incrementally and iteratively. Let's explore each component in detail.
Key Takeaway
The Scrum framework is built on three elements: Accountabilities (who), Events (when), and Artifacts (what). These three components are interdependent and must work together. You cannot have effective Scrum by implementing only one or two of these components. All three are essential for the framework to function properly.
04. The Three Accountabilities in Scrum
Scrum defines three specific accountabilities (previously called "roles") that are essential for a Scrum Team to function effectively. Each accountability has distinct responsibilities and focuses on different aspects of product development.
1. Product Owner
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are the single person responsible for managing the Product Backlog.
Key Responsibilities:
- Developing and explicitly communicating the Product Goal
- Creating and clearly communicating Product Backlog items
- Ordering Product Backlog items to best achieve goals and missions
- Ensuring the Product Backlog is transparent, visible, and understood
2. Scrum Master
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.
Key Responsibilities:
- Coaching the team members in self management and cross functionality
- Helping the Scrum Team focus on creating high value Increments
- Causing the removal of impediments to the Scrum Team's progress
- Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox
3. Developers
Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint. The term "Developers" in Scrum is not limited to software developers. It includes anyone who contributes to creating the product.
Key Responsibilities:
- Creating a plan for the Sprint (Sprint Backlog)
- Instilling quality by adhering to a Definition of Done
- Adapting their plan each day toward the Sprint Goal
- Holding each other accountable as professionals
05. Scrum Events: The Five Events
Scrum uses a set of time boxed events to create regularity and minimize the need for meetings not defined in Scrum. All events are time boxed, meaning they have a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened.
1. The Sprint
The Sprint is a container for all other events. It's a fixed length event of one month or less, during which a "Done," useable, and potentially releasable product Increment is created. Sprints have consistent durations throughout a development effort.
Sprint Characteristics:
- Duration: Typically 1 to 4 weeks (most commonly 2 weeks)
- No changes are made that would endanger the Sprint Goal
- Quality does not decrease
- The Product Backlog is refined as needed
- The scope may be clarified and renegotiated with the Product Owner as more is learned
2. Sprint Planning
Sprint Planning initiates the Sprint by laying out the work to be performed. The entire Scrum Team collaborates on understanding the work of the Sprint.
Sprint Planning Addresses Three Topics:
- Why is this Sprint valuable? The Product Owner proposes how the product could increase its value and utility in the current Sprint.
- What can be Done this Sprint? The Developers select items from the Product Backlog to include in the current Sprint.
- How will the chosen work get done? The Developers plan the work necessary to create an Increment that meets the Definition of Done.
The Sprint Goal: The North Star of the Sprint
During Sprint Planning, the Scrum Team creates the Sprint Goal, a single, cohesive objective that answers "Why is this Sprint valuable?" The Sprint Goal is the single most important outcome of Sprint Planning because it:
- Provides focus and coherence It unifies the team around a shared purpose, ensuring all work selected for the Sprint contributes to a common objective
- Guides decision making Throughout the Sprint, the team uses the Sprint Goal to make trade off decisions and prioritize work
- Enables flexibility While the Sprint Goal is fixed, the scope can be clarified and renegotiated as long as it doesn't endanger the Sprint Goal
- Measures success The Sprint Review evaluates whether the Sprint Goal was achieved, not just whether individual tasks were completed
- Drives Daily Scrum Each Daily Scrum focuses on progress toward the Sprint Goal, keeping the team aligned and coordinated
The Sprint Goal is so critical that it's protected during the Sprint, no changes should be made that would endanger it. This commitment ensures the team maintains focus and delivers meaningful value, rather than just completing a list of unrelated tasks.
3. Daily Scrum
The Daily Scrum is a 15 minute event for the Developers to synchronize activities and create a plan for the next 24 hours. It's not a status meeting, it's a planning event.
Daily Scrum Structure:
Developers can structure the Daily Scrum however they want, as long as it focuses on progress toward the Sprint Goal and produces an actionable plan for the next day. Common formats include:
- What did I do yesterday that helped the team meet the Sprint Goal?
- What will I do today to help the team meet the Sprint Goal?
- Do I see any impediment that prevents me or the team from meeting the Sprint Goal?
4. Sprint Review
The Sprint Review is the second to last event of the Sprint. Its purpose is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders, and progress toward the Product Goal is discussed.
5. Sprint Retrospective
The Sprint Retrospective concludes the Sprint. Its purpose is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done.
The Retrospective is crucial for continuous adaptation, one of Scrum's core principles. Teams identify what went well, what could be improved, and create action items for the next Sprint.
Key Takeaway
All Scrum events are time-boxed to create regularity and focus. The Sprint Goal is the most important outcome of Sprint Planning and serves as the team's North Star throughout the Sprint. Every event, from Daily Scrum to Sprint Retrospective, should connect back to achieving the Sprint Goal and ultimately the Product Goal.
06. Scrum Artifacts: Commitment and Transparency
Scrum's artifacts represent work or value. They are designed to maximize transparency of key information. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured.
1. Product Backlog
The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.
Product Backlog Characteristics:
- Never complete, it evolves as the product and environment evolve
- Ordered by the Product Owner based on value, risk, dependencies, and necessity
- Contains Product Backlog Items (PBIs) that can be user stories, features, bugs, or technical work
- Refined continuously to ensure items are ready for selection in Sprint Planning
Commitment: Product Goal. The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.
2. Sprint Backlog
The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
The Sprint Backlog is a plan by and for the Developers. It's a real time picture of the work the Developers plan to accomplish during the Sprint to achieve the Sprint Goal.
Commitment: Sprint Goal. The Sprint Goal is the single objective for the Sprint. It provides coherence and focus, encouraging the Scrum Team to work together rather than on separate initiatives.
3. Increment
An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together.
In order to provide value, the Increment must be usable. It must meet the Definition of Done, a formal description of the state of the Increment when it meets the quality measures required for the product.
Commitment: Definition of Done. The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.
Key Takeaway
Scrum artifacts are designed to maximize transparency, and each artifact has a commitment that ensures it provides focus and clarity. The Product Backlog commits to the Product Goal, the Sprint Backlog commits to the Sprint Goal, and the Increment commits to the Definition of Done. These commitments ensure that artifacts are not just lists, but meaningful guides for the team's work.
07. How Does Scrum Work? The Scrum Process
Understanding how Scrum works in practice helps teams implement it effectively. Here's a step-by-step overview of the Scrum process:
Product Backlog Creation
The Product Owner creates and maintains the Product Backlog, ordering items based on value, risk, and dependencies.
Sprint Planning
The Scrum Team meets to plan the Sprint. They select items from the Product Backlog and create a plan to deliver a potentially releasable Increment.
Daily Scrum
Every day, the Developers meet for 15 minutes to synchronize and plan the next 24 hours of work.
Development Work
The Developers work on the Sprint Backlog items, creating a "Done" Increment that meets the Definition of Done.
Sprint Review
At the end of the Sprint, the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog as needed.
Sprint Retrospective
The Scrum Team reflects on their process and identifies improvements for the next Sprint.
Repeat
The cycle repeats with the next Sprint, continuously delivering value and improving.
Continuous Adaptation
Scrum is built on the principle of continuous adaptation. Each Sprint provides an opportunity to inspect and adapt, making the team more effective over time. This iterative approach is particularly valuable in Singapore's dynamic business environment, where market conditions and customer needs change rapidly.
08. Benefits of Using Scrum
Organizations worldwide have adopted Scrum because of its proven benefits. Here are the key advantages:
Faster Time to Market
By delivering working increments every Sprint, teams can get products to market faster and start receiving feedback sooner.
Better Team Collaboration
Scrum's emphasis on cross functional teams and daily communication improves collaboration and reduces silos.
Increased Productivity
Teams using Scrum often report 30 to 40% increases in productivity due to better focus, reduced waste, and clearer priorities.
Higher Quality
The Definition of Done and regular inspection ensure that quality is built into the process, not added at the end.
Adaptability
Scrum's iterative approach allows teams to adapt quickly to changing requirements and market conditions.
Transparency
Scrum artifacts and events provide visibility into progress, challenges, and opportunities for all stakeholders.
Customer Satisfaction
Regular delivery of value and frequent stakeholder feedback lead to products that better meet customer needs.
Team Morale
Self organizing teams with clear goals and regular recognition of achievements report higher job satisfaction.
In Singapore, where 81% of businesses have implemented Agile methodologies, these benefits are driving real business results. Companies report improved project success rates, better alignment with business goals, and increased employee engagement.
09. Scrum in Singapore: Why It Matters
Singapore's unique business environment makes Scrum particularly valuable. As a global financial hub, tech innovation center, and gateway to Southeast Asia, Singapore businesses face unique challenges that Scrum helps address.
Why Scrum Works in Singapore
1. Multicultural Teams
Singapore's workforce is incredibly diverse, with professionals from across Asia and the world. Scrum's emphasis on clear communication, shared goals, and regular synchronization helps multicultural teams work together effectively.
2. Rapid Market Changes
Singapore's position as a regional hub means businesses must adapt quickly to changing market conditions. Scrum's iterative approach allows teams to respond to changes within each Sprint, rather than waiting for a project to complete.
3. High Competition
With over 3,700 multinational corporations in Singapore, competition is intense. Scrum helps companies deliver value faster, giving them a competitive edge.
4. Digital Transformation
Singapore's Smart Nation initiative is driving digital transformation across industries. Scrum is particularly well suited for software development and digital product delivery, making it essential for companies undergoing digital transformation.
5. Skills Development
With SkillsFuture eligibility, Singaporeans can use government credits to learn Scrum, making professional development more accessible. This has contributed to the growing adoption of Scrum across Singapore.
Stats in Singapore
According to recent data, 78% of Singapore employers are currently implementing Agile in their workplaces, with Scrum being the most commonly used framework. This represents a significant shift toward more adaptive, value-driven ways of working.
The high demand for Scrum professionals in Singapore has created strong career opportunities. With 83% of employers acknowledging that the COVID-19 pandemic accelerated Agile adoption, certified Scrum practitioners are increasingly sought after. The combination of high adoption rates and the need for skilled professionals makes Scrum certification a valuable investment for career advancement in Singapore's competitive job market.
10. Getting Started with Scrum
Ready to start your Scrum journey? Here's how to get started, whether you're an individual looking to learn Scrum or an organization planning to adopt it.
For Individuals
If you're looking to learn Scrum and become certified, here are the best starting points:
Professional Scrum Master (PSM)
Perfect for anyone new to Scrum. This two-day course covers the fundamentals of the Scrum framework, accountabilities, events, and artifacts. You'll leave with a solid understanding of Scrum and be prepared for the PSM I certification exam.
Learn MoreProfessional Scrum Product Owner (PSPO)
Ideal for product managers, business analysts, and anyone responsible for product success. Learn how to maximize product value using Scrum principles, practices and get prepped for the PSPO I exam.
Learn MoreApplied Professional Scrum with LEGO
A unique, hands-on way to learn Scrum by doing it. This class is facilitated by the creator of the APS with LEGO, making learning hands-on, creative, full of energy, and get ready for your Scrum exam.
Learn MoreFor Organizations
Organizations looking to adopt Scrum should consider:
- Start Small: Begin with one or two teams to learn and adapt before scaling
- Get Training: Invest in proper Scrum training for all team members
- Hire a Scrum Master: Consider hiring an experienced Scrum Master or training someone internally
- Be Patient: Scrum adoption takes time. Expect 3 to 6 months before teams become truly effective
- Focus on Culture: Scrum requires a cultural shift. Support from leadership is essential
We offer corporate training packages tailored to your organization's needs. Whether you need on site training, virtual sessions, or a combination, we can help your teams learn and implement Scrum effectively.
Ready to Learn Scrum?
Join 500+ professionals in Singapore who have transformed their careers with our Scrum training. View our upcoming events or contact us to learn more.
View Upcoming Courses11. Frequently Asked Questions About Scrum
What is the difference between Scrum and Agile?
Agile is a mindset and set of values and principles, while Scrum is a specific framework that implements Agile principles. Think of Agile as the philosophy and Scrum as one way to practice that philosophy. Scrum provides specific roles, events, and artifacts, while Agile is more flexible and can be implemented in various ways.
How long is a Sprint in Scrum?
A Sprint is a fixed length event of one month or less. Most teams use 2 week Sprints, though 1 week and 3 week Sprints are also common. The key is consistency, once you choose a Sprint length, stick with it to maintain rhythm, and predictability. Everything in Scrum is time boxed to create an opportunity to Inspect and Adapt.
Do I need to be a developer to use Scrum?
No! While Scrum is popular in software development, it can be used for any complex work. The term "Developers" in Scrum refers to anyone who creates the product increment, not just software developers. Scrum has been successfully used in marketing, HR, education, and many other fields.
What is the role of a Scrum Master?
The Scrum Master is a servant-leader who helps the Scrum Team and organization understand and implement Scrum. They're not a project manager or team lead. Instead, they coach the team, remove impediments, facilitate Scrum events, and help the organization adopt Scrum practices. Learn more in our Professional Scrum Master training.
Can Scrum work for large organizations?
Yes! While Scrum is designed for small teams, it can be scaled using frameworks like Nexus (for multiple teams working on one product) or Scaled Professional Scrum. We offer Scaled Professional Scrum training for organizations looking to scale Scrum across multiple teams.
How do I get certified in Scrum?
The best way to get certified is to take an official Scrum.org course and pass the certification exam. We offer all Scrum.org certifications, including Professional Scrum Master (PSM), Professional Scrum Product Owner (PSPO), and many others. Each course includes exam attempts and preparation materials. View our upcoming courses to get started.
Is Scrum only for software development?
No! While Scrum is widely used in software development, it's a framework for managing any complex work. Scrum has been successfully applied in marketing, HR, education, research, and many other fields. The principles of transparency, inspection, and adaptation work in any context where you're dealing with complex problems.
What makes Kiwii's Scrum training different?
Kiwii is Singapore's only official Scrum.org training partner. Our courses are hands on, interactive, and designed specifically for Singapore's business environment. We don't rely on boring slides, instead, we use workshops, games, and real world case studies to make learning engaging and practical. Plus, our trainers are certified Scrum.org Professional Scrum Trainers with real world experience.
12. Resources
This guide is based on the official Scrum Guide and supported by research and industry data. Below are the key resources and references used in this article.
Official Scrum Resources
- The Scrum Guide - The definitive guide to Scrum, created and maintained by Ken Schwaber and Jeff Sutherland, the co-creators of Scrum.
- Scrum.org - The home of Scrum, providing resources, training, and certifications.
- The Agile Manifesto - The foundational values and principles of Agile software development.
Research and Statistics
- Scrum Inc. (2024) - "Why 47% of Agile Transformations Fail" - Research on Agile transformation failure rates and common causes. View Research
- Go Beyond (2024) - "How Many Companies Use Scrum?" - Statistics on Scrum adoption and implementation challenges. View Research
- Scrum.org (2024) - "What Makes Scrum Teams Effective: A Scientific Investigation of 1,200 Scrum Teams" - Research on factors that contribute to Scrum team effectiveness. View Research
Additional Learning Resources
- Scrum.org Resources - Articles, videos, webinars, and other educational materials about Scrum.
- Kiwii Blog - Articles about Scrum adoption in Singapore, Agile practices, and professional development.
- Kiwii Training Courses - Official Scrum.org certified training courses in Singapore.
Conclusion: Start Your Scrum Journey Today
Scrum is more than just a framework, it's a way of thinking and working that can transform how teams and organizations deliver value. In Singapore's competitive business environment, Scrum provides the structure, discipline, and adaptability needed to succeed.
Whether you're an individual looking to advance your career or an organization seeking to improve how you work, Scrum offers a proven path forward. The key is to start with proper training and commit to continuous adaptation.
Ready to Learn Scrum?
Join hundreds of professionals in Singapore who have transformed their careers with our Scrum training. We offer official Scrum.org certifications, hands-on learning experiences, and support throughout your Scrum journey.