Skip to main content

Agile Service Management – Techniques and Methods

Most of us are aware that Agile can be used to improve the effectiveness and efficiency needed for software development.  Agile core values and principles are defined in the Agile Manifesto . But wait!  There is more! While there are many techniques, methods and frameworks that can be utilized to ensure agility within your organization, what is important to note is that they can and should be expanded beyond software development.  

Agile Values are realized via many different techniques and methods including:


Continuous integration - A software development practice where:
  • Members of a team code separately but integrate their work at least daily
  • Each integration goes through an automated build and test to detect errors and defects
  • The team collectively builds the software faster with less risk


Continuous delivery - Continuous delivery does not infer that you are deploying every day or every hour. It means that you COULD release when needed.  It is a software development practice where:
  • Software is always in a releasable state
  • Automated testing and deployment is standard
  • Continuous integration is the norm
  • Collaboration between Development and Operational teams (DevOps) is necessary
  • Organizations can rapidly deploy enhancements and fixes


Scrum - Scrum is a simple framework for effective team collaboration on complex projects. Scrum provides a small set of rules that create “just enough” structure for teams to be able to focus their innovation on solving what might otherwise be an insurmountable challenge.  While Scrum was originally intended for software development, it has been successfully applied to other types of complex projects and is”:
  • The most commonly applied Agile practice
  • Deceptively simple yet difficult to master


Kanban - A Kanban board makes work visible and enables team to:
  • Limit work in progress (WIP)
  • Measure velocity (quantity of work done in an iteration)
  • Design and improve processes (i.e. Change and Release)
  • Improve standard operation workflows


ITSM - ITIL defines the processes and best practices that underpin Agile Service Management:
  • ITIL promotes an integrated process approach around a service lifecycle


Lean - The goal of lean thinking is to create more value for customers with:
  • Fewer resources
  • Less waste


These are just a few of the techniques and methods that can be expanded beyond software development for Agile Service Management.  Agile Service Management (Agile SM) ensures that ITSM processes reflect Agile values and are designed with “just enough” control and structure in order to effectively and efficiently deliver services that facilitate customer outcomes when and how they are needed.   


If you are interested in learning more about Agile Service Management or if you would like to become a Certified Agile Service Manger (CASM) … http://www.itsmacademy.com/certified-agile-service-manager-casm-course-accredited/

Comments

Popular posts from this blog

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, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 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 1. 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.      ...

What is the difference between Process Owner, Process Manager and Process Practitioner?

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...