Well, for starters, Quarterbacks are backbone players of the offense line in the American football. It's their responsibility to handle the football through the game, call plays and make decisions during the game. However the game is concentrated on the other players - tacklers, guards and so on.
Arvind
Join us for a Webinar on August 26.
Here is an initiative from the ServiceDesk Plus team for its esteemed customers. We are hosting a Webinar that would help you get trained to successfully roll out Change Management using ServiceDesk Plus.
This Webinar also aims at providing you an insight on the best practices in implementing a Change and how Change Management can be simplified through realistic approach.Title: Change Management:A Realistic Approach using ServiceDesk Plus
Date: Wednesday, August 26, 2009
Time: 2:00 PM - 3:00 PM EDT
After registering you will receive a confirmation email containing information about joining the Webinar.
System Requirements
PC-based attendees
Required: Windows 2000, XP Home, XP Pro, 2003 Server, Vista
Macintosh -based attendees
Required: Mac OS X 10.4 (Tiger ) or newer
Space is limited.
Reserve your Webinar seat now at:
gotomeeting.com/register/318533915
Arvind
I recently came across several discussions on Service Level Agreements and I must say that I am surprised to see the various requirements in handling SLAs.
This made me as curious as a cat to know and understand the use of SLAs in different organizational environment – small, medium and big – and the scenarios that kindle such SLA caution.
Several IT Managers and IT Administrators I am acquainted with have put forth some interesting discussions that they came across while handling SLA at their work place.
One such scenario is say a SLA is set for all High priority tickets to be resolved as 1hour and once the ticket is created the ServicDesk assigns the ticket if it is not automatically routed, then the technician handles the ticket where the some time already lost.
Let me explain one such scenario: An SLA to resolve all High Priority tickets was set as 1 hour. A created ticket was manually assigned to a technician after a while when it was not automatically routed. Time was already lost before the technician set to resolve the ticket issue. Communication with end user, comprehension of the issue, work around, resolving techniques and so on eat up more time. The ticket can be closed after the end user’s response. In such a scenario, what sort of SLA would be applicable fitting all criteria – Assigning time, Response time, Completion time and so on?
Any nouvelle experience in SLA handling is more than welcome. Take the poll and leave your valuable comments.
Hey found this in Swissmiss & Steve Clayton's blog - quite interesting.
Chk the complete Stats Here.
Arvind
Arvind
Arvind
