The beginner's guide to Agile methodologies

Sarah Laoyan contributor headshotSarah Laoyan17 september 20216 min. leestijd
facebooktwitterlinkedin
Agile methodologies header image

Summary

With so many different Agile methodologies to choose from, discovering which one is right for your team can be a challenge. In this article, get a high-level overview of Agile project management, plus a few common frameworks to help you get started.

When it comes to project management, there's a wide array of frameworks you can use to manage your project. Traditionally, projects follow a linear manner where each task precedes the next. This is commonly known as the waterfall model. 

This changed in 2001 as software development became much more common. The linear waterfall method isn’t as effective for software teams, because things are constantly shifting and customer needs are rapidly changing. This is how the Agile methodology was created.

Agile project management isn’t just useful for software project management—all types of teams have been successful with this dynamic methodology. If you’re looking to get started with Agile, you’ve come to the right place.

What is the Agile methodology?

Agile methodology is a project management framework that breaks projects down into several dynamic phases, commonly known as sprints. The Agile framework is an iterative methodology. After every sprint, teams reflect and look back to see if there was anything that could be improved so they can adjust their strategy for the next sprint.

The Agile Manifesto

The Agile Manifesto is a document that focuses on four values and 12 principles for Agile software development. It was published in February 2001 by 17 software developers who needed an alternative to the more linear, process-oriented product development process.

The 4 Values of Agile

As outlined in the Agile Manifesto, there are four main values of Agile project management:

Individuals over processes and tools

Agile teams value team collaboration and working together over working independently and doing things "by the book."

Working software over comprehensive documentation

The software Agile teams develop should work. Additional work, like documentation, is not as important as developing good software.

Customer collaboration over contract negotiation

Customers are extremely important within the Agile methodology. Agile teams allow customers to guide where the software should go. Therefore, customer collaboration is more important than the finer details of contract negotiation.

Responding to change over following a plan

One of the major benefits of Agile project management is it allows teams to be flexible. This framework allows for teams to quickly shift strategies without derailing an entire project.

The 12 Agile Principles

The four values of Agile are the pillars of Agile methodology. From those values, the team developed 12 principles. These principles can be easily adapted to fit the needs of your team. If the values of Agile are the weight-bearing pillars of a house, then 12 principles are the rooms you can build within that house. 

The 12 principles used in Agile methodology are:

  1. Satisfy customers through early and continuous delivery. When customers receive new updates regularly, they're more likely to see the changes they want within the product. This leads to happier, more satisfied customers, and more recurring revenue.

  2. Welcome changing requirements, even late in the project. The Agile framework is all about adaptability. In iterative processes like Agile, being inflexible causes more harm than good. 

  3. Deliver value frequently. Similar to principle number one, delivering value to your customers frequently makes it less likely for them to churn. 

  4. Break the silos of your projects. Collaboration is key in the Agile framework. The goal is for people to break out of their own individual projects and collaborate together more frequently

  5. Build projects around motivated individuals. Agile works best when teams are committed and actively working to achieve a goal. 

  6. The most effective way to communicate is face-to-face. While how we communicate at work has changed dramatically since 2001, the sentiment of this statement still applies today. If you’re working on a distributed team, spend time communicating in ways that involve face-to-face communication like Zoom calls. 

  7. Working software is the primary measure of progress. The most important thing that teams should strive for with the Agile framework is the product. The goal here is to prioritize functional software over everything else.

  8. Maintain a sustainable working pace. Some aspects of Agile can be fast-paced, but it shouldn't be so fast that team members burn out. The goal is to maintain sustainability throughout the project.

  9. Continuous excellence enhances agility. If the team develops excellent code in one sprint, they can continue to build off of it the next. Continually creating great work allows teams to move faster in the future. 

  10. Simplicity is essential. Sometimes the simplest solution is the best solution. Agile aims to not overcomplicate things and to find simple answers to complex problems. 

  11. Self-organizing teams generate the most value. Similar to principle number five, teams that are proactive become valuable assets to the company as they strive to deliver value.

  12. Regularly reflect and adjust your way of work to boost effectiveness. Retrospective meetings are a common Agile practice. It's a dedicated time for teams to look back and reflect on their performance and adapt their behaviors for the future.

Free Agile retrospective template

Why use Agile project management?

You commonly find Agile project management used in application development or other types of software development. This is because software is constantly changing, and the needs of the product have to change with it. Because of this, linear project management methods like the waterfall model are less effective. Here are a few other reasons why teams use Agile:

Agile methods are adaptable

There's a reason why they call it the Agile methodology. One of the main benefits of using Agile processes in software development is the ability to shift strategies quickly, without disrupting the flow of a project. 

