Re: Remote versus collocated teams.
William might correct me on his return, but I think the study he was referring to below is this one , published by IBM in 1978. I found it referred to from this 'Testgeek blog ' site after I Googled "University of Michigan War Room" on the advice of Ron Jeffries.
The IBM study talk about the suitable office environment of a programmer at the time (3270 terminals being the hot new technology) would work best in. Heh, I was four years old then, although my development job in Sydney was on OS/390 (Natural, JCL, TSO), and I'm quite familiar with green screens. Most interaction I had with the mainframe were from emulators on PC's.Thank you Ron,
--- In firstname.lastname@example.org, William Pietri <william@...> wrote:
> Bruce Rennie wrote:
> > I remember that study. I believe that figure for X was very small,
> > like around 5, though I may be misremembering.
> There was a great IBM study on this. I know right where the printout is,
> but I won't be back there for a couple of weeks. If this is still a
> mystery in mid-June, somebody ping me off-list and I'll dig it out.
- Here here Ron! Remote teamwork may be possible but it certainly
isn't ideal. Close collaboration without co-location is a
compromise, sometimes an essential one, but not one you'd advocate
as part of any methodology.
I sometimes like to think of this in terms of new business
startups. How many people would start a business and think, "I
know, let's base our development teams in multiple locations and
have the business owners of the product we're building in a
different place to the developers." For logistical reasons, sales
and other field-based teams maybe, for product development I think
--- In email@example.com, Ron Jeffries
> Hello, Owen. On Sunday, June 3, 2007, at 11:01:30 PM, you wrote:
> > I realise that many people aren't in my position such that they
> > want hard facts to decide. Many are going to trust the opinionsof other
> > people they may think have seasoned opinions, because theyhaven't got
> > the time or the interest to decide for themselves. However, ifJohn
> > Kern's business, as a case in point, can demonstrate that the usepossible,
> > communications tools to facilitate a remote team discussion is
> > then shouldn't the Agile community be a little less hard onremote
> > teaming?want
> Owen, even Jon said that together would be better. Why would we
> to recommend something that wasn't the best we know?
> Ron Jeffries
> The fact that we know more today, and are more capable today,
> is good news about today, not bad news about yesterday.