Getting bugs fixed

- Once development teams have been working together for some time they know how much work they are likely to complete during each development sprint. As the team hits their stride each sprint should contain new features, enhancements, and bug fixes as well. Set goals around how many bugs should be fixed per sprint. You can focus on fixing a percentage of bugs, all the high priority bugs, or a certain number of hours allocated. Whatever the goal, just clarify it with the team and make sure to plan what bugs are being fixed and which sprint. Of course it's inevitable that new bugs will be introduced in the middle of any sprint. Unless bugs are high priority they should not be moved into a sprint while it is in progress. The idea here is to always fix the most important bugs as soon as possible and make a plan for remaining bugs to be fixed later. Your team can also set long term goals around bugs such as reducing the amount…