Agile developers are "test infected", we do test-first development and treat acceptance tests as full-fledged requirements artifacts and work with our stakeholders to acceptance test throughout the dev lifecycle. The end result is significantly higher quality software, achieved with very little input from the testing community. So what is the role of testers and QA people on agile projects?
Scott Ambler is Practice Leader Agile Development within the IBM Methods group in Ontario, Canada. He has worked in the IT industry since the mid 1980s, with object technology since the early 1990s, and is a recognized leader in the Agile software community. He is a Fellow of the International Association of Software Architects, and an Eclipse Process Framework (EPF) committer. www.ambysoft.com
The Toronto Association of Systems and Software Quality (TASSQ) is an organization for Quality Assurance professionals. Their monthly meetings share quality practices and provide an opportunity for networking. The presentations include a wide variety of topics, including testing, project management, risk management, measurement of client satisfaction, other metrics related topics, Year 2000 topics, process improvement, implementing quality practices, etc.
i can rename column :P
I remember this talk...
As a person who's been involved in agile projects for several years now, Scott's comments were right on. A friend of mine (who's also been involved in agile projects for years) and I would often have conversations about exactly this topic. Often the discussion would turn to our disappointment at the contributions of the testers to the project. Occasionally, we would work with a tester who "got it" and things would be wonderful, but this was the exception rather than the rule.
Personally, I think "we" (developers) bear part of the blame here. We've treated testers and testing as an afterthought, as second class citizens for so long that perhaps they shouldn't be blamed for sticking to their comfort zones. After all, in a lot of corporate or non-agile shops, being an aggressive, dynamic, flexible tester isn't always a career enhancing thing.
I'm beginning to believe that the only difference between a tester and a developer in an agile team is their mind-set. Developers always tend to be optimists, even on agile teams. Testers are our pessimists. Beyond that, in terms of skills, they really should be identical.
IBM's view on "traceability"
"Provides detailed traceability views that display parent/child relationships and show requirements that may be affected by upstream or downstream change"
Yet, Mr. Ambler of the IBM Methods groups gives thumbs down to traceability.
It was really confusing, and mischievously fun, to debate with "IBM Rational tools" believers against Scott's AgileModeling.com concepts. I guess IBM isn't in the business of selling paper and pens and whiteboards and markers.
I hope Ambler wins, with AUP...