Re: [agile-usability] Re: Remote versus collocated teams.
- re: It might be good to have a speaker phone handy which will allow members
to lazily connect or contribute when the conversation drifts into topics
that might be of interest to various remote resources as would be
dictated by the natural flow of the conversation. A stenographer would
transcribe the conversation in real-time, and publish this conversation,
or minutes thereof to, say, an IRC channel,
Part of our "tool chest" is IRC.
* All developers, QA, business folks, project managers are always
online, tuned to our channel
* We have a bot that is the "stenographer"
* The IRC chats are recorded and available on our wiki
* If you want someone's attention, ping their name and the IRC
client makes a racket. That way people are only paying attention
to IRC when they need to. Otherwise they are working away.
I pasted just a small part of an IRC log from Friday afternoon (see
below). Participants from:
* Crete (heinz -- "the java specialist")
* Eastern PA (me)
* Georgia (andy)
* Middle PA (ken and andrew)
* California (mike and mark)
* Middle New Jersey (marc, harry, QA)
* missing: Denver and Iowa
*Example from IRC log that was accompanying a daily stand-up/scrum
conference call. missing chunks of time are conversations on the telephone:*
13:50 <jonkern> need to consider how to handle errors...
13:51 <heinzmk> at least convert them to RuntimeExceptions
13:51 <heinzmk> then we don't miss them
13:52 <jonkern> Good idea andy! the issue is all yours :-)
13:52 <ajpowell> fair enough
13:53 <jonkern> mg-256
13:54 <ajpowell> flex.messaging.messages.ErrorMessage
13:54 <jonkern> and maybe an ErrorVO so we can translate to human
readable and do messaging if needed...
14:00 <jonkern> http://confluence. -blurredout-
14:06 <jonkern> mg-257 added for privs/roles mechanism
14:06 <jonkern> mg-245 likely closed today
14:06 <jonkern> perf scripts will be placed under svn
14:07 <jonkern> heinz
14:09 <heinzmk> if we make the delta management flexible, it would
create a lot of SQL queries
14:26 <jonkern> logging time in jira, keep the text small... maybe
a sentence or two
14:26 <heinzmk> and increments of 15m
14:29 <jonkern> http://jira. -blurredout-
14:30 <heinzmk> that is bad ...
14:30 <heinzmk> :)
14:30 <mmatrix> Sorry Mark, had to say it
14:30 <ajpowell> this is an awfully long conversation on brevity :)
14:30 <heinzmk> hehe
14:31 <jonkern> :-)
14:33 <heinzmk> for that we use the SVN logs
14:34 <mmatrix> speaking of brevity, weren't Scrums supposed to be
14:34 <jonkern> yes!
14:34 <heinzmk> bye
14:34 <jonkern> thanks
14:34 <jonkern> END-O-CHAT
Owen Thomas said the following on 6/3/07 2:51 AM:
- 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.