Click here to close now.


@DevOpsSummit Authors: AppDynamics Blog, Carmen Gonzalez, Lori MacVittie, Elizabeth White, Sanjeev Sharma

Blog Feed Post

Michael Spayd on Coaching the Agile Enterprise

Noel Wurst: Hello. This is Noel Wurst with Skytap. I am speaking today with Michael Spayd. Michael's going to be speaking at the Agile 2014 Conference in Orlando, Florida, on Monday, July 28. It had a really interesting sounding session, and I just wanted to learn a little bit more about that session and some of the topics that may come up during it. 

Michael, how are you doing today?

Michael Spayd: I'm doing well.

Noel: Great. 

Michael: Thank you for hosting this, Noel.

Noel: No problem at all. Your session, again, on Monday, July 28, is titled "What would it mean to Coach an Agile Enterprise?" I noticed that the first sentence presents a huge challenge in enterprise level software development today. In your abstract you say, "Enterprise agility is both a hugely popular aspiration and a widely misunderstood buzzword.” That comes up a lot in agile, with the ability to “do agile” in so many different ways. 

Is that the reason that maybe enterprise agility is only an aspiration for many people, and not something they can call an accomplishment? That maybe the phrase is so loose or so misunderstood that, it’s like the difficulty in defining 'done' sometimes, that you get so many versions of it that it's hard to know when you've reached it?

Michael: I think you're definitely pointing in the right direction. I guess, what I'll say about it is that it's an aspiration because people want it. They want what they have experienced on their teams, on their agile teams: more harmony, more productivity or satisfaction, more customer value, and all that kind of stuff. They want that in a big way. They want that everywhere. They don't just want it on their team. They want it with their leadership. They want it in their organization's culture. They want it in the funding process. So that's what attracts people, I think, to it. 

Yes, different people mean very different things by it, from just scaling up the actual software delivery process, as if you could do that in isolation, and maybe to some extent you can, but along with that comes all kinds of cultural assumptions, and cultural beliefs and values, shared values, and organizational structures, and processes and policies and stuff that impact your ability to do that. So you can't just scale, per se, in that dimension, I don’t believe. That's not my experience, so it means a lot of different things. It means all those different things and various ways to different people. It's complex. It's probably complicated, also. It's big, and it's hard.

Noel: Right, it is. That's one thing that no one's ever accused agility of being was an easy process, especially with there not being an end to it. Then to look back at the abstract for this session, again, which I really enjoyed. You talk at one point about the “limits of culture.” I was curious as to what those limitations are. That's not something I feel like I read a lot about is the limits of culture. We hear how about agile, DevOps, and all of these other practices are all about culture. I know one thing we've talked about, here, at Skytap before is the idea that it’s all about culture; you do need that, but at the same time, if you don't have some of the, maybe, collaborative tools or collaborative abilities of your teams to actually do their work and to have access to the environments they need, when they need them for as long as they need them, then you can have all that culture but if people can't get their work done—that there really are some limitations to culture. So I was curious as to maybe what you saw some limits to be?

Michael: Cool. If you'll permit me a digression it would help to explain a little bit of the model that I am developing to answer that question. It's called “Integral Agile” which means a complete view of things, or all the necessary parts. It comes from a field of integral studies or integral theory that is out there in the world, like the agile movement, actually. It's actually a big movement. I'm adapting that into the enterprise agile world. So it talks about four fundamental perspectives that we can take on things that usually we tend to have our bias toward one of them or maybe two of them as being the truth, and we don't pay attention to the others, but to have a complete view of things we really need to take all four perspectives. 

Let me just describe each of them briefly. One of them is what people talk about as being agile, as opposed to doing agile. Those are two of the four perspectives. The being side, what I experience, what I value personally. Maybe my pride in being a software craftsman or my motivation to serve on a team, to not just be an individual contributor, for instance, but to really be part of something bigger than myself. That's one perspective, the being side of things, you might say. 

