THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Buck Woody

Carpe Datum!

The New World of Work: Swarms

I’ve been reading some excerpts from Gartner, Inc. and information from others on the changes they are seeing in the workplace. It’s holding true where I work and in the workplaces of the other data professionals I work with. One of those new trends is called “Swarming” – where informal teams get together to work on a particular project, and in some cases a single task, as a group. They then move on to another task, and so on, like a swarm of bees. These are less formal than the “Tiger Teams” I used to be part of that were also temporary, but had a more formal banding and dis-banding. The Gartner article states that this is more often the norm in companies than not.

 

This is interesting to the data professional because there are usually so few of us in the organization. There are on average a single data professional for every five to ten developers, or in an operational sense, one DBA for every several hundred servers in my experience. So when a “swarm”, or “tiger team” or any other kind of tactical group is assembled, the data professional is usually required to be part of it. That’s fine, but it ends up with a few outcomes that you might not expect.

 

For one, the rate of burn-out or overwork can be higher, since not everyone else works on every project like you do. The data professional has to take part in all of them, so you move from high-stress project to project. The key here is that since not everyone is on every project (except you) they may not notice it happening. They only see you on "their" projects, so they assume you're working at the same level as they are.

 

Another impact of a swarm on a data professional is that over time you might become more tactical than you want, and you might also be perceived that way by others. After all, if they only see you responding to fires, perhaps they’ll think that’s what you like or what you are good at.

 

So how do you mitigate these problems associated with this new way of work? Communication. You need to let your boss know, in a non-complaining way, what your workload looks like. No, not how *much* work you have, but what *kind*. They need to understand that you would like the ability to have a good pace to allow for the best quality work, and most importantly that you would like to build some time into your schedule for strategic work along with the tactical requirements. Of course, you need to balance this with actually getting your work done, but I have a few ideas about that which I think might be able to help. I’ll blog about those another time.

Published Tuesday, August 24, 2010 5:11 AM by BuckWoody

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Chris Allott said:

Greate article summing up exactly how I feel at the moment. Our Business Information team is small (2 developers) but is involved in 7/8 different projects. Any form of stratgic planning for our team goes out the window in favour of just keeping up with the rest of the organisation's goals.

August 26, 2010 5:21 AM

Leave a Comment

(required) 
(required) 
Submit

About BuckWoody

http://buckwoody.com/BResume.html

This Blog

Syndication

Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement