How long do you take for each Development Cycle

2 Developers * 3-4 Days * 40-50 Bugs < Happiness...

Feel free to alter the first, second and/or third terms until the
equation balances.

It sounds like you have the correct processes in place, you just need
some scope management. With the idea that "less is more", fewer bugs
attempted should yield less rework, and less missed dates (and maybe get
you home in time for dinner).

Prioritize the bugs that are on the list, and don't be afraid to start
tossing low priority bugs off the list if the scope of a higher priority
change is larger than anticipated.

Overtime may work for short bursts, but fact is fact... tired
programmers make mistakes.

That's the problem with bugs, you never know how long they will take
to correct.

On the other hand, 4 days to resolve 25 simple bugs does not seem so
tight.

Cheers, Sazima

Sazima wrote:

That's the problem with bugs, you never know how long they will take
to correct.

On the other hand, 4 days to resolve 25 simple bugs does not seem so
tight.

Cheers, Sazima

Yup, i agree. But the bosses and clients never think so. Or actually,
they think so, but changed their mind when other things go wrong
together as the whole process are delayed.

cheers, Arthur