>> Announcer: From around the globe, it's theCUBE with digital coverage of BizOps Manifesto Unveiled, brought to you by BizOps Coalition. >> Hey, welcome back, everybody. Jeff Frick here with theCUBE for our ongoing coverage of the big unveil. It's the BizOps Manifesto Unveil and we're going to start that again. >> From the top. >> Three. >> Crew Member: Yeah, from the top. Little bleep bleep bleep, there we go. >> Manifesto. >> Crew Member: Second time's the charm, coming to you in five, four, three, two. >> Hey, welcome back, everybody. Jeff Frick here with theCUBE coming to you from our Palo Alto studios today for a big, big reveal. We're excited to be here. It's the BizOps Manifesto Unveiling. Things have been in the works for a while and we're excited to have our next guest, one of the really the powers behind this whole effort and he's joining us from Boston. It's Serge Lucio, the Vice President and General Manager, Enterprise Software Division at Broadcom. Serge, great to see you. >> Good to see you, Jeff, Glad to be here. >> Absolutely. So, you've been in this business for a very long time, you've seen a lot of changes in technology. What is the BizOps Manifesto? What is this coalition all about? Why do we need this today in 2020? >> Yeah, so I've been in this business for close to 25 years, right? So, about 20 years ago, the Agile Manifesto was created. And the goal of the Agile Manifesto was really to address the uncertainty around software development and the inability to predict the effort to build software. And if you roll back kind of 20 years later and if you look at the current state of the industry, the Project Management Institute estimates that we're wasting about a million dollars every 20 seconds in digital transformation initiatives that do not deliver on business results. In fact, we recently surveyed a number of executives in partnership with Harvard Business Review and 77% of those executives think that one of the key challenges that they have is really at the collaboration between business and IT. And that's been kind of the case for almost 20 years now. So, the key challenge we're faced with is really that we need a new approach. And many of the players in the industry, including ourselves, have been using different terms, right? Some are talking about value stream management, some are talking about software delivery management. If you look at the Site Reliability Engineering movement, in many ways, it embodies a lot of these kind of concepts and principles. So, we believe that it became really imperative for us to crystallize around that one concept. And so, in many ways, the BizOps concept and the BizOps Manifesto are around bringing together a number of ideas which have been emerging in the last five years or so and defining the key values and principles to finally help these organizations truly transform and become digital businesses. And so, the hope is that by joining our forces and defining the key principles and values, we can help the industry, not just by providing them with support, but also the tools and consulting that is required for them to truly achieve the kind of transformation that everybody is seeking. >> Right, right. So, COVID, now, we're six months into it approximately, seven months into it, a lot of pain, a lot of bad stuff still happening, we've got two ways to go. But one of the things that on the positive side, right, and you seen all the memes in social media is a driver of digital transformation and a driver of change 'cause we had this light switch moment in the middle of March and there was no more planning, there was no more conversation, you suddenly got remote workforces, everybody's working from home and you got to go, right? So, the reliance on these tools increases dramatically. But I'm curious kind of short of the beginnings of this effort and short of kind of COVID which came along unexpectedly, I mean, what were those inhibitors 'cause we've been making software for a very long time, right? The software development community has adopted kind of rapid change and iterative delivery and sprints, what was holding back the connection with the business side to make sure that those investments were properly aligned with outcomes? >> Well, you have to understand that IT is kind of its own silos and traditionally, IT has been treated as a cost center within large organizations and not as a value center. And so as a result, kind of the traditional dynamic between IT and the business is basically one of kind of supplier up to kind of a business. And if you go back to I think Elon Musk a few years ago basically had these concepts of the machines to build the machines and he went as far as saying that the machines or the production line is actually the product. So, meaning that the core of the innovation is really about building kind of the engine to deliver on the value. And so, in many ways, we have missed on this shift from kind of IT becoming this kind of value center within the enterprises. And it's all about culture. Now, culture is the sum total of behaviors and the reality is that if you look at IT, especially in the last decade, with Agile, with DevOps, with hybrid infrastructures, it's way more volatile today than it was 10 years ago. And so, when you start to look at the velocity of the data, the volume of data, the variety of data to analyze the system, it's very challenging for IT to actually even understand and optimize its own processes, let alone to actually include business as kind of an integral part of a delivery chain. And so, it's both kind of a combination of culture, which is required, as well as tools, right? To be able to start to bring together all these data together. And then, given the volume, variety, velocity of the data, we have to apply some core technologies, which have only really truly emerged in the last five to 10 years around machine learning and analytics. And so, it's really kind of a combination of those things, which are coming together today to really help organizations kind of get to the next level. >> Right, right. So, let's talk about the manifesto. Let's talk about the coalition, the BizOps Coalition. I just like that you put down these really simple kind of straightforward core values. You guys have four core values that you're highlighting, business outcomes over individual projects and outputs, trust and collaboration over siloed teams and organizations, data driven decisions, what you just talked about, over opinions and judgment and learn to respond and pivot. I mean, Serge, these sounds like pretty basic stuff, right? I mean, isn't everyone working to these values already? And I think you touched on it, on culture, right? Trust and collaboration, data driven decisions. I mean, these are fundamental ways that people must run their business today or the person that's across the street that's doing it is going to knock them right off their block. >> Yeah, so that's very true. So, I'll mention another survey we did I think about six months ago. It was in partnership with an industry analyst. And we surveyed, again, a number of IT executives to understand how many were tracking business outcomes, how many of these software executives, IT executives were tracking business outcomes. And there were less than 15% of these executives who were actually tracking the outcomes of the software delivery. And you see that every day, right? So, in my own teams, for instance, we've been adopting a lot of these core principles in the last year or so. And we've uncovered that 16% of our resources were basically aligned around initiatives which were not strategic for us. I take another example. For instance, one of our customers in the airline industry uncovered, for instance, that a number of... That they had software issues that led to people searching for flights and not returning any kind of availability. And yet, the IT teams, whether it's operations or software development, were completely oblivious to that because they were completely blindsided to it. And so, the connectivity between the inwards metrics that IT is using, whether it's database uptime, cycle time or whatever metric we use in IT, are typically completely divorced from the business metrics. And so, at its core, it's really about starting to align the business metrics with the software delivery chain, right? This system which is really a core differentiator for these organizations. It's about connecting those two things and starting to infuse some of the Agile culture and principles that emerge from the software side into the business side. Of course, the Lean movement and other movements have started to change some of these dynamic on the business side. And so, I think this is the moment where we are starting to see kind of the imperative to transform now, COVID obviously has been a key driver for that. The technology is right to start to be able to weave data together and really kind of also the cultural shifts through Agile, through DevOps, through the SRE movement, through Lean business transformation. All these things are coming together and are really creating kind of conditions for the BizOps Manifesto to exist. So, Clayton Christensen, great Harvard Professor, "Innovator's Dilemma", still my all-time favorite business book, talks about how difficult it is for incumbents to react to disruptive change, right? Because they're always working on incremental change 'cause that's what their customers are asking for and there's a good ROI.' When you talk about companies not measuring the right thing, I mean, clearly, IT has some portion of their budget that has to go to keeping the lights on, right? That's always the case, but hopefully, that's an ever decreasing percentage of their total activity. So, what should people be measuring? I mean, what are kind of the new metrics in BizOps that drive people to be looking at the right things, measuring the right things and subsequently making the right decisions, investment decisions, on whether they should move project A along or project B? >> So, there are really two things, right? So, I think what you were talking about is portfolio management, investment management, right? And which is a key challenge, right? In my own experience, right? Driving strategy or a large scale kind of software organization for years, it's very difficult to even get kind of a base data as to who's doing what. I mean, some of our largest customers we're engaged with right now are simply trying to get a very simple answer, which is, how many people do I have in that specific initiative at any point in time and just tracking down information is extremely difficult. And again, back to the Project Management Institute, they have estimated that on average, IT organizations have anywhere between 10 to 20% of their resources focused on initiatives which are not strategically aligned. So, that's one dimension on portfolio management. I think the key aspect though, that's we're really keen on is really around kind of the alignment of a business metrics to the IT metrics. So, I'll use kind of two simple examples, right? And my background is around quality and I've always believed that fitness for purpose is really kind of a key philosophy, if you will. And so, if you start to think about quality as fitness for purpose, you start to look at it from a customer point of view, right? And fitness for purpose for a core banking application or mobile application are different, right? So, the definition of a business value that you're trying to achieve is different. And yet, if you look at our IT operations are operating, they were using kind of a same type of inward metrics, like a database uptime or a cycle time or what is my point velocity, right? And so, the challenge really is this inward facing metrics that the IT is using which are divorced from ultimately the outcome. And so, if I'm trying to build a core banking application, my core metric is likely going to be uptime, right? If I'm trying to build a mobile application or maybe a social mobile app, it's probably going to be engagement. And so, what you want is for everybody across IT to look at these metric and what are the metrics within the software delivery chain which ultimately contribute to that business metric? In some cases, cycle time may be completely irrelevant, right? Again, my core banking app, maybe I don't care about cycle time. And so, it's really about aligning those metrics and be able to start to differentiate. The key challenge you mentioned around the disruption that we see is or the investor's dilemma is really around the fact that many IT organizations are essentially applying the same approaches for innovation, right? For basically scrap work than they would apply to kind of other more traditional projects. And so, there's been a lot of talk about two-speed IT. And yes, it exists, but in reality, are really organizations truly differentiating how they operate their projects and products based on the outcomes that they're trying to achieve? And this is really where BizOps is trying to affect. >> I love that. Again, it doesn't seem like brain surgery, but focus on the outcomes, right? And it's horses for courses, as you said. This project, what you're measuring and how you define success isn't necessarily the same as on this other project. So, let's talk about some of the principles. We talked about the values, but I think it's interesting that the BizOps coalition just basically took the time to write these things down and they don't seem all that super insightful, but I guess you just got to get them down and have them on paper and have them in front of your face. But I want to talk about one of the key ones, which you just talked about, which is changing requirements, right? And working in a dynamic situation, which is really what's driven the software to change in software development because if you're in a game app and your competitor comes out with a new blue sword, you got to come out with a new blue sword. So, whether you had that on your Kanban wall or not. So, it's really this embracing of the speed of change and making that the rule, not the exception. I think that's a phenomenal one. And the other one you talked about is data, right? And that today's organizations generate more data than humans can process. So, informed decisions must be generated by machine learning and AI. And the big data thing with Hadoop started years ago, but we are seeing more and more that people are finally figuring it out, that it's not just big data and it's not even generic machine learning or artificial intelligence, but it's applying those particular data sets and that particular types of algorithms to a specific problem to your point, to try to actually reach an objective, whether that's increasing your average ticket or increasing your checkout rate with shopping carts that don't get left behind and these types of things. So, it's a really different way to think about the world in the good old days, probably when you guys started when we had big giant MRDs and PRDS and sat down and coded for two years and came out with a product release and hopefully, not too many patches subsequently to that. >> It's interesting, right? Again, back to one of these surveys that we did with about 600 IT executives. And we purposely designed those questions to be pretty open. And one of them was really around requirements. And it was really around kind of what is the best approach? What is your preferred approach towards requirements? And if I remember correctly, over 80% of the IT executives said that the best approach, their preferred approach, is for requirements to be completely defined before software development starts. So, let me pause there. We're 20 years after the Agile Manifesto, right? And for 80% of these IT executives to basically claim that the best approach is for requirements to be fully baked before software development starts, basically shows that we still have a very major issue. And again, our hypothesis in working with many organizations is that the key challenge is really the boundary between business and IT, which is still very much contract-based. If you look at the business side, they basically are expecting for IT to deliver on time on budget, right? But what is the incentive for IT to actually deliver on the business outcomes, right? How often is IT measured on the business outcomes and not on an SLA or on a budget type criteria. And so, that's really the fundamental shift that we really need to drive out as an industry. And, we talk about kind of this imperative for organizations to operate as one. And back to the the "Innovator's Dilemma", the key difference between these larger organization is really kind of a... If you look at the amount of capital investment that they can put into pretty much anything, why are they losing compared to startups? Why is it that more than 40% of personal loans today are issued, not by your traditional brick and mortar banks, but by startups? Well, the reason, yes, it's the traditional culture of doing incremental changes and not disrupting ourselves, which Christensen covered at length, but it's also the inability to really fundamentally change kind of the dynamic between business and IT and partner, right? To deliver on a specific business outcome. >> Right, I love that. That's a great summary and in fact, getting ready for this interview, I saw you mentioning another thing where the problem with the Agile development is that you're actually now getting more silos 'cause you have all these autonomous people working kind of independently. So, it's even a harder challenge for the business leaders, as you said, to know what's actually going on. But Serge, I want to close and talk about the coalition. So clearly, these are all great concepts. These are concepts you want to apply to your business every day. Why the coalition? Why take these concepts out to a broader audience, including your competition and the broader industry to say, "Hey, we as a group need to put a stamp of approval on these concepts, these values, these principles?" >> So first, I think we want everybody to realize that we are all talking about the same things, the same concepts. I think we're all from our own different vantage point realizing that things have to change. And again, back to whether it's value stream management or Site Reliability Engineering or BizOps, we're all kind of using slightly different languages. And so, I think one of the important aspects of BizOps is for us, all of us, whether we're talking about consulting, Agile transformation experts, whether we're talking about vendors, right? To provides kind of tools and technologies or these large enterprises to transform for all of us to basically have kind of a reference that lets us speak around kind of in a much more consistent way. The second aspect, to me, is for these concepts to start to be embraced, not just by us or vendors, system integrators, consulting firms, educators, thought leaders, but also for some of our own customers to start to become evangelists of their own in the industry. So, our objective with the coalition is to be pretty, pretty broad. And our hope is by starting to basically educate our joint customers or partners, that we can start to really foster these behaviors and start to really change some of dynamics. So, we're very pleased that if you look at some of the companies which have joined the manifesto, so we have vendors, such as Tasktop, or Appvance or PagerDuty, for instance, or even Planview, one of my direct competitors, but also thought leaders like Tom Davenport or Capgemini or smaller firms like Business Agility Institute or AgilityHealth. And so, our goal really is to start to bring together thought leaders, people who've been helping large organizations do digital transformation, vendors who are providing the technologies that many of these organizations use to deliver on this digital transformation and for all of us to start to provide the kind of education, support and tools that the industry needs. >> Yeah, that's great, Serge, and congratulations to you and the team. I know this has been going on for a while, putting all this together, getting people to sign on to the manifesto, putting the coalition together and finally today, getting to unveil it to the world in a little bit more of a public opportunity. So again, really good values, really simple principles, something that shouldn't have to be written down, but it's nice 'cause it is and now you can print it out and stick it on your wall. So, thank you for sharing the story and again, congrats to you and the team. >> Thank you, thanks, Jeff, appreciate it. >> My pleasure, all righty, Serge. If you want to learn more about the BizOps Manifesto, go to bizopsmanifesto.org, read it and you can sign it and you can stay here for more coverage on theCUBE of the BizOps Manifesto Unveiled. Thanks for watching, see you next time. (upbeat music)