A different side is what you actually do. The behaviors you engage in. What other people can see from the outside. I may value software craftsmanship or I say I do, but do I really check in code all the time? Do I really pair with people? Do I really write tests before I write code? That's the behavior side. Do we really follow our team agreements of not letting the sun set on conflict, or whatever it is—do we actually engage in those behaviors? Similarly, what actual processes do we engage in? If you were looking at us from the outside, If an anthropologist was looking at our team or our organization, what behaviors would they notice we engage in? That's an outside perspective, a little more objective. 

On a collective level we have the internal side, which typically we call “culture.” What's the experience? What's the feeling of being in this organization or on this team? I've got to be careful what I say in this organization because we have an uptight culture. Or I work at start-up in Silicon Valley, and we bring our dogs to work, and we wear sandals, and we feel really free and open. That's a more feeling kind of thing or experience: what we share together, what we value together. 

The objective side of that, or the outside of that is what organizational structures do we have? What's our org chart look like? Is it flat? Is it lots of layers of bureaucracy and hierarchy? What about our policies? Do we have lots of policies and really detailed? Do we have very few policies and people have a lot of freedom to make their own decisions? How do we structure things? How do we staff things? How do we deal with funding or whatever? 

So if you think about all those different kinds of things, usually we each have a bias. I might say, "Oh, what I want is, or agile would be great…." My business partner, Lisa Adkins, likes to say, "Agile would be great if only individual leaders would get it." Or somebody else might say, "Agile would be great if only our culture changed." Or somebody might say, "Agile would be great if only we visualized the work flow." Or somebody else might say, "Agile would be great if only we actually followed the agile practices." 

So all those perspectives are valid, but they're also partial. So changing the culture, one, is really difficult, but, two, even if you do shift the culture, the feeling, the belief set, whatever—that might not change the structures. We might have structures, a certain level of bureaucracy or layers or whatever, that keep us entrenched the way we are. 

Noel: Your answer leads me into my next question. It's good that you did digress there for a little bit. It helps out with this next question. You talked about changing culture is hard. A lot of times we hear about how, for agile to have any chance of succeeding, you have to have buy-in from the leadership or executive level, especially on the enterprise scale. I was curious as to, maybe even looking at your Integral Agile that you're working on, what are some of the ways that, maybe those who are in the leadership, executive level, then maybe some ways to approach them, and to be able to sell them on this, maybe not just agility. 

Michael: A couple of things. One is that I think that going in with a persuasion mindset, that “I want persuade them about something,” is usually not very successful. I mean, clearly there are exceptions to that. Particularly, let's say you went in there and you started that way, if that works, great, keep going. But when it starts to reach a limit or when they act like they're interested or whatever, but then they don't. Or they say they're interested but they don't act like it, they're not consistent with what they actually do afterwards, then you've got a problem. 

Usually it helps to go in with seeking to understand. Steven Covey's "Seek First to Understand." We teach in our coaching classes a professional coaching idea of asking powerful questions to people, which are not leading questions. They're not trying to get somebody somewhere, in particular; they're trying to help them explore their own values and what's true for them. Approaching executives, you need to understand where they're coming from. What they're motivated by. What's important to them. How they see the problems in the organization, rather than selling them a solution to what you think is a problem, that they may agree that some part of it is a problem but they may not see it in the same way, and they definitely may not share the same values that you have. 

Another part of the book is talking about different levels of cultural development and individual development, different value sets that see the world in different ways. If you're coming from a success-driven, achievement-driven philosophy exclusively, only part of what the agile manifesto says is going to be interesting to you, not all of it. You're really not going to care about people being empowered, particularly, or shared values together. You're going to care about results and customers being happy, but you're not going to actually embrace all of the manifesto, an organization, or excuse me, a leader or executive wouldn't. Then you're going to have a disconnect. 

So part of what my presentation and my book, Coaching the Agile Enterprise is about, and the parts that I've released called "Downloading the Integral Operating System," part of what that's about is about giving people a framework to understand what's going on in an organization, in an enterprise, so they can make sense of it in a different way. 

