Software Development Cross Solution - Index of - Free

Fixing bugs while you keep working
The development team will start getting bug reports on
their first iteration about the time they’re getting into the
third iteration! And then you have to figure out if the bug’s
important enough to fix right away, roll into the current
iteration, or put off for later. We’ll talk more about this in a
minute, but the straightforward approach is to treat a bug
like any other story. Prioritize it against everything else and
bump lower-priority stories if you need to in order to get it
done sooner.
Another approach is to carve off a portion of time every
week that you’ll dedicate to bug fixes. Take this off of the
available hours when you do your iteration planning, so
you don’t need to worry about it affecting your velocity. For
example, you could have everyone spend one day a week on
bug fixes—about 20% of their time.
The development team
needs to incorporate
bug fixes into their
iterations–and what
happens if there’s a
show-stopper bug that
blocks the testing
team? Do you do a miditeration
build?
You can’t always wait until
you get to the end to fix
all bugs; sometimes further
development depends on
getting some bugs fixed now.
Writing tests for a moving target
Functionality in user stories—even if it’s agreed upon by the customer—can change. So lots of
times, tests and effort are being put into something that changes 30 days later. That’s a source
of a lot of irritation and frustration for people working on tests. There’s not much you can
do here except communicate. Communicate as soon as you think something might change.
Make sure testing is aware of ongoing discussions or areas most likely to be revisited. Have
formal turnover meetings that describe new features and bug fixes as well as known issues. One
subtle trick that people often miss is to communicate how the process works. Make sure the testing
team understands to expect change. It’s a lot easier to deal with change if it’s just part of your
job rather than something that’s keeping you from completing your job.
Development has moved on...
and user stories may have
changed already.
Iteration
3
Download at WoweBook.Com
Test I2’s
build
ending an iteration
Iteration
2
Iteration
3
Bug fixes
The test team is writing tests
for code that isn’t stabilized
yet. And remember, features
can change each iteration since
the customer can reprioritize or
change things.
you are here 4 329