michaela-damm.jpg
blocshop
September 02, 2021
0 min read

Scrum vs. Extreme Programming (XP): What's the difference?

Scrum vs. Extreme Programming (XP): What's the difference?.png


We've covered the Software Development Life Cycle (SDLC) and the Agile development framework. Now it's time to look at different methodologies and approaches to their implementation. There are several, but we'll focus in this article on just two of them, Scrum and Extreme Programming (XP). We'll look at the differences between them and how they can even be used together for even better results.

What is Scrum?

Scrum is a lightweight approach to Agile software development. It helps teams and organizations create value through flexible and cooperative development and problem-solving. It breaks down complex projects into logical and manageable chunks.

Scrum uses a Scrum Master to build and maintain an environment where:

  1. The Product Owner orders the work for a complex problem into a Product Backlog;

  2. The Scrum Team turns part of that work into an ‘increment of value’ during a Sprint;

  3. The Scrum Team and its stakeholders review the results and adjust for the next Sprint;

  4. Repeat.

The Scrum 'pillars' are transparency, inspection and adaptation. These pillars are expressed and addressed through all 'events' during any particular 'Sprint'. The 'events' in a Scrum are:

The Sprint

The 'Sprint' contains all of the Scrum events. They are the manageable chunks that make up the entire project. It is during the Sprint that ideas are turned into value. Through a series of 'sprints', the project is finished. A Sprint cycle in Scrum will consist of a month or less of development time.

During the Sprint:

  • No changes are made that would undermine the Sprint Goal;

  • Quality does not suffer;

  • The Product Backlog is adjusted as needed; and,

  • The scope of the Sprint may be refined and redefined with the Product Owner as more is learned.

The Sprint is further divided into the following events:

Sprint Planning

Sprint Planning kicks off the Sprint by defining the work to be performed in the Sprint. The resulting plan is created by the collaborative work of the entire Scrum Team.

Sprint Planning asks (and answers!) the questions Why? What? And how? Why are we setting these particular goals for this Sprint? What do we plan to do? How will we achieve the(se) Sprint goal(s). While this happens at the beginning of every Sprint, it is reinforced (and/or modified) at each ‘daily scrum’. This allows for both inspection and adaptation.

Daily Scrum

The Daily Scrum is a 15-minute stand-up meeting of the entire Scrum Team. Its purpose is to inspect (assess) progress toward the Sprint Goal(s). It's also an opportunity to adapt the Sprint Backlog as necessary, adjusting the day’s upcoming (previously-planned) work. This creates focus and improves self-management.

Daily Scrums promote better communication, help to identify stumbling blocks, allow for quick decision-making, and eliminate further and needless meetings.

Sprint Review and Sprint Retrospective

Sprint Review involves the presentation of all of the work accomplished during the Sprint. Sprint Retrospective identifies what went well, what went wrong and how the development process may be improved for the next Sprint. The next Sprint begins the following day and this cycle repeats until the project is finished. Learn more about the topic in Sprint Reviews and Sprint Retrospectives blog post.

What is Extreme Programming (XP) and how is it different from Scrum?

In an XP project, work happens in short(er) iterations that can last from one to three weeks. Before each iteration, the development team and all relevant stakeholders decide how much work can be done during that period. The customer prioritizes the work that needs to be done, and the team members commit to the amount of work they estimate they can deliver during that particular iteration.

As opposed to Scrum, development ‘sprints’ (iterations) are much shorter, so production is quicker and the feedback loop is tighter. While Scrum relies more on self-management, XP is much stricter in its engineering practices. XP engineers must:

  • write unit tests before the production code (Test-Driven Development);

  • use pair-programming when writing production code;

  • pairs must integrate their code often (continuous integration);

  • refactor the code as often as possible;

  • adopt 'collective ownership' of the code (this allows for better collaboration and integration = fewer bugs and cleaner code).

Related post: Agile vs. Scrum: Which is better for your project?

The Difference is in the details:

