Find your kernel of certainty
We have entered the vicious stack of crises. This is the cycle of issues that follows the most-recent top-priority law. This stack is not strictly LIFO, however. If the PM receives a call regarding an issue further down the stack, it is escalated to the top.
Our stack is currently three issues deep.
The new features are a week late. But they have to slide because the fix that we pushed to production on Friday didn’t work. We told our customer that the problem would be solved before the weekend, so now they are breathing down our necks for an estimate on the real fix. But we can’t work on that now because the new build is bringing down the QA servers and they can test.
It is in times like this that I look for my kernel of certainty. Instead of tackling the chaos head-on, I need to start from an island of sanity. I need to find one piece of the system that I can trust implicitly. From there I can reach out to other components and bring them under control.
At the moment, I can’t trust MySQL. Two of these issues may be related to the database itself doing something unexpected. I need to bring something else to bear on the problem. Unfortunately, I can’t trust Log4J right now, either, because it wasn’t accepting my configuration changes on the live production server. So I have to retreat one step further. Right now my island consists of Java, Eclipse, MyEclipse, and JBoss running on my own box. And JBoss is in danger of being voted off.
Once I pare the world down into its most sane parts, I can start to extend my reach of confidence out to Log4J. When that is again within my control, I’ll bring that to bear against the MySQL problem. With visibility that I can trust, I may find that I solve all three crises simultaneously. However, I won’t find a solution by attacking each issue directly, with their priorities shifting, using tools in which I have no confidence.