Skip to main content

Agile Process … What?! Is That an Oxymoron?

To survive in today’s competitive business climate organization’s must respond quickly to their customers’ evolving needs and desires.  How many times have you heard that? We know from experience that an agile culture where agility is gained through people, process and tools can enable organizations to gain market share and competitive advantage.  And still, more organizations than not silo agile principles to software and product development. Ever wonder why, as an industry, we are not getting the types of returns that are expected from our efforts?

Agile software development alone will not get us there!  Other factors include:
  • Ability to quickly respond to customer feedback and needs – Customer engagement.
  • An understanding that the customer and business requirements are dynamic and that we must have agile processes in place to respond to them. (Not only agile development)
  • Sustained innovation and speed from idea to end of life for the service and processes.
  • Increased employee engagement, creativity and profitability and talent retention. This could include the support of DevOps, Agile Service Management and Agile Process Owner training and education.
  • New behaviors that are encouraged through experimentation and learning in Development, in Test, in Release and most importantly in Service Operation.
  • Making smaller incremental changes to processes as well as services.
  • A keen pulse on the cadence of demand and having processes in place to meet it. 
  • Agile Process Owners that are skilled enough to ensure incremental improvements that keep service management lean and adaptive.
Agile Service Management throughout the value stream is the only way that organizations will truly be able to achieve the level of agility and value that is required.  In order to obtain this, we must educate and inspire staff, managers and process owners.  Without agile processes that support the activities it will be difficult to streamline and also very difficult to automate. What if we were to have agile software development and then at the same time have overburdened, bureaucratic, change management and other ITSM processes?  What could we gain?  More importantly, how much is that costing?  

A process owner is the individual accountable for the performance of a process and for ensuring the process delivers value to its stakeholders.  Process owners manage the requirements of process stakeholders, translate those requirements into process performance objectives and oversee the entire process design and improvement lifecycle. We need agile people and must have agile processes to support customer and business dynamic requirements.  

It is becoming more apparent every day that we simply cannot silo “Agility”.  Having “Agile Process” is not an oxymoron.  In many cases Agile Service Management with agile process is the missing element in our formula for success.

To learn more about Agile Service Management or to obtain Certified Agile Process Owner information and certification:  http://www.itsmacademy.com/Agile

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 than 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

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 th