>> Narrator: From theCUBE Studios in Palo Alto, in Boston, connecting with thought leaders all around the world, this is a CUBE conversation. >> Hey, welcome back, everybody. Jeff Frick here with theCUBE. We're in our Palo Alto Studios today, talking about a pretty interesting topic. You probably haven't heard of it, but you're going to know a lot of the attributes and it's going to sound very familiar. And that's BizOps, the concept of BizOps. We've heard about DevOps and DevSecOps and a whole bunch of ops, but BizOps is really a new twist and a new way to think about this. And we're excited to have the woman who actually wrote the book on the topic. She's Laureen Knudsen. She's a Chief Transformation Officer from Broadcom. She's also the co-author of the "Modern Business Management: Creating a Built-to-Change Organization", and a founding member of the BizOps Coalition. Laureen, great to see you. >> Great to be here. Thanks so much for having me. >> Absolutely. For people that aren't familiar with BizOps, give us kind of the quick high level. What is BizOps? >> BizOps is a new way of doing business. Just like Agile changed engineering and DevOps changed how we put things into production, BizOps is changing from soup to nuts. So from concept to cash or strategy to execution, right. There's a lot of... This has been talked about for a few years now, but this is formalizing that structure. So what do you need to do to truly have your strategy linked to your customer base? And so it's creating that umbrella over all of these other ops processes that brings it all together to tie the top to the bottom. >> Right. So, DevOps, right, fundamentally changed, the way the software gets developed. There used to be waterfall, it used to be data market's development document and then a product requirements document, then you put together a plan and you code it for six months or nine months, threw it over the Wall operations, and then hopefully they delivered. That doesn't happen anymore. And that was really set forth about 20 years ago when this kind of revolution happened on the software side. So what's been happening on the business side, and why now do they need their own ops to be pulled into this process? >> Well, sort of in the same way that things happened in the late 1990s, where certain organizations started to realize that that wasn't the most efficient way to create software and came together and created the Agile Manifesto. We've realized that there's certain things in doing business that make us much more effective and efficient. Things like bringing a data stream from the top to the bottom so every level of the organization has the data they need to run their business. Having that trust run throughout the organization, having that communication and that transparency from the strategy to the execution. You know, the global economy is just in dire straits right now, and the world is moving faster than ever. And so being able to respond to that change is vital at all levels of the organization. >> So you wrote the book years ago, I'm sure you've speaking to ton of business leaders, you know, as an author of the book, what were the biggest inhibitors to kind of the adoption of these ops and there must have been something, because why then did you found this coalition? What was the, you know, kind of the founding principle behind the coalition? >> Well, a bunch of industry leaders have come together to realize that in the same way that development needed to change in the early 2000s, really business needs to change today. And to your point, we've been talking about this for a while. Different companies are doing it better than others. And the ones that are doing this well are really heads and tails succeeding above the others. So, it's not easy though. It's not easy to change an entire organization and to change the way you do business. So, the coalition is bringing together some principles and values. We've come together to talk about how we're doing business differently and what actually works. And the main things you need to focus on in order to ensure success. >> Right. But you did it loud and proud with this declarative manifesto and then an event, actually, later this month that you're going to have to really unveil the manifesto, October 15th. I think it's 9:00, or excuse me, >> 11: 00 AM Eastern, 8:00 AM Pacific. Manifesto, right? Just the word manifesto, elicits all types of, kind of emotional response and really strong declarative statement of purpose and mission. So, why the manifesto and what's really the key pieces of the manifesto? >> You know, you need the principles that go along to help you change people, process and technology. And a lot of folks are focusing only on the technology and the data that comes from that technology and all that is key and vital to the way that you run your business differently. It's not the only piece. And so we need to focus on how do we get to bring the people along with us, how do we change our processes to be more efficient and effective. And the four values and the principles that we've created as this coalition, really help companies to do that more easily and to know they're on the right track, in the same way that the Agile principles and the values that brought out in the Agile Manifesto did. >> Right. So, I have a preview version here of the values. And I think it is really important for people to stay kind of fundamental values. 'Cause then everything builds from that and if there's ever a question, you can go back to the values as of a reference point. But just to read a few of, you know, business outcomes over individual projects, trust and collaboration over siloed teams and organizations, data-driven decisions over opinions and judgment calls, and finally, learn responded pivot over following a documented plan. And that seems so, right, so simple and so foundational and so fundamental to the way business works today. But the fact that you have to put this coalition together, and the fact that you're publishing this manifesto, tells me that the adoption really isn't where it should be. And this is really a new way to try to drive the adoption of these values. >> Absolutely. I mean, everybody seems to understand that they need to focus on their customers and that they need to focus on outcomes, but you can't just take something, you know, once you have work in progress and say, well, what's the value of this one piece of work. You have to have started at the beginning to come with the right outcome you're trying to meet, and then ensure that you're doing that all along the path to creating that and to bringing that to your customer base. It's focusing on your customers and creating the trust with your customers as well as through your organization. The data is really vital. Being able to run our businesses on real data and know the reality of the situation rather than at status reports that were created by people saying, yeah, I'm done, but there's no definition of done, right? It's fundamentally changing how we do business, which sounds easy. But as we know because of the Agile transformations that we've done and DevOps transformations that we've done, it's not as easy as it sounds. >> Right. So, why not just try to include more of the business people in the DevOps process? Why the strategy to have BizOps as kind of a standalone activity and again, to have the coalition and manifesto, that means it's super important. Can't the business people participate in the DevOps, or why has that not really been effective? >> It's really a different part of the business. And BizOps is a framework that pulls together all of these other operational pieces. So, security, operations, you know, how do you get something from engineering out to your customers, really were DevOps focuses, right? So, that's great. But running your business includes a lot more than your IT organization or your engineering teams. So this really expands out and brings in all of the rest of the business for how you sell software, how you plan, how you fund your teams, how you look at the work from that high strategic level and ensuring that you create that solid pipeline of data so that you truly know the status of any strategy in your organization. I was working with one group who had really good strategies and they had really good execution and they found that they spent over $100 million annually rolling up that data to try and understand the true status of their strategies. So companies are spending and are being very inefficient in, you know, they're spending millions of dollars on trying to do this link where if you just fundamentally change the way you do business a little bit, day to day, you can have that as a natural outcome of your processes. >> Right. 'Cause you've talked about on some of this stuff about using it as a way to do prioritization and to make sure you're not spending money places that you shouldn't. Another thing that strikes me as I go through the principles are, again, things that in 2020 should not be new information, you know, frequent changes, which was not part of the old paradigm. Trust and transparency. And I think you even tied it back into one of the articles I saw, tying trust and transparency really back to employee engagement, which then drives profitability and productivity. So I wonder if you can talk about the role of trust and in your conversations with people, as you've been kind of developing this idea over the years since the book, getting leaders to, you know, to trust their people, to do what that needs to be done rather than managing tasks, you know, manage the outcome, not manage tasks. >> Right. This is really important. Having trust in your organizations, especially today when everyone's remote, right? And in almost every company in the globe right now, most of their employees are working from their houses. You can't really do command and control well when no one is sitting in your building with you. So being able to have that trust to truly trust in your employees, you know, we spend a lot of money on all of these technical folks that we hire, and then we put people in place to try and direct them what to do on a daily basis. And so having... Building that trust within your organization, and it goes both ways, right? Employees need to trust the leadership, leadership needs to trust the employees, but it's not just from the top level to the end level, right? To the team level. It's actually every level in the middle. So this is truly pulling the pieces of work that we've done over the past few years through the entire organization. It's getting rid of what we call that frozen middle, of middle management and making sure that trust is aligned in there as well. And that the communication and transparency is working through that part of the organization. >> Right. Another principle I want to highlight is talking about the role of machine learning and artificial intelligence. Clearly, we all know, right, data's exploding, et cetera, et cetera, and we want to get the data driven decisions. But what this really calls out is that there's probably more data, both in terms of frequency and complexity, than people can really sift through, in terms of finding what they should be working on and what's important and what's not, you know, the classic separating the signal from the noise. I wonder if you can speak to a little bit about the role of machine learning and artificial intelligence, as an enhancer to productivity in this BizOps world versus a threat to people's jobs. >> Absolutely. I mean, like I said already that there's some companies spending $100 million rolling up data on things that computers can do today, even without machine learning and an AI. But when we put that into place, it really doesn't replace people any more than DevOps removed people from the organization. We automated a lot in testing yet we still have test organizations. It's just a different focus and a way of doing business. And this is no different. I'm seeing a lot of companies though start to try and throw all of their data together. And I've recently started saying that they're creating data land fields when they're attempting to create data lakes. And so you really need to understand your data that you're collecting and why you're collecting it and what outcomes you're trying to get from that data so that you can understand your business and you're not just creating, to your point, more noise. >> Right. So let's shift gears a little bit and talk about the event that's coming up on the 15th, about, you know, kind of, what is the role of the coalition? How should people get involved, what's membership all about, and then what can they expect to happen on the 15th? >> We have 10 industry leaders that have come together to author the BizOps Manifesto. And it's everyone from influencers, transformation experts, CEOs of a lot of companies or of organizations. We have people like Evan Leybourn of the Business Agility Institute and Sally Elatta from AgilityHealth, who have come to help author this and are really transformational leaders across the globe. And to get involved, you can go to bizopsmanifesto.org. and you can sign the manifesto. You can align to that if, you know, if you want to bring this into your own organization, we're happy to help work with that as well. So it's a group of industry leaders who are here to help the globe get more efficient and effective in how they do business. >> It's really interesting, right. It's not really an open source project, but it is kind of a co-opetition in terms of, you know, you're reaching out to lots of different companies and lots of different leaders to participate. They may or may not be competitive, but really this is more kind of an industry, kind of productivity thing, if you will, to bring all these people together at the coalition. Would that be accurate? >> It is accurate, but we're also looking to have competitors. I mean, we've... Competitors is an interesting thing today because there's no company just uses one company software, for example, to automate all of their pieces, right? There's all of these products that have to come together and share data today in the same way that we needed to share, you know, access to software. In the past, integrations were really difficult and now, you know, everyone's got open APIs. It's a very similar thing with data today. And so we are working with our competitors and we're working with, you know, like you said, industry leaders. We have Mik Kersten from Tasktop as part of this as well. We're looking at how we can benefit the companies of the world today, much more efficiently and effectively than we have in the past. So it is a group of people who compete with each other, maybe on a daily basis, but also have the same customers and have the need to help companies today, especially in this economy with the pandemic, right. There's a lot of companies in dire straits right now and we all need to come together as business leaders to help those companies get through this time. And anything that we can do to do that is going to benefit us all in the long run. >> Right. You know, it is really interesting co-opetition, is like you say, most companies have everybody's, you know, a lot of different products and people compete as well as having API connections and having all kinds of interesting relationships. So the lines are not so clean, like they used to be. And as we've seen with DevOps, you know, significant delta in the productivity and the responsiveness and the way software is delivered. So, sounds super exciting. We'll look forward to the event on the 15th. I give you the last word. What are you looking most forward to for the big launch in a couple of weeks? >> I'm really excited for people to give us their feedback on what they think and how this benefits them. And I'm excited to help our customers and help the, you know, the big companies of the world get through these next 18 months. I think we're all in for a bit more of a struggled time, you know, at a difficult time, and anything that we can all do to work together. So I'm looking forward to working with other industry leaders on this as well, and to the benefit of, you know, the global economy. >> Right. Well, great. Well, Laureen, thank you for giving us the one on one on BizOps. Really appreciate it. And best of luck to you and good luck to you and the team on the 15th. >> Thanks so much. >> Alrighty. Thank you. All right, she's Laureen, I'm Jeff. You're watching theCUBE. Thanks for watching. We'll see you next time. (upbeat music begins)