5 examples of agile management methods

The agile Scrum method: the most widespread iterative framework

Agile Scrum management is an iterative project management method that organizes work in short cycles called sprints, led by a Scrum Master and a Product Owner, in order to deliver value incrementally and integrate customer feedback continuously.

The term Scrum means “scrum” in English, in reference to rugby. The principle is simple: rather than planning a project over several months without visibility, the team divides the work into sprints of 1 to 4 weeks. At the end of each sprint, a functional deliverable is presented, evaluated, and then adjusted.

Key roles in Scrum

• The Scrum Master : It facilitates the process, removes obstacles and protects the team from external disturbances. He is not a project manager in the traditional sense, but a guarantor of the methodology.
• The Product Owner : he represents the voice of the customer, prioritizes the backlog (the list of features to be developed) and validates the deliverables at the end of each sprint.
• The development team : self-organized, it commits to a realistic volume of work for each sprint.

Real-world use cases

An IT department must redesign a customer portal in six months. Rather than specifying the entire project upfront, the Scrum team delivers a first functional module (authentication and dashboard) in three weeks. The customer tests, gives feedback, and the next sprint incorporates those adjustments. The result: the final product really meets expectations, without a tunnel effect.

Scrum is initially designed for IT project management, but its framework also applies to marketing, R&D or transformation program management. According to the Scrum Guide updated by Ken Schwaber and Jeff Sutherland, the framework is deliberately lightweight to adapt to a variety of contexts (scrumguides.org).

Limitations to be aware of

Scrum requires rigorous discipline in rituals (daily meeting, sprint review, retrospective). Without an experienced Scrum Master, teams quickly fall back into a classic way of operating disguised as agile — what practitioners call the “Scrum goal”.

Lean: eliminating waste to improve performance

The Lean method, historically created by Toyota in the 1950s, consists of boosting the performance and profitability of an organization through the systematic elimination of sources of waste. Applied to software development under the name of Lean Software Development, this agile approach has since spread far beyond the automotive industry.

Lean identifies seven types of waste: overproduction, waiting, unnecessary transportation, unnecessary processing, excessive inventory, unnecessary movement, and defects. By methodically tracking them down, the company obtains:

• Better management of stocks and flows
• Enhanced control of delivery times
• Measurable reduction in operational costs
• Elimination of transactions that do not provide value to the customer

Real-world use cases

A food manufacturer noticed that his production lines generated a high scrap rate. By applying a Lean approach, the team maps the value stream (Value Stream Mapping), identifies the steps that create defects and reorganizes the flow. Unnecessary operations are eliminated, quality control stations are repositioned. The scrap rate is decreasing, the lead times are shortening.

Lean also highlights the quality of the product, thanks to the optimization of all processes: from the development of employees’ skills to the design and implementation of deliverables. According to McKinsey, organizations that deploy Lean at scale see significant productivity gains in their field operations (McKinsey & Company).

This agile approach is one of the most effective tools in a continuous improvement process.

Extreme Programming (XP): technical rigour at the service of quality

Extreme Programming (XP) is an agile management methodology designed for IT project management, and more specifically for the development of applications where code quality is non-negotiable.

As with Scrum, the project is organized around very short iterative cycles, from one to three weeks. But XP goes further on technical practices:

• Pair programming : two developers work on the same workstation. One codes, the other reads in real time. The defect rate is falling, the increase in skills is accelerating.
• Test-Driven Development (TDD): Tests are written before code. Each feature is automatically validated as soon as it is created.
• Continuous integration : Code is merged and tested several times a day, reducing technical conflicts.
• Frequent refactoring: the code is regularly cleaned up and simplified without changing its behavior.

Real-world use cases

A fintech company is developing a mobile payment application. Regulatory requirements are changing rapidly, and every update must be 100% reliable. The XP team delivers increments every two weeks, with automated testing covering every feature. The planning of actions is carried out in the very short term, which allows a precise estimate of the development costs.

One of the goals of XP is to reduce the cost of switching. In a typical project, changing a specification at the end of the cycle is very expensive. With XP, the cost remains stable thanks to short cycles and automated testing.

Limitations to be aware of

XP requires a high level of technical maturity in the team. Pair programming, in particular, can generate fatigue if the sessions are not supervised. This method is not well suited to junior teams or projects where technical skills are heterogeneous.

Feature Driven Development (FDD): driving by features

Feature Driven Development (FDD) is a lesser-known agile project management method but particularly suitable for large-scale and complex projects, for which Scrum would show its limits in terms of coordination.

With the FDD methodology, development is organized around features . Each feature is small enough to be developed in 1-2 weeks, tested quickly by the user, and then adjusted. This agile method places the customer at the center of the project through frequent validations.

The 5 steps of FDD

1. Model globally : Create an ensemble model to delineate the scope of the product.
2. List the features : identify and describe all the features to be made.
3. Plan by feature : Define the development order and dependencies.
4. Design by feature : Each feature is designed in detail before development.
5. Build by feature : Develop, test, and integrate each feature with its user interface.

