Skip to main content

Product Backlog + Process Backlog = Success!

Flexibility and agility are key to success and business performance.  Many Service providers have adopted Agile methods to ensure that they can meet demand for increasing changes in business requirements.  Product Backlogs are common and are generally understood; but what about Process Backlogs?

Product Backlog – In the “Scrum Guide” Ken Schwaber and Jeff Sutherland describe the Product Backlog as an ordered list of everything that might be needed in the product.  It is the single source of requirements for changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.  A Product Backlog is never complete. The earliest development of it only lays out the initially known and best-understood requirements. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. As long as a product exists, its Product Backlog also exists. The Product Backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases. Product Backlog items have the attributes of a description, order, estimate and value.

Agile Process Design - applies the same approach to process design that software developers apply to product development.  Each process is built and potentially released in small, frequent increments.  New procedures and behaviors are introduced gradually, providing greater opportunity for normalization as well as for more frequent feedback and input to guide the future direction of the process. An iterative and incremental approach to process design also allows ITSM processes to mature organically and holistically.  Dependent increments can be built simultaneously or in succession.  Most importantly, the organization can test the boundaries of "just enough" process throughout the service lifecycle.

Process Backlog - In the "Agile Service Management Guide" Jayne Groll describes the Process Backlog as the single source of current or future process requirements.  This includes process activities, tool updates, plans, interfaces, documentation, training and improvements for a single ITSM process.  The Process Backlog continually evolves, is regularly re-prioritized and is never complete.  It exists as long as the process exists. It is solely owned and managed by the Process Owner.  The form and format of the Process Backlog is not prescribed - items can be captured in anything from a Kanban Board to a spreadsheet to a database.  It should be visible to all process stakeholders and readily available for inspection.  Each item in the Process Backlog should be expressed in a User Story. A User Story is a simple statement that describes what a user or process practitioner wants from an aspect of the process.  It is always written from the user's perspective and in their words.  It is not meant to include all of the details about the process aspect but is intended to encourage further dialogue and collaboration.

Like the Product Backlog, the Process Backlog is dynamic and evolves as the process evolves. End-to-end agility can only be achieved if Agile thinking and practices are integrated and exercised by both development and operational teams. Integrating ITSM processes with agility means that the service provider must adopt and adapt to new ways of thinking.  

If you are interested in learning more about Agile and Scrum from a products and process perspective or would like for yourself and your staff to become a Certified Agile Service Manager (CASM) or Certified Agile Process Owner (CAPO) click here 

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…