Comments on: Some Thoughts on Agile QA http://www.bigvisible.com/mdwyer/thoughts-on-agile-qa/ Fri, 03 Sep 2010 00:28:08 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Mike Dwyer http://www.bigvisible.com/mdwyer/thoughts-on-agile-qa/comment-page-1/#comment-18912 Mike Dwyer Fri, 31 Jul 2009 17:43:41 +0000 http://www.bigvisible.com/?p=177#comment-18912 David Thank you for comments as it makes me realize how illusive the definition of Done can be. In the approach I have laid out "done" is specified, as part of the story and task being committed to. If there is a change to the story then it is treated as a new version of the story and is evaluated as such. if the change is a clarification of an existing test of doness then that should be adapted to. If the change is the addition of more functionality the it should be written up as a new story, added to the backlog and the product owner should determine the urgency the enhancement's value is to the customer. In most cases it is faster and cheaper to build the original story and then enhance it with a latter story. As to your second comment, You betcha! The era of Agile products being standalone, independent products is still true, but is becoming less the center of demand. The areas of Agile QA and testing I am working on is finding ways to move these two monsters closer to the iteration. When we have more to say then we will bring it out, but it is coming whether we like it or not. This is because it is so valuable. David
Thank you for comments as it makes me realize how illusive the definition of Done can be.
In the approach I have laid out “done” is specified, as part of the story and task being committed to.
If there is a change to the story then it is treated as a new version of the story and is evaluated as such.
if the change is a clarification of an existing test of doness then that should be adapted to. If the change is the addition of more functionality the it should be written up as a new story, added to the backlog and the product owner should determine the urgency the enhancement’s value is to the customer. In most cases it is faster and cheaper to build the original story and then enhance it with a latter story.

As to your second comment, You betcha! The era of Agile products being standalone, independent products is still true, but is becoming less the center of demand.
The areas of Agile QA and testing I am working on is finding ways to move these two monsters closer to the iteration. When we have more to say then we will bring it out, but it is coming whether we like it or not. This is because it is so valuable.

]]> By: David http://www.bigvisible.com/mdwyer/thoughts-on-agile-qa/comment-page-1/#comment-18910 David Fri, 31 Jul 2009 15:58:40 +0000 http://www.bigvisible.com/?p=177#comment-18910 Asking QA to begin "judging the doneness of a delivery" without updated specifications just seems odd to me. I'm not sure how I feel about Agile. Items may move quickly through dev initially but I wonder what happens when those items need improvement/updating. Also, it seems to me that QA is moving more towards system level regression and performance testing. What are your thoughts on that? Asking QA to begin “judging the doneness of a delivery” without updated specifications just seems odd to me. I’m not sure how I feel about Agile. Items may move quickly through dev initially but I wonder what happens when those items need improvement/updating. Also, it seems to me that QA is moving more towards system level regression and performance testing. What are your thoughts on that?

]]> By: Mike Dwyer http://www.bigvisible.com/mdwyer/thoughts-on-agile-qa/comment-page-1/#comment-17452 Mike Dwyer Wed, 10 Jun 2009 14:49:09 +0000 http://www.bigvisible.com/?p=177#comment-17452 Thanks for your input. I am not sure what you are asking. The cause for the scarcity of test professionals is a multi-faceted statement, beginning with the comparative scarcity of degree granting programs, the limited professional path available, and the historic treatment of testers as second class members of the software industry. During the past few years some of these issues have been recognized, none - IMO - have been resolved, and little has been done to recognize the strategic value of QA and test expertise in the planning, definition, and design process. Does that help to outline the reasons for the scarcity? Thanks for your input. I am not sure what you are asking. The cause for the scarcity of test professionals is a multi-faceted statement, beginning with the comparative scarcity of degree granting programs, the limited professional path available, and the historic treatment of testers as second class members of the software industry. During the past few years some of these issues have been recognized, none – IMO – have been resolved, and little has been done to recognize the strategic value of QA and test expertise in the planning, definition, and design process.
Does that help to outline the reasons for the scarcity?

]]> By: James K http://www.bigvisible.com/mdwyer/thoughts-on-agile-qa/comment-page-1/#comment-17360 James K Tue, 02 Jun 2009 16:46:09 +0000 http://www.bigvisible.com/?p=177#comment-17360 It all sounded okay until you said "scarce test professionals". Why should they be scarce? It all sounded okay until you said “scarce test professionals”. Why should they be scarce?

]]>