Real-world use cases

An ERP software publisher must deliver a new version integrating electronic invoicing, inventory management and an HR module. The project involves several teams spread over three sites. FDD allows this massive program to be broken down into standalone features, each assigned to a dedicated team, with bi-weekly delivery milestones. Coordination is done through the overall model, not through endless meetings.

Limitations to be aware of

FDD requires an experienced software architect to build the initial overall model. On small-scale projects, this modelling phase represents a disproportionate investment.

Kanban: visual management to streamline workflows

Kanban is a methodology from the Japanese automotive sector that is a natural part of a continuous improvement process. It is based on a visual organization of project management, accessible to all team members.

The term Kanban means “label” in Japanese. The method works with a system of cards and tables organized in columns: To Do — In Progress — Done. Each task is represented by a map that moves as it progresses.

The key principles of Kanban

• Limit WIP: Each column has a maximum number of cards. This prevents overload and forces the team to finish before starting.
• Visualize Flow : The board provides an immediate overview of the project’s progress. Everyone knows what needs to be done first.
• Measure lead time : The time between taking on a task and delivering it is tracked to identify bottlenecks.
• Continuous improvement : Regular retrospectives allow the process to be adjusted.

Real-world use cases

A marketing department manages digital campaigns, events and content production simultaneously. Without a method, priorities collide and deadlines get out of hand. By deploying a Kanban board on Jira or Trello, the team can see all tasks, limit the number of concurrent projects to three per person, and reduce delivery times. Daily meetings of less than 15 minutes allow everyone to recap the tasks completed, the tasks to come and any obstacles.

Kanban is also very effective in reducing project time, cost, and risk . Its major advantage: it can be applied to all types of projects and sectors, without requiring a major reorganization.

Comparison table of the 5 agile methods

Method	Cycle Length	Privileged sector	Ideal team size	Highlight	Main Limit
Scrum	1 to 4 weeks	IT, marketing, R&D	5 to 9 people	Structured and adaptable framework	Requires a trained Scrum Master
Lean	Continuous flow	Industry, Services, IT	Variable	Reduction of waste	Long-term cultural transformation
XP	1 to 3 weeks	Software Development	4 to 12 people	Maximum technical quality	Requires high technical maturity
FDD	1 to 2 weeks	Complex IT projects	Large teams (20+)	Scalability on large projects	Heavy initial modeling
Kanban	Continuous flow	All sectors	Variable	Easy to set up	Less structured than Scrum

How to choose the right agile method for your organization?

The choice of an agile approach is not made on the basis of popularity. It depends on three concrete factors:

• The nature of the project : complex software development will lead to Scrum or XP. An industrial transformation program will call for Lean. A need for cross-functional visual management will be solved with Kanban.
• Team maturity : A team that is new to agility will get started more easily with Kanban (no specific roles to create) than with Scrum or XP.
• Deployment scale : For agile transformation at the scale of a large organization, frameworks such as SAFe (Scaled Agile Framework) make it possible to articulate several methods. The Business Agility Institute points out that organizations that successfully scale typically combine multiple approaches rather than imposing one (Business Agility Institute, 2024).

Let’s be clear: adopting an agile method is not just about installing a Kanban board or renaming meetings to “daily stand-up”. Agile transformation affects managerial culture, decision-making methods and customer relations. It is a change of posture as much as a change of process. The Project Management Institute reminds us in its Pulse of the Profession 2025 that organizations with mature agile practices have a significantly higher success rate of their projects than those that remain on purely predictive approaches (PMI, 2025).

Frequently asked questions about agile management

Which agile method should I choose for a non-IT project?

Kanban and Lean are the two agile approaches best suited for non-IT projects. Kanban offers visual management applicable to any sector (logistics, marketing, HR), while Lean focuses on eliminating waste in industrial or service processes. Scrum can also be adapted, but its sprints framework is best suited for projects with iterative deliverables.

How to deploy an agile method in a traditional organization?

The deployment begins with a pilot project on a small team, with dedicated support (Scrum Master or agile coach). First, identify the operational pain points that agility can solve. Train teams in agile rituals (daily meetings, retrospectives). A specialized interim manager can accelerate this transformation by providing immediately operational expertise.

Can you combine several agile methods within the same company?

Yes, and it is even a common practice. Many organizations use Scrum for project management and Kanban for day-to-day operational monitoring. The SAFe (Scaled Agile Framework) framework makes it possible to articulate several agile methodologies on the scale of a large organization. The hybrid Scrumban approach, which merges Scrum and Kanban, is also gaining popularity.

What is the role of the project manager in an agile organization?

In an agile organization, the project manager evolves into a facilitator role rather than a supervisor. In Scrum, this role is split between the Scrum Master (guarantor of the process) and the Product Owner (voice of the customer). The agile project manager removes obstacles, protects the team from interruptions, and promotes self-organization. It no longer dictates tasks: it creates the conditions for the team to deliver value.