Because phases in the traditional waterfall method flow into one another, shifting strategies is challenging and can disrupt the rest of the project roadmap. Since software development is a much more adaptable field, project managing rapid changes in the traditional sense can be challenging. This is part of the reason why Agile project management is favored in software development. 

Agile fosters teamwork

One of the Agile principles states that the most effective way to communicate with your team is face-to-face. Combine this with the principle that encourages teams to break project silos and you have a recipe for collaborative teamwork. 

While technology has changed since 2001, and work has been shifting to welcome more remote-friendly policies, the idea of working face-to-face still hasn't changed.

Lees: 10 eenvoudige stappen om samenwerking tussen teams te verbeteren

Agile methods focus on customer needs

One of the unique aspects of software development is that teams can focus on customer needs much more closely than other industries. With the rise of cloud-based software, teams can get feedback from their actual customers quickly. 

Since customer satisfaction is a key driver for software development, it’s easy to see why it was included in the Agile process. By collaborating with customers, Agile teams can prioritize features that focus on customer needs. When those needs change, teams can take an Agile approach and shift to a different project. 

Common Agile methodologies

The Agile framework is an umbrella for several different variations. Here are a few of the most common Agile methodologies. 

Kanban

Kanban is a visual approach to Agile. Teams use online Kanban board tools to represent where certain tasks are in the development process. Tasks are represented by cards on a board, and stages are represented in columns. As team members work on tasks, cards are moved from the backlog column to the column that represents the stage the task is in.

This method is a good way for teams to identify roadblocks and to visualize how much work is getting done. 

Lees: een beginnersgids voor kanbanborden

Scrum

The Scrum methodology is a common Agile methodology for small teams. The team is led by a Scrum master whose main job is to clear all obstacles for others executing the day-to-day work. Work is completed in sprints and Scrum teams meet daily to discuss active tasks, roadblocks, and anything else that may affect the development team. 

Read: What is Scrum? What it is and why it works so well

Adaptive Project Framework (APF)

The Adaptive Project Framework, also known as Adaptive Project Management (APM) grew from the idea that unknown factors can show up at any time during a project. This technique is mainly used for IT projects where more traditional project management techniques don’t apply.

This framework is based on the idea that project resources can change at any time. For example, budgets can change, timelines can shift, or team members working on the project may transition to different teams. APF focuses on the resources that a project has, as opposed to the resources a project needs. 

Extreme Project Management (XPM)

This type of project management is often used for very complex projects with a high level of uncertainty. This approach involves constantly adapting processes until they lead to the desired result. This type of project involves many spontaneous changes and it’s normal for teams to switch strategies from one week to the next. 

XPM requires a lot of flexibility. This is one of the reasons why each sprint is short—only a few weeks maximum. This methodology allows for frequent changes, trial-and-error approaches to problems, and many iterations of self-correction.

Read: Understanding the iterative process, with examples

Adaptive Software Development (ASD)

This Agile methodology enables teams to quickly adapt to changing requirements. The main focus of this process is continuous adaptation. The phases of this project type—speculate, collaborate, and learn—allow for continuous learning as the project progresses. 

It’s not uncommon for teams running ASD to be in all three phases of ASD at once. Because of its non-linear structure, it’s common for the phases to overlap. Because of the fluidity of this type of management, there’s a higher likelihood that the constant repetition of the three phases helps team members identify and solve problems much quicker than standard project management methods.

Dynamic Systems Development Method (DSDM)

The Dynamic Systems Development Method is an Agile method that focuses on a full project lifecycle. Because of this, DSDM has a more rigorous structure and foundation, unlike other Agile methods. 

There are four main phases of DSDM:

Feature Driven Development (FDD)

Feature Driven Development blends different Agile best practices. While still an iterative method of project management, this model focuses more on the exact features of a software that the team is working to develop. Feature-driven development relies heavily on customer input, as the features the team prioritizes are the features that the customers need. 

This model also allows teams to update projects frequently. If there is an error, it's quick to cycle through and implement a fix as the phases of this framework are constantly moving. 

Organize Agile processes with Asana

You’ll often hear software development teams refer to Agile process—but any team can run Agile. If you’re looking for a more flexible project management framework, try Agile. 

No matter what type of Agile methodology you run, your team needs a source of truth for all of your project information. Asana can help. With Asana, teams can build Kanban boards or manage Scrum sprints in a flexible and collaborative tool. 

Try Agile software with Asana

Gerelateerde bronnen

Artikel

Waterfall vs. Agile project management: What’s the difference?