{"id":7263,"date":"2020-06-18T12:35:07","date_gmt":"2020-06-18T16:35:07","guid":{"rendered":"https:\/\/agileswag.com\/?p=7263"},"modified":"2020-06-18T12:35:07","modified_gmt":"2020-06-18T16:35:07","slug":"remote-agile-transitions-the-top-ten-challenges","status":"publish","type":"post","link":"https:\/\/agileswag.com\/remote-agile-transitions-the-top-ten-challenges","title":{"rendered":"Remote Agile Transitions \u2014 The Top-Ten Challenges"},"content":{"rendered":"
Remote Agile Transitions \u2014 The Top-Ten Challenges<\/strong> Three months into working with distributed teams, at least for the majority of us who are not working for one of the remote work pioneers like Automatic, Gitlab, or Buffer, operational issues at a tactical level have been addressed. Zoom has fixed many of the problems reported, we learned how to organize engaging remote events, and more people start embracing techniques like Liberating Structures or Training from the Back of the Room to get all sorts of work done. With a good outcome, as it seems that\u00a0remote work improves productivity<\/a>, at least when\u00a0team members are engaged with their work<\/a>.<\/p>\n Now that the dust is beginning to settle, I believe it is the right time to switch from survival mode with a focus on keeping operations running back to a more strategic way of handling change to become an agile organization.<\/p>\n
\nvia Scrum.org Blog by Stefan Wolpers<\/p>\nWhy Remote Agile Accelerates Change<\/h2>\n