On Wed, Nov 27, 2013 at 9:39 AM, Quim Gil <[email protected]> wrote:
> On 11/27/2013 08:28 AM, Steven Walling wrote: > > > > On Wed, Nov 27, 2013 at 12:12 AM, Erik Moeller <[email protected] > > <mailto:[email protected]>> wrote: > > > > A bit dated, but still an interesting read: > > http://dt.deviantart.com/journal/We-re-all-remote-220038037 > > > > > > I have to say, I don't think everyone being remote is an ideal working > > environment to copy. We accept remote employees because sometimes you > > need to get talented people. But that doesn't make it the best working > > situation. There are huge benefits to having people co-located, and we > > should be striving for co-located teams where ever possible. > > I think our own projects show that both fully co-located and fully > remote models can work well if you plan for them accordingly. The most > serious problems rise when a team is half-way co-located and remote. > Do we have examples of half-way co-located and remote not working well? The three mobile teams (web, apps, zero) are all mixed and IMO all three are high-performing teams. -- Arthur Richards Software Engineer, Mobile [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687
_______________________________________________ teampractices mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/teampractices
