Thoughts on People and Process

The “Agile Manifesto” states that “We value Individuals and Interactions over processes and tools”. What? Some have taken that statement and interpreted it to mean that when it comes to design and development … “No Process” is required! In fact if we look further in the manifesto we see clearly that the value of process and tools is indeed recognized. The manifesto is trying to impart the importance of people and interactions. If we have a brilliant process that is defined and documented and yet drop the ball when it comes to people and interaction we will surely miss the mark every time. Therefore, while there is value in process and in tools service providers must value the people and interaction with them more.

In her book titled “The ITSM Process Design Guide” Donna Knapp stresses the importance of “Just Enough Process”. When designing ITSM processes such as Service Level Mgmt, Change Mgmt, Incident Mgmt and others, service providers could miss the mark and over design the process. An over designed process more often than not could create more bureaucracy, ambiguity, and frustration than it could ever deliver business value.

This ITSM process design guide is used as a source document in training for those practitioners who want to acquire a “Certified Process Design Engineer” certification. In addition to understanding how to design, re-engineer, or improve processes, there is a section that supports this same idea that we see in the Agile Manifesto. In order for a process to ensure valued outcomes the “people” aspect and the management of organizational change are essential.

“A key to successful organizational change is proactively planning for the change and the inevitable emotional responses that the change will evoke. Successful organizational change takes time and effort and must occur with people and for people, and not to people.”

For more information on:

How to design, re-engineer, or improve processes with just enough process while valuing people and interaction
How to become a “Certified Process Design Engineer”
And… how to gain 38 PDU’s

http://www.itsmacademy.com/certified-process-design-engineer-cpde-course-accredited/

For more information on people and processes:
http://www.itsmacademy.com/itsm-process-design-guide-book/

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