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

Re: [scrumdevelopment] Re:Need some tips on QA Engineer in Scrum

Expand Messages
  • mpkirby
    ... Here s a question. In a scrum team is there a difference between responsibility, accountability, and skills? I could see having team responsibility,
    Message 1 of 34 , Dec 1, 2006
    • 0 Attachment
      > > Does people think we don't need specialized QA engineers
      > > in agile teams?
      >
      > In general I favour "generalising specialists" over
      > specialists in most if not all cases. We need somebody that
      > is good as a QA engineer. Beyond a certain point of
      > specialisation, the best way to improve your specialist
      > skills is to walk a mile in the shoes of those you ought
      > to collaborate with.
      Here's a question. In a scrum team is there a difference between
      responsibility, accountability, and skills?

      I could see having team responsibility, shared skills (to the degree we
      can), but individual accountability for certain functions. So we might
      have a QA person that is accountable, particularly for the external
      relationships involved in QA (getting lab time, acquiring hardware,
      reporting results to some kind of overarching project tracking), but
      having the team be responsible for the individual tasks.

      Mike
    • dnicolet99
      I m sure you re right about the definition of SOX requirements and the separation of QA testing from development. I don t think people are hung up about the
      Message 34 of 34 , Dec 1, 2006
      • 0 Attachment
        I'm sure you're right about the definition of SOX requirements and the
        separation of QA testing from development. I don't think people are
        hung up about the wording of the standards or about COSO guidelines. I
        think the issue for agile development teams is that we don't want the
        teams to spend a lot of time dealing with administrative requirements
        that are outside the scope of software development as such. It's
        better to handle those requirements separately from the development
        effort, to the extent practical. A project as a whole may have to
        support SOX requirements, but the agile development team (which may be
        a subset of the whole project, in a complex enterprise-scale
        initiative) can be most effective if it focuses on the software
        development effort exclusively.



        --- In scrumdevelopment@yahoogroups.com, "Jeff Heinen" <jheinen@...>
        wrote:
        >
        > The myth that SOX requires separation of QA comes from the Committee of
        > Sponsoring Organizations of the Treadway Commission (COSO) framework ,
        > which has suggestions for SOX compliance. It states:
        >
        > "Control Activities. Design, implementation and quality assurance
        > testing teams should be independent. ERP and CRM systems that collect
        > data, but feed into manual spreadsheets are prone to human error. The
        > organization will need to document usage rules and create an audit trail
        > for each system that contributes financial information. Further, written
        > policies should define the specifications, business requirements and
        > other documentation expected for each project."
        >
        > The grammatical ambiguity of that first sentence notwithstanding, it
        > does suggest that test should be independent, however it is nothing more
        > than a suggestion. There is no binding requirement. Having just gone
        > through an audit, I can say that our auditor didn't bat an eye at our
        > integrated scrum teams. She thought it was pretty cool actually.
        >
        > -JH
        >
        > > -----Original Message-----
        > > From: scrumdevelopment@yahoogroups.com
        > > [mailto:scrumdevelopment@yahoogroups.com] On Behalf Of Ron Jeffries
        > > Sent: Tuesday, November 28, 2006 6:17 AM
        > > To: scrumdevelopment@yahoogroups.com
        > > Subject: Re: [scrumdevelopment] Re:Need some tips on QA
        > > Engineer in Scrum
        > >
        > > Hello, David. On Monday, November 27, 2006, at 5:15:48 PM, you
        > > wrote:
        > >
        > > >> 1. Sarbanes-Oxley Act implementation requirements in our company
        > > >> require a separation between developers and testers
        > >
        > > > This is interesting indeed. Could you share a bit more
        > > information on
        > > > this? I ask, because I worked for a division of Adobe.
        > > Adobe is also
        > > > Sarbanes-Oxley compliant and we have cross functional teams there.
        > >
        > > Having read the Sarbanes-Oxley act on a day when I felt like
        > > killing myself anyway, I feel quite confident in saying that
        > > the act itself does not mandate this separation. One's
        > > lawyers and other helpful advisors might do so, of course, in
        > > the mistaken view that it would make things better or safer.
        > >
        > > I always go to lawyers for software development advice, don't you?
        > >
        > > Ron Jeffries
        > > www.XProgramming.com
        > > Here is Edward Bear, coming downstairs now, bump, bump, bump,
        > > on the back of his head. It is, as far as he knows, the only
        > > way of coming downstairs, but sometimes he feels that there
        > > really is another way, if only he could stop bumping for a
        > > moment and think of it. And then he feels that perhaps there
        > > isn't. -- A. A. Milne
        > >
        > >
        > >
        > > To Post a message, send it to: scrumdevelopment@...
        > > To Unsubscribe, send a blank message to:
        > > scrumdevelopment-unsubscribe@...
        > > Yahoo! Groups Links
        > >
        > >
        > >
        > >
        >
      Your message has been successfully submitted and would be delivered to recipients shortly.