<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Remote on Software Engineering Thoughts</title><link>https://software.skipoles.co.uk/tags/remote/</link><description>Recent content in Remote on Software Engineering Thoughts</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 26 Jul 2023 09:22:10 +0100</lastBuildDate><atom:link href="https://software.skipoles.co.uk/tags/remote/index.xml" rel="self" type="application/rss+xml"/><item><title>Continuous Collaboration</title><link>https://software.skipoles.co.uk/posts/continuous-collaboration/</link><pubDate>Wed, 26 Jul 2023 09:22:10 +0100</pubDate><guid>https://software.skipoles.co.uk/posts/continuous-collaboration/</guid><description>&lt;p&gt;The age of teams collaborating by huddling around a whiteboard in a meeting room inside some corporate
office is dead. The future of teams is &lt;strong&gt;continuous collaboration&lt;/strong&gt;. In this post I will explore what
this is, how it works, and why meeting rooms and whiteboards should be consigned to the scrapheap of
failed team collaboration approaches.&lt;/p&gt;
&lt;p&gt;(Note: this is not to say that there isn&amp;rsquo;t sometimes value in meeting rooms and whiteboards for knowledge
dissemination and other group activities, just not collaboration.)&lt;/p&gt;</description></item></channel></rss>