Software Development Cross Solution - Index of - Free

Good system testing requires
TWO iteration cycles
Iterations help your team stay focused, deal with just a manageable
amount of user stories, and keep you from getting too far ahead
without built-in checkpoints with your customer.
But you need all the same things for good system testing. So what if
you had two cycles of iterations going on?
The development
team is hard at
work on their
first iteration.
After delivering
Iteration 1’s build
the development
team goes right
into Iteration 2,
and then 3, etc..
Sometimes you need
a dedicated bug fix
iteration. In that case,
you’d deliver a few builds
within a single iteration.
Development team Testing team
Iteration
1
Iteration
2
Iteration
3
Bug fixes
“It. 1” is short
for Iteration
1, “It. 2” for
Iteration 2, etc.
The test team sends
bug reports back
to be rolled into a
later iteration.
Things always tighten up
at the end of a project.
Download at WoweBook.Com
Prep for
It. 1
Test It.
1’s build
Test It.
2’s build
Test It.
3’s build
ending an iteration
This assumes you’ve got two separate teams:
one working on code, the other handling
system testing. But the same principles apply
if your second team is other developers.
The test team has an
entire iteration to
prep. They’re getting
familiar with the
stories for the incoming
iteration, getting their
environment in place,
building system tests, etc.
At the end of
each iteration
the development
team delivers that
iteration’s build to
the testing team.
At this point, the
test team signs off on
a working version, or
milestone, or release.
you are here 4 327