Skip to main content

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

Popular posts from this blog

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 policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: René. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…