45 COOC An Agile Change Management Method
45 COOC An Agile Change Management Method
45 COOC An Agile Change Management Method
Abstract— Successful completion of the Industry 4.0 or inseparable couple. In fact, agile change wants to be an
Future Industry programs requires support for women and men operational and concrete response to all the new problems
to drive them. The challenge of aligning skills is complemented related to change (more responsiveness, more flexibility for
by the modernization of their practices and tools. All businesses the organization). An agile change management method has
are changing and change management techniques have become already been defined [6] and we propose an extension of this
standard practice in most organizations. However, the so-called method with (1) the identification of supporting tools and (2)
"traditional" methods are limited and it is now proposed change an improvement of the workshops cycle. We also propose an
management methods called "agile", borrowing the philosophy evaluation of our method. The research questions we want to
of agile development methods to reduce the obstacles to change
answer in this work are the following. QR1: Does an agile
by injecting a bit of agility in their way of doing things. We first
argue about this proposal with the results of a questionnaire to
change management induce a better adoption of change?
define the importance of people implication in a change project. QR2: Does the tools proposed by the COOC method can help
We then propose a method based on the agile change model [1] to handle an agile change management?
by proposing tools adapted to each phase as well as an A state of art is given on section 2 about changes and what
optimization of the experimentation phase. An evaluation of the it entails for the organization, as well as about Agile methods,
proposed method is performed with a retrospective on a real their inherent concepts and what they bring to a company. A
case and the interview of an expert.
questionnaire to identify if agility could be useful in a change
Keywords— Change management, Agility, Method
management is proposed in section 3. The tools proposed by
the Concept Of Continuous Change (COOC) method are
I. INTRODUCTION presented in section 4 and evaluated in section 5. We conclude
in section 6.
Change refers to the change from one state to another.
Change in a company has its advantages and disadvantages. It II. RELATED WORKS
can be experienced as a trauma from employees accustomed
to a certain routine, methods and ways of working that can be A. Change, Agility and Agile change management
their own. Change can be experienced as a destabilizing, In business leaders’ speeches, the word Change has
disruptive element, but it also allows a company to adapt to become a permanent leitmotif. Executives do not hesitate to
changes in its environment and time. Industry 4.0 raises fears present it as a virtually automatic solution to the changing
among employees as robots and algorithms were seen, even markets, technology, laws or as the necessary dynamics for
recently, only as machines dedicated to supplanting humans any business. Often, business managers will say these words
[2]. This perception has evolved, as individuals see the "Change or disappear".
benefits of digital technology in terms of workplace well-
being, for example with robotic assistance for handling heavy However, what is a change? For there to be a change, there
loads, or with augmented reality for maintenance operations must be a significant break in modes of operation. This rupture
[3]. But even if we have gone from robots called to take up will force individuals to try to adapt. The transition from the
our jobs to concepts of augmented workers, all worries have present to the future is not a micro-adaptation that can be
not been swept away. Individuals remain concerned about the regarded as a minor evolution but a real leap that will make
possible disappearance of their position, its obsolescence obsolete some or even all of our existing way of workings in
caused by technology or, at best, its profound transformation. favor of a new way of doing things, to do better than before.
The change will be considered as such if the several elements
Before any change, a company must then anticipate future undergo a transformation, like practices, work conditions,
problems related to this change. It must think of the best way tools, management, business, strategies and so on [6].
to drive the change and have also to implement a specific
management to support its employees to combat any change Until the late 1990s, the dominant approaches in the
resistance. Change management involves all the operations development of computer projects were based on the planning
and actions carried out within an organization to handle the and subdivision of the project into sequential lots. Faced with
change with its employees and its environment. the need for adaptability, continual change and responsiveness
Organizational agility [4] is the ability of the company to imposed by an increasingly competitive technological market,
adapt on an ongoing basis in response to an environment the rather "conventional" methods have been put into question
characterized by complexity, turbulence and uncertainty. It by the emergence of new methods called "agile". These are
echoes agile methods, developed for several years in the field generally described as iterative, incremental, self-organising
of computing and originating from the Agile Manifesto, and more adaptable to change. Agility can be defined as a
written in 2001 [5]. It is necessary to see Agile methods more response to the widening and hardening of competitive
as a paradigm, a state of mind, a philosophy than as simple environments that allows to instill in organization,
methods to apply. Change and Agile methods are an responsiveness and performance [7]. Applied to the software
world, the notion of agility refers to the adaptive capacity of
2) Experiment phase (equivalent to the phase Information – TABLE VII. EXPERIMENT PHASE COMPARISON 2
part 1 and 2) Facts Agile change contributions
- Lack of information - The deployment would have
The two parts of the Information Phase have been - Many new tools to adopt been experimented during the
voluntarily grouped together as they are part of the so-called - Blurred Situation experimentation phase
experimental phase or "Experiment" of agile change. They - Lack of knowledge of new business (participatory workshops), so the
correspond to both parts of the project information period. - Lack of knowledge of new change would have been gradual
colleagues and less brutal
Through the Experiment phase, during the workshop cycle,
- Lack of team alignment - Familiarization of new tools on
employees will be able to get the answers to their questions - Many Resistance to Change the part of employees during the
and the information they want and thus reduce their worries. - Numerous requests for departures. experimentation phase.
The various participatory workshops will enable them to
reduce their fears and involve them in the heart of the change 4) Anchor phase
project, transforming them into actors of change. At the same
time, the steering cycle will enable the change teams to carry It was useful to add the "anchor" phase in the grid of
out more or less change actions (participatory workshops, potential inputs of agile change. This phase did not take place
trainings, sensitizations, etc.) in order to obtain a level of and therefore did not really exist in the facts described. This
information, understanding, adherence and satisfactory phase would have allowed absolutely all employees of the
participation. The employees' opinions will therefore be taken company to anchor the change in their DNA and that of the
into account for the change, this will enable a change company. This would have made it possible, in the near future,
management and a "over-tailor-made" change for the to live change better and thus reduce the various resistance to
company and its employees. Future teams (composed of change encountered (table 9).
former BANK A employees and BANK B employees) will
also be able to get to know each other and discuss their TABLE VIII. ANCHOR PHASE COMPARISON
activities and problems encountered during these workshops. Facts Agile change contributions
This will have the effect of strengthening the links between - Employees and managers - Habit of change
the employees but also of cross-linking the knowledge unaccustomed to change - Anchored change in company DNA
between the teams. By making them test and experiment with - Change becomes customary for
employees
change, workshops, more playful than simple training, would - Less resistance to change.
have made it possible to reduce the various aversions to
change developed by employees, as shown in Table 6.
5) Conclusions on the case study
TABLE VI. EXPERIMENT PHASE COMPARISON 1
Analysis of this case study highlighted the inputs related
Facts Agile change contributions to the use of the COOC method and agile change as part of a
- Concerns of employees, - Information obtained during
Blurred Situation participatory workshops
change project or inducing a change in the enterprise. The key
- Lack of information, - Concerns reduced through point corresponds to the various workshops of the experiment
Business activity slowed participatory workshops phase, which make it possible to involve individuals in the
- Employees reluctant to get - Opinions of employees taken into change, thereby reducing frustrations, Questions and different
involved account aversions to change. During a career, there is a good chance
- Choice not given to - Employees become actors in their that an employee will be confronted with a major change, so
employees change
- Numerous questions raised - Ownership of change by employees involving him in the change, ask for his opinion and listen to
by unanswered employees - The steering cycle will enable a him will allow him to better live the change. His company will
- Feeling of abandonment customized change management also be satisfied because an employee feeling happy and
- Lack of information - Fears and blur reduced thanks to considered in his work will exploit all his potential at the
- Employees are undergoing participatory workshops service of his company.
change - The newly created teams will be able
- Numerous aversions to to meet as soon as these workshops are C. Interview of an IT manager
change. held.
The interviewee was responsible for production
management and technical support in the BANK A. During
3) Experiment phase (equivalent to the phase Deployment) his career, he had the opportunity to live and lead several
Table 7 shows the possible improvement of the use of an projects involving a change management but also to live
agile change in this phase. Deployment or promulgation of the several change projects.
change would have occurred during the experiment period. For our interviewee, there are four main objectives when
The various participatory workshops, aimed at experimenting carrying out a change management, the first is to explain the
with change, would have made it possible to inculcate change change to the people who will be impacted by it, then explain
among the individuals involved. The change would have been to them the issues of the change, why we want to change, and
more progressive and less brutal. In the agile change, the
then support the different people in the change in order to V. CONCLUSION
better make them adhere to the change. Finally, the final With an increasingly competitive global market,
objective is to measure the effectiveness of change. When companies around the world must be increasingly efficient
presented with the Agile change management and the COOC and innovative in order to satisfy their customers. This global
method, our expert highlighted the fact that the first phase of context leads companies to adapt to the new requirements of
the agile change model is paramount. If the change and its their customers so as not to lose market shares to decline and
objectives are poorly defined from the beginning, the change disappear. Companies are therefore forced to change more and
project will not succeed. The important thing in a change more often and more quickly.
project is to have a true vision of the project, why we will
realize this project, but also to share and communicate around In the context of Industry 4.0, companies announce
this vision. profound changes that will have a lot of implications on its
employees. Defining a vision, strategy and goal for Industry
He proposed a possible improvement point during the 4.0 projects, setting up a change project plan as well as
"define" phase which would be to include agility during this employee involvement are central factors for effective change
phase as well. A possible practical case would be to rely on management. Accomplishing changes will be very difficult
indicators (such as Indexes of Engagement and without a company culture that supports those changes as
Recommendations (IER)), harvested through digital experiences of change can be traumatic for the employees of
interviews with employees of the company, Presenting a a company and for the company itself. Agile methods, widely
number of figures showing the need for change in the used in the world of IT development, bring a different vision
enterprise, so that the need for change is expressed by the to project management and offer better guarantees for project
employees themselves. Thus the future people concerned by success. Agility echoes agile methods, widely used in the
the change will adhere from the beginning of the project. It world of computer development. We made a questionnaire to
will also be necessary to explain the ins and outs of the project evaluate the impact of people implication in a change project
so that individuals feel involved from the beginning of the and highlight its importance. We concluded that an agile
project. It will thus be possible to involve individuals in the change management should help the change adoption in the
definition phase. process of a change project (RQ 1).
He found the experiment phase very interesting because it Building on the agile change model of [1,15], we have
will allow people to experience change and experience it in provided the tools to drive agile change and thus make change
real conditions. Providing and including on-demand training agile: the COOC (Concept Of Continuous Change) method.
(training cycles) is also an interesting element that can be We evaluate the method by a retrospective case study on a
applied in companies. bank migration and an expert interview. These assessment
Our expert thinks that the agile change model is applicable tools determined that the COOC method should allow a better
in a real company and that’s very important. The tools adoption of the change by the impacted collaborators (RQ 2).
presented in the COOC method will allow a good definition However, this method has a big limitation: by perpetually
of the change and then a good adoption of the change by the redefining change during the "Experiment" phase, one of the
concerned collaborators. The “anchor” phase of the change risks would be that the change would remain at the word stage
will flow if the definition and experimentation phases have and would never really be implemented. Another limitation
been correctly carried out, so individuals will more easily is that the fact that the company is in perpetual change could
assimilate the change or changes in the enterprise. We will still prove to be extremely resource-consuming and the change
have to be careful that the pace of change is not too high, could be detrimental to the company’s main activity. The
because people may have enough after a while. question that can be raised would therefore be How can an
D. Discussion on the evaluation enterprise can make performant business activity by
continuously change?
In the case study (migration of employees from BANK A
to BANK B), we highlight the fact that if the agile change had An on-going perspective is to actually find two similar
been adopted, the change would certainly have been adopted change projects in order to use the COOC method in a real
as well. Less reluctance would have been shown as people case and to have a real comparison with another method. The
would have been more implied in the change process and use of indicators will help to define if the change is going on
decisions. However, the case study, even if based on real facts, smoothly or not in all its phases and if the proposed tools are
is only a hypothetic one as we only pinpoint the areas where really pertinent.
an agile change management could have been an Another improvement is to define a bigger set of tools in
improvement. each of the phases, to apply accordingly to the context of the
The interview with the IT manager, who already deal with change project. Our questionnaire already highlights some of
change management, highlights the qualities of the agile the criteria that could be of use to decide between the tools
change model and the COOC method. In a change project or but there are a lot more of them and a bigger study is required
a change management project, it is vital to involve the people to define them.
involved in the future change from the beginning of the
project. It emerged from the interview that the phase of REFERENCES
experimentation allows to involve all stakeholders. [1] D. Autissier, K. Johnson and J-M. Moutot, « De la conduite du
Nevertheless, there is a future improvement axis which will changement instrumentalisée au changement agile », Question(s) de
management 2015/2 (n°10), pp 37-44, 2015
consist in adding agility to the define phase of the method.
[2] A. Weiss, A. Huber, J. Minichberger, M. Ikeda, “First Application of
Another important point emerged from this interview: the Robot Teaching in an Existing Industry 4.0 Environment: Does It
COOC method is applicable in enterprise, it is not a utopian Really Work?”, Societies 6 (20), 2016
methodology.
[3] M. Trojani, « Industrie 4.0 : mettre l’humain au coeur de la Participation rate (4: yes it is a priority / 3: yes in a 4 3 2 1
transformation », blog SAP, https://news.sap.com/france/2017/12/ partial way / 2: no but I would like / 1: no and it does not
industrie-4-0-mettre-lhumain-au-coeur-de-la-transformation/, 2017 interest me)
[4] F. Becker, “Organisational agility and the knowledge infrastructure”, Have you participated in project meetings?
Journal of Corporate Real Estate, Vol. 3 Issue: 1, pp.28-37, 2001 Have you produced diagnostics, analyses and
proposals for the project?
[5] The Agile Alliance, “The Agile Manifesto”, 2001 Have you considered integrating the elements of the
[6] D. Autissier and J-M. Moutot, « Méthodes de conduite du project into your activity?
changement », 2ème édition : « Diagnostic - Accompagnement – Have you tested some elements of the project in your
Pilotage », Dunod, 2010 activity?
[7] J-P. Vickoff, « Méthode Agile, Les meilleures pratiques,
Compréhension et mise en œuvre », QI, 2009 Wished information rate
[8] K. Lewin, “Psychologie dynamique : les relations humaines”, Presses Scale Signification Phase Rate
Universitaires de France, 1935 0-25% No information Annoncement 25 %
[9] D. Autissier and J-M. Moutot, « La boîtes à outils de la conduite du 25-50% Partial Information Exploration 50 %
changement », Dunod , 2013 50-75% Irregular Information Experimentation 75 %
75-100% Complete Information Déployment 80 %
[10] G. Teneau, “La résistance au changement organisationnel : Wished comprehension rate
Perspectives sociocognitives”, Broché, 2005
Scale Signification Phase Rate
[11] J. P. Kotter, “Leading Change”, Harvard Business School Press, 2012 0-25% No Understanding Annoncement 25 %
[12] R.M. Kanter, “The Change Masters”, Simon and Schuster, 1983 25-50% Wished Exploration 40 %
[13] L. Dietze, “Putting people front and center: user-centered change”, Understanding
ThoughtWorks blog, 50-75% Partial Understanding Experimentation 60 %
https://www.thoughtworks.com/insights/blog/putting-people-front- 75-100% Complete Déployment 80 %
and-center-user-centered-change, 2017 understanding
Wished adoption rate
[14] P. Alsher, “5 Implications for Change Management in an Agile
World”, IMA blog, https://www.imaworldwide.com/blog/5- Scale Signification Phase Rate
implications-for-change-management-in-an-agile-world, 2018 0-25% Rejection Annoncement 45 %
25-50% Low adoption Exploration 20 %
[15] D. Autissier and J-M. Moutot, « Le changement agile, Se transformer 50-75% Partial adoption Experimentation 60 %
rapidement et de manière durable », Dunod, 2015 75-100% High adoption Déployment 80 %
[16] A. Uzan, “Outils pour diriger : faire adopter le changement”, 2017 Wished participation rate
[17] G. Benoit-Cervantes, « La Boîte à outils de l'innovation », 2e édition, Scale Signification Phase Rate
Dunod, 2008 0-25% No participation Annoncement 20-40%
[18] M. Combe, “Change Readiness: Focusing Change Management Where 25-50% Low participation Exploration 40- 60%
It Counts”, PMI White Paper, 2014 50-75% Partial Participation Experimentation 60- 80%
[19] F-X. Duperret, J-M. Moutot and D. Autissier, “Passez en mode 75-100% High Participation Déployment 80-100%
workshop agile ! 50 nouveaux ateliers pour améliorer l'agilité de votre
équipe”, Pearson, 2018
[20] A. Rondeau, “Comprendre, mesurer et développer la capacité à changer APPENDIX B : CHANGE EVALUATION GRID
des grandes entreprises”, 2003 Context
[21] C. Torrelles, J. Coiduras, X. Carrera and S. Isus Barado, « Du (4 : always / 3 : often / 2 : sometimes / 1 : never) 4 3 2 1
changement dans l’évaluation du travail d’équipe : validation de l’outil Has the external environment (economic, political,
RUTE », 2014 social) had an impact on employees' perceptions and
practices regarding change?
Is change a priority for the company’s manager(s)?
APPENDIX A : QUESTIONNAIRE FOR ICAP BAROMETER AND Is there a real culture of change in the company?
WISHED VALUES, FOLLOWING [6]
Does the company strategy propose operational change
Information rate (4: regularly / 3: yes irregularly / 2: 4 3 2 1 projects?
yes once / 1: never) Is a change management method and/or tools available
Have you heard of the project? to employees?
Did your hierarchy introduce you to the project? Content
Did you receive any information about the project? (4 : always / 3 : often / 2 : sometimes / 1 : never) 4 3 2 1
Did you search for information about the project? Do employees assess the level of change in the situations
Comprehension rate (4: yes exhaustively / 3: yes 4 3 2 1 they face?
partially / 2: no but I would like / 1: no at all) Do employees change the way they do things after the
Do you understand the objectives and terms of the change?
project? Do employees have the opportunity to assess their ability
Have you solicited people or experts for a better to change themselves?
understanding of the project? Do employees have an idea of their own ability to change
Do you have a clear idea of what will change for you in their employees?
your activity? Is the management of change subject to a recognised and
Have you looked on the project and its topics? valued competence in the company?
Adoption rate (4: yes completely / 3: yes overall / 2: yes 4 3 2 1 Process
a little / 1: not at all) (4 : always / 3 : often / 2 : sometimes / 1 : never) 4 3 2 1
Do you think this project is useful for the community? Do employees communicate with each other on the
changes to be made and how to do so?
Do you think this project is useful for your business?
Do employees use the tools and resources available to
Do you think this project is well received by the them in terms of change management?
individuals concerned? Do employees define themselves as relays of change
Do you think that all the conditions are met for the Do employees see change as an opportunity to improve
success of the project? the existing one?
Are there indicators and/or tools for managing change?