Skip to main content

Building a Community of Practice (Part 1)

What do you think would happen if everyone who attended an IT service management (ITSM) class – ITIL, ISO/IEC 20000, MOF – went back to work and talked to the person who sits next to them about how their organization could apply best practices? Or, what if everyone shared their ideas with just the people in their work groups. Those organizations would see tremendous benefit. Even small steps – think plan-do-check-act – can reap large benefits over time.



But why stop there? Many organizations have people in different departments and locations, perhaps even in different parts of the world, who must work together to realize the true benefits of a consistent, integrated approach to ITSM. A community of practice can be used to bring these people together. A community of practice (CoP) is group of people who are bound together by similar interests and expertise. Members are active practitioners who come together to share information, experiences, tips and best practices. Members provide support for each other to avoid ‘reinventing the wheel,’ and look for innovative ways to overcome challenges and achieve common goals.
A CoP can be an informal network of practitioners, or it can be created specifically with the goal of developing members’ capabilities and providing a forum for collaboration. Come back next week for ways to foster that collaboration and build a thriving CoP.

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

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

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th