MENU
When introducing agile processes to a company, a quality assurance (QA) manager resists and believes that the switch to agile will remove quality controls and documents.
How should the agile practitioner address this concern?
The correct answer is A -- Educate the QA manager that in agile, quality is integrated from the beginning to the end of the project. Agile emphasizes ''built-in'' quality through test-first approaches, continuous integration, and Definition of Done. Addressing resistance through education helps clarify that quality is a core part of Agile---not an afterthought.
From the PMI Agile Practice Guide:
''Agile does not remove quality controls; rather, it integrates them throughout the development process. Quality is everyone's responsibility and is embedded through practices such as TDD, automated testing, and continuous feedback.''
(PMI Agile Practice Guide, Section 3.5 -- Quality and Agile)
Mike Griffiths adds:
''In Agile, quality is not sacrificed. It is a fundamental principle. Teams ensure quality by defining acceptance criteria, using continuous integration, and practicing test-first development.''
(Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 -- Value-Driven Delivery)
Incorrect options:
B may be helpful tactically, but doesn't address the underlying concern.
C misrepresents technical debt.
D places too much QA responsibility on the product owner.
Answe r: A