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

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