Claims:1. A processor-implemented method for improving Information Technology (IT) agility in an organization, said method comprising:
collecting, via one or more hardware processors, at least one organization specific data as input, by a transformation system;
determining current maturity level of the at least one organization, via the one or more hardware processors, by the transformation system;
assessing at least one requirement of the at least one organization, via the one or more hardware processors, by the transformation system;
identifying at least one difference between the current maturity level and the at least one assessed requirement, as a gap, via the one or more hardware processors, by the transformation system; and
generating at least one recommendation to bridge the at least one difference, via the one or more hardware processors, by the transformation system.

2. The method as claimed in claim 1, wherein the at least one requirement is defined as a benchmark in terms of at least one of a process and product in the organization, in the transformation system.

3. The method as claimed in claim 1, wherein the IT agility is provided across at least one of a system, process, and organization dimension.

4. A transformation system for improving Information Technology (IT) agility in an organization, said transformation system comprising:
a hardware processor; and
a storage unit, said storage unit comprising a plurality of instructions, said plurality of instructions cause the hardware to:
collect at least one organization specific data as input, by an Input/Output (I/O) module of the transformation system;
determine current maturity level of the organization, by a maturity assessment module of the transformation system;
assess at least one requirement of the organization, by a recommendation engine of the transformation system;
identify at least one difference between the current maturity level and the at least one assessed requirement, as a gap, by a gap analysis module of the transformation system; and
generate at least one recommendation to bridge the at least one difference, via the one or more hardware processors, by the transformation system.

5. The transformation system as claimed in claim 4, wherein the transformation system is configured to define the at least one requirement as a benchmark in terms of at least one of a process and product in the organization.

6. The transformation system as claimed in claim 4, wherein the transformation framework is configured to provide the IT agility across at least one of a system, process, and organization dimension.
, Description:FORM 2

THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENT RULES, 2003

COMPLETE SPECIFICATION
(See Section 10 and Rule 13)

Title of invention:
SYSTEM AND METHOD FOR IMPROVING INFORMATION TECHNOLOGY (IT) AGILITY OF AN ORGANIZATION

Applicant:
Tata Consultancy Services Limited
A company Incorporated in India under the Companies Act, 1956
Having address:
Nirmal Building, 9th Floor,
Nariman Point, Mumbai 400021,
Maharashtra, India

The following specification particularly describes the embodiments and the manner in which it is to be performed.

TECHNICAL FIELD
[0001] The disclosure herein generally relate to data analytics, and, more particularly, to improve organizational adaptability by improving Information Technology (IT) agility of the organization, using data analytics.

BACKGROUND
[0002] According to studies, average lifespan of Standard&Poor (S&P) 500 companies have come down to 15 as of 2012, as opposed to 67 in 1920s. There are various factors/challenges that affect lifespan of companies, a significant one being tough competition they face in a world where customer demands are changing at a much faster rate. As the demands are changing at a rapid pace, companies are expected to be adaptable to changes, and those which are not, fail to stay alive in the competition. The Banking and Financial Services Industry is in the midst of such a disruption as well triggered by the digital revolution.
[0003] Any organization can have multiple verticals and internal units working synchronously, and delays or inefficiencies of one unit can affect productivity and overall output of the organization. Various techniques are being used by the organizations to improve adaptability and agility of the organization to cope up with changing requirements. However, the existing systems that are being used for improving organizational output rely on trial and error methods, and do not provide a holistic, definite and efficient mechanism for improving organizational adaptability and agility. Further, the existing systems require constant user interventions at various stages of data processing and analytics and do not provide recommendations based on the right benchmarks.

