In 2004, we began down the road of adopting the IT Infrastructure Library framework. We began implementing our ITIL processes with Incident Management and Service Desk. We quickly followed with creating a Service Catalogue. The next major process was Change Management. A group of  key people were assigned to become our IT Change Advisory Board (CAB). The membership of the CAB was solely IT Services technical staff and managers at the start.

The IT Services CAB had representation from all our teams: Service Desk, Desktops, Satellite Campuses, Applications, Web Services, Servers, Storage and Network teams.

Over the years, we have worked to establish the credibility of the CAB and the value that it brings to our organization.   I am the current Change Manager and take every opportunity to talk about our Change Management Process to stakeholders in our community.

We have slowly grown our IT CAB into an enterprise CAB.  We now have membership from our Learning and Teaching Centre, our Library, our Facilities Management group and now from our Broadcast Engineers (from our School of Business – Broadcast programs).  As more and more groups ask to join, we get better communication about enterprise wide and campus wide (we have 5 campuses) changes.

The end result of this maturing process is that we can better manage changes initiated by service departments. reduce risk and maintain highly available, quality services to our students and our stakeholder community.

Here are some links to information about our change management process:

IT Services Scheduled Downtime http://www.bcit.ca/its/services/downtime.shtml

IT Services Maintenance Announcements http://www.bcit.ca/its/services/maintenance/

 

Failing to consider your followers may result in you being the only one charging out of the trench towards the enemy. (credit Stephen Lamb – @SEE_EYE_OH) If I am leading, I need my team with me to be successful. In the complex world of IT Service Management, working as a team is the only way we can be successful.  Leading and managing my application development team has shown me that if we focus on what our work principles are, we can accomplish our goals together.  Teamwork is the key to building a successful service management culture.

I had to change the one particular practice within of our team when I started as the manager.   I particularly hate the phrase “That is not my job”.  The people we serve don’t care that it is not our job; they want their problem resolved so they can carry on with their work day.

My team worked hard while having a narrow vision of what delivering a service end to end meant. If an application was not functioning due to an infrastructure problem, they would hand it off to the Infrastructure team to manage the problem. The result was that many of our application clients had to run the gauntlet of our internal IT Services departmental complexity. Those unfortunate clients were not able to work and became very unhappy by getting the run around by our team.

I introduced the concept that “We are the face of IT Services for the Application Services”.  This means that “we own the problem end to end”  and no longer hand off our problems. Instead, my team navigates our internal complexities, manages the issue for the client and ensures we get a resolution for our clients. Our clients interact with the person who took the issue and never have to figure out who else to talk to. I got initial resistance to this approach.  It took about a year to instill this new principle into my team’s culture and work habits. This approach has turned around our clients’ impression of our team.  We are now a team that everyone wants to work with because they know if we take on a problem, we will own it end to end.

Service management? It is all our jobs … together!

 

Greg Milligan, National Technology Strategist, Microsoft Canada

Dynamic IT in Education

IT deliverables on campus today – supporting users, providing services and governance

Higher Education IT Challenges – cost containment, security, reliability, interoperability, available choices

Looked at maturity models, first used Gartner Maturity Model and then MIT Maturity Model.  Measure 3 areas: core infrastructure, business productivity, application platform.  Move from cost center to more efficient cost center, business capability, strategic asset

Bridging the business drivier to IT

  1. Understand business drivers, needs and challenges
  2. Define desired business capabilities to deliver – 3 phased measure – planned, underway, complete
  3. Assess current capabilities
  4. Gap Analysis of current vs desired delivery
  5. Roadmap
  6. Build the architecture for the specific solutions

Look at Capabilities – basic, standardized, rationalized, dynamic across the enterprise.  Use questions to assess the maturity

What is the Optimized Desktop?  Reduce TCO, increase flexibility, streamline management by separating desktop components – desktop virtualization is the enabler.  Separate user data and settings, applications and operating system

Application Optimization Scencario – improving application delivery and management

© 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