Skip to main content

Agile_ITSM – Ingredients for Success! Part 2

In part one of this topic we discussed the “dynamic” needs of business and also discussed how we the service provider must be “agile” to meet those dynamic needs.  Understanding of course that none of that can be done without the support of “processes and technology” and the best practices that enable them. 

In part two of “Agile_ITSM – Ingredients for Success” I would like to discuss the most important ingredient for the success of all service providers: people.  

People

People with their skills, their diversity, their productivity and innovation are at the heart of agility and speed to deliver quality in a world where business needs and demand are dynamic.

Empowerment! Trust the intentions of your people.  We have to be careful not to hobble the productivity with micro management of staff members and their effort.  When considering trust, it is not just a matter of whether a single member of the team or workgroup is trustworthy but do you trust that the team will fulfill the mission?  Will it be ok if they do not do that in the way that you would? Do you trust it enough to get hands off and let it run?  There will always be check-in points and deadlines but sometimes it is difficult in a culture where management has been all about control. Agile encourages self-organizing teams. Let the team govern themselves with guidance and leadership and most importantly support from management and then they will truly be empowered.  Guide, coach, encourage and lead the group.  Empower with clear direction to the individual but also empower the team or workgroup to work as a single entity able to ebb and flow with the changing tide.  Being rigid will not help us to deliver with quality and speed when the business requirements and demand are dynamic.

Shifting the Culture – It’s all about the “People”.  When it comes to provisioning a service and Agile_ITSM we are really talking about a cultural shift.  Many of us have been or are still caught in the internal or external silos that manage the design, transition and/or operation of our services. Those silos often end up in a lot of finger pointing with crossing T’s and dotting I’s for the sake of saying “I did my job”.   How much time, money and resources are wasted collecting data, documenting tasks, and reporting on “It’s not my fault”?  We know this is counterproductive.  In the same way that we want our departments to function with clearly defined roles, common goals and outputs, we also want our processes, technology and workgroups that form to focus on business value.  We cannot continue to silo departments, processes, and technology and expect to be agilet. 

I particularly like this quote from a recent Scrum Alliance webinar where Bob Hartman stated “SCRUM is a framework for completing work that recognizes and embraces the realities of life and the value of people."

Process cannot be executed without people.  Projects cannot be completed without people.  “People” are our single most important and not-so-secret ingredient.  If empowered, it will be the “people” that make it work!


Comments

Popular posts from this blog

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