What is Scrum: Explained in Detail

Key Takeaways

1. Scrum is used for addressing complex problems and generating value through iterative and incremental work. 

2. Transparency, inspection, and adaptation form the three empirical pillars that underpin Scrum. 

3. Scrum Teams consist of three accountabilities: the Product Owner, Scrum Master, and Developers. 

4. Scrum uses defined events and artefacts to support planning, collaboration, feedback, and adaptation. 

5. Regular inspection and adaptation help Scrum Teams respond to change and continuously improve their work.

A board full of colourful cards.

A 15-minute meeting every morning. 

Tasks move steadily from To Do to Done. 

It might look like Scrum, but those things alone do not make Scrum work.

The real framework goes deeper. Values shape behaviour, pillars support empirical decision-making, accountabilities establish responsibility, and events and artefacts create opportunities to inspect and adapt. In this blog, you'll get detailed information about all the above aspects under What is Scrum.

What is Scrum?

Scrum is a lightweight framework that helps teams generate value by addressing complex problems through an iterative and incremental approach. Work is organised into Sprints, during which the Scrum Team creates a usable Increment and regularly inspects progress to determine what should be adapted next.

Scrum does not prescribe every technique a team must use. Instead, it provides a structured framework of accountabilities, events, artefacts, values, and rules within which teams can apply suitable practices.

Scrum Theory and the Three Pillars

Scrum is founded on empiricism and lean thinking. Empiricism means that knowledge comes from experience and decisions are based on what is observed. Here are the three pillars of Scrum Theory

1) Transparency

Transparency means that everyone can see the work and understand what’s going on. It helps team members understand each other and avoid confusion. When information is open and visible, problems can be spotted and solved faster.

a) Share work updates with the whole team

b) Use boards or tools to show task status

c) Keep goals and progress clear to everyone

2) Inspection

Inspection means checking the work often to see if everything is going well. The team looks at their progress and finds areas that need fixing. Regular checks help spot issues before they become big problems.

a) Review work during daily meetings

b) Catch mistakes early through regular checks

c) Look at results after each work sprint

3) Adaptation

Adaptation means making changes when something isn’t working. If a plan or task doesn’t go as expected, the team quickly adjusts. This helps improve the product and the way the team works.

a) Change plans when problems show up

b) Try new ideas to work better

c) Fix issues before they slow down progress

Trainer’s Insight

Scrum works best when inspection leads to meaningful adaptation. Simply holding Scrum events is not enough. Teams should use what they learn from progress, feedback, and outcomes to adjust how they work and what they prioritise next.

Improve team collaboration and focus with Scrum Master Certification Training - Join today!

What are Scrum Values?

Scrum is built around five core values that guide team behaviour and decision-making: Commitment, Courage, Focus, Openness, and Respect. These values foster trust, collaboration, and continuous improvement within Scrum teams.

1) Commitment

Scrum team members personally commit to achieving the goals of the team. This involves dedicating themselves to the team's objectives and being accountable for their contributions.

2) Courage

Team members must have the courage to do the right thing and tackle tough problems. This means being open to feedback, admitting mistakes, and addressing challenges directly.

3) Focus

Everyone must concentrate on the work of the Sprint and the goals set by the Scrum Team. By focusing on the tasks at hand, teams can deliver valuable increments efficiently.

4) Openness

The Scrum team and its stakeholders must agree to be open about the work and the challenges that come with it. This transparency fosters trust and facilitates problem-solving.

5) Respect

Scrum Team members must respect each other to be capable, independent people. This mutual respect encourages a collaborative environment where diverse perspectives are valued.

Own the product, own the process! Be in the driver's seat with Scrum Product Owner Certification Training - Sign up now!

What are Scrum Roles?

There are three different roles in Scrum. It ensures that the team is successful in delivering high-quality products. The primary Scrum Roles are Product Owner, Scrum Master, and Development Team. Let's learn about them in detail:

1) Product Owner

The Product Owner makes sure the team builds what brings the most value to the business. They understand customer needs and set clear priorities. Good Product Owners:

a) Order Product Backlog items according to product needs and value

b) Act as a link between business goals and the team’s understanding

c) Create and communicate Product Backlog items

2) Scrum Master

The Scrum Master supports the team in following Scrum and making it more effective. They coach team members, help improve processes, and ensure smooth delivery. Scrum Master also performs the following functions:

a) Coach team members in self-management and cross-functionality

b) Help the Scrum Team focus on creating valuable Increments

c) Help remove impediments to the Scrum Team's progress

d) Ensure Scrum events take place and remain productive and within their timeboxes

e) Help the organisation understand and adopt Scrum effectively

3) Developers

Developers are the members of the Scrum Team committed to creating a usable Increment during each Sprint. Their professional skills can vary depending on the product and type of work being undertaken. Developers perform the following:

a) Create the Sprint Backlog

b) Maintain quality by adhering to the definition of done

c) Adapt their plan each day towards the Sprint Goal

