DevOps Transformation - Key Factors to predict timeline

Many organizations looking for DevOps transformation are putting a common query before vendors and service providers on “how much time it will take to do DevOps transformation”. Quite a few time, Vendors end up referencing other client example and quote experience from there. In most of such cases, information being asked and information being provided does not have any co-relation.

Answering such query on spot may be difficult unless we have not understood the current context completely. Any reference to other client may not be at all relevant in the given context.

This blog will help to such clients and vendors to understand factors influencing estimation of DevOps transformation timeline.

DevOps Transformation Estimation (Timeline) = Function of(CoI, SoT,TD&SD, TD, F)

Abbreviations:

CoI -- Circle of Influence

SoT -- Scope of Transformation

TD&SD -- Technical Debt & Strategical Debt

TD -- Transformation Dimensions

F -- Funding

1.      Circle of Influence ( CoI ) :

Let’s understand the circle of influence. Who are our sponsors? What they can influence back in their own organizations. What all is mandated to them? For example an Engineering head may not have authority over architectural practices. In this case, it is better to understand if multi disciplines within organization are aligned for proposed transformation or it is coming through individual function head. This will influence timeline decisions.

2.      Scope of Transformation ( SoT ) :

Timeline decisions also get impacted by the fact that how big will be the transformation. Whether this will be for a few applications, or for a department / function or LoB or at enterprise level? Whether all layers of enterprise (system of records, system of differentiation and System of engagement) will be considered. Understanding of overall spectrum will help determining while planning for transformation timelines.

3.      Technical Debt & Strategical Debt (TD&SD) :

Before we plan for DevOps transformation timeline, it is very important to understand underlying Technical debt and Strategical debt. Technical Debt may be in form of manual process, poor test automation coverage, architecture complexity, monolithic vs Microservices or poorly maintained code base. In terms of Strategical debt, you may would like to consider failed initiatives in past, wrong selection of tools and frameworks, redundant tools in ecosystem, multiple systems and tightly integrated architectural strategy etc.

All these considerations will impact overall DevOps transformation timeline, hence better to have understanding on those in current context.

4.      Transformation Dimensions ( TD ) :

Many times, clients looking at DevOps transformation does not have full awareness on multiple dimension of DevOps transformation. In most of the cases, individuals have very vague idea on different dimension of transformation. This is also important for vendors providing services, because it depends on their understanding and maturity model followed as well. For some it may be only automation, whereas for other it may encompass Agile + Process + Automation + cloud + architectural simplification + cultural change + Organizational change management and so on.

Let’s be very clear with Transformation dimension while evaluating Transformation timeline projections.

5.      Funding ( F ) :

Finally, funding is important element, as it will have an ultimate impact of all other key dimensions discussed above. Many times vendors over commit as their model encompasses many of the dimensions in their maturity model whereas client does not have either understanding or money to spend on.

Hope if you have read so far, you must have enjoyed understanding key factors to be considered for making projections for DevOps transformation timelines. Please like, comment or suggest your views.