Tag: digital transformation

  • Navigating the MLOps Revolution: Three Missteps to Avoid

    Navigating the MLOps Revolution: Three Missteps to Avoid

    With nearly 60% of businesses set to adopt MLOps by 2024, this function has quickly established itself as an indispensable part of the enterprise technology world. And with computing needs rapidly expanding as digital transformation efforts continue, the growth of the MLOps market is unlikely to stop anytime soon.

    That said, as with any emerging technology–particularly something as powerful as MLOps–there is no shortage of potential pitfalls that businesses and their tech teams can fall into if they move too quickly. More importantly, these missteps can have significant impacts on a company’s ability to generate revenue and optimize performance.

    With that in mind, below are three of the biggest mistakes that companies tend to make when adopting MLOps.

    Jumping in Without Testing the Waters

    If you doubt your MLOps maturity, you should probably wait. One of the biggest factors that undermine MLOps adoption and long-term success is that companies jump in before they are actually ready to adopt the technology. This not only leads to MLOps feeling like a burden but also often devolves the customer-vendor relationship into a transactional sales relationship rather than what it should be: a partnership. Onboarding technology needs to be a give-and-take process with ongoing dialogue between the customer and the vendor. If not, vendors – even the most ethical ones – have to rely on partial situational intelligence and guesswork to offer solutions that may or may not address the problems and deliver results. The best way to overcome this is for companies to map out exactly what MLOps challenges they are up against, what barriers are present, and also the outcomes they are looking for. With these key components understood and agreed to in advance, not only can companies make sure they are getting the best vendor partner, but the vendor can then provide much more tailored guidance.

    Misunderstanding What MLOps Actually Is

    There is a tendency among new adopters to distill MLOps down to the idea that it is made up of two components: Storage and compute. Yes, these are two significant elements of the MLOps equation, but this view is a massive oversimplification. Also, if it is not clarified at the outset, this misperception can lead organizations to feel overwhelmed by MLOps and make adoption less “sticky” as a result.

    The fact is, MLOps is composed of numerous pieces–from experimentation to deployment–that each come with their own specific nuances. Each of these parts is interconnected to the next and can derail MLOps results if not properly planned for and maintained. In addition, making sure that every necessary component is functioning the way it should in order to meet the needs and expectations of each client takes time. So businesses and their broader DevOps teams need to be prepared to exercise patience if they have any hopes of successfully adopting MLOps in a way that is geared towards long-term sustainable results.

    Not Realizing the Amount of Iteration MLOps Takes

    When looking at projects from a traditional DevOps perspective, there is a common belief that if a project is stable enough to get it to DevOps, it is ready for production. With MLOps projects, however, this simply isn’t the case. In comparison to DevOps, MLOps is prone to evolution – meaning that iteration and reiteration are incredibly common. For example, in the midst of the MLOps process, companies will want to iterate over the existing process, sometimes at a much more frequent cadence than their software release cadence. This means that there is greater ongoing contact and collaboration between MLOps teams and other teams. This interaction stands in stark contrast to traditional DevOps projects where once production is complete, developers hand over the keys and are essentially hands-off. Businesses and their traditional DevOps teams need to become comfortable with this new way of doing business and build in the flexibility and leeway to make sure that while their MLOps is able to function correctly and grow, that it does so in a way that works for them.

    Businesses are right to be excited about the prospect of adopting MLOps. However, to hit the ground running and deliver impact over the short, medium, and long term, it is essential that companies deploy a comprehensive strategy to ease onboarding headaches and make the process as seamless as possible. And by keeping these key missteps in mind, businesses can do just that.

  • CloudBees Survey Sees VSM Driving Digital Transformation

    CloudBees Survey Sees VSM Driving Digital Transformation

    A global survey of 600 senior executives conducted by CloudBees suggested a high correlation between investments made in value stream management (VSM) and digital business transformation success.

    The survey found 90% of respondents agreed that organizations that committed to VSM are likely to be further ahead in terms of achieving their digital business transformation goals, with 92% noting VSM also creates more time to focus on innovation.

    Hope Lynch, senior director for platform at CloudBees, said the challenge is that too many executives equate VSM with legacy Six Sigma processes rather than application development and deployment processes that advance digital business transformation initiatives. The survey found that while 90% of senior executives claimed they were familiar with the VSM concept, only half could select the correct answer when asked. In fact, two in five respondents confused the concepts of value stream management and value stream mapping. Nearly two-thirds (72%) of respondents admitted there is still confusion about what VSM is.

    VSM traces its lineage back to lean manufacturing methods, which called for each step of a manufacturing process to be continuously measured. As software development has evolved and organizations realize how dependent they are on software, there is a growing appreciation for the value of monitoring things such as the impact of missed software development deadlines on the business. At their core, VSM platforms aggregate DevOps metrics and then match them to a set of key performance indicators (KPIs) defined by business leaders. Once those metrics are gathered and correlated, organizations can apply advanced analytics.

    Eventually, the goal is to apply algorithms and other forms of predictive analytics that will enable organizations to more easily identify the precise impact software development processes have on the business, noted Lynch.

    In the meantime, the CloudBees survey identified manager commitment as the main roadblock to VSM adoption, with 35% of respondents saying getting mid-level employees committed and 31% saying getting senior leadership committed are the biggest roadblocks. That’s a significant issue because more than half of respondents (56%) said C-level executives make VSM investment decisions.

    Survey respondents also reported that scaling VSM efforts throughout the organization is a significant issue for a third (33%) of respondents.

    In general, many VSM initiatives were sidetracked by the COVID-19 pandemic, noted Lynch. However, organizations will now be looking to evaluate the results of those efforts, she added. Digital transformation plans are in place and going well, according to 96% of survey respondents, with only 18% reporting that they are moving, but not fast enough.

    However, all software development processes could be improved by surfacing real-time insights, added Lynch. Most senior executives today don’t have a lot of visibility into the software development processes that are driving multiple digital transformation initiatives, she added.

    In theory, VSM platforms should one day help narrow the divide that has long existed between IT and the rest of the business, as dashboards make it simpler for everyone involved to appreciate the cascading impact a software development decision has across the entire business.

  • Old Software Never Dies – But What is it Really Worth?

    Old Software Never Dies – But What is it Really Worth?

    I’ve been thinking about the news from last week that OpenText acquired Micro Focus for what seems to be $6 billion in cash. Mike Vizard did a nice write-up on the news with his take on it here on devopsy.kinsta.cloud (and if you’re interested in the security industry implications, Techstrong Research’s Mike Rothman talked about that, too). While I don’t flat-out disagree with Mike Vizard’s opinions, I do have a slightly different view.

    To me, this is part of a trend we have been seeing from some of the largest tech companies who are sitting on or have access to loads of dry-powder cash. In tougher economic times, cash is king and it is not unusual for the large companies to come in and pick up other companies and lines of business, usually on the cheap. 

    For instance, Broadcom’s acquisition of VMware (though I don’t know that you could call $61 billion cheap). It seems, at first blush, the Micro Focus deal would seem to fit the same kind of bill. I don’t think people believe OpenText overpaid based on these numbers:

    • Total purchase price is 2.2x Micro Focus’ pro forma TTM revenues
    • Total purchase price is 6.3x Micro Focus’ pro forma TTM adjusted EBITDA

    However, I think there’s more here than meets the eye. By OpenText’s CEO’s own admission, it is going to take at least eight quarters (two years) to integrate the Micro Focus portfolio into OpenText’s cloud delivery model.  

    In the meantime, Micro Focus has struggled to maintain profitability and previously announced a $300 million cost-cutting program which will continue with the acquisition. Additionally, the company is saying they will cut another $100 million in costs on top of that; so, a total of $400 million in cuts. 

    Where are the cuts coming from? It’s not like Micro Focus’ broad portfolio of software products are revolutionary new technology—quite the opposite, in fact. Micro Focus, through various acquisitions over the years, has largely scooped up mature product lines from large technology brands that unloaded unwanted or non-strategic software lines-of-business. Of course, the HP/HPE deal was a whole different animal, but the result was not much different. 

    Some mature software came under Micro Focus’ control and Micro Focus has done a decent job of keeping those lines of business turning out what cash they can. They haven’t really “reinvigorated” that software, but have been running out the cycle. Now, OpenText says moving it to their cloud service over the next eight quarters is going to turn things around. I’m skeptical, to say the least.

    I think it will be old software that will be two years older and delivered via the cloud. What must be done goes beyond just putting that software in the cloud—they have to commit to truly relaunching it. Move it to cloud-native architecture; kill some of the older product lines that are near end-of-life and, frankly, which should have been put out to pasture some time ago. Build on the brand equity, sure, but launch some new software.

    At the end of the day, $6 billion is a lot of money—but more money than that has been wasted buying old software in the past. Without a much bolder plan from OpenText, just mumbling about digital transformation and cloud will not be enough to make the Micro Focus portfolio worth anything close to the amount of money they paid for it.

    Like Mike Vizard—and, I am sure, many OpenText investors and Micro Focus users—I will be looking for signs that OpenText are not settling for a lift-and-shift with the old Micro Focus software wrapped in the cloud. It is going to take more than that for this deal to pay dividends. 

    I am not saying it can’t be done. When this deal closes, OpenText will be a software powerhouse with a broad set of customers. Finding new software and services to sell to those customers is the key to this deal.

  • OpenText to Create Software Powerhouse – Acquires Micro Focus for $6B

    OpenText to Create Software Powerhouse – Acquires Micro Focus for $6B

    OpenText this week announced it will acquire Micro Focus for $6 billion. The acquisition is part of an effort to reinvigorate a broad portfolio of information management, application development and testing, integration and cybersecurity platforms by accelerating the rate at which they are transitioned to OpenText’s managed private cloud.

    The acquisition is expected to close in the first quarter of 2023, and the combined company expects to reduce costs by an additional $100 million on top of the $300 million Micro Focus previously committed to cutting as part of an ongoing effort to return to profitability and growth.

    OpenText CEO Mark J. Barrenechea told analysts the ultimate goal is to enable organizations to accelerate their digital business transformation initiatives using a set of application programming interface (API)-centric offerings that reside on a private cloud.

    Digital transformation represents the largest opportunity in the history of computing, he said, but Barrenechea also acknowledged that a lot of companies are still struggling with making that transition. “There has to be a better way to get digital transformation right,” he said.

    The Micro Focus portfolio includes everything from a robotic process automation (RPA) offering, a recently-launched IT service management (ITSM) offering—dubbed Service Automation Management X—along with the Vertica database and LoadRunner testing tools. There is also a slew of cybersecurity platforms that include ArcSight, Fortify, IDOL Zenworks and Sentinel along with legacy COBOL application development tools and even the remnants of Novell.

    In effect, OpenText now has one of the broadest software portfolios in the industry after previously acquiring Documentum, Carbonite, Hummingbird and Zix. “The strategy appears to be to simply gather up all the pieces on the chess board,” said Mitch Ashley, principal analyst for Techstrong Research, an arm of Techstrong Group that is also the parent company of devopsy.kinsta.cloud.

    Despite the disjointed Micro Focus portfolio, OpenText has no intention of selling off any of those offerings, said Barrenechea. Going forward, the strategy is to not only accelerate the transition to the cloud but also expand application license renewal services, he added. OpenText also sees an opportunity to expand the appeal of the Micro Focus portfolio into the small-to-medium business (SMB) market, noted Barrenechea.

    All told, it will take six quarters once the deal is closed to align the Micro Focus business model with the one OpenText currently employs, which Barrenechea said should result in growth starting eight quarters after the deal closes.

    There’s no doubt that, once the deal closes, IT organizations that rely on Micro Focus will be closely watching the level of ongoing investment in the portfolio for any signs of one platform being deemphasized in favor of another. It’s also probable that many customers will be relieved to see the stewardship of those platforms assumed by a company that is on firmer financial footing.

    Regardless of how the OpenText portfolio evolves in 2023, however, one thing that is certain is IT organizations have no shortage of alternatives to consider.

  • Techstrong TV: Leveraging Low-Code Technology with Tools & Digital Transformation

    Techstrong TV: Leveraging Low-Code Technology with Tools & Digital Transformation

    Low-code is playing a big role in Henkel Corporation’s digital transformation by connect remote workers with 30 shop floors all over the globe. Catarina Pinto, Henkel Digital Transformation Manager discusses how the team leverages low-code technology to deliver weekly releases across ten apps. HCL Software AVP Product Management Andrew Manby shares the role HCL Volt VX is playing at Henkel and other customers’ digital transformation initiatives. The video and a transcript of the conversation are below.

    Announcer:                 This is Digital Anarchist.

     

    Interviewer:                Well, the really great pleasure being joined by two very fantastic people talking about low-code/no-code and some of the impact from digital transformation projects. First joining me is Catarina Pinto, who is the digital transformation manager with Henkel, and she’s – Henkel Corporation. She’s gonna be talking about their project and involve low-code and that has been taking place. And a repeat guest, returning guest sitting in the right-hand chair is Andrew Manby, who’s AVP product management with HCL Software. Welcome to you both.

     

    Interviewee 1:             Thank you so much.

     

    Interviewee 2:             It’s great to be back,  Mitch.

     

    Interviewer:                Welcome back. Well, let’s do this. Andrew, why don’t you briefly introduce yourself, and then, Catarina, I’ll have you do the same, tell us a little bit about Henkel, and then we’ll go right into talking about your transformation project.

     

    Interviewee 2:             Right, perfect. So my name’s Andrew Manby. I head up product management for our HCL Digital Solutions portfolio. My specific focus and passion is really about digital transformation and using low-code to do that, and our tool of choice here is Volt MX, our low-code tool for professional developers.

     

    Interviewer:                Funny, that’s our topic today. And then –

     

    Interviewee 1:             I think this is.

     

    Interviewer:                Yes, go ahead.

     

    Interviewee 1:             Sure. Catarina. I am, as were said, digital transformation manager here at Henkel. I’m based in Amsterdam and I mainly work with the factories, so my goal is to lead partly the digitalization of the factories. I’m responsible in leading a global project that is the Connected Worker, where we basically aim to augment our workers in the shop floor. One of the biggest parts in this program is the Connected Worker apps, and that’s made with Volt MX as well.

     

    Interviewer:                Excellent. Well, I’m sure that a lot of interesting things have been happening over the last 18 months plus. How long has this project, digital transformation project been happening? Has it been more related to the pandemic, or is this part of the bigger program that’s going on across the company?

     

    Interviewee 1:             This is part of the bigger program we have. It’s one of our core pillars in the company, and it has been in full force since I joined, so 1. years ago.

     

    Interviewer:                Great. So your part of the project, would you say that’s a big component of it or one of several?

     

    Interviewee 1:             In this moment is the strongest component of it, so especially the Connected Worker apps, but we have a lot of things going on in our factories. We have a very powerful digital backbone. There are plenty of articles out there, business cases out there in terms of our digitalization in the supply chain, especially in Laundry, where I sit in this business unit. And basically what we aim is to extend this super powerful backbone that connects our machines in more than the 30 sites that we have worldwide, and also give the extra information of the user, so the knowledge of the person that is operating the machines, that is making sure that products are with extreme quality, that is making sure that everything is safe in the shop floor.

     

    Interviewer:                Now, we talked about the project you’re doing and with remote workers to the factory floor. Is that people who are across all 30 of those locations generally? Is it more concentrated in certain areas, locations?

     

    Interviewee 1:             No, we have, we are a real global program, so whenever we deploy an app it’s for everyone. It certainly helped during the pandemic because there was less need for people to be all the time in the shop floor if they are not business critical, and you can still see all the information from far away about what is going on in the shop floor, and basically are establishing a new way of communication here.

     

    Interviewer:                Great. And are you most of the way complete with this project? Are you still in the sort of early throes of it? Where are you at on your journey for this particular initiative?

     

    Interviewee 1:             So I would say that we are certainly in the scale up phase. So imagine this as a mini startup within the company where we see in the shop floor what are the processes that we can digitalize, so basically everything that is done in paper we will try to create an app or incorporate in our ecosystem so that we allow this information to be part of our data lake and really have insights from that. So we will work on everything from designing the product based on customer needs, so a lot of needs finding that is out there. Product design is also on our feet. Then we do the development with two teams of developers in this moment that we have, one in Cairo, one in Serbia. And then we also lead the implementation within the factories, so it’s a big project with a lot of scoping and that really hits all the parts of the factory, be that continuous improvement, be that safety, quality, and other departments that we are also thinking about expanding to.

     

    Interviewer:                Yeah. Mission critical for sure. So let’s talk a little bit about the role of low-code and the tools that you’re using, obviously Volt MX being one of those. And I know you’re here not as an endorsement necessarily, but clearly you’ve partnered with HCL Software and they’re playing a role in this also. Is low-code type tools, is that something relatively new to Henkel, or have you been using those types of tools for quite some time?

     

    Interviewee 1:             So they are relatively new, since the project started I would say, but it was super important for us because we really wanted to be very quick to market. And since the beginning of the project we kind of work like an Amazon company would do, so our goal is to get products that are unfinished into the shop floors, so MVPs, and make sure that we kind of use it as a playground with the people in the shop floor to get real user needs, to make sure that it’s customizable to 30 locations. So it’s really important for us to be not only fast in getting the MVP, but also fast in getting the feedback introduction of our people. So we are very people based, very customer obsessed. We really did this very big mindset shift in terms of it’s not creating the whole product and then shipping, but delivering that iteratively with the people that will use it in their day-to-day, and here low-code plays a very important role because it allows us to be very fast in getting to the market needs.

     

    Interviewer:                Yeah, a very lean approach doing MVP, rapid development iterations of your releases, so totally, that’s a great use of low-code type technology. Andrew, are you working directly with Catarina on this in the organization, or kind of observing as part of the HCL team from a little bit more distance?

     

    Interviewee 2:             I would say observing more about what they’re doing, and I think there’s a good interchange between our people in Europe working with Catarina and her team. We want to invest in some future innovation things that they’re looking at as well, and to bring those and help Catarina. Because I think part of the value that I hear from customers is us coming to the customer and saying, “Well, we’re sort of seeing these trends. How do they apply to your individual business?” And then take them through a period of exploration to really try and understand what is your digital vision? Now let’s get concrete on a specific area, and how does that innovation really help?

    I think in terms of Henkel, they are a leading innovator in digital transformation. I mean I, given the types of things they’re doing, they’re very data centric and very outcome oriented, and I think this initiative dovetails. But what delights me about what some of Catarina’s point of view is very pragmatic, but it’s – I think one of the things that you said, Catarina, is when you’re interacting with the people on the shop floor, you’ve got to show the value to them directly. Right? So if it’s – I was thinking about the expression you have. It’s not only simplifying their lives, but it’s as easy as paper. It’s got to be. Yeah.

     

    Interviewee 1:             Exactly. With our biggest competitor, so in the end it’s really difficult to compete with, and that was really a key, it plays a key role that we really have the interest of the people. And if people feel ownership in the sense, oh, I asked for this feature. Two days later it was there, it’s so much more important. They understand. And in the beginning I had to do a lot of push to say, “No, please give me your feedback. Bring me your problems. That’s exactly why I am here. I’m contacting you every day.” Until the problem today that is I get my inbox flooded with all the requests, and I don’t know where to turn to. But I think it’s much, much more – it’s a much better environment.

     

    Interviewee 2:             Yeah. So that’s actually interesting, Catarina, ’cause you’ve reached that sort of tipping point where it’s actually, instead of being push, it becomes a pull –

     

    Interviewee 1:             Exactly, and that –

     

    Interviewee 2:             – from the factories, which is tremendous, and I think you were also telling me where they’re actually saying now is, you know, we want these features and we want more iPads. Right?

     

    Interviewee 1:             Yeah, and that’s a big pull from the company as well, but I think it’s, I see it as a very positive insight into the program. Just building on the previous point, for example we are trying to build now a product, also app-based, but the idea is that it’ll be a company-wide product, so be for all the functions within the factory. And especially in the beginning I was a little bit unsure. I was thinking maybe this is too much. And then one of the factories just told me, “Hey, if you add these two little things, I can push this all over the factory.” Like okay. One week later, they were implementing in all functions, and I got, wow, that’s amazing. I didn’t even need to do marketing because their, it was one of their biggest needs, and we are really cooperating with HCL to really take this to the next level, and I think it will be a very awesome product.

     

    Interviewer:                What’s interesting is over so much time people have gotten conditioned when requesting technology applications, systems, you know, they don’t get what they want very quickly, at least they haven’t historically, and so I imagine it’s a big shift, a big mind – initially they didn’t expect you to be able to deliver as quickly as you are, and now that they are, of course, they flood your inbox. Right? Be careful what you ask for, too, right?

     

    Interviewee 2:             Yeah. Yes, exactly.

     

    Interviewee 1:             _____.

     

    Interviewer:                I’m curious, how many people do you have working on the project? And is this inside IT? Is this outside of IT? How’s it considered –

     

    Interviewee 1:             No, it’s inside IT. So we have in this moment four developers sitting in two places, two kind of scrum masters, say it like this. I act as product owner as well, so I have a lot of hats during the development of the products, so from end to end of the products, but that’s basically the core of the team. So very, very small team, and we really need – it’s like I said, like almost a mini startup, and we have ideas and we say, “Okay, find a way to do it. Let’s do it. Let’s put this into the ground and let’s make people happy with what we do.”

     

    Interviewer:                Are you doing sort of an agile two-week sprint type approach?

     

    Interviewee 1:             One-week sprint –

     

    Interviewer:                Are you doing more DevOps release it as it’s ready, it’s tested, it’s good to go?

     

    Interviewee 1:             In this moment we are doing one-week sprints, so really we – especially because we have a lot of apps simultaneously. So we have in this moment around ten apps that are part of our major ecosystem that all need some kind of maintenance or they have new requests from the guys on the shop floor, or I have new ideas that I want to implement. They are based obviously in customers’ feedback. So it’s really very, very fast. We don’t release in all of the streams of course, but we try always to be very based on customer requests and superuser centric.

     

    Interviewer:                So how would you say using low-code, using Volt MX low-code kind of tools, how does that – has it fundamentally changed your ability to deliver that quickly? Is it that revolutionary? Is it sort of an evolution of a journey you’ve been on to get to this point? How would you describe it?

     

    Interviewee 1:             I think it certainly helps, and especially with the connection with HCL that provides a lot of support so that we can also take advantage of this low-code product, that we can create things that are repeatable. Right? That we don’t have to reinvent the wheel every time that we build something. And here really the size of the market decreases, yes.

     

    Interviewer:                Interesting. And something Andrew and I have talked about is the citizen developer, the professional developer, inside, sometimes both inside IT, can also be external. Would you consider your team more of a professional development team as what people – that’s their jobs is being developers, or are these citizens, business people sort of performing the development functions?

     

    Interviewee 1:             In this moment a little bit more towards the professional developers here, because we really are not that big and we really have a lot of apps, so we really need to be a little bit more focused on that.

     

    Interviewer:                Interesting. I’m curious, Andrew, what do you see – you see some commonalities between things that are contributing to the success that Catarina is having at Henkel that you maybe have seen with other customers?

     

    Interviewee 2:             Yeah, absolutely. Yeah. I mean our focus, Mitch, is predominantly in enabling people like Catarina and Henkel with the professional development teams, and they don’t need to be big teams. I mean you can tell they’re a very agile team, a very responsive team. It’s very impressive to hear that. In our world, it’s really that idea if they’ve got the vision around the digital transformation and a willingness to be able to do that, we can help facilitate to do that very quickly with them, and I think it’s really that partnership. Sometimes that’s simply just being able to sit down, train, work with the customer, train them, build some prototypes, and sometimes it’s a little bit more of a discussion around a business process that they want to re-engineer. And we have a, what we call a studio process where we can bring them in, we can reimagine or think about what that would look like, build a prototype, and then get the feedback from the people on the ground about whether that would work. And sometimes either of those approaches works. it just really depends, I think, on the maturity of the organization.

    But what I also find interesting, which is embedded in what Catarina was saying about the only if you add that couple of thing, you know, we’re seeing that – we did a session recently with Jarrod from VELCO which is up in Vermont, the Vermont Electric Company, and they’re like the nation’s first purely distribution network, and they’ve got about 15 apps out there and they’re starting to think about how can they sort of consolidate some of those apps and build some super apps in the area of field service. So we’re seeing the folding in on some of those developments to go in new directions, but one of the impressions and the feelings I get talking to the customers, where they start and where they end up are two different places. I mean like the old adage, right? There’s always new ideas that come from customers that take them in different directions. In the case of VELCO, they have a scientific application which is part of the government reporting to say, you know, in times of hot temperature, what happened on the loading of the transmission lines. So that required them to integrate with MATLAB software and lets you do some heavy computational analytics.

    So I mean what we’re seeing is people are asking the questions, and we’re sitting down with them and figuring out how to do it, so it’s an exciting time.

     

    Interviewer:                It definitely is. And Catarina, sorry for stumbling on your name. I’m curious, success breeds more success, or certainly brings a lot of attention, and one of the things that’s happening in this whole COVID time acceleration of digital transformation projects is as people had success other parts of the organization started looking at that and say, “Well, how come they can deliver in a week, and we deliver every two months,” or every whatever. Are you getting some attention from the rest of the organization? Is that part of why you’re adding more apps, or are other groups looking at potentially spinning up and doing low-code kind of work?

     

    Interviewee 1:             A little bit of both. So from our organization, I would say yes because we are really working, maybe we are even extreme agile because we are one-week sprint. But the mindset shift of delivering products to the shop floor that are not extremely ready, that are still to be improved, that are lending pages in apps that then are created with the people, I think it’s an almost new paradigm shift that we are starting to see more and more and more, and people are also requesting things that are more useful for them for their daily lives.

    And one of the things that we are also doing is we are going into this exact idea of having less mini apps and have one core that connects our backbone to different modules, and the apps worked basically as modules and puzzle pieces. And that’s more or less type of ecosystems that we want to have, one thing that connects everything that’s basically our core, this big problem that I was talking about, and then having the different workflows that the guys have to do every day, just piece in in order to make the complete puzzle.

     

    Interviewer:                Wonderful. This has been fascinating. Thanks for sharing your story with us, and congratulations on your success, and congratulations also to the HCL software team with a very apparent, a happy customer and productive team using your technology and leading digital transformation. Catarina Pinto, thank you for joining us from Henkel, and Andrew Manby, thank you of course from HCL Software.

     

    [End of Audio]

  • Tech Workers Struggle With Hybrid IT Complexity

    Tech Workers Struggle With Hybrid IT Complexity

    Confidence levels among IT workers have plummeted as tech teams’ jobs have become more complex. The reasons behind IT worker angst are unprecedented, signaling a shift paralleling other post-pandemic industries. Running applications across cloud and on-premises infrastructure, hybrid office environments with distributed workforces and the accelerated adoption of new and automated technologies have all contributed to increased IT complexity.

    In our recently-released SolarWinds IT Trends Report 2022—Getting IT Right: Managing Hybrid IT Complexity, we examined the current state of IT along with areas of opportunity for technology professionals who must manage this increased complexity as hybrid IT accelerates. “The continued shift to hybrid IT drives increased levels of IT management complexity, but tech pros feel a lack of confidence in how to best manage it,” according to the report.

    Manage Hybrid IT Complexity

    Solutions are necessary, as the research shows only 8% of tech pros surveyed for the IT trends report feel “extremely confident” in their ability to manage increasingly complex networks. More than half of the tech pros interviewed said their organization manages hybrid IT complexity by training staff and adopting IT monitoring/management tools. However, budgeting, time constraints and hybrid work environments exacerbate this challenge. These responses point to a need for intervention and assessment, as IT professionals’ work is more business-critical now than ever. Strong IT infrastructure is necessary for fundamental processes across all industries and business environments.

    Half Lack Visibility

    According to a report by market intelligence firm IDC, as more mission-critical workloads move to connected cloud architectures spanning public, private, hybrid and multi-cloud environments, enterprises recognize the need to invest in the tools which will help them ensure consistent policies and performance, despite budget and observability implementation issues. The SolarWinds IT Trends report revealed nearly half of respondents lack visibility into the majority of their organization’s apps and infrastructure.

    Indeed, visibility is increasingly becoming the clear answer for tech pros charged with managing greater levels of complexity in these diverse and distributed environments. To develop their teams and business for long-term success, organizations must set aside time and resources to upskill and train tech pros to help them properly implement observability strategies and manage hybrid IT realities more effectively.

    Effectiveness Lost Off-Site

    But some aspects of the remote revolution, including training IT workers for increasingly complex network management, brainstorming sessions, providing sensitive feedback and onboarding new employees, lose their effectiveness when done off-site. For those who’ve made the switch to teleworking, most have found more work-life balance but less connection with co-workers or consistent support from leadership, according to a Pew Research Center study.

    Software company Culdesac announced it’s moving workers online and closing its San Francisco offices. Over 14,000 Google workers worldwide moved to a new office or went fully remote during the pandemic. Other companies, like Microsoft, have said employees who want to work more than 50% of the time remotely must have their schedules approved by their managers.

    Things are quickly shifting as we enter the era of post-pandemic IT infrastructure existence.

    Standards for Automated Network Management

    Solutions are growing in availability. The Internet Engineering Task Force (IETF), an international community of network designers, operators, vendors and researchers, is working on standards for automated network management, which aim to improve and make the management of networks more efficient as they continue to increase in size and complexity.

    While organizations also lack insight into their network’s impact on ROI due to increased hybrid IT complexity, looking forward, they must re-examine their investments from the past few years. Part of this requires companies to have visibility into their IT environments to understand what’s working and not working.

    Economic Growth for Those Willing to Adapt

    Technological change could bring about economic growth and opportunity, but only for those willing to adapt. IT infrastructure is so much deeper than most businesses understand, and as the existing data confirms (and most experts in the field agree), investing in IT infrastructure is necessary. A business’ network—and its speed and security—can be the difference between satisfied or frustrated employees and customers.

    As hybrid IT acceleration has increased network complexity and lowered tech pros’ network management confidence, these post-pandemic problems are a chance for organizations to evolve. “The healthy thing to do is to look ahead, accept the reality, and start getting ready for the transition,” said Chirag Shah, an associate professor at the University of Washington Information School. “So instead of feeling the anxiety and being defensive, think of this as an opportunity for advancement.”

  • Don’t Let Developer Toil Affect the Business Value of Your Apps

    Don’t Let Developer Toil Affect the Business Value of Your Apps

    It is no surprise that the world today is driven by apps. Organizations all over the world are basing their business goals on their capacity to integrate new apps quickly, and they need to constantly reimagine how they interact with and communicate with their consumers and employees to fulfill changing expectations. To do this effectively, businesses need to operate at a high level of speed and agility. But in many cases, this isn’t happening. The phrase ‘move fast and break things’ could not be further from the truth when it comes to how enterprises approach innovation today. In fact, according to Forrester Consulting, 48% of executives say they haven’t changed their applications in a year or more. One reason for this may be that organizations are dealing with a high amount of developer toil and technical debt. Developer toil is the repetitive, predictable, constant stream of tasks that support the creation of software and how it’s run, but don’t actually affect the features in the software that people use. Or in other words “any activities that don’t directly create business value.”

    Typically, developers spend too much time on processes that could be automated or even eliminated. Ironically, this toil builds up over time as their organizations prioritize shipping features rather than addressing these problems in their overall software process. While developers can change their software quickly at first, just like debt in real life, if this toil and tech debt are neglected, it takes over and consumes the organization’s ability to grow. This results in long, infrequent release cycles. A feature that seemed simple and once took just 15 minutes now takes weeks, even months, to get in front of users.

    Conducting a Developer Toil Audit

    Anything you can do to speed up your software release cycle will improve the quality, resilience and business value of your software. Continuously addressing developer toil provides a significant boost to your organization’s software capabilities. For one of VMware’s customers, addressing developer toil reduced the time taken to introduce a new feature significantly–from 400 hours to just 24 by doing a developer toil audit and addressing key factors contributing to this technical debt.

    So how can organizations overcome developer toil? One way to do this is through a developer toil audit. This is a systematic process for finding, valuing and prioritizing fixing waste in your software process. First, the process finds wasted time and process debt in how you build and release software. Second, the process then helps you justify delaying working on features in favor of eliminating and automating your software creation process. The result is speeding up your software release cycle. The more frequently you can change and release software, even with just small changes, the more opportunities you must learn what works and put those features in front of customers, employees, and other users.

    The process of conducting a Developer Toil audit includes:

    1. Asking the right questions: A great way to uncover developer toil is to ask about people’s struggles, frustrations, and even boredom in the form of a tailored question set. We advise using questions that are specific to your organization in addition to general questions like “how long does it take to perform a full build?” For example, highly regulated organizations should ask about tasks involving compliance. Once the survey is completed, you can do some quick analysis to locate and prioritize developer toil.

    2. Combine into usable metrics: You now have a single metric for each type of developer toil. And by combining all the questions you create a single metric to track overall developer toil. Extra points for creating dashboards with visualizations! As with all such aggregate metrics, these are more directional than exacting—their job is to point you to problems that should be solved.

    3. Link these metrics to business value: A simple ranking of developer toil is better than nothing. However, before deciding which developer toil to address, we recommend linking each type of developer toil to the business value created by fixing the toil. Put briefly, the value you get will be related to the time saved, and, thus, the ability to ship more features in the future.

    The less time developers spend on toil, the more time they can spend on tasks that directly benefit the business. Another way of looking at this is plain old productivity: Developers can now do more with the same amount of time.

    Another important outcome is increased staff morale. The less time developers spend on boring, repetitive work—toil—the happier they’ll be. Stronger employee hiring ability and retention are (or should be) a strategic imperative for any organization that depends on software. Morale also increases software quality: happier people make better software.

    Slow Down to Speed Up

    With the survey results in hand, you should have a pretty good idea of which developer toil to fix. The last step is to do the usual product management prioritizing to weight fixing these items with other tasks you could do. These are strategic decisions that product managers need to make. To fix toil, you need to stop shipping features to free up time. You need to slow down the business. At the start, before product managers have been empowered to make these kinds of decisions, higher-level management should be involved to calibrate how much slow down you’re willing to put up with for future agility. The calibration you’re doing is this: If I fix one item of toil and ship just one feature (instead of two) this release cycle, then in the next release cycle I can ship four features. Humans are not great at that kind of bird-in-the-hand versus birds-in-the-bush thinking, so you’ll need to figure out what works in your organization.

    Through our experience as consultants working with product teams in different industries, we’ve used Developer Toil Audits to focus and motivate product managers and developers to fix toil and speed up their release cycles and, thus, improve how their organizations build software. This directly improves the business by adding more capabilities and capacity to deliver more features, even in the short term. Each time you fix any technical debt, you gain more capacity and capabilities to create new features and improve your software. This is how you use a modern software culture to increase business agility. Or, put more simply: Less developer toil leads to better software, and better software leads to better business.

  • TechStrong Con 2022: Exploring What’s Next in Tech

    TechStrong Con 2022: Exploring What’s Next in Tech

    We have become increasingly reliant on technology and it’s hard to imagine life without all the great tech inventions we use in our daily lives. As technology keeps progressing, more is expected of IT teams, and security is a top priority.

    While we are still trying to get used to the new normal, the IT community continues to shine as a beacon, demonstrating how humans are leveraging technology to overcome the many challenges we face. On June 21, business and tech leaders who are working on transforming the world and moving it forward will come together at TechStrong Con Virtual Summit to celebrate the power of technology, share their stories, provide practical insights and lend valuable advice to help other professionals succeed in their careers. More than a virtual event, it is a community gathering that offers learning, networking and upskilling opportunities. Now in its third year, TechStrong Con continues to serve as a testament to the ways in which technology can improve human existence.

    Things You’ll Learn

    The agenda features a mix of topics including live coding, cloud-native, cybersecurity, digital transformation, observability, DevOps, open source and more. Attendees will have the opportunity to learn from some of the brightest minds in the industry about:

    • Managing the security of APIs
    • Key observability trends for 2022
    • How to accelerate digital transformation
    • Habits that will help improve your security posture
    • The state of the software supply chain post-Log4Shell
    • The distributed cloud
    • The future of data engineering
    • Building a diverse cybersecurity workforce
    • Crypto and NFTs
    • Low code and citizen development
    • The value of feature flags
    • How DevOps must be part of your future to attract the right talent
    • Managing and motivating teams in a hybrid environment

    Meet the Speakers

    The speaker lineup features globally recognized business leaders, DevOps, cybersecurity and IT experts including:

    • Sholmi Ben Haim, co-founder and CEO at JFrog
    • Chenxi Wang, founder and general partner at Rain Capital
    • John Willis, senior director of the global transformation office at Red Hat
    • Caroline Wong, CSO at Cobalt
    • Thomas Krane, principal at Insight Partners
    • Lisa Plaggemier, executive director at National Cyber Security Alliance
    • Tami Mazel Shackar, CEO at Incredibuild
    • Tom Sweet, VP in IT solutions at GM Financials

    Visit the Exhibit Hall

    In addition to the sessions, attendees can visit the virtual exhibit hall to interact with partner sponsors including Chronosphere, ConnectALL, Tidelift and TechStrong Research. The expo hall will be open throughout the event, giving attendees the opportunity to chat with the sponsors and download information at any time.

    Registered attendees will also receive a link to access the virtual environment on-demand. To see the full agenda and to register for free, please visit the TechStrong Con website.

  • Why is Security Still in the Way? A Look at DevSecOps Right Now

    Why is Security Still in the Way? A Look at DevSecOps Right Now

    According to industry trend reports for 2022, DevSecOps is now considered to be one of the most effective approaches to building software quickly and securely. This effort, of course, means development, security and operations teams commit to addressing security as early as possible in the software development life cycle (SDLC). The goal of the shift into DevSecOps revolves around the need for more automation, streamlined CI/CD pipelines, less friction among teams and plenty of time for productive innovation. Incorporating DevSecOps practices into an organization unites security, compliance and development issues into a collaborative concern, one that allows DevOps to move fast without jeopardizing code quality. 

    As we approach the middle of 2022, it’s worth looking back and considering why security is still standing in the way of smooth software development. Security vulnerabilities have always been present in the process, and yet these pesky bugs continue to be the biggest threat to software performance. The question is, why?

    The Truth About Security

    Software has always been deployed and shipped with some existing bugs. But as software and services continue to dominate our everyday lives, the reality of this statement continues to plague both businesses and the end user. On some level, software development has yet to evolve into the next phase of security. Code is still rolled out regularly, only to discover security vulnerabilities in production. Some say the way software is developed today actually lends itself to defects, mostly because the pace of work required supersedes best practices around AppSec. 

    While the larger cybersecurity industry—and every DevSecOps team in the world—is striving to make software more secure, many organizations still prioritize speed and productivity over digital risk. This means the state of security (and, to some extent, the DevSecOps world) has become somewhat lopsided, with some enterprises making great efforts while others embrace a more lackadaisical approach. To make matters worse, many professionals today believe there has been a general under-investment in cybersecurity over the past several decades. 

    The Next Phase of DevSecOps

    The shift to remote and hybrid work models has led to mass adoption of cloud technologies and digital transformation, across all sectors and industries. As a result of this evolution, organizations today need to bear in mind that the more services they use, the more digital threats and overall risk they face. As this exposure to vulnerabilities increases, so does the need for new approaches to security. 

    The majority of modern enterprises do, in fact, have a security process in place, as well as other risk management solutions. But with the cybersecurity reckoning of 2021 and the stakes of cloud computing being higher than ever, businesses right now are feeling the pressure to think long and hard about why security still isn’t a guarantee. The trend of slowing down software development to address security more thoroughly, also known as the secret sauce of DevSecOps, is not free from roadblocks—but it is also far from optional. For many organizations, the implementation of DevSecOps practices feels less like security and more like speed bumps that just slow down the shipping of software. 

    Even so, the effort to improve security is happening now. Organizations do not need several solution platforms or tools to get started. They can begin right away; evolving their security tools and practices as they grow the business. With this growth comes one of security’s biggest challenges—scalability. Because toolchains across the cloud have become more and more complicated, setting policies and/or workflows in one tool is challenging. While these issues can be largely addressed by the adoption of an end-to-end security solution, organizations must continue to focus on strengthening supply chains, improving security oversight, and bolstering their approach to DevSecOps. Some ways to make this happen include:

    • Making sure CI/CD pipelines are integrated with DAST and SAST testing in development
    • Ensuring developers and DevOps teams complete vulnerability scanning before commit or merge, as they write code
    • Minimize manual security as much as possible with automated AI/ML tools to support more effective scanning and monitoring
    • Invest in management solutions that improve security in a multi-cloud environment

    Addressing the Supply Chain

    According to an industry survey, 60% of companies have decided securing the software supply chain should be a top priority for 2022. When we think about software supply chain attacks, we need to think about better controls to validate its integrity through all stages of the SDLC. Obviously, DevOps and automation have provided considerable help in this area; however, they cannot pull all the weight of security without proper governance and guardrails. 

    With a secure supply chain comes better security, as well as compliance, privacy and transparency. When a supply chain is secure, it can automatically enforce policy requirements for things like instrumentation, testing and architecture. As a result, software development and deployment become a repeatable process that is also reliable. Teams across the organization can rest assured that the products and services they are building comply with security expectations, such as validating code before production with static analysis and scanning tools. 

  • When DevOps-as-a-Service (DaaS) Meets Security

    When DevOps-as-a-Service (DaaS) Meets Security

    One of the most recent IT methodologies to be offered as a service is DevOps, a cultural and practical approach that brings development and operations teams together under one umbrella of work. DevOps-as-a-Service (DaaS) ensures that everything related to the selection, management and maintenance of DevOps tools and infrastructure, including all policies and procedures, are addressed through a centralized team who are able to provide this service to development teams across the organization. 

    From a 30,000-foot view, DaaS represents DevOps capabilities made accessible to practitioners through portals and APIs. Because DevOps capabilities vary among organizations, there is no standardization of these services. For the business, DaaS enhances competition. Application users and developers find DaaS improves overall software development, while specialized DaaS teams say it improves the management of DevOps capabilities.

    What Are the Other Benefits of DaaS?

    DaaS offers many benefits, especially to development teams who no longer want to spend all their time configuring and deploying the necessary security tools to run DevOps pipelines. This means it’s no longer necessary to understand all the differences between DevOps tools and the underlying infrastructure, as the appropriate tools and technologies are automatically deployed for development teams. As a result, developers are able to focus their efforts on creating innovative software at the speed of business. 

    Further, Daas delivers clear business and operational benefits in the form of a more streamlined process for facilitating DevOps across the enterprise. Daas supports governance while also enabling centralized oversight and visibility into development workloads and productivity. As we know, this shift leads to increased accountability among teams and an overall optimization of business processes. Add on resource efficiency and cost savings through tool selection, and it’s easy to see why DaaS has found a home in the world of software development. 

    But despite the benefits, Daas also presents new security challenges that can’t be fully addressed by traditional management solutions. These approaches are often sluggish, expensive, and/or incredibly complex to manage.

    What About Security and DevSecOps?

    Because the principles of DevSecOps proactively address the risks and threats associated with DevOps processes, it has seen rapid adoption in recent years. By integrating AppSec tools and strategies within a DevOps pipeline, developers are able to find and fix security vulnerabilities earlier within the software life cycle—not after the fact. This ability is what allows developers to generate secure and high quality software from the beginning, while also preventing any deployment delays stemming from last-minute security checks in production. With DevSecOps processes in place, AppSec testing becomes seamless and transparent for developers, who need a frictionless experience to facilitate steady and reliable software development and deployment. 

    DevSecOps is a  natural fit for the as-a-service delivery model. Similar to DevOps, AppSec involves various tools, policies and processes that demand a certain degree of professional expertise—not to mention the time and resources it takes to to select, maintain, and deploy them to drive DevSecOps practices. Security and development teams looking to  implement and manage DevSecOps can reap major benefits from a centrally defined and managed process, to be administered by a specialist team and delivered “as a service” to those in charge of DaaS.

    Standardizing AppSec through a DevSecOps-as-a-Service offering would guarantee security is applied evenly across all DevOps activity, thereby allowing businesses to produce secure and high-quality software consistently while also supporting AppSec compliance demands. This shift also establishes a foundation where a holistic and homogenous view of AppSec can be found, one that is critical to the assessment and management of application and business risk. 

    Developing DaaS Metrics

    First, don’t try to boil the ocean by measuring all applications at the same time. Instead, choose an application that’s supported by DaaS processes and appoint a specialized team to develop metrics for the application. This team can look many ways—but would likely include stakeholders, developers and other DaaS-supporting roles. Service-level indicators (SLIs) and service-level objectives (SLOs) are also baked into this model, which are chosen to best suit the requirements of an individual application. 

    Once the most valued SLOs of DaaS are determined, the service can be tailored to identify the most critical SLIs. With this knowledge, things like instrumentation, telemetry and analysis requirements can be identified and used to design alerts, dashboards, analyzers and more. Next, setting up policies and procedures around accountability establishes a complete solution. And once the solution for the chosen application is tested, confidence kicks in and creates an easier process for adapting and expanding the process around other applications. 

    This means DaaS can provide many key capabilities to both the organization and the teams who rely on them. A specialized DaaS team can then figure out the best metrics for larger implementation on any application. As a result, SLOs can be evolved for other future applications, to be used as a baseline for future improvements.