wipro.com IT4IT & DevOps Transformation The Common Ground

Transcription

1 wipro.com IT4IT & DevOps Transformation The Common Ground

2 DevOps transformation draws on the many concepts from Lean and Toyota Production systems. Terminologies such as Kanban board, continuous improvement, product backlogs to name a few. These words are some of the more manufacturing and assembly line production oriented terms which has been applied in the context of technology. The objective is to have a fast paced, continuously improving pipeline of deployable code ready to be productionized. Seamless orchestration and integration of development, building and operations activities using automation and team cohesiveness are some of the unique characteristics of DevOps delivery process. Thus IT4IT is an overarching IT management framework that promotes agile philosophy through DevOps implementation. IT4IT reference architecture prescribes guidelines towards efficiently managing the business of IT with degree of predictability to the desired business outcome. There are four value streams that IT4IT categorizes in terms of the core of IT. These are Strategy to Portfolio, Requirement to Deploy, Request to Fulfill and Detect to Correct in an integrated manner with data traceability at its core. IT4IT reference architecture maps to DevOps delivery process and architecture through the various functional and information models across the 4 value streams. IT4IT is an overarching IT management framework that promotes agile philosophy through DevOps implementation. The IT4IT reference architecture promotes the agile philosophy of requirement gathering, development deployment and change management, leveraging the functional, information, services and integration models 2

3 IT4IT & DevOps IT4IT emphasizes on process and method agnostic vendor neutral framework for managing the business of IT. It shows how functional and information models across value streams can be harnessed to effectively designit service portfolios, meeting or exceeding customer expectations, fulfilling demand requests and proactively resolving production issues even before it disrupts the business. IT4IT proposes reusability and repeatability in the prescribed processes architecture so as to enable more time for innovation and value creation.it emphasizes on many elements of the agile manifesto such as Customer collaboration and co-creation of value Workable software instead of stream of documentations Continuous feedback and traceability early on in the development cycle Emphasis on Value to the Left of the software development lifecycle Less number of team handoffs and more team cohesiveness Design IT Portfolio for value creation Strategy Requirement Exceed customer expectations in delivery through collaboration and co-creation of value added services to Portfolio to Deploy Detect Request to Correct to Fullfill Proactively remediate and diagonize incidents, problems and manage changes with minimal disruption to business Catalog, fulfil and manage service usage Figure 1: DevOps style continuous feedback loop across IT4IT value streams 3

4 Design of DevOps process architecture is based on the principles of performing plan-build-test-deploy cycles continuously and getting feedback early on in the cycle. One of the key focus of DevOps is to have less number of features per release and have more releases over a period. The orchestration of activities ranging from story design, coding, automated testing, continuous build integration, automated release and configuration management and auto provisioning of environment need to be performed in small batches by DevOps teams. It has to be done repeatedly while at the same time getting timely feedback. The typical size of the team shouldn t be more than with emphasis on interchangeability of roles. A term in DevOps referred to as Generalizing Specialists where DevOps engineers can wear multiple hats at the same time. Accelerating the flow of software delivery from ideation to production based on agile philosophy with continuous feedback loop is what makes DevOps tick. The term DevOps having been coined by Patrick Debois breaks the traditional boundaries between development and operations. There is a tight integration between automation tools and processes which enable the highly streamlined deployment pipeline to function without bottlenecks. IT Security and compliance is also built end-to-end in the DevOps tool and process chain. Collabration Plan > Develop Build Performance Virtualize Security Instrument Validate Release Operate Functional Provision & Deploy Automated, Integrated, Collaborative Figure 2: Automated, Integrated, Continuous and Collaborative Deployment 4

