What is your bug fix versus improvements?

Question

In the spirit of this question, I wanted to have an idea of ​​how much time is shared between fixing bugs and introducing new features. If possible, try to give an estimate for the product as a whole, in contrast to the individual indicators of the developer, and try to make an average value over a typical year. Provide a generic product / project descriptor for comparison. In particular:

• project maturity
• Still actively developing or strictly supported?
• Product / Project Size Estimation
• The size of the team developing it (all inclusive)
• What is the assessment of your team on the Joel Test .

Example:

• approximately 80% of corrected time errors 20% of new things
• Mature programs (20 years)
• Actively developed
• 1.5M Line of text, approximately 700k - 900k LOC
• 12-15 actively encodes in it.
• we got 5/12, of course, some would say 7/12.

Answer 1

I would rate: New features 70%, errors 10%, technical debt (refactoring, etc.) 20%

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

You did not request a technology stack, but if you are interested, Ruby on Rails

Answer 2

I would estimate that we spend about 70% of our time on new features and 30% on Errors.

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

Answer 3

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

Answer 4

From our time tracking software, I see that the component / defect ratio of our teams last year:

• 75% of functions
• 25% defect problems

Other statistics:

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

Answer 5

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

We are developing a game (C ++) using our own infrastructure and engine, so it is actively developing. The statistics given above are rounded off from our tracking software, however I could point out here that while developing minor bugs are already resolved without creating a list of bugs.