Preeti Desai - How do we go about bringing in the DevOps revolution in an organization?

What is the background situation/context for your probe?

Bringing in the DevOps culture in a service organization starts with the very basic aspect of the mindset of the organization. Shifting from a fixed mindset to a growth mindset is a huge shift and needs sustained efforts to do so. We have tried to bring in this mindset in our organization for the past 2 years which has been detailed out in the experiment related question. The context of the probe is to see how to bring in sustenance on the same.

What is (or has been) your hypothesis?

Change has to start with the right mindset of the Leadership. A change agent has to be identified at the start of the journey. However just 1 or 2 people who are the agents cannot bring in the revolution in the organization. The hypothesis is to ensure sustenance across the organization, as the change agents interact with one set of people, they will need to identify a similar set of change agents across the organization.

What is the experiment you would like to run (or you have run) and how can this experiment validate or invalidate your hypothesis?

Practical things done in our organization

  • Identified the innovators and the early adopters in the organization.
  • In terms of implementation, targeted the early adopters and on a cadence basis had touch points with the leadership to show the progress on the journey
  • Published the DevOps Maturity Assessment targeting the entire leadership to bring in their focus on the availability of the same
  • Implemented Lean Chai sessions with the DevOps enthusiasts across the organization. This is a learning forum with a monthly cadence.
  • We have a tracker where we track the traction on the number of projects on a month on month basis.
  • We publish the quarterly status of the initiative to our management and they same is then further published to the leadership
  • Came up with Process documents that are available at an organization level.
  • We would now like to identify more and more change agents for bringing in the DevOps Revolution in the organization. As and when such change agents are identified, we can get that specific business unit started on their journey (even here we would look at a focus few projects)
Is there a specific skill/technique you would like to learn/explore at this coach camp?

What has been done in other organizations is what I would like to understand more about at this coach camp.

Call for Papers CLOSED
Ended on Jan 25 '20 05:29 AM IST

Interested in attending the Agile Coach Camp on Oct 11th in Bengaluru? Read on...

It's been 12 Years and almost 110 viral Agile Coach Camps since our very first coach camp experiment. This year, Coach Camp co-creator Naresh Jain along with Jutta Eckstein and John Buck will lead participants in this Coach Camp in Bangalore, organized as part of the Agile India 2020 Conference.

Coach Camp Theme

As a coach, you're often the one who needs to drive and sustain change. Yet, how do you do this? What has helped and hindered you doing so and how can you best pass your experience on to other coaches or how can you best learn from other coaches?

This is the theme for this year's coach camp. To tackle this challenge, we invite you to try something new:

  • Currently, we face the following situation: Constantly driving change is getting more and more important for companies to survive in this VUCA world. At the same time, it is (or should be) the core skill of every coach – no matter if you coach individuals, teams, or organisations. However, sometimes it seems every coach has to come up with her own experience on how to drive change successfully.
  • Our hypothesis is that for driving change, every coach uses so-called probes, that are defined by small, safe-to-fail experiments based on hypotheses derived from reflection on the current situation as well as on theory. So, probing allows discovering (based on the hypothesis) what's working and what is not through one or several experiments. This allows to make sense of both the current situation but even more important of the situation we are aiming for. And if we create a knowledge base of our collective wisdom on probes we used (or intend to use) we can learn from each other.
  • Therefore, as an experiment we want to invite this year's coach camp participants to jointly discover, share, create, improve, and finally publish probes that help(ed) driving and sustaining change. As in a typical coach camp, we will use the Open Space format to explore different topics for driving change and we invite you to use probes to focus the discussions on these different topics. We anticipate as a result that the discovered and created probes will provide a foundation for such a knowledge base.

Registering for the Coach Camp

The coach camp is free of charge (financially) yet, for registration we ask you for the following:

  • Please click on the Add Paper button and submit your position paper. In your position paper, you will be asked to share an idea for a probe, consisting of a background situation (context), a hypothesis, and an experiment. This can be a probe you've implemented before, one you've discovered/heard of others implementing it, or you intend to implement. The probe should focus on the coach camp's theme: Driving Change.
  • The discussed probes provide a basis for a free and publicly accessible knowledge base.

Final Note

Please note, we want to invite you to use probes for the discussion and recording of the Open Space sessions. This is by no means an enforcement. We are well aware that there might be situations where probes are not the right means for discussing or/and recording a particular topic - and that is of course fine. After all, using probes for this coach camp is a probe in itself (and we are open to possibly invalidate our hypothesis.)