Skip to main content

ITSM Learnings from Fusion 2010

I recently attended a great opportunity to connect, learn and grow at the itSMF USA Fusion 10 Conference in Louisville, Kentucky. It was a wonderful chance to see old friends and acquaintances, to meet and make new friends and learn from some of the most articulate and impressive speakers on ITSM and ITIL available in the industry. I came away with some key points that I thought I would share with you so you can also gain the benefit and value of the data, information, knowledge and wisdom presented at the Conference.



Here are my key take0aways:
  • Service Management is alive and well. A new wave of users and supporters has emerged and were present at the show. I saw and met so many new people. I was impressed that ITSM and ITIL has not simply remained in the hands of a core group of users but has found continued life among new industries and implementers.
  • ITSM and ITIL seem to be growing especially among colleges and university IT departments and in the medical and scientific fields as well. For the first time I saw a large number of people from our institutions of higher learning discovering the value and benefit of using ITSM approaches in providing support to faculty, students and staff. This is especially touching given my own background and work as the ITSM Professor! 
  • Social Media is becoming a growing force within ITSM and ITIL usage. Using tools such as Twitter, Facebook, Foursquare, Linked-In and numerous others can help to underpin the efforts of ITSM and ITIL rather than just being seen as potential security threats or detractors from proving value through services. Functions like the Service Desk and IT Operations Management can use these social media tools to help provide even better support while increasing responsiveness to customers and users and increasing and tracking customer satisfaction.
  • Cloud computing is still an unknown quantity among ITSM and ITIL users. Not that the tools have not gained a measure of maturity—they have. Rather, the traditional support personnel and IT departments just do not seem to know what to make of something that is not under their full control. ITSM and ITIL do not go against the concepts of the “cloud”. Rather users of ITSM and ITIL need to accept that the methods of governance, management, control and maintenance can just as easily be applied to “virtual” situations as to more tangible, physical realities. It takes the ability to see things from the bigger perspective, rather than just a detailed operational perspective. Cloud computing and its connection to ITSM is definitely an area to watch for the future. 
  • ITSM frameworks continue to grow, mature and improve by using their own Continual Improvement ideas.   Organizations are often adapting guidance from multiple frameworks.
  • People are the most important part of a great ITSM and ITIL effort. Without people Service Management is simply a set of processes and guidance. It is the people side of ITSM that must not be forgotten. Leadership, governance, management, control and support are all defined in terms of the people who use these ideas and those customers and users that we serve.
  • The best way to learn more about ITSM and ITIL is to meet others (whether in classes taken together, at conferences, local interest group meetings, or on webinars and calls) and spend time talking, asking, discussing and sharing about what works and does not work, how ITSM works and most important WHY it works!
I hope to be able to connect, learn and grow with many of you in the future at similar shows and events. Do not hesitate to meet others and share your experiences and insight about ITSM and ITIL. By working together on our shared journeys we can all benefit and gain value!

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…