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 On Jan 28, 3:42 pm, Ar Chron <rails-mailing-l...@andreas-s.net> wrote: > 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. > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
