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

Re: [scrumdevelopment] Re: Testers/QA not needed in scrum teams ?

Expand Messages
  • Mythili Somasundaram
    Hi, Why do we have 2 weeks or 4 weeks Sprint duration. Is it not a rule to have 3 weeks duration? When we will begin the Sprint if a Sprint is cancelled? If we
    Message 1 of 22 , Jul 18 9:59 AM
    • 0 Attachment
      Hi,

      Why do we have 2 weeks or 4 weeks Sprint duration. Is it not a rule to have 3 weeks duration?
      When we will begin the Sprint if a Sprint is cancelled? If we cancel Sprint 2, do we begin as Sprint 2 or Sprint 3?

      Thanks,
      Mythili


      From: Baiju <baijuglad@...>
      To: scrumdevelopment@yahoogroups.com
      Sent: Wednesday, 18 July 2012 8:20 AM
      Subject: [scrumdevelopment] Re: Testers/QA not needed in scrum teams ?

       
      Thanks mj. As you mentioned "definition of done" clearly call out "testing" in scrum guide page 15 (http://www.scrum.org/storage/scrumguides/Scrum%20Guide%20-%202011.pdf)"Each Increment is additive to all prior Increments and thoroughly tested, ensuring that all Increments work together."

      What I believe is that we still need good agile testers in scrum teams even if coders do self testing. Good agile tester need to play the quality enabler role by building tools and frameworks for the team. By wearing the domain expert and customer hat and ensuring complex multi module complex integrations work well.

      Baiju

      Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway

      --- In scrumdevelopment@yahoogroups.com, "mj4scrum@..." <mj4scrum@...> wrote:
      >
      > Two key concepts in Scrum are *definition of "done"*, and *team self organization*. It turns out these are interdependent. You won't be effective at one without clarity about the other.
      >
      > Doing Scrum effectively places a *greater* emphasis on testing than what's happening at most orgs I've seen that have a specialized QA department.
      >
      > People who have doubts about the effectiveness of pushing quality upstream should book a tour of the Toyota plant in Nagoya and see how little final testing is required when testing was incorporated throughout. Any layman can do this, so James Whittaker really has no excuse for embarrassing himself with such ignorance.
      >
      > --mj
      >
      > Sent from a phone that often corrects words I tapped to words I may not have meant.
      >
      > On Jul 17, 2012, at 8:46 AM, "Baiju" <baijuglad@...> wrote:
      >
      > > I have heard that some of the internet companies have moved to a model where there is no specialist tester/qa in the scrum team. What are your thoughts on this? Are we going back to the early days of industry without much testing?
      > > Taking all possible preventive measures to design and develop good quality code first time is good. Developers need to ensure that they own the quality of the code. But at the same time we need a 2nd eye to ensure the software meet the requirements and end to end integrations are working fine , scrum team has the right tools and automation frameworks etc...to write tests.
      > >
      > > "One of the things that annoys me is the whole "push quality upstream" movement. That's like taking all your vitamins when you are a baby and then expecting a long healthy life. Obviously upfront debugging is good, but quality is an ongoing endeavor. " James Whittaker @ TestNewsOnline (http://www.testnewsonline.com/2011/10/03/test-talk-with-whittaker-google/)
      > >
      > >
      >



    Your message has been successfully submitted and would be delivered to recipients shortly.