What Is Agile? An Iterative Approach to Project Management

Agile is a popular approach to project management that emphasizes iteration and short-term development cycles. It has sometimes been called a methodology—and it does serve as the foundation for popular project management methodologies such as Scrum and Kanban—but think of it more as a guiding framework for how best to complete a project. Agile prioritizes quick delivery, nimble responsiveness, and collaboration. Often used in software development, Agile primarily focuses on collaboration and constantly improving a product or service.

Learn more about Agile, including the methodologies that use it. Afterward, strengthen your abilities in Agile with Google's Agile Project Management course—part of the larger Google Project Management Professional Certificate.

What is Agile project management?

Agile is an approach that was originally created for software development but is now widely used as a framework for popular project management methodologies in other industries. It uses short cycles, often called sprints or iterations, to develop a product or service. In and of itself, it can even be applied to a company's overall way of doing work [1]. Agile organizations tend to be responsive rather than rigid, which means they can better respond to change.

Traditional project management generally progresses linearly through the lifecycle. One stage must be completed before moving on to the next one.  The Agile process encourages continuous feedback, allowing team members to adjust to challenges as they arise.

Learn more about some of the benefits of Agile from a technical program manager at Google:

The Agile Manifesto: values and principles of the Agile mindset

In 2001, a group of software development managers created the Agile Manifesto, which emerged from perceived bottlenecks in the software development process at the time. [2] From that initial philosophy, Agile project management grew to encompass four values and twelve principles.

Four values of Agile

• Individuals and interactions over processes and tools: While tools and processes are important, the Agile Manifesto prioritizes the people behind them. Having the right people in place and empowering them to interact smoothly with each other can lead to successes that tools by themselves won’t be able to.

• Working software over comprehensive documentation: The creators of Agile believed that it was more important to get stuff done than get bogged down in the planning and documentation stages.

• Customer collaboration over contract negotiation: Instead of siloing stakeholders off from the project, Agile aims to maintain contact with them throughout the creation process.

• Responding to change over following a plan: Following a plan that no longer makes sense can be counterproductive. Adaptation is central to the Agile philosophy.

The twelve principles of Agile define early and frequent delivery, simplicity, constant feedback, the collaboration of interested parties, and individual support, among others [3].

Learn more: 9 Major Project Management Trends

5 stages of the Agile project management lifecycle

Agile project management typically involves five key phases, often referred to as the Agile lifecycle. These phases are designed to ensure continuous improvement, flexibility, and collaboration throughout the project. The type of Agile methodology used will dictate the details of each phase, but in general, the lifecycle involves [4]:

1. Preplanning: Define project vision, objective, high-level requirements, stakeholders, and project feasibility.

2. Planning: Plan the first iteration (sprint) in detail, as well as the release of subsequent iterations, creating a backlog, user stories, tasks, and iteration goals.

3. Release planning: Once the first iteration is completed or the product backlog is created, review the results to gain insights for continuous improvement via subsequent iterations.

4. Iteration planning: After each iteration completion, plan the next iteration by adding or removing features necessary for optimal product functionality.

5. Product backlog management: Reassess the project timeline after each iteration based on the product backlog and customer feedback. The cycle can continue until a satisfactory product is produced.

Agile methodologies

Agile isn't considered a methodology because it doesn't specify the tools and processes that should be used. However, it is the umbrella term for many types of management methodologies, each with its own pros and cons. Some are hybrids of multiple methodologies. Scrum is the most commonly used, with Digital.ai finding that 63 percent of Agile adopters use Scrum [5].

Popular Agile project management methodologies

Agile teams benefit from using one workflow. Some Agile teams use Scrum, while others prefer Kanban, Lean, or other methods. Some teams combine Agile with the Waterfall approach, which means they may use a traditional workflow for stakeholders, but the team uses a Scrum approach for its work. 

Agile vs. Waterfall

Waterfall is a traditional project management methodology best suited for projects with well-defined requirements and a stable environment. Tasks are planned out linearly and sequentially, and a team must complete one before moving on to the next one.

Agile is well-suited for projects with uncertain requirements or a need for rapid adaptation. The team creates a high-level roadmap of tasks but then creates detailed plans for each sprint, which can be adjusted as needed.

Learn more: Types of Project Management: Methodologies, Industries, and More

Scrum

Scrum is a framework for developing, delivering, and sustaining complex projects. Scrum, which got its name from rugby teams in training, emphasizes cross-functional teams that are self-organizing and open-minded. Ken Schwaber and Jeff Sutherland developed Scrum in the 1990s and wrote the Scrum Guide to help others use this project management framework. The theory behind Scrum is leanness and empiricism: the idea that true knowledge comes from actual, lived experience. The five values of Scrum are commitment to achieving goals, courage, focus, openness, and respect.

Scrum requires the roles of Scrum Master, product owner, and the development team. A Scrum Master is the person on the team who helps everyone understand and implement Scrum, and the person is responsible for the Scrum team’s effectiveness. The Scrum Master: 

• Coaches the team on self-management

• Helps the organization implement Scrum

• Helps team members remove impediments

• Facilitates communication with stakeholders

• Makes sure meetings are productive and positive

• Supports the product owner in efficiently maintaining the product backlog

• Helps teams focus on completing high-quality project outcomes

The product owner maintains the product backlog, a living document that contains a prioritized list of features for the product or service. It lists the value, order, description, and estimate of effort for each item. The product owner refines the backlog regularly so that the Scrum team can work effectively.

Kanban

Kanban is another framework used in Agile and DevOps software development. Kanban emphasizes transparent visual feedback, real-time communication, and maximized efficiency. Work tasks are shown on a Kanban board, which is created using project management software such as Jira. Each column on the Kanban board represents the phases or steps tasks must pass through from to-do to completion. Each task or item on a Kanban board is represented on its own card, which shows its critical information, including possible screenshots. Kanban templates allow users to customize their dashboards and have views such as a flow diagram, charts, and other reports. 