If you're coming from one kind of motivation and the leader you're approaching is coming from a different kind, that's doomed to failure on some level. So seeking first, like I say, to understand, to go in and understand the mindset, the value set, that the person is coming from, and then decide what to do with that. Are you really trying to change them or persuade them? Are you trying to do it through aggression, through your own ego, in some sense? Or are you actually doing it in a way that's facilitating and that's useful to the other person or to the organization? Or is it just that you think it will be? Those are really different. 

Noel: Yeah, absolutely. I was just thinking that it seems like it maybe hard sometimes to go in there and talk about needing to change a culture if that's not something that that person, like you were saying, has ever experienced or known was a problem, but then being able to show them how, through that change, customers, perhaps, get a higher quality product, and even faster than they were getting in the past, is a good idea. 

Michael: Yeah, you have to connect to what they find to be of value and that may not be ... They may focus on that thing. Let's say it's a faster time to market, but they may not want to bring all the other things along with it, particularly, or they may not value them. Then you've got a disconnect. Then you've got a disappointed agile coach. We see a lot of them. 

Noel: Lastly, to wrap things up, for those who are able to attend your session which, again, is at Agile 2014, in Orlando, Florida, on Monday, July 28. For those who are able to attend it, what's maybe something that you hope that in that short amount of time that you them there in the room, that you can basically give them something small enough that they can begin, on day one, when they return, maybe to their own projects or organizations?

Michael: I think it's really more than something that they would do afterwards; it's a way that they would see the world differently. 

Noel: Oh, wow.

Michael: So that's what I think that the integral perspective has to offer people is a very different way of seeing the world. Seeing its greater complexity. Being able to, at least, start to work with, in a realistic way, the complexity of it, not think that there's easy answers to it, because there's just not. Easy answers are usually ... They sound good and they're tempting, but they usually fall flat after some period of time. 

My hope would be that people would actually start thinking about things differently after my session. That would eventually lead into what they would do differently, but it would really start with, I think, helping them understand why things are happening in their organizations, particularly things that disappoint them about the adoption of agile in a more widespread way.

Noel: That's awesome. I hope the session is a huge success. I'm going to definitely try and be there myself. Sounds fantastic. 

Michael: Okay. Well, thank you. 

Noel: Your welcome! Again, everybody, this was my conversation with Michael Spayd who is going to be speaking at Agile 2014, Monday, July 28, with a session called "What would it mean to Coach an Agile Enterprise." Thank you so much again. 

Michael: You're welcome. Thank you, Noel. 

Read the original blog entry...

More Stories By Skytap Blog

Author: Noel Wurst is the managing content editor at Skytap. Skytap provides SaaS-based dev/test environments to the enterprise. Skytap solution removes the inefficiencies and constraints that companies have within their software development lifecycle. As a result, customers release better software faster. In this blog, we publish engaging, thought provoking stories that revolve around agile enterprise applications and cloud-based development and testing.

