Skip to main content

Flow of Work

Agile Software Development is very well known and practiced in most organizations today in order to respond quickly to the ever increase in demand for IT Services.  Many of these organizations, while making some improvement, are not seeing the outcomes they had expected.  Why is this?   We are applying Lean methods, cycle time is increasing and yet, unplanned work, delays in deployment and unstable production environments remain.

Consider the time from idea to delivery as the “Value Stream”.  Through this Value Stream, we want to increase the “Flow of Work”.   We will never see the type of optimization that is required unless we look at this Value Stream as a whole.  Applying Agile, Lean, and even tools in development without integrating Change, Security and Operations will break down and decrease the Flow of Work.

DevOps helps with this idea.  Many companies, both large and small, are attempting to integrate the development and operations teams.  We have cloud services and things like infrastructure as code and Continuous Delivery (CD) techniques, which all help, but why aren’t we getting there?

If we really are to consider the entire Value Stream and the Flow of Work service providers must look at “Agile Service Management”.  Being Agile in only one segment of the Value Stream (development) will most likely create a huge bottleneck when you get to Change.   If the development team is working faster, faster, faster and it takes two or more weeks to turn around an approval for change what have you gained? As demand increases, and it will, the bottleneck becomes more and more of an impediment in the Flow of Work throughout the entire Value Stream.   We can no longer afford to silo Agile.
Agile Service Management - www.itsmacademy.com/agile
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.

There are two aspects of Agile Service Management: Agile Process Design and Agile Process Improvement

The goals and objectives of Agile Service Management include:
  • Ensuring that agile values and principles are embedded into every service management process from design through implementation and continual improvement
  • Improving IT’s entire ability to meet customer requirements faster
  • Being effective and efficient (lean)
  • Designing processes with “just enough” scalable control and structure
  • Provide services that deliver ongoing customer value
Agile Service Management encourages a continuous learning environment and promotes better collaboration between development and operational teams.  It enables DevOps and Continuous Delivery.   Without incorporating Agile Service Management service providers are at risk to miss the mark when it comes to the velocity and cadence that is required to meet changing business requirements and customer results.

Educate & InspireTo Increase Your “Flow of Work”!

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