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

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

Search