Prioritizing Technical Debt, Bugs, and Features | Using an Eisenhower Matrix

As you write software, you are going to make mistakes.  These mistakes, or bugs and defects, have to be fixed while you continue to make your product better and build new features.  So how can you make sure you're making enough progress on your product while addressing all the of the bugs that are bound to pop up?

First, we'll begin by classifying bugs, features, and technical debt.  Then, we'll be able to talk about how much time should be devoted to these types of work, and finally top it off with some tips and tricks on how to prioritize these things relative to one another.

You don't have to be Agile to follow along, but I'd highly recommend it!  Having a backlog of work defined will make the prioritization much easier.