d) Hold one another accountable as professionals

WHO OWNS IT?

Match each responsibility to the correct Scrum accountability:

A. Product Owner

B. Scrum Master

C. Developers

Creates the Sprint Backlog →?

Orders Product Backlog items →?

Helps remove impediments →?

Maintains quality through the Definition of Done →?

Helps establish Scrum within the organisation →?

Answers: 1-C | 2-A | 3-B | 4-C | 5-B

What are Scrum Artefacts?

Scrum artefacts are important tools that help you ensure that your team and the stakeholders are on the same page. They show what’s being worked on, what’s already done, and what still needs to be done. The three main Scrum artefacts are the Product Backlog, Sprint Backlog, and Increment.

1) Product Backlog

The Product Backlog refers to a list of changes, features, and fixes that are needed for the product. It’s managed by the Product Owner and is updated regularly as the project grows or changes. This list helps the team know their next point of focus and keeps their work aligned with business goals.

2) Sprint Backlog

The Sprint Backlog includes tasks picked from the Product Backlog to be performed in the current sprint. It also has a clear plan to reach the Sprint Goal. The team updates this list daily so everyone can track progress and make sure the work is on track.

3) Increment

The Increment is the finished work from the current sprint, combined with all past completed work. It should be complete, usable, and ready to release if needed. Every increment must meet the team’s agreed definition of “Done.”

What are Scrum Events?

Essentially, Scrum events are regular meetings that help drive the team through each stage of the work. They keep everyone focused, help track their progress, and support continuous improvement. The main Scrum events include:

1) Sprint

A sprint is a set time, usually one to four weeks, where the team works on the planned tasks. The goal is to deliver the working parts of the product by the end of the sprint.

2) Sprint Planning

At the beginning of a sprint, the team meets to plan what work they’ll complete. They choose the top items from the backlog and agree on a goal. Then, they break the work into smaller tasks and decide how to complete them.

3) Daily Scrum or Stand up

This is a quick, 15-minute meeting held every day during the sprint. Team members share what they’re working on, what’s done, and if there are any problems. It helps keep everyone on track.

4) Sprint Review

During the Sprint Review, the Scrum Team and key stakeholders inspect the outcome of the Sprint, discuss progress towards the Product Goal, and consider what to do next. The Product Backlog can also be adapted based on what has been learned.

5) Sprint Retrospective

After the sprint review, the team meets to talk about how the sprint went. They discuss what went well, what didn’t, and how to improve in the next sprint. This helps the team keep getting better.

Interesting Fact

A new Sprint starts immediately after the previous Sprint concludes. There is no separate gap between Sprints built into the Scrum framework, creating a continuous rhythm of delivering, inspecting, and adapting.

Bring structure and agility to every project with our Managing Agile Projects With Scrum Course - Register now!

Benefits of Scrum

Below are a few benefits of Scrum:

1) Faster Delivery of Value: Short Sprints enable teams to deliver usable outcomes more frequently. 

2) Greater Adaptability to Change: Teams can respond to changing requirements and priorities throughout development. 

3) Improved Team Collaboration: Regular Scrum events encourage communication, coordination, and shared accountability. 

4) Better Project Transparency: Scrum provides clear visibility into progress, priorities, challenges, and remaining work. 

5) Continuous Improvement: Regular inspection, feedback, and retrospectives help teams improve both the product and their working practices. 

6) Stronger Customer Focus: Frequent feedback and value-based prioritisation help ensure that development remains aligned with customer needs.

Scrum in Practice: Real-world Example

Consider a team developing a mobile banking application. Instead of building the entire application at once, the team uses Scrum to deliver it through a series of short Sprints.

1) Product Backlog: The Product Owner prioritises features such as secure login, account balance viewing, money transfers, transaction history, and payment notifications.

2) Sprint Planning: The Scrum Team selects high-priority Product Backlog items that it believes can be completed during the Sprint. For example, one Sprint might focus on secure login and account balance functionality.

3) During the Sprint: Developers work towards the Sprint Goal, while the Daily Scrum helps them inspect progress and adapt their plan for the next day's work.

4) Sprint Review: The completed Increment is presented to stakeholders. Their feedback can influence what is prioritised in the Product Backlog next.

5) Sprint Retrospective: The Scrum Team reviews how it worked during the Sprint and identifies improvements for the next one.

This cycle continues across Sprints, allowing the banking application to develop incrementally while incorporating regular feedback and adapting to changing requirements.

Difference Between Agile and Scrum

Here are the key distinctions between Agile and Scrum:

Conclusion

Scrum is a flexible approach to Project Management that highlights communication, teamwork, and continuous improvement. It can be a highly effective method for delivering high-quality results in a timely and efficient manner. Scrum offers a framework for building better products and empowering teams to achieve their full potential. By understanding What is Scrum and applying it to your organisation, you can enable teams to collaborate effectively and respond quickly to any changes.

Build better and sprint smarter with our Scrum Developer Training - Sign up now!