Toyota began using the Kanban method in the 1930s in its car factories, and today it can be applied to any industry. Software teams use the same principles to match the work in progress (WIP) to the team’s capacity. 

Lean

Lean is a collection of tools that help teams improve their processes. In Lean, the goal is to cut out waste and inefficiency. According to the Project Management Institute, the difference between Lean and Agile is that Lean has more structure: “Lean’s focus on continuous process improvement, based on an analytical systems and process analysis of performance adds significant value to the generally more informal, single project focused intuitive approach of Agile” [2].

Additional Agile methodologies include:

• Crystal

• Extreme Programming (XP)

• Feature-Driven Development (FDD)

• Domain-Driven Design (DDD)

• Dynamic Systems Development Method (DSDM)

• ScrumBan

• Agile-Waterfall/Hybrid Agile

• Scrum XP Hybrid

Who is part of an Agile project management team?

The team's roles depend on the methodology used. The project or program manager is a key figure on an Agile project management team. Scrum roles include Scrum Master, product owner (or product manager), and development team, for example. 

The Agile method emphasizes face-to-face communication, so many teams work in one location, though some organizations have a remote workplace with team members in various locations. Agile teams should contain motivated individuals with the resources needed to fulfill their roles. The roles within the team depend on which Agile methodology an organization uses.

Read more: What Is a Development Team?

Scaling Agile for large projects 

Agile scaling methods are used to implement Agile practices across multiple teams, or entire organizations. There are several scaling methods, including the following:

• Scaled Agile Framework (SAFe)

• Scrum of Scrums

• Disciplined Agile Delivery (DAD)

• Large Scale Scrum (LSS or LeSS)

• Enterprise Scrum

• Lean Management

• Agile Portfolio Management (APM)

• Nexus

What type of projects is Agile useful for?

Agile's focus on adaptability, iteration, continuous delivery, and short time frames makes it a better approach for ongoing projects and projects where certain details aren’t known from the outset. That means if a project doesn’t have clear constraints, timelines, or available resources, it’s a good candidate for an Agile approach.

For example, designing and launching new products might push project teams against several unforeseen challenges. Having an Agile approach can mean projects already have the methodology to test products as often as needed, iterate quickly, and communicate changes with project stakeholders.

On the other hand, projects with clearly demarcated constraints (like a strict budget or timeline) or projects where teams are expected to work independently of stakeholders may be better suited for traditional approaches, like Waterfall.

Industries that use Agile methods

Since it originated from the needs of software development, Agile has grown in popularity and expanded to other industries and areas as well. These include finance, IT, business, fashion, biotechnology, and even construction—among many others.

Benefits and challenges of Agile

Although Agile has gained in popularity and has a host of advantages, there are also unique challenges to consider. It may not be ideal for every project. Below are some of the benefits and drawbacks Agile users have faced, according to Digital.ai’s 2024 State of Agile Survey [4].

Choosing the right Agile methodology for your project

Here are some key factors to consider when selecting the most suitable Agile methodology for your project:

Project characteristics

• Project size and complexity:

  • Small to medium-sized projects: Scrum can be a good fit, providing a structured approach to iterative development.

  • Large and complex projects: Consider scaling frameworks like SAFe or LeSS to manage multiple teams and dependencies.

• Level of uncertainty:

  • High uncertainty: Kanban can be effective in handling dynamic environments and prioritizing tasks based on their value.

  • Moderate uncertainty: Scrum can provide a balance between structure and flexibility.

• Regulatory compliance:

  • Strict compliance: A more structured approach like Scrum or a hybrid model can help ensure adherence to regulations.

Team dynamics and culture

• Team experience:

  • Experienced teams: Consider a more flexible approach like Kanban or a hybrid model.

  • Less experienced teams: Scrum can provide a structured framework and clear roles.

• Team culture:

  • Collaborative culture: Scrum can foster teamwork and shared ownership.

  • Individual contributors: Kanban can empower individuals to self-organize and prioritize tasks.

Desired outcomes

• Rapid delivery: Scrum and Kanban can accelerate time-to-market by focusing on iterative development and continuous delivery.

• High quality: Extreme Programming (XP) emphasizes practices like test-driven development and pair programming to ensure quality.

• Customer satisfaction: Agile methodologies prioritize customer involvement and feedback to deliver products that meet user needs.

Agile certifications

There are a number of popular Agile certifications to consider if you're interested in obtaining professional credentials that confirm your distinct abilities and knowledge.

Common Agile certifications include:

• PMI-Agile Certified Practitioner (PMI-ACP)

• ICAgile Certified Professional (ICP)

• AgilePM Foundation - APMG

You can also consider a certification in a specific methodology, such as Scrum. These include:

• Certified ScrumMaster (CSM)

• Professional Scrum Master (PSM)

• Certified Scrum Product Owner (CSPO)

Read more: 7 In-Demand Scrum Master Certifications

Subscribe to our weekly newsletter Career Chat. It's a low-commitment way to stay current with industry trends and skills you can use to guide your career path.

Build or strengthen Agile skills on Coursera

Completing online learning programs can be an excellent way to build your knowledge of Agile and strengthen your ability to work with this popular framework. Consider some of Coursera's top-rated Professional Certificates and Specializations to get started:

To build a strong foundation in project management, consider the Google Project Management Professional Certificate. This program covers project execution, stakeholder management, and strategic communication, as well as including a course on Agile Project Management.

When you're ready to advance your career in Agile, take the University of Virginia's Agile Development Specialization. This course takes about a month to complete and covers how to lead product development teams using the Agile approach.