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

It doesn't matter if a team is small or large—its members should all follow the same coding and design standards. This standard is typically accompanied by the programming model, which is a general guideline on how to use the architecture, any specific patterns, and the like.
# Why do standards fail?
If a standard is not met, we have to find and eliminate the reasons for this. Possible reasons include:
* The standard is overwhelming. It is either so large in scope that nobody will ever read it, or it is so precise that it does not leave any space for the developer’s creativity.
* The standard was not defined by the developers and, in turn, has never been accepted by them. Like the process, a standard has to serve the developers, not act as a guardian over them. Therefore, the standard has to be developed by the developers and adapted to their needs.

# Engage the developers during standard adaptation 
Standards and programming models tend to have high acceptability with the team if these were developed by the developers themselves and are very short and simple. We cannot expect people to read 100 pages of documentation and remember and internalize the contents at the same time. It is easiest to start with an industry standard and adapt it accordingly if necessary. Therefore, if the standard is not overwhelming but is still not accepted, we have to ask the developers to change it for the better.



Learn about important considerations while developing standards in an agile process.

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

Techniques and Good Practices: Standards