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

#
## Summary
The "Agile Manifesto" formulates a value system for software development. Even though it provides fundamental meaning, it is not very explicit and leaves room for interpretation. This freedom has the risk of processes being sold as being agile, when they are really heavyweight. The resulting change in culture and the ability to adapt as necessary are some of the clear signs of an agile process.

Switching to agile development may arouse some fears, which in turn could foster mistrust in the success of the approach. Although some artifacts and tools promise putative security for controlling and steering a project, this security is just that—putative. It is much more important to establish an environment of trust, which will allow open and honest communication even if the project is in a bad shape. Trust can only be built by transparency, consistency and integrity.


In order to ensure the provision of a system with the highest business value possible, developers must work very closely with their customers during project development. This involvement not only helps the developers to better understand the requirements, it also helps the customer determine what kind of system would serve his business needs best.

Let’s review what we've learned so far.

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

Chapter Wrap Up

Summary