SUMMARY
[0004] Embodiments of the present disclosure present technological improvements as solutions to one or more of the above-mentioned technical problems recognized by the inventors in conventional systems. For example, in one embodiment, a transformation system for improving Information Technology (IT) agility in an organization, the transformation system comprising a hardware processor; and a storage unit, the storage unit comprising a plurality of instructions, the plurality of instructions cause the hardware to collect at least one organization specific data as input, by an Input/Output (I/O) module of the transformation system; determine current maturity level of the organization, by a maturity assessment module of the transformation system; assess at least one requirement of the organization, by a recommendation engine of the transformation system; identify at least one difference between the current maturity level and the at least one assessed requirement, as a gap, by a gap analysis module of the transformation system; and generate at least one recommendation to bridge the at least one difference, via the one or more hardware processors, by the transformation system.
[0005] In another aspect, a processor-implemented method for improving Information Technology (IT) agility in an organization. The method comprising collecting, via one or more hardware processors, at least one organization specific data as input, by a transformation system; determining current maturity level of the organization, via the one or more hardware processors, by the transformation system; assessing at least one requirement of the organization, via the one or more hardware processors, by the transformation system; identifying at least one difference between the current maturity level and the at least one assessed requirement, as a gap, via the one or more hardware processors, by the transformation system; and generating at least one recommendation to bridge the at least one difference, via the one or more hardware processors, by the transformation system.
[0006] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS
[0007] The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the description, serve to explain the disclosed principles:
[0008] FIG. 1 illustrates a functional block diagram of a transformation system for improving IT agility of an organization, according to some embodiments of the present disclosure.
[0009] FIG. 2 is a flow diagram illustrating steps involved in the process of improving IT agility of the organization, using the transformation system, in accordance with some embodiments of the present disclosure.
[0010] FIG. 3 is a flow diagram illustrating steps involved in the process of assessing requirements and generating recommendation(s) for improving IT agility of the organization, using the transformation system, in accordance with some embodiments of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS
[0011] Exemplary embodiments are described with reference to the accompanying drawings. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. Wherever convenient, the same reference numbers are used throughout the drawings to refer to the same or like parts. While examples and features of disclosed principles are described herein, modifications, adaptations, and other implementations are possible without departing from the spirit and scope of the disclosed embodiments. It is intended that the following detailed description be considered as exemplary only, with the true scope and spirit being indicated by the following claims.
[0012] Referring now to the drawings, and more particularly to FIGS. 1 through 3, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments and these embodiments are described in the context of the following exemplary system and/or method.
[0013] FIG. 1 illustrates a functional block diagram of transformation system for improving the IT agility of an organization, according to some embodiments of the present disclosure. In various embodiments, the transformation system 100 improves the IT agility across different dimensions such as but not limited to system, process, and organization. The transformation system 100 includes an Input/Output (I/O) module 101, a maturity assessment module 102, a gap analysis module 103, a recommendation engine 104, a hardware processor 105, and a memory module/ Knowledge Engine 106.
[0014] The I/O interface 101 is configured to provide at least one channel with suitable communication protocol to enable communication between the transformation system 101 and at least one external entity. The external entity can be any or all of another transformation system, one or more user equipment, one or more external database(s), and so on required to execute any function of the transformation system. The I/O interface 101 is further configured to provide at least one suitable interface for the components of the transformation system 100 to interact each other. The I/O interface 101, by providing a suitable interface, collects at least one organization specific data pertaining to at least one organization, as input. The I/O interface 101 further provides the collected organization specific data as input to the maturity assessment module 102. In an embodiment, the I/O interface 101 collects data of different formats and types as input. The organization specific data can be pertaining to one or more functions/characteristics/attributes of the organization as a whole, and/or specific to that of one or more units of the organization. A few examples of the organization specific data that can be collected as input by the I/O interface are data pertaining to IT system design characteristics of the organization, data pertaining to engineering methods, practices, and tools, and data pertaining to various strategy and release approaches in the organization. The design characteristics can refer to and cover information such as but not limited to verticals of the organization, functionalities, and reporting structure. The ‘engineering methods’ can refer to parameters such as but not limited to technologies/processes being used across different verticals/functional areas of the organization. ‘Tools’ can refer to mechanical/software tools being used to support the engineering methods and/or any other requirement in the organization. The strategies and release approaches also are industry and/or organization specific. The I/O interface 101 can be further configured to receive data from at least one external entity (for example: stakeholder) as input to address a specific problem statement in response to which agility recommendation is to be provided.
[0015] The memory module 106, can be configured to store, in at least one associated database, data pertaining to benchmarks/best practices with respect to various verticals/processes/functions/practices and so on that matches a set of characteristics of an organization. The benchmarks and best practices vary according to certain characteristics of an organization. For example, benchmarks that suit an organization that is 10 years old and having 1000 employees is different from that of an organization that is 5 years old and having 600 employees. In addition to the age and number of employees, one or more factors such as but not limited to area(s) of operation(s), targets and so on also can affect benchmarks set for a company. Accordingly, standard benchmarks as well as customized benchmarks can be stored in the memory module 106. Further, for each group/team/vertical of an organization, different benchmarks/best practices can be set, and the same can be stored in appropriate databases of the memory module 106. The memory module 106 can be further configured to allow access to all or selected data for one or more other components of the transformation system 100. The memory module 106 can be further configured to provide secured data access to all or selected components of the transformation system 100 and/or to any external entity which requires access to data. The memory module 106 can be further configured to allow storage of target IT agility level for one or more organizations. The memory module 106 and the contents stored in the memory module 106 act as a Knowledge Engine. The memory module 106/ Knowledge Engine comprises of one or more databases related to best practices knowledge, benchmarks, and so on.
[0016] The maturity assessment module 102 is configured to collect the organization specific and/or third-party inputs from the I/O interface 101, and process the collected inputs further for assessing current maturity level of the organization. In an embodiment, the maturity assessment module 102 assesses the current maturity level of the organization by comparing the organization specific input and/or input collected from one or more external entities with the set benchmarks/standard practices. In an embodiment, maturity assessment involves determining current status of various processes/functions/practices in the organization.
[0017] The gap analysis module 103 collects information pertaining to the current maturity level of the organization as input, from the maturity assessment module 102, and performs a gap analysis using the data collected. In an embodiment, the gap analysis module 103 performs the gap analysis by comparing data pertaining to the current maturity level of the organization with the benchmarks/ standard practices, and identifying extent to which the current processes/functions/practices differ from an expected level as indicated by the benchmarks/ standard practices.
[0018] The recommendation engine 104 is configured to collect the output of the gap analysis module 103, and identifies at least one requirement to be met by the organization so as to achieve a targeted IT agility level as represented by the benchmark. The recommendation engine 104 further determines at least one action to be taken, and associated steps, and provides recommendation(s) to achieve the targeted agility level.
[0019] The hardware processor 105 can be configured to collect data as well as instructions from one or more of the other components of the transformation system 100, and execute corresponding action(s). The hardware processor 105 can be any processor that has capabilities to handle the data processing requirements of the transformation system 100.
[0020] FIG. 2 is a flow diagram illustrating steps involved in the process of improving IT agility of an organization, using the transformation system, in accordance with some embodiments of the present disclosure. In order to perform the IT agility transformation for an organization, the transformation system 100 collects (202) at least one organization specific data pertaining to the organization, as input. A few examples of the organization specific data are total number of employees in the organization, age of the organization, requirements in terms of IT agility, field of operation, client and service type (if applicable) and so on.
[0021] By processing the collected input(s), the transformation system 100 determines (204) a current maturity level of the organization. In an embodiment, the maturity level is in terms of IT agility, in terms of multiple associated parameters (for example number of employees, responsibilities, work-place arrangements and so on, pertaining to various verticals/functions in the organization that account for IT agility of the organization as a whole and/or of a vertical/section of the organization), and represents status of IT agility in the organization. Further, requirements of the organization are assessed (206). In an embodiment, requirement assessment involves identifying steps to be taken for the organization to achieve the target IT agility level.
[0022] Further, one or more recommendations/suggestions are generated (208) by the transformation system 100, wherein the recommendations are to be implemented in the organization so as to achieve the target IT agility level. By providing appropriate recommendations, the transformation system 100 addresses at least the following problem statements in an organization:
1) Benchmark and Enhance
2) Define
3) Fix and Improve
[0023] Benchmark and Enhance: This involves at least one of:-
i. Assessment and enhancement of IT architecture in the organization for greater agility
ii. Assessment and enhancement of engineering processes for greater agility and efficiency
iii. Building an automated tool chain for improved productivity, efficiency, and automation
iv. Assessment and enhancement of workspace design for greater collaboration and innovation.
[0024] Define: This involves at least one of:-
v. Re-defining organization structure for improved business collaboration and efficiency
vi. Defining ideal governance structure, contract models for agile program execution
vii. Define the right engineering methodology for each type of product
viii. Define a continuous learning and performance assessment model for IT organization
[0025] Fix and improve: This involves at least one of:-
ix. Improve the time to market/delivery cycle time
x. Improve the quality of delivery
[0026] The steps in method 200 can be performed in the same order or at least one other order, as required. Further, one or more steps in Fig. 2 can be removed as per requirements.
[0027] FIG. 3 is a flow diagram illustrating steps involved in the process of assessing requirements and generating recommendation(s) for improving IT agility of an organization, using the transformation system, in accordance with some embodiments of the present disclosure. In the requirement identification process, the transformation system 100 compares (302) the determined current maturity level of the organization with the target IT agility level, and identifies (304) one or more differences between the determined current maturity level of the organization with the target IT agility level as gap(s).
[0028] Further, at least one step to be executed by the organization to achieve the targeted IT agility level is determined (306) by the transformation system 100, and suggestions/recommendations are provided accordingly. In an embodiment, the recommendations are provided in the form of a prioritized road map that the organization can follow so as to achieve IT agility. The steps in method 300 can be performed in the same order or at least one other order, as required. Further, one or more steps in FIG. 3 can be removed as per requirements.
Example implementation scenario:
[0029] For the purpose of determining changes to be made in an organization so as to achieve IT agility, the transformation system 100 is configured to store one or more databases that can act as a reference point of benchmarks related to various best practices with respect to different dimensions of the organization. Consider an example below:
CARTRIDGE ASPECT PROCESS AREA PRACTICE PRACTICE_MATURITY_LEVEL WEIGHTAGE CURRENT MATURITY
System Agility Core Processing & Integration Business Process Leverage of Business Process Modeling Tools Adoption in Pockets 0.15 0.5
System Agility Core Processing & Integration Business Process API-fication of Services Initiated Pilots 0.1 0.25
System Agility Core Processing & Integration Technology Focus Technology Standardization Adoption in Pockets 0.15 0.5
System Agility Core Processing & Integration Technology Focus Leverage of Service Oriented Architectures Good Level of Adoption 0.15 0.75

