Jump into the conversation with new questions and insights here in TSIA Exchange.
Is there a standard for what % of time a SW dev team works on features to satisfy existing users?
Hello TSIA community!
I hope you are all doing well. I am hoping to get some insight from the community regarding on average, what percentage of time a software development team is working on different types of feature work for a given product. While I understand this is going to differ depending on what type of product they are working on or how long a given product has been released, I am just trying to look to see what others have experienced.
The different buckets of feature work I was think of were the following:
-New features/UX to expand market reach to bring in new users
-New features/UX to satisfy and provide value to existing user base
-Tech debt items
-Customer issues/escalations and product bug fixes
I am also not sure if others view those top two buckets of feature work as different areas or just merged and prioritized as a single backlog. If you treat them as a single backlog, do others see potential for the new features to expand the market to starve out the development time from the features for existing users? If not, what metrics do you use to justify the existing user feature work over the feature work for new markets?
I appreciate any insight and look forward to the responses.