A few years ago, Scrum used to be the only Agile methodology. But, times have changed. Right now, there are more than fifty known Agile methods.

So, what is Agile? Agile is a form of project management style that is iterative and incremental in approach. Its leading use is in software development, but not limited to it. It differs from traditional project management as it is very responsive to change.

In this article, you will learn about Agile methods, how they work, and how to use them in your projects.

1. Scrum

Scrum is one of the most popular subsets of Agile methodologies. This method was created by Ken Schwaber and Jeff Sutherland, who define Scrum as a framework for developing and sustaining complex products.

In Scrum, you divide the work into units called sprints. A sprint is a set time that a Scrum team works to complete a set amount of work. The Scrum Master, who leads the Scrum team, creates the sprints and organizes the work.

Through the daily Scrum (that usually happens in the morning), every team member reviews their performance for the past 24 hours. Then, they are briefed with the sprint goals for the next 24 hours, and everyone gets to work. If a team member needs help, the Scrum Master helps them resolve it.

The Scrum method is scalable and flexible. It is best suited for projects that change rapidly and need the flexibility to change as the project evolves.

2. Kanban

Kanban board

The origin of Kanban is in car manufacturing. It is a method that optimizes every stage of the production process and ensures production is just in time. Today, Kanban has evolved beyond manufacturing and is now widely used in project management.

So, what is Kanban? Kanban is a workflow project management approach that helps you visualize your work and ensure a smooth flow of your work. When using the Kanban method, you use a Kanban board that visualizes your work into three columns. Those columns are To Do, In Progress, and Complete.

Each column has a Work In Progress (WIP) limit that limits the number of items under a column. So, if a column has a limit of four, there cannot be more than four cards on it. If a column is packed, your team has to work on the items on the columns before moving forward or adding more cards.

Kanban is ideal for knowledge work that is often not tangible. Having the visualization helps you see what you're working on.

3. Adaptive Software Development (ASD)

The Adaptive Software Development Agile methodology was developed by Sam Bayer and Jim Highsmith in the early 90s. It was created as a refinement of Rapid Application Development (RAD) that was popular with hackers. ASD's strong point is that it handles the uncertainty in software development and fosters collaboration.

ASD, just like other agile methods, works in iterations. However, it differs from the rest as the iterations are component-based and not task-based. These components are a group of features that are delivered together. They are grouped into three: primary components, technology components, and support components. It allows for on-time delivery of projects, and in some cases, even earlier.

The drawback of ASD is that it demands intense user involvement. And, in some cases, it may be difficult to facilitate. Another draw is that ASD is change tolerant and adopts shorter time-frames. That can lead to scope creep during projects.

4. Dynamic Software Development Method (DSDM)

Woman-coding

Dynamic Software Development Method (DSDM) is another Agile methodology developed from Rapid Application Development (RAD). It brings structure to the free-form of RAD. Its philosophy is that any project must have clear goals and should focus on the early delivery of its goals.

This philosophy is backed by its eight principles, which are: focus on the business need, delivering on time, collaborate, don't compromise on quality, build incrementally, develop iteratively, communicate clearly and continuously, and have control.

DSDM uses the MoSCoW prioritization method of productivity that groups tasks into four priorities. Those are must-have, should-have, could-have, and won’t-have. This method helps if you have budget constraints and gets you to prioritize the must-haves of the project. Also, if there is a constraint on expertise, it prioritizes work based on the skillsets already on your team.

Another feature of DSDM is timeboxing. DSDM sticks to strict deadlines, and it does that by breaking down the project into smaller units that have a deadline and tight budget. Other than that, it is also strict on the order of events in a project. It has them as Pre-Project phase, Project Life-Cycle phase, and Post-Project phase.

5. Feature-Driven Development (FDD)

Feature-driven development is a client-centric and pragmatic approach in software development. Its first use was in 1997 to develop software for a Singaporean bank. Since then, it has grown as an approach. It is now mainly used in long-term complex projects that need a simple but comprehensive approach.

FDD's structure is straightforward, and teams with complex projects can scale it to meet their needs. Unlike other Agile methods that are iterative and incremental, FDD follows five steps. These are:

1. Developing the Overall Model

It covers the scope of the project.

2. Build a Features List

Identify all the features that are to be built. For this, no feature should take more than two weeks to build. If a feature takes longer, you break it down into smaller features.

3. Plan by Feature

Arrange the order in which the features are to be developed and implemented.

4. Design by Feature

Design and build a feature in a two-week iteration. When complete, there is a review of it by the team before developing the next feature.

5. Build by Feature

The completed feature in step-4 is added to the main build.

These steps are borrowed from engineering best practices and create consistency in a project. These also help reduce confusion and rework as everything is clear from the get-go.

Be Agile

Traditional project management methods like linear have been around for a while. They are steady and predictable. However, they have their limitations. One of the main ones is that they're slow in responding to the changes in the market.

This is where Agile comes in. Agile project management may be the newcomer in project management compared to the rest, but it is highly adaptable to the changes in the market. It has shortened product development timelines, increased productivity, and empowered teams to develop great products.