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
It is absolutely impossible to establish a project as an island in a large company. The organizational structure of the company will always have an influence on the agile project. Of course, we'll have the fewest problems if our company already has a project-oriented structure in place.

More often, however, we will encounter a departmental structure that can interfere with the agile development. Integrate the cross-section departments early on, so they are aware of the changed approach and their required role. By communicating openly and honestly with these departments, we'll gain their support. This approach is also a marketing strategy. As soon as these other departments recognize the benefits of our process, they will provide better support, thus helping us improve the process further.

Establish a learning environment to compensate for missing skills and to make the job of the developers more challenging.

If help is needed from outside, keep in mind that there is no substitute for direct communication, so always try to have the external teams work on-site—if not permanently, at least occasionally.

An agile project means breaking with old habits on different levels. Only flexibility in the whole company allows the successful switch to agile development.


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