As public policy mandates a fast increase in remote work, businesses face significant impact and potential disruption. After putting off the first fires of the new WFH reality—from getting laptops to putting basic collaboration tools in place—it’s clear that quick fixes won’t last, and businesses need to start developing a long-term strategy for enabling remote teams.
Technical teams are an area of the organization that are especially challenged by this new reality. This includes developers, test engineers, support engineers, customer success engineers, and even sales engineers. Technical teams are often not accustomed to working from home, and when they get to work, they need more than just a laptop to get their jobs done. They need applications, services, and infrastructure resources—whether it is from the company’s private data center, on-premise labs, public clouds, or a combination of all three. This raises several challenges for business leaders with regards to technical teams’ operations.
Join 451 Research's Jay Lyman and Quali's Maya Ber Lerner as they discuss the requirements for enabling remote technical and WFH teams and best practices for putting such strategy in place.
Maya is Chief Technology Officer and Chief Evangelist at Quali. Originally a biomedical engineer, she somehow got into software and automation, and immediately felt at home. When not traveling she is the IT person at home, and the only one allowed to change router configurations. Outside of work, she likes drawing, carving, and reading.
Jay Lyman is a Principal Analyst with 451 Research’s Applied Infrastructure & DevOps Channel. He covers infrastructure software, primarily private cloud platforms, cloud management and enterprise use cases that center on orchestration, the confluence of software development and IT operations known as DevOps, Docker and containers. Jay's analysis encompasses evolving IT operations and software release models, as well as the technology used to create, deploy and support infrastructure and applications in today's enterprise and service-provider markets. Key areas of research also include OpenStack, PaaS and enterprise end users.
"The flexibility of CloudShell Colony and AWS has not only allowed us to innovate our solutions faster, but it also allowed us to build on top of the Colony software. Now, our developers can use a Slack integration that we built to reserve the dynamic application environments they need for testing all without the need for our DevOps teams to disclose sensitive passwords. This has resulted in reduced time to market, more productivity, and better visibility into our cloud usage."