Scrum and XP are both approaches to and methodologies of Agile software development, so they have a lot in common. While the differences may be subtle, they're very important:

  1. Scrum teams usually develop in iterations (called Sprints) that are from two weeks to one month long. XP teams tend to develop in iterations that are one to two weeks long.

  2. Scrum teams do not allow for any major changes in their Sprints. Once the Sprint Planning meeting is completed and a commitment made to delivering a set of Product Backlog items, that set of items is set in stone. XP teams are much more flexible within their iterations and can easily swap out a major requirement, provided work has not yet begun on it.

  3. XP teams work in a strict priority order. Features are prioritized by the customer (Scrum’s Product Owner) and the team works on them in that particular order. By contrast, it’s the Scrum Product Owner who prioritizes the Product Backlog. But it's the team that determines the sequence in which they will develop those items.

  4. Scrum doesn’t prescribe any engineering practices; XP does - a lot (see above).

Both approaches provide flexibility and adaptability, but at different points and levels of the development cycle. See the table below:

Aspect / Practice

Scrum

XP

Cycle (iteration):

2 – 4-week ‘Sprints’

1 – 2-week iterations

Priority determined by:

The Team (loose)

The customer (strict)

Changes to Backlog:

Not allowed

Flexible

Validation:

End of the Sprint (Review)

Before any code is written

Prescribed Engineering Practices:

None

Many

Ultimate responsibility:

The Scrum Master

Any developer (collective)

Both frameworks have a lot to offer, so which to choose? Well, that depends on the project and the team, but the good news is you don’t have to choose! You can apply the best practices and approach of both; perfectly-suited to each individual project! Here at Blocshop, we rely mostly on Scrum for our projects, as we feel it provides the greatest flexibility and freedom to our developers while still focusing on outcomes. But we also apply aspects of other methodologies depending on project and customer requirements. We are always open to fashioning an individual, per-project, hybrid methodology to overdeliver, early and under budget, the cleanest code and maximize customer value.


Learn more from our insights

roro665_depict_a_data_sample_thta_completely_changes_its_form_725a4f20-ea40-4dd1-a68d-5c4327c9bf24_1.png
June 20, 2024

Generative AI used for data conversions and reformatting

How to use generative AI for data conversion, addressing integrity, hallucinations, privacy, and compliance issues with effective validation and monitoring strategies.

DALL·E 2024-05-30 09.37.01 - An illustration suitable for an article about ISO 20022. The scene should feature a modern, sleek representation of the ISO 20022 logo in the center. .webp
May 28, 2024

ISO 20022 Explained: A Comprehensive Guide for Financial Institution Managers

What is ISO 20022? How does it affect companies and institutions in the fintech and banking industry and how to prepare for its adoption? All explained in this article.

DALL·E 2024-05-22 20.55.08 - A detailed and high-quality DSLR photo of a person using a laptop to shop online, showing personalized product recommendations on the screen. The back.webp
May 16, 2024

Key AI Trends in E-commerce and Overview of AI integrations for E-commerce Platforms in 2024

Transform your e-commerce platform with AI tools for personalization, analytics, chatbots, search, and fraud detection. Boost sales and improve customer experiences.

eIDAS mark.png
May 09, 2024

Digital Identity and Payment Services in the EU in 2024: Key Updates

eIDAS 2.0 and PSD3 are set to enhance how digital identities and payment services are managed across the European Union in 2024. Here’s an overview of how each framework contributes to the digital landscape of the EU, what to expect, and how to prepare.

eIDAS 2 in fintech and open banking EU market.png
May 06, 2024

What is eIDAS 2.0 and EU Digital Identity Wallet and how will it change the EU digital market

Learn how eIDAS 2.0 and the EU Digital Identity Wallet will transform digital transactions and identity management across the European Union.

best large language models for ERP systems.png
March 31, 2024

Language Models Best Suited for Integration into ERPs

Four prominent large language models stand out for their compatibility and effectiveness in ERP system processes and automation. See what they are.

PSD3 in open banking Blocshop.png
April 23, 2024

PSD2 vs. PSD3: The Evolution of Payment Services Regulation

