Your Process Is Either Improving or Deteriorating

Do you ever notice you can hear things over and over and then there is that one moment where a comment or phrase all of a sudden shouts at you with real meaning and significance? I’d like to share one of those aha moments with you. I recently took a class called Certified Agile Process Owner (CAPO). During that class the instructor, Donna Knapp responded to a learner and said …

“Remember that your process is either improving or it is deteriorating”.

For some reason while thinking about that from an Agile Service Management perspective I thought REALLY?! That is so very true. If we think about it, by the time we define, deploy and utilize any set of process activities the objectives could change, the technology used certainly has changed and the overall requirements for any one of those process activities or procedures could have changed.

Today we all know that business requirements are dynamic. All the more reason for taking an iterative approach to process design. For those of you that understand how taking an iterative approach to software development brings value, the idea and concepts are the same. I learned that each process is built and potentially released in small, frequent increments. New procedures and behaviors are introduced gradually, providing greater opportunity for normalization as well more frequent feedback and input to guide the future direction of the process. The Agile Service Management Guide also states that, dependent increments can be built simultaneously or in succession. Most importantly, the organization can test the boundaries of “just enough” process throughout the service lifecycle.

While considering ITIL best practice guidance I thought that this is what ongoing CSI is really all about? Agile Principles and Scrum allow us to optimize our ITSM processes in an efficient manner. Agile Service Management is agnostic when it comes to frameworks and best practice. It is clear that elements of LEAN, DevOps, ITIL, Scrum and Agile can all be leveraged for the two main aspects of Agile Service Management, those two being “Process Design” and “Process Improvement”. Hmmm… If my process is deteriorating is it dying? An iterative and incremental approach to process design allows ITSM processes to mature organically and holistically. Let’s do the right things right, improve rather than deteriorate and consider Agile Service Management. It is the next logical step.

Learn the skills needed to help make your IT Operations more Agile
Certified Agile Service Manager (CASM) and Certified Agile Process Owner (CAPO)

To see all ITSM Academy's Agile Service Management offerings:
http://www.itsmacademy.com/agile/

Comments

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People: Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products: These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group . As a service provider, we can’t stop there! We must know what the contracts of our service offering are and be able to put them into context as required by the customer. Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include: Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods. Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you. You the consumer own these and they are yours to take with you. Note: Goods may not always be provided for every Service Offe

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

Search