On Tuesday, February 1, 2005, at 9:39:33 AM, John Keane wrote:
> I guess the thing that I don't understand about the functions that you
> mention is why can't that be handled w/n the main sprints? What is the
> need for a separate QA function? I would think that you would want to
> have the QA group as tightly integrated into the main sprints as
That's certainly my view (as I suspect you know ;->). The QA
functionality needs to be there, certainly. And as much of the
feedback as possible wants to be inside the current sprint.
> We have been doing SCRUM and haven't gotten there completely
> but that is the drum that I am beating w/ my team. I manage our team of
> QA engineers here and we are going in an entirely different direction
> from an independent QA function. I think it is a testimony to SCRUM how
> well it functions in almost any environment; however I am trying to move
> my team to more of an xp model with the QA function closer to the
> construction task.
This seems to be happening more and more. Scrum is silent on just
how to develop and test, and the XP canon includes some good ideas
that more and more people are adopting as part of their Scrum
> I would love to say that we are completely there,
> but that isn't the case today. The way we currently solve it is that we
> have the main sprints and we tack on a release sprint at the end. The
> intent of this release sprint is to move the code from dev to out
> Production Test environment.
This is not uncommon. It might be nearly universal. I believe that
the team should be able to get to the point where any CD off the
stack is shippable, but for many teams that's kind of a limiting
state they never get to. There's always something to clean up.
If I were doing a one-week iteration, I'd be more comfortable with a
release iteration than with a one-month one. That's a long time to
wait with no new functionality. (I'm not a patient man.)
> This is as much for IT as it is QA, but
> the intent is that most of the new functionality is already tested
> before we enter the release sprint. In the final phase we handle the
> regression and environment related testing. In the future, I really
> want us to be developing a large suite of automated tests ala xp and
> using the regression period for only exploratory testing. I think the
> tools that we can use to get there is XP, so we are going to prototype
> it on one team in the coming months.
I'm delighted to hear that! :)
Make it real or else forget about it -- Carlos Santana