What is PSD3 in open banking? See how PSD3 compares to PSD2 and what should banks and fintech businesses do to ensure regulatory compliance in the EU market.

roro665_hands_working_with_a_laptop_in_a_modern_office_there_is_20dca307-c993-4539-99d7-fd5ca264248c.png
April 14, 2024

Enhancing ERP Systems with AI Chatbots

Explore how AI chatbots can transform ERP systems, enhancing efficiency, decision-making, and user interaction.

eIDAS in fintech and open banking EU market.png
April 29, 2024

eIDAS: The regulation helping secure Europe's digital future

See how eIDAS enhances EU digital transactions with secure identity verification, supporting e-commerce and public services across Europe.

hybrid ERPs.png
March 21, 2024

Hybrid ERP: An Innovative Approach to Enterprise Resource Planning

Hybrid ERP is a blend of cloud and on-premise solutions. With expertise in both, Blocshop is uniquely positioned to help you with hybrid ERP development and implementation.

0-4 cover.png
October 03, 2023

IT Staffing: Individual Hiring vs. Specialized Developer Teams

Should you hire individual developers or go for a specialized, custom-built developer team?

chatgpt-35-limitations.jpg
July 17, 2023

ChatGPT-3.5: An Overview and Limitations

In this article, we'll take a closer look at the capabilities and limitations of ChatGPT-3.5, providing you with a comprehensive overview of what it can do and what its boundaries are. So, let's delve into the inner workings of this large language model.

gpt4 vs gpt3-5 and the key differnces.png
June 15, 2023

A Deep Dive into GPT-4 vs GPT-3.5 Differences and Ability to Revolutionize Software Development

There are key differences between ChatGPT-3.5 and ChatGPT-4 that software developers and companies procuring software solutions alike should be aware of. Let's see how these differences affect the output generated by these models on specific examples.

ai-development-cto-2023.jpg
May 09, 2023

AI-powered software development: What CTOs need to know in 2023

As technology continues to evolve at a rapid pace in 2023 and beyond, CTOs must stay ahead of the curve by utilizing predictive analytics, automated testing processes, and deployment solutions.

ai-web-development.jpg
May 05, 2023

How Artificial Intelligence is changing web development

AI technology is now being used in many different industries, including web development. It’s important to understand the impact that AI can have on web development as it can help companies to create more efficient and user-friendly websites.

cto-ai-software-development.jpg
May 05, 2023

How AI-powered software development is changing the role of the CTO

As AI-powered software development becomes increasingly commonplace, CTOs must prepare themselves to take on a new set of responsibilities that require more than just technical know-how.

build-mvp.jpg
April 17, 2023

How to build a minimum viable product (MVP)

The MVP is the version of a new product that allows Blocshop and your team to collect the maximum amount of validated learning about customers with the least amount of effort. The essence of your core idea is delivered as a barebones solution. The solutions is, however, sufficient for usage by early adopters. As a product, it has tangible qulities that express a look and feel.

ai-tools-developers.png
March 21, 2023

10 AI tools for developers you should know about in 2023

For developers, programmers, and data scientists, AI coding solutions can free up thinking time, allowing such professionals to focus on the fundamentals of their projects, and complete such projects much faster.

web-app-ideas.png
February 14, 2023

17 Ideas for Web Apps in 2023

Gazillions of web apps and ideas for web apps are floating around the metaverse - so creating one that properly represents a unique brand is a huge challenge. Our list provides a number of areas of simple app ideas to help businesses transform their online presence through a web app.

Top 15 micro-SaaS ideas for your startup in 2023.png
December 06, 2021

Top 15 micro-SaaS ideas for your startup in 2022

What exactly do we mean by micro SaaS? Micro Saas solutions use a web browser or mobile app interface. Micro SaaS solutions usually come about through the effort of an individual or very small team. It aims to solve precise problems. Micro SaaS projects have small budgets and overhead. Customers use Micro SaaS solutions on a monthly or yearly subscription basis. Micro SaaS projects target a small niche of the consumer market.