Re: Any advice on remote pairing?

It is best if the team really wants to pair (and wants to do all of the XP
practices, for that matter).

The worst case is forcing the team to do any specific practices after they
have already agreed to join.

A middle ground that is not disingenuous is to make it clear that the team
will be doing pairing (or all of XP) before each individual is given the
choice to join or not.



On Sun, Oct 9, 2016 at 2:56 PM, George Dinwiddie [email protected]
[extremeprogramming] <[email protected]> wrote:

>
>
> Milton,
>
> I haven't noticed whether the programmers WANT to pair, or if this is
> something you're imposing on them. That makes a big difference.
>
> - George
>
> On 10/9/16 9:13 AM, [email protected] [extremeprogramming] wrote:
> >
> >
> > Michel,
> >
> > It looks like I'll be the mentor. At least in this case, the project
> > manager. The hardest part will be getting the pair to work together. It
> > all new for them.
> >
> > I read 'Building Successful Online Communities", a good book. I hired
> > the developers not because of their technical skills but based on their
> > social skills. I'll still have to see if they can like each other.
> >
> > I am asking one to act as the navigator, who will take on the extra
> > responsibility of setting up the remote systems that will help us
> > collaborate as she prepare the style guidelines and testing and
> refactoring.
> >
> > They need these contracts and I need to make sure they produce quality.
> > We're forming a partnership, so team work is part of what we are doing.
> > Because I am the leader, they will have to learn with me.
> >
> > Thanks
>
> --
> ----------------------------------------------------------
> * George Dinwiddie * http://blog.gdinwiddie.com
> Software Development http://www.idiacomputing.com
> Consultant and Coach http://www.agilemaryland.org
> ----------------------------------------------------------
>
> 
>