Monday, February 6, 2012

Important / Urgent

From the good old Important / Urgent time management graph, we can see how Code Quality is not "Urgent" but the fallout of poor code, Bugs, are both Important and Urgent.

If we ignore Code Quality, we borrow against future effort and build up a technical debt. We end up with more bugs which are important/urgent, which means less time for Code Quality, which means more bugs.....

Rinse, Repeat, buy an "Inside I'm Screaming" teeshirt.

Not Urgent Urgent
Important Code Quality Fix Bugs
Not important Fix "trivial" bugs Coffee

Clearly, this is an incomplete table, but you get the idea.

No comments:

Post a Comment