Tag Archive for 'Priority'

Documenting the (SLA) Service Level Agreement

The most difficult job is being a Network Administrator. The reason is simple:

  1. They have never get credit for what they do
  2. They always have a problem which does not have an easy solution
  3. Everyone complaints that the network performance is slow

Recently I was requested to document the Service Level Agreement (SLA) for our organization. The SLA is intended to provide guidance on how the network and telephony infrastructure is expected to perform, and the Network Team’s commitment to maintaining the quality and reliability of services provided to the enterprise.

The Structure of an SLA can be summarized by:

1.0    Statement Of Intent
1.1    Document Approvals
1.2     Document Review Dates
1.3     Time Conventions

2.0     About This Service
2.1     Services Covered Under This SLA
2.2     User Environment
2.2     User Support Services

3.0     About Service Availability
3.1     Scheduled Events That Impact Service Availability
3.2     Nonemergency Enhancements
3.3     Change Process
3.4     Change Management

4.0     Service Measures

5.0    Network Team Prioritizes

Network SLA cover all services under the administration of the Network Team, and includes, but is not limited to:

  1. Desktop Services
  2. LAN Services
  3. WAN Services
  4. Telephony Services
  5. Backup & Restore
  6. Security
  7. Audit

The SLA is governed by both the response time and the resolution time. Response time does not mean resolution. Response time is the time in which you will be contacted by a IT operations team member to triage/troubleshoot the issue.

Here is how we prioritize requests for support according to the following severity guidelines:

  1. Highest Severity (Response: Within 15 minutes)
    Impacts the whole business unit (Department); Employee Termination; Involuntary Employee Termination; Phone System Affected; etc.
  2. High Severity (Response: Within 1-4 hours)
    Workstation failure; etc.
  3. Normal Severity (Response: Within 2-4 hours)
    Causes partial loss of productivity for an individual user; Cannot Receive Emails; etc.
  4. Low Severity (Response: Within 24-48 hours)
    Hardware Approval; Software Upgrade; Email setup in Blackberry; A user needs administrative assistance; etc.
  5. Very Low Severity (Response: Within 1 week)
    Enhancement requests are logged as Severity 5-Very Low Priority, but are reviewed and scheduled by the Network Team Advisory Board.

For an SLA to be honored the “Technology Resource Utilization Policy” should be used to bring accountability amongst the stakeholders and the Network Team. The purpose of the SLA is to ensure that the proper elements and commitment are in place to provide optimal data processing services for the business function.

Share this:
  • Digg
  • del.icio.us
  • Facebook
  • Google
  • LinkedIn
  • Reddit
  • StumbleUpon
  • Technorati
  • TwitThis

Must-Do | Should-Do | Nice-to-Do

Whenever I speak about Priorities, I describe it as a Cold War for “A Beautiful Mind”. Almost everyone I know is overwhelmed with work and most of them are unable to decide on their priorities.

I receive over 400 email messages each day (with virtually no Spam, so they are all legitimate). Currently I am a member of two departments; Product Management and the Network Team. I also work on at least 10+ projects under direct management supervision. Each day I attend at least 2 meetings (in-person/conference calls) and I have multiple walk-in corridor one-to-one conversations each time I walk to/from my desk.

In such a varied environment, one of the most difficult choices is to prioritize work and make sure you deliver your work on time without loosing focus of your other priorities.

How do I prioritize my work?

  1. I make a list of all tasks and activities which I need to accomplish.
  2. I divide my work into these three categories 1) Must-Do 2) Should-Do 3) Nice-to-Do
  3. I give the highest preference/score to requests from the senior management and my direct reports.
  4. If an email is sent on a “High Importance” notification I give it my attention.
  5. If I am mentioned in the “To”, I give it my attention. If I am mentioned in the “cc” or “bcc” field I partially assume the person is trying to keep me in the loop.
  6. I identify the areas in a task for which I am accountable for. This way I take ownership of the allocated task and prioritize accordingly.
  7. If I am allocated an “Action Item” in a meeting, I choose to complete it before the next meeting. I also make it a point to browse through the agenda and revise the previous “Meeting Minutes” before I join a meeting.
  8. I consider the real world limitations on execution of a work plan.
  9. If my current skill set is inadequate for the task allocated to me I will discuss it upfront with the management and try to find an alternative replacement for the task.
  10. If I am stuck in a complicated scenario I run down the “Prisoners Dilemma” model for Game Theory to identify the best available option which will allow me to prioritize my work.
  11. I do not waste excessive time on low-priority tasks.
  12. At the end of each day and the end of each week I try to reconcile with my daily & weekly scheduled tasks and I reorganize them according to meet the needs. Tasks may move to a higher priority as a deadline draws near.

To accomplish any task raw data needs to be filtered so that it becomes information; Information needs to be transformed so that it becomes knowledge. This complex environment of work prioritization involves structuring of data into relevant information by scanning, selecting and justifying data into useful knowledge.

With the idea that there should be a measure to control the work, I use Outlook’s “Calendar” and “Task” options to constantly remind me of meetings and incomplete tasks. I try to answer any questions/emails in a real-time fashion.

These twelve areas are a starter kit to appropriate prioritization in a complex organization. Work prioritization cannot be an afterthought; it is a project which must be resourced.

Share this:
  • Digg
  • del.icio.us
  • Facebook
  • Google
  • LinkedIn
  • Reddit
  • StumbleUpon
  • Technorati
  • TwitThis