Agile teams are designed to respond to change. But even for the most seasoned agile teams, responding to the changes brought about by COVID-19 was a pretty tall order. This is the story of how one agile team responded to the abrupt transition to remote work without missing a beat, and without losing its sense of synergy. If you’re in need of some tips on how agile software teams can maintain both their productivity and their morale while remote, this post is for you.

Maintaining business continuity is both more difficult and more important than ever in the era of COVID-19. Typically, IT departments evolve their approaches and technologies over time to meet the needs of customers. But that approach may soon be outdated thanks to the global pandemic.

High productivity. Low turnover. Satisfied workers. Less stress. A larger talent pool. Fewer office expenses. ADA compliance. And better work-life balance. When you list the benefits of remote work, there’s a lot to love – for both businesses and the people they employ – which is a huge reason why more and more companies are starting to embrace a remote workforce.

Working remotely has grown over the past several months for many organizations. The ability to provide remote access involves being able to control access to network and cloud-based servers while allowing employees to access the data and files they require to do their jobs. Remote access is also needed to monitor what data and files employees are accessing. Working remotely allows a business to continue to operate when employees are not able to work in the office.

Five worthy reads is a regular column on five noteworthy items we’ve discovered while researching trending and timeless topics. This week, we discuss the merits of going hybrid in this era of distributed workforces and remote working culture. While it has become imperative for organizations to implement remote work policies, the question of cloud adoption has become almost unavoidable.

The Internet has enabled a level of collaboration like never before in history. With just a few mouse clicks, you can see other people on the other side of the world and work with them remotely on whatever you want. Remote work is becoming new normal in many organizations. Managing teams remotely sometimes even in different time zones, with poor communication, monitoring becomes complex, and team misalignment is paramount.

In administrating all technology and application requirements within an organization, IT operations management (ITOM) is pretty complex, and tends to send IT admins scrambling for authentic and actionable insights across the internet. We’re taking matters into our own hands and launching our very own podcast series to provide you valuable information on ITOM, which you can choose to listen to at your leisure or on the go!

Just like countless other business functions, cloud delivery has now shifted entirely to remote working for now and perhaps longer term. Canonical has been a remote-first company for some time, so we thought we’d take this opportunity to share some of the best practices we’ve learned along the way. Communication Effective communication between customers, engineers, and project managers is the most critical element of successful cloud delivery.

The way we work has fundamentally changed in recent months due to the impact of the global COVID-19 pandemic. As more employees are working remotely, organizations are looking at new ways to ensure their workers can stay productive and secure. We released Splunk Remote Work Insights (RWI) to help IT and security teams have insight into the systems that their employees rely upon while working remotely.

I am making a digital transformation during this novel work-from-home (WFH) era due to a COVID-19 quarantine. Many of you are going through the same and distractions abound while sharing a workspace with housemates, children, and pets. Moreover, we have to contend with an increased risk to cybersecurity, given recent attacks on work-related software such as Slack and Zoom.