--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumallianc...@googlegroups.com.
To post to this group, send email to scruma...@googlegroups.com.
Visit this group at https://groups.google.com/group/scrumalliance.
For more options, visit https://groups.google.com/d/optout.
--
On Jun 20, 2016, at 1:03 PM, Alan Dayley <ada...@gmail.com> wrote:I proved the two clarifications above by way of context for the answers you may get. In other words, your statements already imply an expectation that is contrary to basic Agile principles. Some of our answers might be for your organization to change their basic assumptions in order to be more aligned with Agile and Scrum ideas.That said, I would say that for a QA group to serve Scrum Teams doing projects, that group would be mentoring, supporting. They would be building environments, processes and structures that allow the teams do do QA for themselves as much as possible. And the QA group would help with specialized knowledge and doing some tests that might be too deep or too specialized for every team to do on their own.So the pattern for a QA service would be one of helping and specialty knowledge.