Loading ...
Sorry, an error occurred while loading the content.

156551Re: [XP] Agile challenges

Expand Messages
  • Jeff Langr
    May 6, 2011
      Someone should put that on a card or something. (hint, hint, Tim!)

      Seriously, this is a great list. On #3 ("don't turn your local people into
      remotes") absolutely, don't insist that everyone deal with the
      far-less-effective agile PM tools to accommodate all the remote folks.
      But I'll also suggest that it's probably very useful to have the locals to
      experience the perspective and disadvantage of being remote.

      Teleconferences are interesting: of course it's far more effective for
      everyone to be chatting in the same room, face-to-face, but I'd say the next
      most effective is *everyone* online. I've seen mixes where half the people
      are in a room and the rest are on the phone go sour too often (usually one
      of these halves dominates).


      ps--Well, perhaps there is still a bit of life to beat out of this horse.

      Langr Software Solutions
      http://agileinaflash.com <http://agileinaflash.com-->

      On Fri, May 6, 2011 at 8:14 AM, Tim Ottinger <linux_tim@...> wrote:

      > Five rules:
      > 1) Don't
      > 2) Dont' treat remotes as locals.
      > 3) Don't treat locals as remotes
      > 4) Latitude hurts, longitude kills
      > 5) Don't always be remote
      > Take the first with a grain of salt. I'm once again a remote member of a
      > team,
      > so I see value in having remote members. We have to have special
      > considerations, like skype, webex or yuuguu or teamviewer, distributed
      > version
      > control helps, phone numbers for when something bad happens, interoffice
      > text
      > chat, extra email conversations, etc.
      > The second is dead serious. Remember that the remote is unable to move
      > through
      > the room, unable to eavesdrop on conversations in the bullpen, unable to
      > see the
      > signage and charts, and has limited visual range. It's like a handicap of
      > sorts,
      > but great people can overcome such things.
      > The third is dead serious. Don't turn all your local people into remotes.
      > Don't
      > eliminate physical charts, card walls, and conversations. Ignore what you
      > hear
      > about agile tools being as good as physical presence, because it's not
      > true.
      > Keep your locals working like locals, and pair them with the remotes
      > working as
      > remotes.
      > Fourth one is dead serious. Time zones suck. It's almost nice if you are
      > centrally located to have peers one or two time zones earlier and some one
      > or
      > two time zones later, but a lack of "common hours" really screws up the
      > pairing
      > work.
      > Fifth one is a joy. You want your remotes to come visit sometimes. It
      > establishes a rapport, it builds a sense of team, and it's good to like the
      > people you're compensating for. Definitely build a team with your remotes.
      > Tim Ottinger
      > http://agileinaflash.blogspot.com/
      > http://agileotter.blogspot.com/
      > ----- Original Message ----
      > > From: hennahsugumaran <hennahsugumaran@...>
      > > To: extremeprogramming@yahoogroups.com
      > > Sent: Thu, May 5, 2011 9:54:45 AM
      > > Subject: [XP] Agile challenges
      > >
      > > Hello guys,
      > >
      > > I wanted to know the Challenges that the agile developers face in the
      > >dispersed environment (i.e. when the developers in a team is spread
      > across the
      > >various places). The real time challenges.

      [Non-text portions of this message have been removed]
    • Show all 11 messages in this topic