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

1. Ambler, Scott, _Agile Modeling_. New York: John Wiley & Sons, 2002.
2. Banmen, John; Jane Gerber, Maria Gomori, and Virginia Satir, _The Satir Model, Family Therapy and Beyond_. Palo Alto, CA: Science and Behavior Books, 1991.
3. Beck, Kent, _Extreme Programming Explained: Embrace Change_. Reading, Mass.: Addison Wesley, 2000.
4. Beck, Kent and Martin Fowler, _Planning Extreme Programming_. Reading, Mass.: Addison Wesley, 2001.
5. Beckhard, Richard and Wendy Pritchard,
_Changing the Essence: The Art of Creating and Leading Fundamental Change in Organizations_. New York: John Wiley & Sons, 1992.
6. Brooks, Frederick P., Jr., _The Mythical Man-Month, 20th anniversary edition_. Reading, Mass.: Addison Wesley, 1995.
7. Carmel, Erran and Ritu Agarwal, _Tactical Approaches for Alleviating Distance in Global Software Development._ IEEE Software, March/April 2001.
8. Cockburn, Alistair, _Surviving Object-Oriented Projects._ Reading, Mass.: Addison Wesley, 2001.
9. Cockburn, Alistair, _Agile Software Development._ Reading, Mass.: Addison Wesley, 2002.
10. Cohn, Mike and Doris Ford, _Introducing an Agile
Process into an Organization,_ 2003 
11. Conway, Melvin E. _How do committees invent?_ Data-mation, 14, 4, pp. 28-31, April, 1968.
12. Cooper, Alan, _The Inmates Are Running the Asylum: Why High Tech Products Drive Us Crazy and How To Restore The Sanity._ Indianapolis, Indiana: Sams 1999.
13. De Geus, Arie, _The Living Company: Habits for Survival in a Turbulent Business Economy._ Boston: Harvard Business School Press, 1997.
14. DeGrace, Peter and Leslie Hulet Stahl, _Wicked Problems, Righteous Solutions: A Catalogue of Modern Software Engineering Paradigms_. Eaglewood Cliffs, New Jersey: Prentice Hall, 1990.
15. DeMarco, Tom, _The Deadline: A Novel about Project Management._ New York: Dorset House, 1997.
16. DeMarco, Tom, Slack. _Getting past Burnout, Busywork, and the Myth of Total Efficiency_. New York: Broadway Books, 2001.
17. DeMarco, Tom and Timothy Lister, _Peopleware: Productive Projects and Teams._ New York: Dorset House, 1987.
18. Demmer, Christine, _Guetesiegel fuer fleissiges Aufschreiben_ (Mark of quality for busy documenting). Sueddeutsche Zeitung, Bildung und Beruf, Nr. 40, 16./17. p. V1/15, February, 2002.
19. Fowler, Martin, _Refactoring: Improving the Design of Existing Code._ Reading, Mass.: Addison Wesley, 1999.
20. Glazer, Hillel, _Dispelling the Process Myth: Having a Process Does Not Mean Sacrificing Agility or Creativity_, Crosstalk November 2001.
21. Highsmith III, James A., _Adaptive Software Development: A Collaborative Approach to Managing Complex Systems._ New York: Dorset House, 2000.
22. Hunt, Andrew and David Thomas, _The Pragmatic Programmer: From Journeyman to Master._ Reading, Mass.: Addison-Wesley, 2000.
23. Jeffries, Ron, “Extreme Programming and the Capability Maturity Model,” _XP Magazine_, 2000
24. Kerth, Norman L., _Project Retrospectives_. New York: Dorset House, 2000.
25. Larman, Craig, _Applying UML and Patterns._ Eaglewood Cliffs, New Jersey: Prentice Hall, 1998.
26. Leuf, Bo and Ward Cunningham, _The Wiki Way: Collaboration and Sharing on the Internet._ Reading, Mass.: Addison-Wesley, 2001.
27. McBreen, Pete, _Software Craftsmanship: The New Imperative._ Reading, Mass.: Addison Wesley, 2002.
28. McConnell, Steve, _Best Practices. Daily Build and Smoke Test._ IEEE Software, Vol. 13, No. 4, July, 1996.
29. Paulk, Mark C., _Extreme Programming from a CMM Perspective._ Proceedings of the XP Universe 2001, Chicago, 2001.
30. Rechtin, Eberhardt and Mark Maier, _The Art of Systems Architecting_. London: CRC Press, 2000.
31. Senge, Peter _The Fifth Discipline: The Art & Practice of The Learning Organization._ New York: Currency Doubleday, 1998.
32. Sollmann, Ulrich and Roderich Heinze, _Visionsmanagement. Erfolg als vorausgedachtes Ergebnis_ (Vision Management. Success as the predefined result.). Zürich: Orell Füssli, 1994.
33. van der Helm , Peer and Dieter Stopper,_ Von Makrelen und Menschen_ (About Mackerels and Human Beings.). DAV Panorama, Nr. 1, Issue 54, 2002.
34. Yourdon, Edward, Death March: _The Complete Software Developer’s Guide to Surviving “Mission Impossible” Projects._ Eaglewood Cliffs, New Jersey: Prentice Hall, 2nd edition, 1999.


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

Bibliography

Book references