Quality is not the sole responsibility of QA. If the whole team doesn't take quality seriously, the release of new features will always be delayed or worse, buggy software gets released. I have heard many people referring to QA as just a testing entity, which possibly means QA does nothing within the agile environment other than testing. In addition, speaking of agile software development QA, some people may also think that it is just for monitoring agile software development processes, or doing testing only on the project. In Agile Quality Assurance, Anthony Baah shows clear evidence of the benefits for using agile QA in the software development concept and the Quality. QA acts as a liaison between the agile team and the business to ensure agile development policy and practices are adhered to. The agile QA provides the agile system engineering lifecycle expertise and guidance to the business people, release management and stakeholders. The team ensures that all the systems of the project go through the agile system engineering lifecycle process successfully. -PART I: Overview: Transitioning into Agile Transformation oChapter 1 Agile Software Development Approach Transformation oChapter 2 What QA Team Stands For in Agile Software Development oChapter 3 The Evolving Role of QA oChapter 4 QA and the Agile Development oChapter 5 Scaling Agile QA oChapter 6 QA - Risks And Cost Reduction in Agile Software Development -PART II: Agile Methodology: The Big Picture of Agile QA