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

Although Quality Assurance (QA) and Quality Control (QC) are often organized in one department, they are different things, as defined by #key# Hillel Glazer : Author of Software Engineering Institute’s white paper "CMMI or Agile: Why Not Both!?" and an expert in blending Lean, Agile, and modern development techniques with CMMI and ISO. #key#:
> QA is not quality control (QC). [...] To put it simply, QC is testing. [...] In a nutshell, QA is process-oriented and QC is product oriented. [...] QA makes sure you are doing the right things, the right way.



Learn about the notions of quality, quality assurance, and quality control 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

Quality Assurance and Quality Control