Loading ...
Sorry, an error occurred while loading the content.
 

Re: [scrumdevelopment] Re: Integrating SQA into the scrum team

Expand Messages
  • mike.dwyer1@comcast.net
    Question Why aren t your team members better dividing up the work? Since the team is not getting credit for work done they could advance their stories by
    Message 1 of 8 , Jun 27, 2008
      Question
      Why aren't your team members better dividing up the work? Since the team is not getting credit for work done they could advance their stories by doing some of the SQA taskings. They would also improve their overall work level
      Sent via BlackBerry by AT&T

      -----Original Message-----
      From: "elisabethshendrickson" <esh@...>

      Date: Fri, 27 Jun 2008 14:08:51
      To:scrumdevelopment@yahoogroups.com
      Subject: [scrumdevelopment] Re: Integrating SQA into the scrum team


      Ed wrote: "The team consists of 3 developers and one SQA. I am
      consistently incurring SQA debt every sprint with very few items
      actually achieving a status of 'done'. As you can imagine, I have most
      items coded, unit tested and in the test environment, but very few
      items actually having completed or passed testing."

      Congratulations! My guess is that the SQA debt problem already
      existed and Scrum just made it visible. When problems like SQA debt
      become visible, it means you're doing it right. Now the challenge is
      how to respond effectively.

      Bob Schatz replied: "Since your definition of "Done" now includes the
      functional/system testing, that means the WHOLE team is responsible
      for it. Testing is not the sole job of the SQA person."

      I totally agree with Bob and recommend strongly that the whole team
      discuss what it would take to get all the testing tasks done in the
      sprint.

      In particular I would hope that the team ends up discussing how to
      automate the regression tests to reduce the burden of manual
      regression. (Ed didn't say that manual regression testing is the
      cause of the bottleneck, but it usually is.)

      Scrum doesn't specify any practices, but my experience has been that
      it's extremely difficult to become agile without the fast feedback
      that automated regression tests provide.

      (This is *not* to say that all testing should be automated. Manual
      exploratory testing is vital as well.)

      Elisabeth
      ---------
      Elisabeth Hendrickson
      http://www.testobse <http://www.testobsessed.com> ssed.com
      http://www.qualityt <http://www.qualitytree.com> ree.com
    Your message has been successfully submitted and would be delivered to recipients shortly.