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
We should never underestimate the value of face-to-face communication, especially with large and distributed teams. We should do everything we can to provide as many opportunities as possible for direct communication. Direct communication, together with transparency, helps to build trust both inside the team and between the team and the outside world. If team members trust one another, they will not fear taking up responsibility.

A tool like a wiki web will help us build trust by empowering everybody through shared ownership. In doing so, such tools change the flow of communication from control-driven to collaborative-driven.

When building subteams, we should ensure that the skills within each subteam are mixed. Furthermore, the technical service teams should serve the domain teams. If desired, they can also be established as virtual teams.

Last, but not least, allow the team to have fun. This not only helps teams jell but more importantly, also makes the work environment a pleasant one, which will make everybody want to work and succeed with the team. Considering the values of the gift economy as open source does, it will also help to make work much more enjoyable.

Let’s review what we have learned so far.


Chapter Wrap Up

Let’s review what we have 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