" Agile Development, in the end need not QA? "
The answer is ... Of course it is needed.
Just expect QA from the traditional focus on "process quality", instead of working with the team together to focus on "product quality."
so-called Focus " Process Quality " refers to: Focus only on the team "No" engage in continuous integration, automated testing, stand-up meetings, select presentations, review meetings, and collect metrics data ... and so on.
so-called with team, focus " Product quality " : with the team, from the product rather than from the process perspective, focus only on the team
: team Product Owner Because of personal considerations, and lack of courage to go to " slash " qa It stands in product quality " angle, with Product Owner work together to do " should be " The mission is to improve efficiency and quality due to reasonable workload. Due to the reasonable workload, the team makes the delivery of the version more consistent with the customer's expectations and benefits.
" The value of anyone in business, is because he can be with the product together; QA is no exception. "
" product quality is the quality of people. Good product quality, always only from the right people, always only from the right people, have the courage, enthusiasm, ability to do what should be done. "
" It's a pity that ... good process quality is not necessarily a good product quality, because, processes and products (especially software) is not absolutely inevitable causal relationship. "
Agile development, do you need QA?