5 Common ground So, how exactly does IT4IT reference architecture map to DevOps delivery framework? In the Strategy to Portfolio value stream, the functional component Portfolio Demand looks at all incoming requests for IT Services. The Portfolio Backlog item keeps record of all those incoming demand requests originating from Defects, Incidents, unresolved Problems and Changes as well as new IT initiatives. The prioritization of these requests are done by balancing the strategic and operational demands and other parameters such as cost value analysis, business priority, impact on architecture and service roadmap. Enterprise Architecture functional capability comprising of defining the service architecture. This can be mapped to identification, analysis and prioritization of DevOps epics and stories. In the Requirement to Deploy value stream, the project functional component comprises of IT initiative data which is analogous to having DevOps sprint cycles. Defects, Test and Build components are analogous to having automated testing, continuous build integration and feeding defects back into the product backlog to be scheduled for the next release cycle. The release component signifies what goes into the designing of the release features for services. This in a DevOps perspective is also significant based on which it is easier to manage the tight and continuous integration between continuous coding, testing, build integration and having continuous deployment pipelines. It uses a continuous feedback loop from operations in the form of Defects, Incidents, Problems or Changes. Having a source control, build and build packaging capabilities are also key functional components of the Request to Deploy value stream. Similar in DevOps architecture, source control, versioning of the latest builds and doing integration of multiple builds into a build package ready for deployment are critical work items for the DevOps engineering teams. In the Request to Fulfill value stream the emphasis is on the how part of service fulfilment cycles and making it abstracted from the end users. It is also to ensure end users (internal or external customers) have a great experience in ordering services through shopping carts and catalogs. It is analogous to the continuous deployment on production ensuring that the DevOps engineering is able to manage the deployment pipeline of quality code securely and steadfastly into Production environment. It also means ensuring that the Production environment can be configured both from an infrastructure and application points of view on demand either on cloud or hybrid or on premise. 5

6 In the Detect to Correct value stream, objective for the functional components is to proactively monitor and diagnose failures in business systems. It is to report out changes in event states in terms of incidents and problems. The problems which are likely to have far reaching impacts on business or architecture or both need to be reevaluated by business as changes. In the DevOps world this is akin to product owners in DevOps teams identifying and scheduling changes as part of standard release cycles or emergency releases having done due diligence in carrying out automated regression, functional and security testing. In this value stream emphasis is also on keeping the Configuration Items records in the most current updated state. The importance cannot be over emphasized because in DevOps too the automated build packaging and integration depends on having the latest Configuration Item (CI) in the repository. The IT4IT reference architecture promotes the agile philosophy of requirement gathering, development deployment and change management leveraging the functional, information, services and integration models. It is clear to see that Agile methodology of continuous integration and continuous deployment of small and frequent release features is fully supported by IT4IT. The origin for the DevOps product backlogs being the new services, defects or request for changes from the 4 value streams. Therefore we conclude DevOps architecture is supported and reinforced in the overarching IT4IT architecture framework. Conclusion The IT4IT reference architecture promotes the agile philosophy of requirement gathering, development deployment and change management leveraging the functional, information, services and integration models. It is clear to see that Agile methodology of continuous integration and continuous deployment of small and frequent release features is fully supported by IT4IT. The origin for the DevOps product backlogs being the new services, defects or request for changes from the 4 value streams. Therefore we conclude DevOps architecture is supported and reinforced in the overarching IT4IT architecture framework. 6

7 About the author Sandipan Chakraborti: Sandipan is a senior Enterprise Architect working for the Wipro Global Enterprise Architecture practice. He has provided EA transformation solutions and domain solution architectures to several fortune 100 customers globally over the span of his career of more than 17 years. Prior to Wipro was with PwC consulting in the Strategy & Architecture SBU. He holds a bachelor in Electrical & Electronics Engineering from University of Mysore and a masters in IT and Computer Engineering from Indian Institute of Engineering Science and Tech, Shibpur. He may be reached at Sandipan.chakraborti@wipro.com. About Wipro Wipro Limited (NYSE: WIT, BSE: , NSE: WIPRO) is a leading information technology, consulting and business process services company that delivers solutions to enable its clients do business better. Wipro delivers winning business outcomes through its deep industry experience and a 360 degree view of Business through Technology. By combining digital strategy, customer centric design, advanced analytics and product engineering approach, Wipro helps its clients create successful and adaptive businesses. A company recognized globally for its comprehensive portfolio of services, strong commitment to sustainability and good corporate citizenship, Wipro has a dedicated workforce of over 170,000, serving clients across 6 continents. For more information, please visit wipro.com or write to us at info@wipro.com. 7

8 DO BUSINESS BETTER CONSULTING SYSTEM INTEGRATION BUSINESS PROCESS SERVICES Wipro LTD 2017 IND/BRD/APR 2017-MAY 2017 No part of this booklet may be reproduced in any form by any electronic or mechanical means (including photocopying, recording and printing) without permission in writing from the publisher, except for reading and browsing via the world wide web. Users are not permitted to mount this booklet on any network server.