Today Industry across various organizations is on a journey towards multiple transformation initiatives with the core aspect of bringing Business Agility to their existing construct. As they embark on the journey of transformation initiatives unfortunately each initiative operates in siloes due to reasons across limited Perspective, Partial Collaboration and Inefficient Execution approach.

The Organization Culture and hence the Mindset restricts their thoughts towards being able to transform across areas of Overall Strategy, Customer Experience, Products (& Services), People, Organization and Technology. What is the intrinsic motivation behind driving towards this huge initiative and the desire to adopting to change.

Through this session we intend to share the characteristics of a business transformation and the mindset change required to work towards the various transformation initiatives which potentially cuts across;

1. Agile Transformation :

• Ingrain the concept of “think small” – thinking away from monolithic and breaking smaller towards microservices adoption

2. Business Process Re-engineering

• Incubate “Build and own concept” with federated business objectives focused towards business process improvement and outcome based approach

3. Engineering Transformation

• Achieve Predictability ingrained while building system – Anticipate the system of failure
• Reliability Incubate – Resilient and Fault tolerant system
• Quality – Defect reduction across life cycle using Automation

4. Workforce Transformation

• Cadre building focused towards Engineering skills
• Utilizing the concept of “Core” and “innersourced” team to leverage Critical skills across the board.

5. Technology transformation - Open Source and Cloud Adoption etc

• Time to market by creating pipeline in matter of minutes
• Pattern Implementation (Immutable Infrastructure, Blue-green deployment, Canary release)
• Executable across multiple platforms and Teams. Infrastructure(Cloud) Agnostic

6. Improving Operational Efficiency.

• Cost Effective - Effective utilization of development and operational teams
• Being able to groom stories into buckets allowing to distribute across "Core" and "Innersourced" teams hence allowing flexibility of operating model,
• Speed – Improving processes and playbook adoption

Enterprises and their individual feature teams are in a rush to build DevOps Pipelines with all the right reasons.

While central teams are provisioning tools to be consumed at Enterprise level, individual feature teams are focusing heavily on building pipelines instead of building and enhancing business priorities.

This results in "duplicate pipelines” solving the same problem of automation for build, test, package, infra, deploy and release using the given toolsets. - This results into duplication of efforts and redundancy.

We intend to share our approach to build a pipeline enabled to for polygot programming languages and consumption patterns supporting various areas including.

• A single click to deploy the complete pipeline infrastructure and app pipeline
• Support multiple cloud deployment (AWS, Azure, etc…)
• Adoption of open source tools
• Clustered or non-clustered infrastructure deployments

We will also emphasize on the implementation experience of the advanced Engineering practices in the area of immutable infrastructure, Chaos Engineering, blue-green/canary deployment.