Peter Maddison - How to maintain governance when adopting Agile practices in large organizations?

What is the background situation/context for your probe?

As we undergo digital transformations in organizations we bring in new tools to enable capabilities that will accelerate the delivery of value to customers. Problems occur in the traditional enterprise when they try to balance the adoption of these new tools with the operational overhead of managing them. Switching to SaaS solutions isn't always an option (data locality, scale, cost) and companies run into unexpected issues with managing their newly added complexity. Additionally, regulatory requirements may force organizations to internally manage these capabilities. Done poorly I've seen this badly impact the ability for teams to form. 

What is (or has been) your hypothesis?

My hypothesis is to building this into the delivery platform itself allowing for the build-out of opinionated pipelines and the reduction in decision points in the delivery team. In order for this work, there needs to be a clear understanding of what is supported by automation. This is best achieved by having a central platform team responsible for seeing these capabilities are in place. However, advanced teams can often find this restricts them too much. 

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

Building a tools strategy, creating a community and appropriately allocating funds can all help. Allowing developers to experiment while still ensuring we have the right governance in place requires a careful balance. Understanding how different companies have approached this problem at the different stages of maturity and scale will allow us to see what is working and what is not. I've done this effectively within a few large organizations but adoption has been a problem. What have people done to solve this?

Is there a specific skill/technique you would like to learn/explore at this coach camp?

Ways to properly manage this tooling complexity and thoughts on the best ways to streamline the adoption of new tools. How do people manage governance within the delivery process at scale when the regulators come knocking?

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.)