Prioritizing

We’ve differentiated strategies for prioritizing what to work on.

Project without much technical debt / bugs

There can be a healthy focus on expanding project, attracting more customers. Fixing bugs to prevent project decline or customer chore is a close second.

• bug[critical]
• bug[urgent]
• bug[high]
• seo[high]
• feature[high]
• techdebt[high]
• devux[high]
• repeat of above, on prio normal
• repeat of above, on prio low (or consider skipping it, focus attention on other projects instead)

Project with significant technical debt and bugs

First, you don’t want to turn away new customers interested in the project. Therefore we need to balance new feature requests and bugfixes with catching up with older technical debt and bugs. Customers waiting for those older fixes likely left already or might want to wait a little bit longer.

• devux[high] (it’s important to enhance productivity of devs to speed up getting on top of things)
• bug[high]
• feature[fresh+high]
• seo[high]
• techdebt[high]
• feature[high]
• repeat of above, on prio normal
• repeat of above, on prio low (or consider skipping it, focus attention on other projects instead)