Tag: digital transformation

  • What Makes Digital Transformation a Success?

    What Makes Digital Transformation a Success?

    Despite more than $5 trillion having been spent on digital transformation efforts, survey after survey shows that successful digital transformations are far and few in-between. By many estimates, more than 50% of digital transformation efforts failed in recent years.

    While a recent survey conducted by Hanover Research and commissioned by AHEAD, the State of Enterprise Digital Transformation, found that 93% of enterprises are undergoing some digital transformation as they seek to cut costs (77%) and improve customer experience (71%). The survey found 42% of enterprises struggling to reach success as their efforts fall behind or stall.

    This survey found many challenges, both demanding and typical among enterprise digital transformation efforts, including hurdles created by legacy systems (36%) and technical debt (24%). With that in mind, it’s no shock that 67% cited infrastructure as a critical part of their digital transformation efforts.

    Additionally, the survey found that improving operational efficiency and cost-cutting are motivators in 77% of digital efforts. Those needs beat improving the customer experience, at 71% of enterprises.

    When it comes to results, this survey found more optimistic results. According to the survey, 58% of those surveyed said their digital transformation projects are on target or even ahead of schedule, with only 42% citing faltering progress.

    The State of Enterprise Digital Transformation survey found six core factors of success:

    1. Dedicated Leadership: The survey found that 83% of digital transformations that are on track or ahead of schedule are led by a CIO, CEO, CDO or CTO. As digital transformation touches every part of an enterprise, the company-wide buy-in is critical. While 27% of organizations have a CIO leading their transformations, only 8% of organizations have a chief digital officer leading the transformation efforts. Chief technology officers are leading the efforts at 16% of organizations.
    2. All-In Approach: Transformations that are on track are 30% more likely to be structured as full-scale change initiatives. Because digital operations are often so interconnected, piecemeal and partial transformations can often be siloed and result in limited impact on the factors driving the transformation.
    3. Defined Digital Roadmap: Ninety-two percent of transformations that are on target or ahead of schedule have a defined strategy and roadmap that includes IT infrastructure and operations.
    4. Alignment Between Infrastructure and Apps: Enterprises powered by an integrated DevOps approach are 43% more likely to see success in digital transformation efforts. To avoid bottlenecks, enterprises should audit DevOps functions before undergoing digital transformation.
    5. Platform Mindset: Businesses that include IT infrastructure as a big part of their digital transformation are 36% more likely to have a successful transformation. As the backbone of a digital change initiative, an enterprise’s infrastructure determines how far the transformation will go and its limits.
    6. Commitment to Intelligent Operations: Companies that monitor IT performance in real-time and remediate issues quickly are 24% more likely to undergo a successful digital transformation. Further, the survey found that enterprises are more likely to see success in digital transformation if they have confidence in their abilities to perform highly in areas of automation, monitoring, hybrid cloud models and integrated security.

    Last year, in Digital Transformation: Coming from Behind, we cited research from the consultancy McKinsey & Company found that less than one-third of transformations are successful. While this survey from AHEAD finds more optimistic outcomes, most previous surveys and our interviews with transformers echoed AHEAD’s survey findings, with the need for leadership, dedication to platforms, defined strategy and proper alignment all being essential to success.

    The State of Enterprise Digital Transformation survey was conducted by Hanover Research through September and October 2019. The survey is based on the responses of 293 IT decision-makers with a direct influence on IT spend at companies based in the U.S., and with more than 1,000 employees.

    — George V. Hulme

  • The Definition of Faster in the Age of App Capital

    The Definition of Faster in the Age of App Capital

    Businesses want speed. One of the impacts of digital transformation—and the associated pressure to succeed in an app economy—is the desire to move at speed. Nearly half (48%) of organizations are driven by digital transformation to deploy faster according to our State of Application Services 2019.

    But it’s not all about deployment. It’s also about development and responsiveness to threats and changes in demand.

    Organizations want to develop and deliver apps faster. They want to adapt to unpredictable changes in business conditions faster. They want to respond to attacks faster.

    So, how are they going to get it?

    Faster Development

    Deploying more frequently implies you’re first developing faster. That often means adoption of speed-oriented Agile methodologies. GitLab’s 2019 Global Developer Report: DevSecOps found that the majority (54%) are choosing Scrum, while 37% go for Kanban.

    Componentization

    Methodologies aren’t enough if application architectures aren’t well-suited to development styles. Smaller, focused teams sprinting toward frequent releases isn’t really a good fit for developing new features or fixes for traditional and monolithic applications. Componentization through the adoption of microservices and more distributed forms of architecture fit more naturally with modern architectural and operational principles. It’s no surprise that, on average, more than 80% of a modern application is made up of third-party components, heavily weighted toward open source.

    APIs

    Adoption of APIs, as well, is no surprise amongst those seeking faster development through componentized application architectures. APIs decouple implementation from interface and allow teams to make modifications to processing without impacting the use of APIs from other components or applications. This is a common pattern, with an impressive 64% of organizations creating APIs today for use in either internal or external use cases. Nearly 50% of those organizations rely on APIs to get ideas to market faster according to Jitterbit’s State of API Integration 2018.

    Automation (CI/CD)

    The build pipeline, too, has to keep up if frequently deployment goals are to be met. That means CI/CD tools that seamlessly move code from commit to test to release. The most popular CI and build tools in GitLab’s survey were, unsurprisingly, GitLab (61%) followed by Jenkins (36%) and Travis CI (12%). Notably, our own research finds Jenkins in use by 16% for network automation as well—a promising result if organizations are seeking to extend DevOps beyond delivery into deployment.

    Faster Deployment

    Developing faster doesn’t get ideas to market faster. That requires deployment. While born-in-the-cloud technology companies have mastered the delivery-deployment divide with ease, many established enterprises find this transition challenging. Existing organization structures as well as the continued need to support traditional and monolithic applications introduces conflicts that can be challenging to integrate with modern operational demands. But there is no doubt that organizations must overcome these challenges for those applications requiring faster and more frequent deployments.

    Continuous Deployment

    Don’t be fooled; established organizations are embracing automation and applying it to the deployment pipeline. The issue is often that traditional IT structures introduce inconsistent automation and self-service efforts. We see this play out in our own research, where strongly siloed team structures continue to impact automation efforts across IT.

    Team structures matter and organizations whose compass is pointed at automated pipelines will need to address the cultural aspects of continuous deployment if they want to consistently deploy faster.

    Public Cloud

    Traditionally, the inability to achieve continuous deployment has pushed developers and app owners to turn to the public cloud, because it eliminates the obstacles in the slower, enterprise deployment path. The disparity in opinion on frequency of deployments is, in part, a contributor to the issue. Our 2018 NetOps/DevOps survey found that while 55% of DevOps and 52% of cloud architects felt their organization did not deploy frequently enough, only 30% of NetOps and the same percentage of operations agreed. 

    But it’s not the only driver. Digital transformation is certainly a factor; 33% of respondents in our State of Application Services indicated they are intentionally moving to deliver apps from the public cloud as a result of embracing digital transformation initiatives. The ability to easily integrate application services and subsequently automate operation is a huge boon to organizations seeking a faster route to frequent deployment.

    Containers

    In the cloud—but also on-premises—continuous deployment often requires the ability to adopt per-app pipelines and application services that support the model. Increasingly, organizations are turning to containers because of their ability to support rapid updates and operate seamlessly in highly volatile environments. We see containers in demand not only to support modern application architectures such as cloud native—the top container use-case at 33% of respondents to Diamanti’s 2019 Container Adoption Benchmark—but also for infrastructure. The demand for on-premises application services in containers has consistently grown year over year in our own research, rising from just 4% in 2017 to 15% in 2019.

    Faster Responses

    Not everything is about delivery and deployment. Organizations also need speed when it comes to security and operations. In today’s world, where more than half of all app interactions are conducted by bots, it’s important for organizations to respond quickly with a reject message to avoid falling prey to exploits or infection. 

    Real-Time Threat Analytics

    One of the ways organizations are seeking to speed up their ability to respond to attacks is through the adoption of real-time threat analytics. With security continuing to be a top priority and consistent challenge, it was no surprise to see this category ascend into the top five strategy trends and technology in 2019 with 41% of respondents tagging it.

    The availability of intelligent security application services will accelerate as machine learning and automation continue to apply their considerable capabilities to the problem of identifying troublesome traffic faster.

    Orchestration Included

    Machine learning isn’t the only way in which infrastructure and application services are getting smarter. As the need for faster responses to capacity and processing grow along with users, infrastructure and application services are evolving to include orchestration as a core capability rather than an add-on. Application service platforms with integrated orchestration layers will mean services that scale along with demand—on-demand. While such capabilities exist today—indeed, they are part and parcel of cloud and containers—the capabilities to automatically scale up and down based on application and user defined requirements is not native to most systems today. But they will be.

    Faster Identification of Bad Actors

    Finally, organizations need to combat bots for both business and security purposes. Whether organizations need to stop scraping—a real threat to business—or prevent bots from probing for vulnerabilities, identifying bad bot actors faster is critical today. Checking a box (I’m not a robot) isn’t enough today as bots are growing more intelligent and are able to foil such primitive techniques.

    Organizations are turning to Bot Defense services capable of applying more modern, successful techniques to quickly identify and block bad actor bots. We’ve seen the use of bot defense services grow quarter over quarter in response to this need, and expect this trend to continue.

    Faster Development, Faster Deployment, Faster Responses

    When it comes to business’ need for speed today, we wind up looking at processes. Development processes are automated to gain speed with CI/CD. Deployment processes are automated to gain speed with continuous deployment and cloud. Scaling and security processes are being automated by systems and the introduction of orchestration as native to application service platforms.

    Faster, it turns out, relies on an organization’s ability to automate processes across development, deployment and security. 

    — Lori MacVittie

  • Survey: Internal IT Teams Embrace ‘DevOps Inspired’ Processes

    Survey: Internal IT Teams Embrace ‘DevOps Inspired’ Processes

    The “2020 State of Application Services” survey published today by F5 Networks suggests more IT organizations than ever are adopting some elements of DevOps principles to manage an increasingly diverse application portfolio.

    Based on a global survey of 2,600 IT professionals, the report finds 63% of organizations still place primary responsibility for application services within IT operations. However, more than half the organizations surveyed said they are moving toward “DevOps-inspired” teams. In addition, 73% of respondents said their organizations are automating network operations to boost efficiency.

    Lori MacVittie, principal technical evangelist for F5 Networks, said the report makes it clear many IT organizations are trying to adopt best DevOps practices gradually. They may in some cases set up dedicated DevOps teams, but the preference long-term is trending toward a more evolutionary transition, she said.

    At the same time, application environments are becoming more complex at a faster rate. The survey finds three-tier web and mobile application architectures come are most common (40%), followed by client-server applications (34%), microservices/cloud-native applications (15%) and mainframe monolithic applications (11%). The survey also finds 87% of organizations are using multiple clouds, but only 27% of respondents will have more than half of their applications in the cloud by the end of 2020. It’s also worth noting less than half the applications being managed (45%) are external-facing.

    In terms of application services deployed today, the most common are SSL VPN and security services such as firewall, IPS/IDS, antivirus and spam mitigation, followed by load balancing, global server load balancing and DNS and web application firewall (WAF) and distributed denial of service (DDoS) protection. In the next 12 months, however, software-defined wide area networks (SD-WANs) take the top slot at 41%, followed by DNSSEC (37%) and service mesh (37%). Botnet protection, anti-fraud and common performance optimization services fill out the top six, with 36% of organizations planning to deploy each.

    MacVittie said the survey results make it clear IT organizations will find themselves having to cope with more complex IT environments for years to come, with the most intense pressure being on cybersecurity. The survey finds 71% of organizations admit to having a skills gap in security.

    Overall, 62% of respondents said they are confident in their ability to protect applications in an on-premises data center. However, only 45% of respondents said the same for applications residing in public clouds.

    The study also suggests there is a strong link between organizations that have embraced digital business transformation and the need to build and deploy applications faster. A total of 80% of respondents said their organizations are executing on some form of digital transformation.

    However, as organizations make that transition, it is apparent IT teams are challenged by the need to be more responsive to the business, said MacVittie. The day is coming to an end when IT could operate as a utility that was managed by open and closing tickets as regimented tasks were completed. IT teams need to embrace DevOps to respond faster to rapidly changing business conditions, she said.

    It’s unclear how long it may take for best DevOps practices to be absorbed across mainstream IT teams. However, the one thing that is clear is that many of the DevOps concepts associated with ruthlessly automating IT in the name of agility are finally starting to hit home.

    — Mike Vizard

  • Cloud Center of Excellence: Pivot for Enterprise Digital Transformation

    Cloud Center of Excellence: Pivot for Enterprise Digital Transformation

    Across industry verticals, enterprise cloud adoption has increased significantly. Enterprises are leveraging cloud models to transform applications, infrastructure and operations. According to a survey by LogicMonitor, 83% of enterprise workloads will be in the cloud by 2020. This, however, is also giving rise to concerns across areas such as security, cost management, compliance, governance, lack of cloud expertise, vendor lock-in and partner management.

    To address these issues, an enterprise requires common functions under one umbrella that can define architecture standards, security guidelines and governance policies, thereby establishing an industrialized transformation approach for applications and IT infrastructure across various cloud models. This central team, which defines cloud strategy, execution and operational approach, is called Cloud Center of Excellence.

    The Cloud Center of Excellence plays the role of a centralized team and acts as the guiding and governing unit for planning, executing and operating an organization’s cloud transformation process. The Cloud Center of Excellence (CCoE) owns an enterprise’s most important cloud initiatives and works on multiple dimensions to make the client transformation journey successful.

    Advisory and Evaluation

    Enterprises running legacy applications on traditional infrastructure require a cultural shift to enable their digital transformation journey. The advisory and evaluation function of CCoE works toward evangelizing cloud across enterprises, creating cloud awareness and providing solutions advice. It also assists in identifying applications for cloud fitment by discovering application data and assessing applications besides evaluating features of cloud service providers to ensure alignment with application reference architectures.

    Design and Build

    Cloud is being adopted at a very fast pace across enterprises. This necessitates defining common design standards, configurations guidelines and automating application environment build and operational support processes. This will not only save costs but also shorten time to market and improve service levels. This function of the CCoE defines architecture, network, security and integration design guidelines besides creating application blueprint templates, configuration parameters and deployment process.

    Develop and Deploy

    The ever-changing customer expectations lead to frequent changes in business requirements. This requires fast-paced development, error-free functionalities and releases in a shorter time. This function of the CCoE defines and designs CI/CD processes, identifies and configures CI/ CD tools and implements agile development processes.

    Governance

    The CCoE needs to monitor enterprise cloud spend, ensure efficiency and establish governance policies as a part of its objectives. It also needs to define and implement a process for cloud financial management, define security compliance controls, communication processes and change management. Technical (business continuity, architectural and performance, etc.) and operation governance are some of the other focus areas of a CCoE.  

    Operation

    Operating in the cloud efficiently requires proper planning combined with an operational strategy and discipline. The CCoE defines future mode of operation for applications running on cloud. It ensures ITIL compliant processes are followed for managing cloud environment.  It enables automation of operational processes such as monitoring, backup, patch and self-healing apart from others, and defines SLAs based on business criticality for application availability and business continuity requirements. Additionally, it also defines change management and incident service requests processes.

    Partner/Product Connect

    There are multiple cloud service providers (CSPs), a plethora of tools and SaaS products that exist in the market. This CCoE function focuses on coordinating with product and tool vendors for implementation and service realization. It works with cloud service providers’ technical teams to evaluate new services besides assisting the enterprise applications team. The CCoE liaises between applications teams and CSPs/external product teams to resolve technical challenges.

    Innovation/Ideation and Knowledge Management

    CSPs continually evolve to keep pace with innovation. This function of the CCoE evaluates new services by developing proof of concepts and publishes guidelines and best practices based on PoC learnings. It also creates a knowledge base leveraging past learnings. 

    Conclusion

    CCoE plays a critical role in implementing the cloud strategy of an enterprise. It defines a framework for governance, designs guidelines and manages the cloud-specific knowledge base. It is, however, of paramount importance that it should start with a small and right kind of team. As cloud adoption increases in an enterprise, responsibilities and scope of the CCoE will expand accordingly. It is important for enterprises to empower the CCoE team allowing them to teach and uphold best practices.

    — Akhilesh Laddha

  • Five Technology Trends to Shape Future Investments

    Five Technology Trends to Shape Future Investments

    Humans invented technology to introduce innovative products in the market. Technology’s relentless cycle of innovation has now touched humanity, redefining what it means to be a human, a meaningful change that is impacting business priorities and is expected to do so in the future.    

    The most important tech investment for C-level executives relates to digital transformation, artificial intelligence (AI), Internet of Things (IoT) and cybersecurity. With 71% of the world expected to use mobile phones by 2024 and the successes of mobile banking in developing countries, experts predict that mobile and blockchain technologies will also join to bring about more financial inclusions.

    Here are five things that C-suite business people should invest in.

    Digital Transformation: Everything Online

    As one of the weapons in the arsenal of business innovation, digital transformation has become such a buzz word that it turns people on. According to a report by Forrester, 90% of the executives believe digital transformation is a necessity for their business, and around 60% believe they lag behind in digital transformation. By the end of 2020, a company would either have transformed or will be on its way to adapt to digital transformation.

    IoT: A Thousand Points of Entry?

    Business implementation of IoT and blockchain are very popular these days. However, if we look to enterprises it’s a different story. Costs, security and current political climate are the major hurdles for the enterprise-level implementation of IoT. To get the most out of this innovative technology, businesses need to determine what stands in their way and then work on strategies to sort things out. So until the issues are dealt with, IoT will be seen as a promising technology that’s not ready for prime time.

    AI: A Real Game-Changer

    Every so often a technology comes along that has the potential to completely change everything around it. The last such thing was cloud computing. Like cloud computing, AI has been around for a long time. AI, machine learning and deep learning are catching up with the initial promises and it will become more evident in the coming years.

    Most common usage of AI and machine learning will be seen in business intelligence, automating the repeated tasks, and making future prediction using the previous data. Previously, AI has been used for decision making using data analytics and this is expected to increase in the coming years with more businesses investing in the AI-driven decision-making system. Another use of AI that will be more common is digital identity verification for online businesses.

    Ultimately, AI/machine learning and deep learning will be seen more frequently in the years ahead. However, the promises it brings are far fetched and it’s worth waiting to see the true potential of AI.

    Quantum Computing: The Next Big Thing

    Currently, in R&D, quantum computing will open new ways by solving problems that require a lot of computation. Google’s investment in quantum R&D is expected to grow and more researchers will shift their focus from AI to quantum. With the emergence of 5G, the quantum research industry will see a boom.

    DevOps: For a Customer-Centric Approach

    According to the Forrester report, firms will embrace a customer-centric approach as the DevOps speeds flatter. DevOps continues to impress the heart and minds. However, with a slow-release speed, engineers are experiencing a stress point. DevOps teams must see this as an opportunity to approach DevOps differently. Within the next six to 12 months, DevOps adoption will change and the team will implement new strategies. Testing will revolve around previous radical methods and new technology will help developers to learn new skills.

    — James Efron

  • DevOps Chats: Simplifying Digital Adoption, With WalkMe

    DevOps Chats: Simplifying Digital Adoption, With WalkMe

    WalkMe recently announced a funding round of $90 million, bringing its total raised to over $300 million. But according to President and Co-founder of WalkMe Raphael Sweary, the real measure of WalkMe’s success is its annual recurring revenue being more than $100 million (which it is) and whether the company is helping its customers.

    WalkMe’s customers are comprised of businesses undergoing digital transformations and looking to accelerate their digital platform adoption.

    In this DevOps Chat, Raphael and I discuss WalkMe’s plans for its latest funding, including plans for its SaaS-based digital platform. As usual, the streaming audio is immediately below, followed by the transcript of our conversation.

    Transcript

    Alan Shimel: Hey, everyone, it’s Alan Shimel for devopsy.kinsta.cloud and you’re listening to another DevOps Chat. You know what, we’re recording this—oh, December 23rd, here, getting near the end of the year. This is probably the last DevOps Chat of the year. So, what a great way to end our year of fantastic DevOps Chat with Rafael Sweary, president and co-founder of WalkMe. Rafael, welcome to DevOps Chats.

    Rafael Sweary: Thank you, Alan. I’m super excited being here. It’s one of the last days of selling in Q4, and you know how it is when you’re a B2B business. It’s a big quarter for us, so I’m actually feeling privileged that I can spend some time with you.

    Shimel: I appreciate you taking it, I know how crazy it is. You know, Rafael, just on the subject, that’s something I’ve noticed the last two, three years. Years and years ago, kinda the consensus was that especially here in the U.S., after Thanksgiving, things kind of shut down, people got in that holiday mode and business slowed up. But I don’t know whether it’s because we live in a more global economy now or just, things are that different. The last couple years, the last couple weeks of the year have been absolutely frenetic with people doing things and deals coming in and sales being done, right up to the last second, it seems.

    Sweary: Yeah. So, I’ve never felt the Thanksgiving effect. For us, it’s always, the last quarter of the year was strong. I think it’s because of budgets that companies have and they want to use it. And sometimes people have something on their desk that they want to come to closure with by the end of the year. So, next year, they can start building and start implementing the new software that they bought. So, I’ve never felt it, but I’ve definitely heard people talking about this phenomenon.

    Shimel: Yeah.

    Sweary: So, it might be, as you say, the globalization and everybody’s connected all the time. And so, we’re kind of hooked. We’re kind of—

    Shimel: Yeah. I agree, I agree. But Rafael, the big news is—well, the big news for WalkMe is, you guys have recently announced, what was it, a $90 million round?

    Sweary: Yeah, it’s a $90 million round. It brings the total that we raised to $307 million.

    Shimel: Wow.

    Sweary: We went into this funding, this funding we didn’t really thought about raising money, and we started entertaining with the idea—because we were very, very well-funded before and we’re selling a lot, so we are, we didn’t really, we’re not a startup that is in a dire need of cash. We weren’t in such a situation. We were very lucky there. And we were planning—we’re planning, we had, our hope is to go cash flow positive and start thinking about going public, et cetera.

    Now, what is happening is that, on one hand, we saw a huge opportunity to grow much faster than what we planned, because things were going really, really well with our larger accounts. And, on the other hand, there is a lot of uncertainty crippling into the market. So, you see some instability in the financial markets. Overall, it’s not—it’s not sustainable, but you keep seeing people are, you start seeing those articles about being, writing about the evaluations being too high, et cetera.

    And the second thing, you’re going into an election year. Now, uncertainty is not good for business, and those two things brought us into the option of possibly raising capital. We didn’t plan to raise so much money, but when you are dealing in such evaluations and when you’re raising money from later stage funds, they have a minimum that, below that minimum, they’re not interested in the deal, even if the deal is great. Just because they can’t, from a portfolio management, they gotta deploy a lot of money to every company. The minimum for Vitruvian, which is the fund we selected to work with, was 70 million, and then, you know, we have preempt rights, which was exercised by our existing investors, which made the round into 90 million.

    Shimel: Right. That’s crazy. So, you know, Rafael, as we were talking off mic, you know, we live in a bit of a crazy time—I don’t know if it’s crazy or if it’s just the new normal—but we live in a time where large numbers like this are not as unusual as it was when I was doing startups, you know, even 10, 20 years ago. And so, first of all, congratulations, alright, because I don’t care what anyone says. It’s hard raising money and it’s hard raising that kind of money, so obviously, you’re doing good stuff there.

    But I think the question for our audience is—okay, so now, we have another well financed startup here, raised 307 million, unicorn valuations. But what does it mean to them? How is this gonna change and affect their life, right? When we look at WalkMe, right, the digital adoption technology to help bridge the digital skills divide—

    Sweary: Yeah.

    Shimel: How are you helping people with that?

    Sweary: So, I want to first start with the unicorn. It’s a nickname I don’t like, I gotta say.

    Shimel: Fair enough.

    Sweary: And it’s overly inflated. So, when I get up in the morning, I’m not worried whether we’re a unicorn or not, right? [Laughter] What I’m concerned about is our stakeholders. Our stakeholders is our, first of all, our employees and our customers are in the number one place. And I wanna make sure that we’re providing a business for them and we’re working in such an environment where we make everything better for everyone, okay? So, this is my concern. My concern is not whether we’re a unicorn or not.

    By the way, speaking about that, I think that TechCrunch, I think it was TechCrunch, suggested to stop looking at whether you’re a unicorn or not, but over you over 100 million in ARR or not?

    Shimel: Right.

    Sweary: I’m glad to say that we are—

    Shimel: Good for you.

    Sweary: Well over 100 million in ARR. So, it’s not—now, let’s talk about, a little bit about digital adoption. So, for us as users, there is a lot of technology available, and we can use technology everywhere. The problem is that the technology is changing very, very fast, and for us as humans, we don’t change that fast. The common saying is that when practice makes perfect—but actually, practice makes a habit, and changing a habit is something that is very hard to do. You’re accustomed to do something in one way and to change how you adapt to these changes is something that takes very long.

    So, I don’t know if you ever moved from a Windows to a Mac machine or from—

    Shimel: Oh, I have. [Laughter]

    Sweary: You’ve been?

    Shimel: Oh, yeah.

    Sweary: So, you know that the first few days were painful, right?

    Shimel: Mm-hmm.

    Sweary: They were painful. They weren’t fun.

    Shimel: I know.

    Sweary: Right? It takes some time until you—so, Mac, I don’t know what the move you’ve done, but Mac might be much better than what you had before or Windows much better than what you had before. But when you make the change, those first few days, weeks are very tiring, you gotta focus very hard.

    Now, but this is a change you wanted to do. Nobody forced you to do this change, you wanted to do it. Now, when you go into an enterprise environment, what is happening is that you’re forced to make—you are forced by the company to make many, many changes to the way you work. Because the company implements a new software, because the company is, has a new process on an existing software, et cetera, et cetera.

    And what happens is that you find yourself overwhelmed with all those changes. You go to do your performance appraisal and the process changed or the application changed, and you find yourself learning it again and again and again.

    Now, this is where WalkMe comes in. WalkMe reverses the relationship between the user and technology. If today when a user uses technology, he has to focus and he has to think and understand what he needs to do in the software—we do the opposite. The software tries to understand the user and help him achieve what he came to do.

    Now, usually what he came to do is to do something specific. So, this is how we help on the user level. But the way we—so, when you are in a company and you’re an employee of a company, today you have many software packages and it’s very hard to track them and we help you to do that. But also important is what we do for the company itself.

    So, the general idea when you implement new software is to improve your business. Usually, companies don’t buy products for spite. Like, I might buy a jacket because I feel like it. But no company buys anything because they feel like it. They buy in order to do something.

    Now, usually the things that they’re looking to do is to sell more or to spend less or to reduce risk. Like, any expense that a business will do will fall into one, at least one of those buckets. Now, what companies buy most is technology. It’s the biggest expense after human resources. So, companies invest massive amounts of money in technology, but a lot of the times, they’re not gaining the benefits.

    So, let me dive a bit deeper, there. When a company buys or implements a CRM, what is their goal? Is their goal to replace the Excel file or the notebook that the salesperson was using? No. That’s not their goal.

    Shimel: [Laughter]

    Sweary: Their goal is to cell better, right?

    Shimel: Yeah.

    Sweary: Their idea is that if the salesperson will use the CRM correctly, they will be able to use AI to recommend which pipeline to focus on, on one hand. On the other hand, they would have better predictability so they can report to the market, and also the HR team will be able to look at it and understand if they need more employees or less, and the purchasing department will understand what supplies they need. So, the hope is that, with putting digital, the company will operate better.

    Now, what happens? What happens is that the salesperson, when he comes to the CRM, it’s not helping him. He’s struggling. And what happens is that he’s forced to use the CRM. So, what he does is documenting in the CRM. He actually continues to work on his Excel file, and he works on his notebook, okay? So, you’re not gaining all those benefits because it’s not predictable, it’s done retroactively, okay? It happened—once the action happened, okay, it’s a lagging indicator.

    And a lot of companies, a lot of time I talked to them and they say, “I have a great usage for my CRM.” And I said, “Look, if you wanna know if you have adoption for your CRM, go to a salesperson and ask him what he’s gonna close this quarter. If he opens the CRM, you have adoption. If he’s going into his notebook or his Excel file, he’s documenting, and you’re not gaining all the benefits.” And then it’s very easy to see that a lot of, for example, the pipe moves from stage two to stage eight, right? Because you’re not really keeping current.

    This is, of course, one example. The same thing is true about any type of professional applications that companies use, and even more on everything that is a digital workforce application. If it’s interesting, I can give you some more examples of what we see at our customers.

    Shimel: Agreed, agreed. You know, I’m sitting here listening to you talk, Rafael, and you know, you can’t help but put your own, how it fits in your—we went through this right here at MediaOps, right? We have a CRM tool, and I’m trying to break the people of using whiteboards and spreadsheets, you know? [Laughter].

    Sweary: Mm-hmm.

    Shimel: It’s just as you describe, right? All the reasons, all the motivations. But it’s also a process.

    Sweary: Yeah. How do you handle this process?

    Shimel: So, I’ve gotten older. I think I’ve become a better parent and a better supervisor. I used to try to force people and say, “You can’t use the spreadsheet, wipe the whiteboard, I want it all in the”—in our case, it’s HubSpot—“I want it all in HubSpot.”

    Sweary: Yeah.

    Shimel: And what I found is, you know, they would pay lip service to me and they would just move the wipe board out of the way or they’d have a spreadsheet that they didn’t show me, and then it would be like double work, Rafael. So, they would do it in a spreadsheet and then, to make me happy, they would kinda transfer that stuff into the CRM [Cross talk].

    Sweary: Right.

    Shimel: But a funny thing happened—as they transferred more and more into the CRM, the CRM became more and more valuable, right? So, you wanted, having things in there that you couldn’t put in there, just as you’re talking about.

    Sweary: Yeah.

    Shimel: You couldn’t put these things in a spreadsheet any more, right? Because there was more intelligence, if you will, built in there. And so, eventually, we started using it more. But—

    Sweary: Yeah. Now, think about this, about, with an enterprise that is global and has multi-branches and has a diverse workforce with different digital IQ. And no parents is there to tell them, “Put it into the Excel sheets and then—uh, put it into the CRM,” and then you start understanding the problem. Now, I assume that your CRM was stabilized.

    What is happening a lot of the times, it’s not stabilized, it keeps on changing because companies have new processes and then the process changes. So, for example, you keep learning from your business and you’re like, “Well, if it’s 30% discount, you need this approval process versus 15.” And now you add another complexity, and the salesperson is not able to work, right?

    So—and I think there is a solution. There is a solution. I think that what is stopping us from using technology to its fullest is the gap that happens between what the technology can do, what we can do as users, and how much, how long does it take until it gets better, right? So, anyone who’s ever used the GPS would never wanna go back to a map, right?

    Shimel: Right.

    Sweary: As soon as you experience it, it’s much better than anything you did in the past, do you agree?

    Shimel: I agree.

    Sweary: So, you don’t need to work—yeah.

    Shimel: I agree, I agree.

    Sweary: You don’t need to work—exactly. You don’t need to work on adoption. But when you’re talking about an enterprise application, there is a very big gap between the perceived value to the organization, and until you see the value and until it trickles down to the employees.

    So, let me take you through another example. So, a lot of companies are implementing HRMs, and they idea behind the HRMs is that the employee can self-task, right? You want vacation, you can take vacation. Now, in the past, let’s assume, let’s go back 20 years ago. An employee wanted vacation, he would fill out a form, it would go to his manager. His manager will scribble something, put it in his outbox, it will go into the HR department and then into the finance department and then back to the manager and then back to the employee.

    Now, all those people worked on something that didn’t add any value to the company. It’s just an employee taking vacation. So, the company has this great idea—we’ll put a ____ and when an employee wants to take vacation, he would see whether he has a balance or not. Once he asks for the vacation, if there is an issue and other people in his positions are already on vacation, he’s gonna get an alert, and if he doesn’t have the balance, he will get an alert, et cetera, et cetera. And you say, “Let’s automate this process.”

    Now, it comes down to the employee. The employee wants vacation. He doesn’t care about the process and how much time is spent, he wants vacation. He comes into this software, he doesn’t remember the log-in, because the last time he took vacation was a few months ago. And he goes in and he’s not sure how to ask for vacation and he gets stuck a few times and what does he do? He sends an e-mail to his boss. What does his boss do? Sends an e-mail to HR, that sends an e-mail to finance, that sends—and then you’re not gaining the benefits, right? Because you don’t see the value.

    Now, for the company, it’s super important that people use this application, because it makes sure that all the vacation days are deducted on time, and it really closes the loop, and less people are working on it. But you’re not gaining the benefits. Make sense?

    Shimel: Yeah, makes perfect sense to me.

    Sweary: Mm-hmm.

    Shimel: Perfect sense. Rafael, I wanna take a moment, because we’re running low on time—you know, we spoke about how much money and all of that and it’s all great. I wanted to give people a sense, though, of how many organizations you’re helping with WalkMe, right? And the amount, and how many applications you guys have done integrations.

    Sweary: Okay. So, customers, we have close to 2,000 customer logos, which means that when I say a logo, if—let’s say a company of ours, let’s say just as an example, Coca-Cola. So, we have, let’s say, Coca-Cola Greece and Coca-Cola U.S., it would be one logo, although there are two separate companies and that might be completely unrelated. So, we look at the logo level, and we have close to 2,000, including 30 percent of the Fortune 500.

    Regarding applications, WalkMe is platform agnostic. We really don’t care what application you use WalkMe on. We have some enhancements that are specific for the big and popular applications such as Salesforce, Dynamics, Workday, SuccessFactors, and those enhancements—again, they’re not about integration, it’s about, we already have a lot of data about what’s working in those systems and what is not, because we did hundreds of deployments over them. So, there is a lot of things you learn between customers.

    When we come to a new Workday implementation today, because we did a few hundred of them, we already know what the employees are gonna struggle with. We already know what the managers are gonna struggle with, and we built it into our system so it’s easier for our customers to create content, specific content. Make sense?

    Shimel: Mm-hmm. Got it—got it, got it, got it. Excellent. Rafael, I feel like you and I could talk about this stuff all day and lessons for people out there to learn to hopefully make their businesses better, but we’re out of time. I try to keep these, as I mentioned to you, to 15, 20 minutes. We might have gone over.

    Sweary: Sure.

    Shimel: But first of all—hey, congratulations on all of the success with WalkMe. And more than just the raising money—2,000 organizations using your product and really making a difference in trying to bridge the digital skills gap. It’s a great, great thing you’re doing, and keep it up. Secondly—love to have you back on again soon, maybe in the new year, and we’ll keep—

    Sweary: Sure. I would love to join and talk to you a little bit about what we do specifically for companies, how we help, and try to give some tips to some organizations that we see and what we learn from there, because we’re always humbled by what we learn from our customers. And it’s some of the best businesses in the world, and it’s really fascinating to see, when technology works, the competitive advantages that you’re able to gain.

    Shimel: Yeah. Agreed. You know what? You’ve got an open invitation, my friend, so when you’re ready, you’ll reach out to me and we’ll continue this.

    Sweary: Awesome. I hope Marissa hears that as well. So, Alan, thank you so much.

    Shimel: Thank you.

    Sweary: And I look forward to talking to you again.

    Shimel: Okay. Rafael Sweary, president and co-founder of WalkMe. This is Alan Shimel for devopsy.kinsta.cloud, and you’ve just listened to another DevOps Chat. Have a happy new year, a happy season’s greetings, merry Christmas, holidays, Hanukkah—whatever you’re celebrating, enjoy, folks.

    — Alan Shimel

  • Four Ways to Modernize Processes and Measure Performance With APM

    Four Ways to Modernize Processes and Measure Performance With APM

    Change is everywhere and the stakes are high. For 2019, businesses are on track to spend over a trillion dollars on digital modernization, according to a recent study from IDC.

    A crucial part of modernization is the growing number of IT organizations using the latest in dynamic, cloud-scale technologies to develop applications. As a result, technology professionals in the businesses you serve must now work with a much more complex and dynamically changing tech stack.

    When building and maintaining an app, it’s becoming even more common to have hundreds (or thousands) of pieces of code in containers being continually reconfigured and brought in and out of production. And many of these operations take place in customer-facing applications.

    The stakes are high, because if something goes wrong operations could halt. It’s therefore vital to understand the underlying technologies throughout an organization’s IT environment to better equip customers with the tools needed to be successful. Application performance management (APM) tools that simplify stack management, whether it’s on-premises, hybrid or fully cloud-native, provide a level of visibility needed for modern businesses—and they work across multiple cloud environments, such as AWS or Azure.

    As a channel partner, you need to be prepared to help your businesses and their customers through this modernization process. 

    Try the following to help your customers modernize business processes.

    Help Them Realize Software Is Now Business-Critical

    As IT departments move from on-prem infrastructure and a mix of commercial off-the-shelf (COTS) and monolithic custom applications to increasingly adopted cloud-based Kubernetes microservices applications, they’re accelerating the adoption of software at the core of all their business processes. The result? Business is increasingly dynamic and responsive—new applications are built and delivered to market faster than ever. But companies are also at risk now when things don’t go well—that strategic app could degrade or fail.

    All the tech layers underpinning these applications are also becoming more sophisticated, dynamic and interwoven—and making it still harder to administer as they continuously change at an even faster rate.

    Focus Your Customers on Core Competency

    There are plenty of open-source tools out there for your customers to use to build their own monitoring. The biggest obstacle for businesses rolling out their own apps while using an open-source tool is core competency. 

    If, for example, your customer is a wholesale plumbing supply company, is their competency sourcing plumbing supplies or knowing how to write instrumentation code for all their plumbing supply chain applications? Help them focus on what they’re good at and give them tools to manage the rest.

    Perhaps you have a large financial services customer who is spending tens of millions, across multiple years, on a team of outsourced experts to write precisely the code required. This is an extremely time-consuming and costly effort, but financial institutions do this because their needs are highly specific and mission-critical, and the cost of not doing it is even higher. 

    If you look at real-time high-frequency trading environments—where billions of dollars are moved in matters of tenths of a second—you come to understand the stakes justifying these herculean efforts. All of which supports the need for APM tools to help empower the tech pros in-house who monitor and manage these high-speed trading environments.

    At the other end of the spectrum are the small tech companies with a new idea they’re out to promote. But when it comes to most companies, their core competency is often not monitoring and managing their infrastructure and applications. It’s understanding the market requirements for their custom apps and getting those apps to market quickly. At the same time, organizations of all shapes and sizes are still confronting the reality that to successfully deliver modern applications we must shift from pure infrastructure performance metrics to the KPIs that best demonstrate end-user experience.

    Ultimately, many of the organizations described above have either focused on IT as a core competency or, in the absence of dedicated tech teams (at SMBs, in particular), they have outsourced management of their complex, dynamic tech stack and custom application builds. In both instances, APM tools are a necessity and it’s prime time for the channel to deliver those services.

    Be the Most Viable Modernization Partner

    By understanding the needs of modern organizations as they grapple with their complex tech stacks, you can ensure you have the right set of tools for your customers. 

    Provide full-stack capabilities for today’s businesses to manage their applications and keep operations running smoothly. Cater to unique business problems and equip your customers with APM tools based on their needs—advanced logging, trace metrics, performance optimization and full-stack visibility across applications and the compute infrastructure on-premises, hybrid and cloud. Help them check all their functional boxes.  

    Measure Performance with Full-Stack APM

    In all cases, your customers should be measuring performance. Because every company uses a mixture of digital technologies, arming them with full-stack APM will help gain visibility into performance throughout the business. With APM, businesses can see if their system is degrading—and fix it before disaster strikes. That’s the business value for APM—it gives visibility into the complexity underpinning today’s application environments. Full-stack APM provides this visibility, whether the apps are cloud-based, on-premises or hybrid.

    But here’s the reality—not all APM tools are the same. Traditional APM solutions weren’t built for the environment IT departments now have, with the addition of containers and microservices-based applications to their existing monolithic and n-tier/SOA applications. Those solutions were made to manage hundreds or thousands of objects with slower rates of change, not the tens of thousands, or even hundreds of thousands to millions of objects IT works with today.

    Also, note the ephemeralness of container-based microservice applications able to live and die in a matter of seconds or less. There’s no time to automatically install a traditional agent, let alone do so manually. The container’s life span is shorter than the time it would take to do such instrumentation. Direct them instead toward a full-stack APM solution with complete coverage of all application architectures: monolithic, n-tier/SOA and microservices based. With anything less, they’re running at a higher risk of brand damage and revenue impact.

    By being the experts on APM, providing full-stack visibility and measuring performance, your customers will find modernization success.

    — David Wagner

  • The Difference Between Capacity and Scalability Planning

    The Difference Between Capacity and Scalability Planning

    Not only does the tech industry love terms, we love to make them super nuanced. For example SecOps versus DevSecOps, continuous delivery versus continuous deployment, hybrid cloud versus multi-cloud, etc. These terms may seem similar on the surface, but when you dig in they are quite different.

    Here are two more: capacity planning versus scalability planning. Both are critical aspects of keeping applications up and running, but two different activities.

    The reason we invest time in capacity and scalability planning is simple: We want to make sure that system resources such as compute, storage and memory are not the cause of an application outage. It is a response to expected and unexpected increases in application usage, as well as the steady growth of application adoption.

    Here are a few differences between capacity planning and scalability planning.

    Long Term Versus Short Term

    Capacity planning is more focused on the base resources, as it relates to the long-term growth in application traffic. The goal is to have enough resources to handle the steady state of the application without breaking the bank by over anticipating usage. With capacity planning there is a big assumption that the application requires to always have a pool of resources available.

    Automated Versus Static

    Scalability could be a manual task, you see utilization creeping up and you respond with more instances. This is probably more common than not. But I don’t believe it’s the overall objective of most teams. Auto-scaling is the goal, where the system knows on its own when it’s time to spin up new resources. The public cloud providers, instrumentation of kubernetes, etc., help support this. Whereas capacity planning is a more deliberate identification of needs, and then statically setting those resource needs within the cloud.

    Strategic Versus Responsive

    Similar to static versus automated, capacity planning is a more strategic activity whereas scalability planning is a more responsive activity. Usually, scalability comes up during peak usage activities such as black Friday sales or school registrations.

    Capacity planning generally calls for more research and leveraging tools such as load balancers and historic data to understand the best path forward. It also should involve the input from the broader team, especially development to discuss the resource usage of new functionality and application architectures.

    There is a good possibility that scalability planning could be all that is left with some modern applications. The reason this might be true is resource allocation theoretically can be 100% application based, where the resources are always one step ahead of current utilization. In order to embrace this model resources need to be provisioned 100% automatic, which means that all infrastructure needs to be scripted. As more companies adopt serverless components of their application, this is already inherently true.

    Capacity planning is where most operations teams spend their time, but resource utilization is shifting left and scalability planning is becoming more common. Scalability planning has become the responsibility of DevOps engineers, SREs and even developers. The main reason capacity planning will survive the long haul relates to budgets. While the application itself can fully control the infrastructure laid out before it, the IT organization and the organization itself will want to impose an upper limit so there is an indicator of when the cost of running the application on the resources may or may not be an issue. Capacity planning in this case will be purely a cost control mechanism, and negotiated just as any budgets are.

    — Chris Riley

  • Five IT Ops-tackles that Stifle Business Growth

    Five IT Ops-tackles that Stifle Business Growth

    I was recently asked about the top five IT obstacles that stifle business growth, and I want to help clear a path too often lined with fear, uncertainty and doubt. In the not-so-distant past, IT was all about the tools. Solutions were more straightforward, teams were less globally connected, and the ever-present data deluge was not changing our business landscape by the millisecond.

    With this in mind, I have created a list of the five most common IT obstacles and will pinpoint the single tool you can implement to help alleviate these pain points.

    IT Staff Lack Time to Learn New Technologies

    This is not to slam our tech teams or leaders; this is just the byproduct of condensed customer schedules, tight purse strings and managing the MOOSE (maintenance and operations of the organization, systems and equipment). The demand on IT teams is high, and we don’t always have the opportunity or the resources to restructure operations for a new tool, as upgrading requires learning new APIs, UI/UX and deployment architectures.

    Difficulty Supporting New Technologies Quickly

    It is hard to keep pace with IT complexity and manage it properly. New services, applications and infrastructures are constantly being added and there are plenty of vendors out there that will get you locked into solving a single issue versus addressing your macro problems. While the benefits of upgrading are there, the difficulty lies in understanding the complexity of these systems and how to leverage them most effectively.

    Lack of Support for Hybrid IT

    Hybrid by definition adds complexity, and multi-cloud, on-prem and private/public clouds are only a few ways to make your hybrid dream a nightmare. No matter the combination, understanding different architectures and their components is a must. Additionally, we need to understand how we manage our own data as well as how our vendors are managing it.

    IT Complexity

    We need to know our machines and architectures well enough to focus limited resources on what impacts the business most. IT will always be complex—there’s always something new, and the amount of information to process is insurmountable and exhausting. Adding context to IT data can help you identify the root cause of overly complex systems. The most difficult task will be to understand the technology well enough to know what to do next. 

    Inability to Understand Business Impact in Order to Prioritize Tasks

    Prioritization is by far the most important aspect of IT. There is a lot of noise, lack of visibility, lack of context, and—the squeakiest wheels of them all—legacy tools. Prioritizing means routing the right people to the right problem to get it solved quickly and elevating IT service visibility, health and risk into the business function.

    Let’s Get Digital

    IT pros can start to tackle these challenges through prioritization and then automation, or AIOps—the principal of AIOps being to add context to data, using machine processes to enrich the data and bring it to a business level. Understand what is important to the organization and think about the outcomes important to IT. To do this, you can create a realization plan to tackle the low-hanging fruit and create achievable milestones and outcomes. For example, look for opportunities and create a crawl-walk-run phased approach driven by business priorities. Each organization has different needs and different timelines—and this process can be applied to customers, too.

    Next, take into account how your team does work and focus on automation as a principle within how you do work. One of the biggest impediments to digital transformation is culture. Remove manual processes, capture tribal knowledge and figure out how to repeat this approach in a consistent way. Additionally, absorb feedback and learn from it. This will drive acceleration when done right, and we all know that better digital experiences boost enterprise value.

    Finally, automation is useless if your data is flawed, and accuracy is a key fault for legacy configuration management database systems. Data must be accurate for effective machine-enabled automation. Leverage the tech you have to build an interconnected ecosystem that is fully integrated and automated—and that avoids tool sprawl. Have an open mind to consider new approaches and be brave enough to shed the legacy mindset. Additionally, take into consideration your partners and vendors, and how that team collaborates, to determine your strategy.

    The Light at the End of the Tunnel

    The path for today’s CIO can be unclear. But you can take bite- (or “byte-”) sized steps to put machines to work and leverage processes that deliver on AIOps. By understanding business outcomes, prioritizing automation as a principle and leveraging trustworthy internal and external relationships, you will have more time in the day for more important tasks. I measure outcomes based on customer experiences, and I ensure great customer experiences by running a great system. While your mileage may vary, moving forward is the most important part.

    — Erik Rudin

  • The Role of Developers in Digital Transformation

    The Role of Developers in Digital Transformation

    Developers are an integral part of digital transformation. They architect the modular systems that overcome legacy and build the applications and solutions that allow firms to deliver products and services in new and innovative ways. Yet, when it comes to business decisions, many organizations overlook their developer talent.

    Developers come from a variety of different backgrounds, but it’s safe to say that most have studied computer science, engineering or mathematics in some form. Coming from these disciplines means they are inherent problem solvers, so giving them a seat at the table when it comes to discussing business goals is, of course, beneficial.

    To ensure the business insights of developers can be unlocked, organizations should consider the following four points. 

    Encourage Personal Development

    More and more developers are actively taking an interest in improving their communication and leadership skills, recognizing that these are important tools for career development. 

    Soft skills, for example, are key to establishing relationships internally, as well as communicating to external parties. At any moment, stakeholders may want to understand the workings of product teams, or it may be the case that a customer requires more attention when implementing a solution. In the former scenario, developers must become advocates for the business and the way they work; in the latter case they must ensure that they take an empathetic approach to end users. 

    Whether it’s learning new programming languages, getting to grips with new technologies, or developing soft skills, developers relish the chance to grow. Organizations that offer learning and development programs internally will likely attract developers who are both apt and keen to involve themselves in other areas of the business. 

    Keep Things Agile

    Operating within an Agile framework gives developers and other members of product teams a chance to develop soft skills through scrum meetings. During a scrum meeting, each member of the team is given the opportunity to communicate openly about their challenges and devise solutions for other issues. This not only ensures a high level of transparency internally, it also allows business analysts to provide an accurate picture of progress to clients.

    Sharing insights and troubleshooting in an open forum enables those with a natural inclination for leadership to establish themselves as effective communicators. The limited size of Agile teams also keeps things personal enough that each team member’s feedback can be heard and considered by their colleagues. 

    Agile software development brings disciplines together, encouraging an exchange of ideas and an expansion of knowledge. This is in stark contrast to the Waterfall method, where siloed teams hand off work with little communication.

    With Agile, teams share responsibility, communicate and apply their disciplines in contexts outside those they are used to. In essence, Agile is the ideal way to establish a culture that enables learning and development on the job. This is much more practical than setting up a program that teaches soft skills and educates teams about other areas of the business, as these sessions can eat into work time and reduce productivity.

    Be Clear on Requirements

    It’s all well and good attracting the best and brightest developer talent, but in order to get the best from them, firms must be transparent about what is expected day to day.

    Firstly, efficient code delivered in a timely manner should be the goal of every developer. Testing and QA will, of course, reveal issues, and no one is perfect, but developers must be mindful of the impact inefficient or inaccurate code can have on a business. Workarounds may get you past a problem, but this is not best practice and leaves the business exposed should a client pick up on it–especially if the workaround causes more serious issues further down the line.  

    Fewer bugs or defects means scrum meetings can naturally focus more on strategy and new initiatives that might help grow the business. Organizations should therefore establish best practices and coding guidelines to reduce the temptation for workarounds, ensuring code releases are reliable and ready for the production environment. 

    Developers must also be able to comprehend the requirement to work with designs given to them by design teams, as these will align with customer expectations. Being able to dynamically incorporate client feedback into the development process is also key, particularly for those working with continuous delivery and continuous integration pipelines. 

    An interest in emerging technologies is desirable, as is an eagerness to innovate new solutions using them, but so too is an aptitude to leverage rather than re-invent solutions. This helps to keep costs down and ensures a maximum return on investment in existing solutions. 

    Keep an Eye on the Future

    Increasingly, the ease with which organizations can react to advances in technology will determine their long-term success. It is therefore in their interest to ensure developers have the freedom to learn new skills and explore new tools that might increase efficiency or unlock new offerings. 

    Advances in IoT, connected devices, augmented and virtual reality, AI and machine learning, blockchain and 5G networks are just some of the technologies opening up new challenges for firms and developers alike.

    Developers with the skills to harness these technologies will increase their employability, allowing them to secure better positions and salaries. They will also be well placed to advise on wider business goals, positing new use cases and solutions and fueling innovation.

    — Arun Ramachandran