NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall in perl.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Evolving bugs (Score:2)
If there's any sort of quantitative incentive for knocking off bugs--even if it's indirect incentive such as bragging rights--the easy bugs will go first, and the harder ones will tend to get avoided until they're unavoidable.
Have you tried treating bugs like any other story? Let your customer (or customer proxy) prioritize them and decide which go into the mix for an iteration. This has the benefit of keeping a single set of priorities, and helps avoid cherry picking on small problems, or playing hot p
Re:Evolving bugs (Score:2)
We do treat bugs like other tasks. The only major exception is bugs that affect the availability of our site or our data inputs/feeds. Those are almost always "drop everything and fix them now." Our data is what we get paid for (the Web site is a free bonus to many of our customers) so we can't afford to drop the ball there.
Reply to This
Parent