What is your ratio Bug fixing vs Enhancements? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 7 years ago.

Improve this question

开发者_运维问答In the spirit of this question I wanted to have a sense of what is the proportion of time split between fixing bugs and implementing new features. If possible try to give an estimate for the product as a whole as opposed to individual developer stats and try to make an average over the course of a typical year. Do provide a general descriptive of the product/project to allow comparison. Specifically :

• Maturity of project
• Is it still actively developed or strictly in maintenance ?
• Size estimate of the product/project
• Size of team developing it (all inclusive)
• What is your team score on the Joel test.

Ex :

• approx 80% time spent bug fixes 20% new stuff
• Mature software (20 years old)
• Actively developed
• 1.5M Line of Text, approx 700k - 900k LOC
• 12-15 actively coding in it.
• we got 5/12 for sure, some would say 7/12.

---

I would estimate: New features 70%, Bugs 10%, Technical debt (refactoring etc.) 20%

• Maturity: 2 years
• Actively developed
• Team size: 8
• LOC: 50k-100k
• Joel Test: 9/12

You didn't ask for technology stack but if you are interested it's Ruby on Rails

---

I'd estimate we spend around 70% of our time on new features and 30% on Bugs.

• Maturity 10 years
• Actively developed
• Team size 14 (1 manager, 1 tester, 1 UI designer, 11 developers (8 on new features and 3 dedicated to maintenance))
• 2.2M lines of text (950K actual code)
• Joel Test 10/12

---

• 50% debugging, 50% new code (and personally I want the debugging part to be lower)
• Software is 15 years old
• 1.5M line of text (with 170K empty lines, 250K lines of comment, 800K lines of actual code)
• about 10 people developing on it
• Joel Test: 8/12

---

From our time tracking software I see our teams feature/defect ratio of last year is:

• 75% feature tasks
• 25% defect tasks

Other stats:

• Software is ~10 years old
• 4M lines of text
• Currently 11 developers
• Joel Test: 7/12

---

• 50% New features, 25% bug fixing, 25% testing
• Actively developed
• 9M lines of text
• around 25
• 9/12

We're developing a game (c++) using our own framework and engine, so it is actively developed. The stats above are rounded up from our tracking software, however I could make a note here that while developing minor bugs are already resolved without creating a bug listing for it.