2. Agile Working: An Introduction

The English term ‘agile’ refers to a philosophy and working method that is widely used in the business world. It enables teams to develop a product in a flexible, customer-focused, and iterative way (that is, in successive steps). Central concepts include collaboration, adaptability and the continuous creation of value for the customer.

Origins

The origins of agile working can be traced back to the period between 1990 and 2000. During this time, particularly in the field of increasingly complex software development, dissatisfaction grew with the traditional ‘waterfall’ approach to project management and similar rigid methods.^[1] Under these approaches, projects or major phases of a process were planned in as much detail as possible in advance and then executed in a single linear sequence, leaving little room for adjustment along the way.

These methods offered limited flexibility. Products had to be delivered in finished form after a fixed period of time, which sometimes resulted in outcomes that did not correspond to the actual needs of the customer. Problems were often identified only during the testing phase, making corrections costly and time-consuming. As a result, many projects failed to be completed within the set timeframe or available budget.^[2]

In 2001, seventeen experienced software developers came together at a ski resort in Utah in the United States to discuss these challenges. Their discussions resulted in the Agile Manifesto,^[3] a concise document that sets out four core values and twelve principles that form the foundation of agile working. The Agile Manifesto marked a paradigm shift in the way software development projects were managed and carried out.

Today, agile methods are applied in many other sectors of the business world, including marketing and communication, financial services and product development. Public sector organisations, such as the Dutch National Police, also use agile working methods in certain areas, for example in the investigation of criminal offences, even though this does not yet constitute a widely adopted organisational model.

Examples: Scrum, Kanban and Extreme Programming

Scrum, Kanban and Extreme Programming (XP) are three widely used agile methodologies in software development and project management. They share the common goal of promoting flexibility, collaboration and continuous improvement, but differ in their approach, processes and roles. To illustrate both their similarities and differences, these methods are briefly discussed below.

Scrum: an agile method based on short iterations

Scrum is a widely used agile framework that enables teams to deliver working software in short, iterative cycles known as sprints.^[5] Each sprint aims to produce a functional and usable increment of the final product.

Core roles

Scrum defines three essential roles: the Product Owner, the Scrum Master, and the Development Team.

The Product Owner is responsible for managing the Product Backlog, a prioritised and evolving list of desired product features. This role ensures that the team focuses on delivering the highest value to the customer.

The Scrum Master supports the team by ensuring that Scrum principles and practices are properly applied. He facilitates meetings and helps remove any obstacles that may impede progress.

The Development Team is collectively responsible for completing the work within each sprint and delivering the agreed outcomes.

The Scrum process

Work in Scrum is organised into sprints, which typically last between two and four weeks. Each sprint follows a structured sequence of meetings, commonly referred to as ceremonies.

Each sprint begins with Sprint Planning. During this meeting, the Development Team selects the most important tasks from the Product Backlog in consultation with the Product Owner. These tasks are recorded in the Sprint Backlog, which sets out clear and realistic goals for the upcoming sprint.

During the sprint, the Development Team meets briefly each day to discuss progress, identify obstacles and coordinate activities for the next twenty-four hours. This meeting is known as the Daily Scrum or stand-up.

At the end of the sprint, the completed work is presented to stakeholders, including the Product Owner, in order to gather feedback. This is followed by a reflection on the sprint process itself. The lessons learned are used to improve the next sprint.

This structure, with its focus on short cycles, regular feedback and ongoing reflection, enables Scrum teams to respond flexibly to changing requirements and to deliver valuable results efficiently.

Kanban: visualizing workflows

Kanban is an agile methodology that is generally more flexible than Scrum.^[6] Its core principle is the improvement of workflow through visualization. Tasks are displayed on a Kanban board, which may be physical or digital. This board consists of columns representing different stages of the work process, such as ‘To Do’, ‘In Progress’ and ‘Done’. In this way, all team members can see the current status of each task at any time.

To prevent overload, limits are usually set on the number of tasks allowed in each column. These so-called work-in-progress (WIP) limits help ensure that teams focus on completing tasks before starting new ones.