Table. 1
[0030] A benchmark database is also created and maintained by the transformation system 100. In order to generate the benchmark database, various dimensions in the organization are identified first. Further, for the identified dimensions, parameters such as but not limited to aspect(s), process area(s), practice(s), and choice(s) are identified and listed in the database. Further, for each entry in the database, current maturity score, process gap, and priority are determined and listed against the corresponding entry in the database. For instance, assume that one dimension listed in the benchmark database is ‘System Agility’. Further, ‘Core Processing & Integration’ corresponding to the system agility dimension is listed as ‘aspect’ that is related to the ‘system agility’ dimension. Further, for the listed aspect, processes ‘business process and technology process’ are identified and listed as the matching ones. ‘Practice maturity level’ corresponding to the selected processes also are considered. ‘Practice maturity level’ is user input which represents current state/status of a process being considered. Further, for each process listed, weightage, and current maturity also are determined.
[0031] The current maturity is then compared with the corresponding benchmark to determine ‘process gap’ if any. The process gap is identified as difference between the current maturity and the benchmark. This is depicted in Table. 2. For example, current maturity of the first practice listed in Table. 2 is 0.5, whereas the benchmark for the same process is 1. So, the process gap here is (1- 0.5 = 0.5), which indicates that there is a difference between the current maturity level and the benchmark.
DIMENSION PROCESS AREA PRACTICE
CURRENT
MATURITY BENCHMARK
PROCESS
GAP
System Agility Business Process Leverage of Business Process Modeling Tools 0.5 1 0.5
System Agility Business Process API-fication of Services 0.25 1 0.75
System Agility Technology Focus Technology Standardization 0.5 1 0.5
System Agility Technology Focus Leverage of Service Oriented Architectures 0.75 1 0.25

