There are some tricks that I've been using to not get totally over whelmed and flooded with work. I don't know if it's good or bad, but it helps me stay sane while working with other developers.
Filter #1:
When someone raises an issue while in passing or at the water cooler (figuratively), I'll ask them to raise a ticket so that can be addressed. If I never see the ticket, then the issue wasn't important enough to them to spend the 30 seconds of their time. It's not worth me spending time on it either. This kills 75% of "issues".
Filter #2:
On the rare cases that it gets past #1, then most of the time the ticket is somewhat vague and needs some clarification. I could guess what they mean, but I bounce the ticket back to them so they can fill out what they mean with their fuzzy ticket hand waving. When you later follow up with these issues you find out that they weren't really issues after all. This kills another 20% of issues.
That leaves the tickets that people need and want, and have a clear idea of the requirements. It takes off 95% of the tickets and reduces it to the issues of the "now". I'm not saying that this is a good idea to do with all people. I'm saying that it works for developers interacting with developers.
No comments:
Post a Comment