Database team structure

  • Hi all,

    Currently part of a large global organisation with A DBA team of around 20 members spread throughout the globe. Structure is currently an overall manager with two team leads, one in the APAC region and one in the American region. I.e. Eastern and western hemispheres and everyone else sitting below. Team is entirely core infrastructure DBA's - i.e. not report writers, not developers - we simply deploy, monitor and maintain SQL Server and other DB platforms with our contingent of junior, intermediate and senior DBA's.

    Organization is proposing a restructure whereby the team splits into a standards/design/projects team and a run/operations team - both with completely separate lines of report. You'd be going up 3 or 4 levels of management before you landed on a common manager. I'm curious whether anyone has had any experience having a DBA team split in a similar way and what worked well and/or did not work well? From my perspective I would be concerned that as part of the standards/design/projects team me and my colleagues would lose the ability to influence how operational work is done. Don't get me wrong, I see some positives too, just not sure about how detrimental some of the negatives would be.

    Cheers.

  • SQLDBAPerth - Wednesday, December 5, 2018 9:57 PM

    From my perspective I would be concerned that as part of the standards/design/projects team me and my colleagues would lose the ability to influence how operational work is done.

    That's interesting. My assumption would be the exact opposite if you're defining the standards. I can definitely see how tensions could arise in that kind of setup.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply