Skip to main content

Shifting Sands - Minimum Viable – What is it Really?

For high performing IT providers, the sands are shifting. If you are getting certified in ITIL 4, DevOps, or Agile Service Management you hear that we have to “Think BIG and ACT small!”. Minimum Viable Products and Minimum Viable Processes (MVP) are on the move. Historically, IT organizations delivered products and processes into production with huge batch runs or the big bang approach. This method is fraught with issues, escalations, and constant firefighting. These large releases are tightly managed, governed from the highest levels, and require participation from all parts of the organization. The days of large batch runs that take months to create and war rooms staffed 24×7 for weeks before and after the release, have given way to small incremental deployments.

In comes Minimum Viable Products/Processes: 
High performing organizations know that deployments that deliver value to the consumer fast are required. The idea is not to stage, stage, stage until you have a huge batch big bang deployment, but instead get something that will help your business customers and consumers get the job done now!

This example taken from a recent class that was delivered by the DevOps Campus at ITSM Academy is a great visual. If the goal of your customer is to get from point A to point B, rather than delivering non-usable bits at a time until you get the Cadillac of transportation you could deliver them a skateboard. 


The happy/sad faces indicate that you continue to get feedback along the way and evolve the incremental delivery of value throughout the relationship with your customer. This follows the second way in the “Three Ways of DevOps" and allows for the ITIL 4 Best Practice of embedding continual improvement into your deliveries while co-creating the service with your customer.

Recent DevOps Leader and 
Certified Agile Service Manager (CASM) courses (YES! This applies to Process Design too!), introduced these key concepts for creating a Minimum Viable Product or Process that are worth sharing. 

Whether it is a process, product, or software that you are deploying; these questions help you to focus on the type of MVP that delivers value: 
  • What kind of idea do we want to test? What kind of prototype should we build?
  • How quickly can I give it to my customer? How do I listen – focus groups, metrics?
  • What should we track? How do we know we have enough data to adjust course, pivot?
  • How do I keep repeating the process until I get it right?
  • What does the final confirmation look like?
Educate & Inspire!


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