Whenever I think about process and tool changes, in addition to thinking about what I want to work better, I think about what I don't want to change. If somethi

Whenever I think about process and tool changes, in addition to thinking about what I want to work better, I think about what I don't want to change. If something is working well and you don't strive to keep it working while monkeying with how the "process" works, you will surely break it. I saw an entire team self-destruct while building a product because management (including the inexperienced dev lead) kept wanting just a little more clarity into what was going on. Tweak after tweak increasing process, planning, and reporting at the expense of getting stuff done until the debs (myself included) couldn't take it any more. If you don't try very hard to keep what is working, you will lose it. Often, what is working is more important than what is not.