Slash Boxes
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Let's just pretend I never said any of that

    I have to admit that I snickered slightly when I read that. Sorry :-)

    Despite the agreement, we're not pairing and the workload doesn't seem much slower

    I've found that moving to shorter iterations for a bit can sometimes help with this. It forces you to make the stories smaller, which means that people get to work on more stories in the same period of time. The more different stories you get to work on, the more domain knowledge you need to cover, so you h

    • We have one-week iterations. We've wanted longer ones, but I think that shorter iterations have been a benefit when we get a bit sloppy.

      • We have one-week iterations.

        Scratch that advice to try shorter iterations then :-)

        We've wanted longer ones, but I think that shorter iterations have been a benefit when we get a bit sloppy.

        That's been pretty much my experience. Longer iterations work well if things are going okay, and moving to shorter ones helps when there are problems.

  • 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

    • It also lets you put the time spent fixing bugs into the "how's our estimating?" feedback loop./p.

    • 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.