Software Development Cross Solution - Index of - Free

issues with test iterations
More iterations means more problems
System testing works best with two separate teams, working two
separate iteration cycles. But with more iterations comes more
trouble—problems that aren’t easy to solve.
Running two cycles of iterations means you’ve got to deal with:
LOTS more communication
Now, not only do you have inter-team communication issues, but you’ve got two teams
trying to work together. The testing team will have questions on an iteration, especially
about error conditions, and the development team wants to get on to the next story, not
field queries. One way to help this is to bring a representative from the test team into
your standup meetings as an observer. He’ll get a chance to hear what’s going on each
day and get to see the any notes or red stickies on the board as the iteration progresses.
Remember that your standup meeting is your meeting, though—it’s not a time to
prioritize bugs or ask questions about how to run things.
The test team (reasonably)
needs to know some details
that the development
team probably doesn’t have
yet. Error codes, invalid
values, API information,
how to set things up, etc.
328 Chapter 9
Iteration
1
Testing in a FIXED iteration length
If you’re keeping your two iteration cycles in sync—and
that’s the best way to keep the testing team caught up—
you’re forcing testing to fit into a length that might not be
ideal. To help give the test team a voice in iterations, you
can have them provide you a testing estimate for stories
you’re planning on including in your iteration. Even if you
don’t use that to adjust what’s in your iteration (remember,
you’re priority-driven) it might give you some insight into
where the testing team might get hung up or need some
help to get through a tough iteration.
Prep for
I1
Download at WoweBook.Com
Test I2’s
build
The testing team is looking
ahead to what’s coming at the
end of Iteration 1, even while
your developers are still coding.
A fixed iteration length forces
testing into the same time box
as development. But if you’ve got
different teams and different
schedules, this may be tricky, if
even possible at all.