10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
Presentation
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Recorded at:
The Role of Testing and QA in Agile Software Development
Presented by
Scott Ambler
on
May 03, 2007
Length 01:21:13
How would you like to view the presentation?
In case you are having issues watching this video, please follow these simple steps to help us investigate the issue:
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
Summary
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?
Bio
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
About the conference
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.
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?
Bio
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
About the conference
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.
RelatedVendorContent
Transforming Software Delivery: An IBM Rational Case Study
Five Key Practices to Agile ALM
Agility at scale, become as agile as you can be
Related Sponsor
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
- This article is part of a featured topic series on Agile
- See more Agile content at: http://www.infoq.com/agile
- Other recent content items in this topic
i can rename column :P
by
Rave Man
Posted
I remember this talk...
by
Bruce Rennie
Posted
IBM's view on "traceability"
by
Rajesh Duggal
Posted
-
i can rename column just like that, you just have to rename it in hibernate mapping xml file. people forget that we all are using ORM.
-
and found the reaction in the audience to be pretty amusing. Heck, it was even brought up at later meetings. Way to make a lasting impression, Scott!
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. -
I wonder when IBM will decide if traceability is a good thing to track and measure or not.
Rational RequisitePro
www.ibm.com/software/awdtools/reqpro/
"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...
www.ambysoft.com/unifiedprocess/agileUP.html
Go,go,go! :)
Raj.
3 comments
Watch Thread Reply