@DevOpsSummit Stories
Docker is hot. However, as Docker container use spreads into more mature production pipelines, there can be issues about control of Docker images to ensure they are production-ready. Is a promotion-based model appropriate to control and track the flow of Docker images from development to production? In his session at DevOps Summit, Fred Simon, Co-founder and Chief Architect of JFrog, will demonstrate how to implement a promotion model for Docker images using a binary repository, and then show how to distribute them to any kind of consumer, being it a customer or a data center.
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively.
Achim Weiss is Chief Executive Officer and co-founder of ProfitBricks. In 1995, he broke off his studies to co-found the web hosting company "Schlund+Partner." The company "Schlund+Partner" later became the 1&1 web hosting product line. From 1995 to 2008, he was the technical director for several important projects: the largest web hosting platform in the world, the second largest DSL platform, a video on-demand delivery network, the largest eMail backend in Europe, and a universal billing system.
In today's digital world, change is the one constant. Disruptive innovations like cloud, mobility, social media, and the Internet of Things have reshaped the market and set new standards in customer expectations. To remain competitive, businesses must tap the potential of emerging technologies and markets through the rapid release of new products and services. However, the rigid and siloed structures of traditional IT platforms and processes are slowing them down – resulting in lengthy delivery cycles and a poor customer experience.
The modern software development landscape consists of best practices and tools that allow teams to deliver software in a near-continuous manner. By adopting a culture of automation, measurement and sharing, the time to ship code has been greatly reduced, allowing for shorter release cycles and quicker feedback from customers and users. Still, with all of these tools and methods, how can teams stay on top of what is taking place across their infrastructure and codebase? Hopping between services and command line interfaces creates context-switching that slows productivity, efficiency, and may le...
As a CIO, are your direct reports IT managers or are they IT leaders? The hard truth is that many IT managers have risen through the ranks based on their technical skills, not their leadership ability. Many are unable to effectively engage and inspire, creating forward momentum in the direction of desired change. Renowned for its approach to leadership and emphasis on their people, organizations increasingly look to our military for insight into these challenges.
DevOps and Continuous Delivery software provider XebiaLabs has announced it has been selected to join the Amazon Web Services (AWS) DevOps Competency partner program. The program is designed to highlight software vendors like XebiaLabs who have demonstrated technical expertise and proven customer success in DevOps and specialized solution areas like Continuous Delivery. DevOps Competency Partners provide solutions to, or have deep experience working with AWS users and other businesses to help them implement continuous integration and delivery development patterns or to help them automate infr...
Overgrown applications have given way to modular applications, driven by the need to break larger problems into smaller problems. Similarly large monolithic development processes have been forced to be broken into smaller agile development cycles. Looking at trends in software development, microservices architectures meet the same demands. Additional benefits of microservices architectures are compartmentalization and a limited impact of service failure versus a complete software malfunction. The problem is there are a lot of moving parts in these designs; this makes assuring performance co...
Containers are changing the security landscape for software development and deployment. As with any security solutions, security approaches that work for developers, operations personnel and security professionals is a requirement. In his session at @DevOpsSummit, Kevin Gilpin, CTO and Co-Founder of Conjur, will discuss various security considerations for container-based infrastructure and related DevOps workflows.
The cloud has reached mainstream IT. Those 18.7 million data centers out there (server closets to corporate data centers to colocation deployments) are moving to the cloud. In his session at 17th Cloud Expo, Achim Weiss, CEO & co-founder of ProfitBricks, will share how two companies – one in the U.S. and one in Germany – are achieving their goals with cloud infrastructure. More than a case study, he will share the details of how they prioritized their cloud computing infrastructure deployments and the details they’ve learned. From performance to network configurations, they've got interesting...
Chris Van Tuin, Chief Technologist for the Western US at Red Hat, has over 20 years of experience in IT and Software. Since joining Red Hat in 2005, he has been architecting solutions for strategic customers and partners with a focus on emerging technologies including IaaS, PaaS, and DevOps. He started his career at Intel in IT and Managed Hosting followed by leadership roles in services and sales engineering at Loudcloud and Linux startups.
Between the compelling mockups and specs produced by analysts, and resulting applications built by developers, there exists a gulf where projects fail, costs spiral, and applications disappoint. Methodologies like Agile attempt to address this with intensified communication, with partial success but many limitations. In his session at DevOps Summit, Charles Kendrick, CTO and Chief Architect at Isomorphic Software, will present a revolutionary model enabled by new technologies. Learn how business and development users can collaborate – each using tools appropriate to their expertise – to buil...
In his session at DevOps Summit, Bryan Cantrill, CTO at Joyent, will demonstrate a third path: containers on multi-tenant bare metal that maximizes performance, security, and networking connectivity.
JFrog has announced a powerful technology for managing software packages from development into production. JFrog Artifactory 4 represents disruptive innovation in its groundbreaking ability to help development and DevOps teams deliver increasingly complex solutions on ever-shorter deadlines across multiple platforms JFrog Artifactory 4 establishes a new category – the Universal Artifact Repository – that reflects JFrog's unique commitment to enable faster software releases through the first platform-agnostic approach to storing and sharing binary artifacts.
IT data is typically silo'd by the various tools in place. Unifying all the log, metric and event data in one analytics platform stops finger pointing and provides the end-to-end correlation. Logs, metrics and custom event data can be joined to tell the holistic story of your software and operations. For example, users can correlate code deploys to system performance to application error codes.
SYS-CON Events announced today that Dyn, the worldwide leader in Internet Performance, will exhibit at SYS-CON's 17th International Cloud Expo®, which will take place on November 3-5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Dyn is a cloud-based Internet Performance company. Dyn helps companies monitor, control, and optimize online infrastructure for an exceptional end-user experience. Through a world-class network and unrivaled, objective intelligence into Internet conditions, Dyn ensures traffic gets delivered faster, safer, and more reliably than ever.
The last decade was about virtual machines, but the next one is about containers. Containers enable a service to run on any host at any time. Traditional tools are starting to show cracks because they were not designed for this level of application portability. Now is the time to look at new ways to deploy and manage applications at scale. In his session at @DevOpsSummit, Brian “Redbeard” Harrington, a principal architect at CoreOS, will examine how CoreOS helps teams run in production. Attendees will understand how different components work together to solve the problems to manage applicatio...
The APN DevOps Competency highlights APN Partners who demonstrate deep capabilities delivering continuous integration, continuous delivery, and configuration management. They help customers transform their business to be more efficient and agile by leveraging the AWS platform and DevOps principles.
Containers are revolutionizing the way we deploy and maintain our infrastructures, but monitoring and troubleshooting in a containerized environment can still be painful and impractical. Understanding even basic resource usage is difficult - let alone tracking network connections or malicious activity. In his session at DevOps Summit, Gianluca Borello, Sr. Software Engineer at Sysdig, will cover the current state of the art for container monitoring and visibility, including pros / cons and live demonstrations of each method. Special emphasis will be put on sysdig, an open source troubleshoo...
Manufacturing has widely adopted standardized and automated processes to create designs, build them, and maintain them through their life cycle. However, many modern manufacturing systems go beyond mechanized workflows to introduce empowered workers, flexible collaboration, and rapid iteration. Such behaviors also characterize open source software development and are at the heart of DevOps culture, processes, and tooling.
DevOps is gaining traction in the federal government – and for good reasons. Heightened user expectations are pushing IT organizations to accelerate application development and support more innovation. At the same time, budgetary constraints require that agencies find ways to decrease the cost of developing, maintaining, and running applications. IT now faces a daunting task: do more and react faster than ever before – all with fewer resources.
Any Ops team trying to support a company in today’s cloud-connected world knows that a new way of thinking is required – one just as dramatic than the shift from Ops to DevOps. The diversity of modern operations requires teams to focus their impact on breadth vs. depth. In his session at DevOps Summit, Adam Serediuk, Director of Operations at xMatters, Inc., will discuss the strategic requirements of evolving from Ops to DevOps, and why modern Operations has begun leveraging the “NoOps” approach. NoOps enables developers to deploy, manage, and scale their own code, creating an infrastructure...
In their session at DevOps Summit, Asaf Yigal, co-founder and the VP of Product at, and Tomer Levy, co-founder and CEO of, will explore the entire process that they have undergone – through research, benchmarking, implementation, optimization, and customer success – in developing a processing engine that can handle petabytes of data. They will also discuss the requirements of such an engine in terms of scalability, resilience, security, and availability along with how the architecture accomplishes these requirements. Lastly, they will review the gory details of the technolo...
DevOps has often been described in terms of CAMS: Culture, Automation, Measuring, Sharing. While we’ve seen a lot of focus on the “A” and even on the “M”, there are very few examples of why the “C" is equally important in the DevOps equation. In her session at @DevOps Summit, Lori MacVittie, of F5 Networks, will explore HTTP/1 and HTTP/2 along with Microservices to illustrate why a collaborative culture between Dev, Ops, and the Network is critical to ensuring success.
Saviynt Inc. has announced the availability of the next release of Saviynt for AWS. The comprehensive security and compliance solution provides a Command-and-Control center to gain visibility into risks in AWS, enforce real-time protection of critical workloads as well as data and automate access life-cycle governance. The solution enables AWS customers to meet their compliance mandates such as ITAR, SOX, PCI, etc. by including an extensive risk and controls library to detect known threats and behavior and usage analytics to identify unknown risks.