Process is a great tool - and if used properly -can keep teams more efficient and maybe even propagate some culture or history.
And then Rands touches on something important: every time there's a new policy addition in the office engineers groan. Why?
* Because a manager is going to try to "fix" something (and will probably make things worse). ("Yes, we know the bug tracker sucks, but (sarcasm) yes blame the _developers_ when the requirements change half eay through implementing the ticket")
* "If you listened to us in the first place... We wouldn't be overworked and making these mistakes you're compensating for"
* The "green lieutenant" problem. (see any war movie for this)
See enough of those and yeah you'll roll an eyewhensome manager bursts into the door with a great idea... Especially when asking "why?" too mny times certainly will get you branded as a trouble maker.
And then Rands touches on something important: every time there's a new policy addition in the office engineers groan. Why?
* Because a manager is going to try to "fix" something (and will probably make things worse). ("Yes, we know the bug tracker sucks, but (sarcasm) yes blame the _developers_ when the requirements change half eay through implementing the ticket")
* "If you listened to us in the first place... We wouldn't be overworked and making these mistakes you're compensating for"
* The "green lieutenant" problem. (see any war movie for this)
See enough of those and yeah you'll roll an eyewhensome manager bursts into the door with a great idea... Especially when asking "why?" too mny times certainly will get you branded as a trouble maker.