Table. 2

[0032] As the current maturity of the process is less than the benchmark set (0.5<1), recommendations are to be generated to improve the process and match the maturity level with the benchmark. This is depicted in Table. 3. Last column in table. 3 indicates time period and duration for which each process is to be executed to meet the benchmark.

DIMENSION PROCESS AREA PRACTICE
CURRENT_ MATURITY PRIORITY DURATION
System Agility Business Process Leverage of Business Process Modeling Tools 0.5 1 6
System Agility Business Process API-fication of Services 0.25 3 12
System Agility Technology Focus Technology Standardization 0.5 1 6
System Agility Technology Focus Leverage of Service Oriented Architectures 0.75 2 12

Table. 3

[0033] The written description describes the subject matter herein to enable any person skilled in the art to make and use the embodiments. The scope of the subject matter embodiments is defined by the claims and may include other modifications that occur to those skilled in the art. Such other modifications are intended to be within the scope of the claims if they have similar elements that do not differ from the literal language of the claims or if they include equivalent elements with insubstantial differences from the literal language of the claims.
[0034] The embodiments of present disclosure herein addresses unresolved problem of IT agility in organizations. The embodiment, thus provides mechanism to assess current IT agility level in an organization, and generate recommendations to improve the current agility level to meet a target agility level.
[0035] It is to be understood that the scope of the protection is extended to such a program and in addition to a computer-readable means having a message therein; such computer-readable storage means contain program-code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The hardware device can be any kind of device which can be programmed including e.g. any kind of computer like a server or a personal computer, or the like, or any combination thereof. The device may also include means which could be e.g. hardware means like e.g. an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. Thus, the means can include both hardware means and software means. The method embodiments described herein could be implemented in hardware and software. The device may also include software means. Alternatively, the embodiments may be implemented on different hardware devices, e.g. using a plurality of CPUs.
[0036] The embodiments herein can comprise hardware and software elements. The embodiments that are implemented in software include but are not limited to, firmware, resident software, microcode, etc. The functions performed by various modules described herein may be implemented in other modules or combinations of other modules. For the purposes of this description, a computer-usable or computer readable medium can be any apparatus that can comprise, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
[0037] The illustrated steps are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments. Also, the words “comprising,” “having,” “containing,” and “including,” and other similar forms are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items. It must also be noted that as used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural references unless the context clearly dictates otherwise.
[0038] Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present disclosure. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term “computer-readable medium” should be understood to include tangible items and exclude carrier waves and transient signals, i.e., be non-transitory. Examples include random access memory (RAM), read-only memory (ROM), volatile memory, nonvolatile memory, hard drives, CD ROMs, DVDs, flash drives, disks, and any other known physical storage media.
[0039] It is intended that the disclosure and examples be considered as exemplary only, with a true scope and spirit of disclosed embodiments being indicated by the following claims.