Agile – My Product Backlog is Out of Control!

If a product backlog is growing faster than you deploy, if it cannot be prioritized properly, and business outcomes suffer, are your “Agile” efforts really working?

Agile software development is a group of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, continuous improvement, and encourages rapid and flexible response to change.

A broken product backlog is only one of many symptoms that something is broken. If there are bottlenecks in change, delivery and deployment than what real value can evolutionary and faster development bring to the business? It is time to consider “Agile Service Management”.

Agile Service Management ensures that agile principles and methods go beyond software development to ensure the product backlog is in control and that we, as service providers, can meet the speed of delivery while producing quality outcomes for changing business requirements. Agile Service Management is framework agnostic and does not attempt to redefine any of the ITSM processes. ITIL® and other service management frameworks have done an excellent job of describing best practices for managing IT services, including the processes that are necessary for a complete service lifecycle. Agile Service Management supplements those frameworks with agile thinking and practices.

A Certified Agile Service Manager (CASM) is the operational equivalent of a Certified ScrumMaster (CSM). Working together, ScrumMasters and Agile Service Managers instill agile thinking and integrate them into an integrated approach throughout the entire development, delivery and operational lifecycle stages.

The Agile Service Manager bridges a relationship with the organization’s software development ScrumMasters. Cross‐populating Agile practices, vocabulary and automation across all sides of IT will serve to increase speed and consistency. Collaboration between Agile Service Managers and ScrumMasters helps to create and maintain a DevOps culture.

Simply put, we can not silo agility. If we silo these methods to “development” and do not integrate with our service management process activities in the entire value stream we are likely not to see the benefit and efficiency hoped for.

Get educated and start your journey to become a “Certified Agile Service Manager”. http://www.itsmacademy.com/casm

Comments

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

Search