In Agile, the whole team is responsible for this. Having any particular person officially fulfill this role dilutes that responsibility. It might seem more effective to have such a role in the short term, but it would erode agility in the long term.
So, while QA still exists under Agile as a responsibility, QA should be a shared, collaborative, continuous responsibility not a role that specific people play at specific points in time and others do not.
SteveG
On Fri, Jan 6, 2012 at 1:43 PM, karthikeyan M <gotukarthik@yahoo.com> wrote:
Personally I feel QA -> Quality Analyst -> means a person whose job role is is to analyze the flow of the project and ensure quality of the project deliverable. The deliverable could be Production Code, Unit/Integration Test Code, Functional Test Code, Any documentation like Release Notes etc... There are also other deliverables like Stories written for every iteration, and those stories should be reviewed by the QA to ensure there is no functional Gap's (sometimes BAs might miss to add an acceptance criteria). Now to emphasize Quality in all these places, the QA can chose to use any appropriate method to achieve the same. When he tests the application to ensure the production code is of good quality, he is referred to as a tester but Philosophically the job doesn't end only with that.- Karthik
__._,_.___
MARKETPLACE
.
__,_._,___
0 comments:
Post a Comment