ITSM Professor

Business requirements are not static.  The rate of dynamic change for new evolving business needs is increasing as you are reading this blog.  The traditional software development practice for building one big honking monolithic program to provision services is not applicable to the explosion of need. This old way of thinking and deploying is not conducive to Agile. To understand a microservice let’s first start with our traditional view point.  For this purpose, let’s say that you want to build a “Self Service Catalog”.   To make this seemingly complex service less complex let’s break it up into many microservices.   For example; one microservice might be for “Creation of Online Account” another for making a selection from the “Service Catalog”.  One might be to “Select Payment Method” and yet another microservice for “Invoicing” and so on.  These are many microservices or sub-services that will eventually be connected via Application Programming Interfaces. These microservices are …

Artificial Intelligence (AI) is on the move and the race is on. In previous years, and for the most part even today, AI has been dominated by the worlds high tech companies like Google, Microsoft and Amazon.  Regardless of where you work or the size of your business, the industry is starving for more information and true knowledge management.  AI goes beyond knowledge management and moves us into knowledge engineering.

As found in an MIT Technology Review article, Microsoft has its own AI-powered cloud platform.  You may have heard of Azure.  This team is joining with Amazon to offer Gluon.  It is an interesting name. I don’t know its origin, but it is essentially an open-source deep-learning library. Gluon is supposed to make building neural nets – a key technology for AI that crudely mimics how the human brain learns – as easy as building a smartphone app.
It is no longer just a high-tech game.   With the onslaught of cloud services, any/all service providers (including enterprise-…

What is your biggest challenge when trying to increase the flow of work through your DevOps or Continuous Delivery Pipeline?  In a recent conversation an IT Director laughingly said that his greatest challenge was that they can not get the development “Divas” to recognize that change approval and compliance requirements are necessary and that it takes time.
I chuckled as I thought to myself what those development “Divas” were thinking.   Maybe their thoughts were that those paranoid risk adverse Change and Compliance process people do not understand that we need to get this work to the finish line and we need to go fast.  Sound familiar?
This is not an uncommon issue.   The us-vs-them environment, if not corrected, will continue to disrupt IT service delivery and therefore, business performance.
We must recognize that DevOps and Continuous Delivery (CD) do not stand alone.   It is not just the tools and automation and, although it is more about culture, it is not just culture either. …

Appropriate testing is THE differentiator for high performing IT organizations.
What is the Same?
Tests need to be classified according to the attributes of the system or the product that is to be tested.  Test types include:
Unit Test - This is a method that validates that the code statements satisfy assertions.
Static Code Analysis – Testing that checks source code logic and consistency.  Static testing evaluates code against development standards and guidelines. Code execution is not required.
Dynamic Analysis – This type of testing might also be referred to as “Functional Testing”. In this type of test, code is executed against positive and negative functional scenarios.
Code Coverage – Measures the percentage of relevant lines of code tested.
Integration Test – This form of testing will help to determine if code changes work after a code merge.   Integration testing may also be referred to as smoke test, sanity test or build test.
Compatibility Test –  This is used for testing feature …

The combination of continuous monitoring with continuous testing and analytic tools can provide a broader strategic view of test results.  This view is necessary to collect, aggregate and organize test data that enables a gain in confidence for each release. 
Key Concepts for Realizing Your Test Monitoring Strategy:
Determine continuous test monitoring priorities: Some examples of problems that continuous test monitoring can help with include intermittent failures caused by marginal designs, marginal test designs, environmental condition changes not detected by individual tests, memory leaks, varying starting conditions, interactions with other systems, system topologies and performance degradation within the margin of a test. These can and will accumulate over time. The best practice for continuous monitoring indicates that the problems of most concern to a specific product or DevOps environment will be monitored.

Regression test product areas even though there were no expected change…