A key difference from Scrum is that Kanban does not prescribe fixed roles or time-bound sprints. Tasks can be added, adjusted or reprioritised at any moment. The emphasis lies on maintaining a continuous and efficient flow of work through the system. Bottlenecks and delays quickly become visible through the board, making it possible to identify and address problems at an early stage.

Extreme Programming (XP): strengthening technical quality

Extreme Programming (XP) is an agile method that focuses primarily on the technical aspects of software development, such as improving code quality, continuous testing and frequent customer feedback. One of its most distinctive features is intensive collaboration between developers. In XP, two developers work together at a single computer on the same code, a practice known as pair programming. This encourages knowledge sharing and allows errors to be detected and corrected more quickly.

Another central element of XP is frequent code testing, which allows problems to be detected at an early stage. In addition, all team members are permitted to modify the code to correct errors or implement improvements. Software is developed in small increments and released regularly, enabling rapid customer feedback and ensuring that the product evolves in line with user needs.

Overview

The three examples of agile methodologies discussed above illustrate that ‘agile’ does not refer to one single way of working, but rather to an overarching concept that includes different approaches. What these methods have in common are flexibility, effectiveness and close communication between stakeholders in the creation and delivery of products.

Scrum can be described as a structured method with clearly defined roles, fixed time frames and formalised meetings. This creates a predictable development process with regular moments for consultation and evaluation.

Kanban, by contrast, is far more flexible and is particularly suited to managing a continuous workflow. It does not rely on fixed time limits or formal ceremonies.

Extreme Programming (XP) focuses primarily on improving specific technical aspects of the production process. It places strong emphasis on the quality of the product itself and less on the overall management of the development process.

Advantages of Agile Working

In the business world, agile working offers a wide range of benefits for both teams and organisations.^[7]

– First, it enables faster delivery of working products.

Agile methods rely on short iterations in which partial results are delivered continuously. This leads to quicker value creation for customers.

– Second, agile working allows for greater flexibility.

The iterative approach enables teams to respond rapidly to changes in the market, technology or user requirements. This offers a clear advantage over traditional waterfall methods, where adjustments can often only be made at a late stage.

– Third, agile working promotes more intensive and effective collaboration.

The strong emphasis on cooperation between customers, clients and developers improves communication and decision-making, resulting in a more efficient development process.

– Fourth, agile methods contribute to higher product quality.

Through frequent evaluation and feedback moments, products are continuously improved. Problems are identified and addressed at an early stage, leading to a better final outcome.

– Fifth, agile working increases team engagement and motivation.

Teams are given the autonomy to take responsibility for the final result. Active involvement in the process strengthens a sense of ownership and contributes to a positive working atmosphere.

– Sixth, agile working enhances transparency.

Regular reviews, stand-up meetings and other recurring activities provide insight into progress, bottlenecks and decision-making.

– Finally, agile working can lead to greater customer satisfaction.

By delivering valuable interim results on a regular basis and by involving customers closely in the development process, customers feel heard and engaged. They can see progress in the short term, which increases confidence in the process and overall satisfaction.

The Challenges of Agile Working

Despite its benefits, agile working also presents several challenges, particularly when implemented in large organisations that are accustomed to clearly defined and structured processes. For individuals familiar with more traditional working methods, agile practices may initially feel overwhelming. When this approach becomes the dominant way of working, adequate preparatory training is therefore essential.

Moreover, agile working is less suitable for projects that must operate within strictly fixed budgets. Because the methodology emphasises flexibility and responsiveness to change, it can be difficult (especially in large-scale projects) to define precise budgets and timelines in advance. This may create difficulties for customers or stakeholders who require certainty regarding costs and planning.

Finally, there is the risk of so-called scope creep, which refers to the continuous addition of new requirements that cause projects to expand beyond their original boundaries. It is therefore crucial that the Product Owner, who holds ultimate responsibility for the project, establishes clear limits and consistently monitors them throughout the process.