I have been thinking a lot about re-engineering the service delivery model for the application services team that I lead. I have been guiding my team to think about:

“We deliver the platform and work with the business to provide services”.

Our applications team is made up of subgroups aligned by major application services.  Here are the major applications:

  • Business Intelligence
  • Collaboration Tools
  • Document Management
  • Email and Calendaring
  • ERP (Student, Finance, HR, Doc Mgmt)
  • Identity Management
  • Learning Management Applications
  • Microsoft Applications
  • Oracle Database
  • Portal (for students and employees)
  • SQL Server Database

Currently, there are 3 teams in place in our Business Application Services group. Here are the roles in each team:

Support Team

  • Oracle DBA
  • Document Management
  • Business Intelligence
  • Project Management
  • Business Analysis
  • Identity Management

Email and Collaboration Team

  • Email
  • Calendaring
  • Instant Messaging
  • Collaboration Platforms
  • SQL Server DBA
  • Microsoft Applications
  • Enterprise Portal

Developer Team

  • Oracle Developers
  • Lotus Domino Developers
  • Microsoft Developers
  • Java/Web Services Developers

I am interested in hearing from any of you that lead groups with similar responsibilities.  Do you have a suggested structure for me to consider?  Do you split your team based on roles (technology domains)  or by application (vendor) platforms? Do you split operational work from project delivery?  Does your governance structure influence your teams organization?

Any suggestions are very welcome and I hope to learn from some of your experiences.  Thanks in advance.

Related posts:

  1. What kind of IT Application Shop are we …
  2. Consistency in Technology Solution Delivery
  3. Delivering Projects by Managing Ops with a Duty Analyst
  4. Adaptive Leadership in EA
  5. Helping your team be effective … the role of a Duty Analyst

Leo de Sousa

 Leave a Reply

(required)

(required)

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

   
© 2007-2012 Enterprise Architecture in Higher Education - Leo de Sousa Creative Commons License
Enterprise Architecture in Higher Education by Leo de Sousa is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
Based on a work at leodesousa.ca.
Suffusion theme by Sayontan Sinha

Switch to our mobile site