Gain insights into applying Agile methods in large projects and teams. Explore challenges, best practices, and strategies to secure organizational buy-in for successful implementation.

Agile methods allow us to handle rapidly changing requirements, typical in most software projects. These methods are conventionally used for small teams and software projects. However, in this course, you will learn how to effectively apply Agile methods to large software projects and large teams.

You’ll start with a recap of the Agile Manifesto, followed by a description of the common challenges associated with Agile methods in the context of large software projects. You’ll learn how Agile approaches have been applied to build responsibility. Next, you’ll learn about approaches to apply Agile methods in the processes. You will then learn best practices for applying Agile methods such as software testing, and software architecture. 

This course provides insights into successful and unsuccessful approaches to introducing agility to teams, processes, and technology aspects of large projects. It also teaches strategies to secure organizational buy-in for agility in the context of large projects and teams.

Applying Agile Methods to Large Teams and Projects

## The Agile Alliance
The Agile Alliance is a federation of representatives of what was formerly known as **lightweight processes.** The best-known members of the Agile Alliance are probably:
* Adaptive Software Development
* Crystal Methodologies
* Extreme Programming
* Feature-Driven Development
* Scrum

Despite the fact that a competitive relationship exists among all representatives of agile processes, they were able to come up with a conclusion in the manifesto. According to James Highsmith, there are no plans to develop this conclusion toward a unified agile process. 
## The manifesto
Below are the main points of interest in the manifesto:
* **Individuals and interactions over processes and tools:** In the center of all agile processes is the individual.
 This means an agile process will never be introduced or established over the heads of the project members. The project members are the ones who determine and fine-tune the agile process.



# The Agile Alliance
The Agile Alliance is a federation of representatives of what was formerly known as **lightweight processes.** The best-known members of the Agile Alliance are probably:
* Adaptive Software Development
* Crystal Methodologies
* Extreme Programming
* Feature-Driven Development
* Scrum

Despite the fact that a competitive relationship exists among all representatives of agile processes, they were able to come up with a conclusion in the manifesto. According to James Highsmith, there are no plans to develop this conclusion toward a unified agile process. 
# The manifesto
Below are the main points of interest in the manifesto:
* **Individuals and interactions over processes and tools:** In the center of all agile processes is the individual.
 This means an agile process will never be introduced or established over the heads of the project members. The project members are the ones who determine and fine-tune the agile process.



Get an overview of the "Agile Manifesto" and some agile methods that talk about large projects.

Introduction to the Course

Agility and Largeness

Dealing with Large Teams

Dealing with the Process

Dealing with the Technology

Dealing with the Company

Putting It All Together: A Project Report (Case Study)

Final Thoughts

The Agile Manifesto

The Agile Alliance

The manifesto