Quick rundown - the way software management works:
There are tons of teams, but there are almost always software developer teams, and ‘product’ teams. PM’s for short, ‘product management’. PM is responsible for gathering and assessing which features and changes would be most valuable to the customer. PM takes it’s orders from Engineering/R&D (whatever it happens to be called). Engineering takes its orders directly from the top, usually a CTO (chief technology officer), who will typically direct PM to focus on feature requests submitted from ‘x’ customer base. A company like Avid is constantly adding and debugging features. But the rate they’re shipped to market may be less noticeable to home studio users, as their subscription + integrated hardware sales income targets a different client echelon.
Testing (Quality assurance teams) - Regression testing and smoke testing is much more complicated when you have integrated hardware. The more lean and flexible a code base and ecosystem are, the faster QA/QE (quality analyists/quality engineers) can test and ‘ship’ changes.
Here the catch. NONE OF THIS APPLIES TO REAPER. The reason: Cockos only has a couple developers. Yes, like… between 2-5. Avid has hundreds of these guys on full time payroll. Knowing what I know now about software, i was thinking a group of 6-9 devs could be behind Reaper, but its even fewer than that. And that’s how they get away with only charging $60 per license, with 2 left of the decimal upgrades included. After they pay themselves, the company is probably barely profitable.
I would guess that decisions around ‘which feature to add next/which bug to fix next’ are likely made with a simple conference call (we call these ‘standup meetings’ in tech) and notifying the other developer what they’re going to be working on.
Imagine having that level of independence and freedom to collaborate!!