| Newsgroups |
gmane.comp.programming.extreme-programming |
| Message-ID |
<[email protected]> |
The absolute necessity for close collaboration (let alone
pairing) is a physical environment that supports it -
sufficiently visible screens, sufficient comfort with
whichever editor, enough room for each to move and
breathe, chairs that don't tangle, etc., etc., etc.
Right alongside that is a willingness to work that
closely and to make accommodation to and show respect
for the partner.
Have never worked in a pairing shop, but can identify
quite a number of conditions that will certainly kill
you. I recall a great session at Agile 2012 where what
pairing dysfunctions can occur were well exposed and
the solutions dealt with. Two important take-aways:
1. It takes a while, with the help of a good mentor,
for most teams to get the hang of pairing and to
become productive. 4-6 weeks minimum was cited.
2. Not everybody can, or will, acquire the skills
of pairing. Whether you have such people on your
team, who could say.
Finally, if it's the whole team who work together and
it's just you who are remote to them - bite the bullet,
get on the jet, and go work with them. If several are
remote in different places, well, you use what you have
available or can find to achieve collaboration.
BTW, my observation over several shops is that a common
will to accomplish what is good for the business and to
deliver the best quality will achieve better results
with almost any process than almost any other process
can without that will. People who care and have
humility work better.
jonathan berger [email protected] [extremeprogramming] wrote:
>
>
> Hi Milton!
>
> My buddy Joe has been doing remote XP-style pairing for years, and keeps a pretty good blog about it. Lots of good resources here: http://remotepairprogramming.com/
>
> Are you acting as a PM on the team or an engineer? It'll be a steep bar to ask others to pair if you're not able to drop in and set the example—doubly so if you're remote.
>
> Good luck!
> JPB
>
>
>
> On Sat, Oct 8, 2016 at 9:30 PM, Michael Hill [email protected] <mailto:[email protected]> [extremeprogramming] <[email protected] <mailto:[email protected]>> wrote:
>
> __
>
> milton...
>
> i lean in massimo's direction on this.
>
> pairing is one of those things that surprises noobs. it doesn't *sound* like a skill, but it is one, and you have to learn it. there *are* natural pairs, but a natural skill here is relatively uncommon.
>
> if you're already skilled, then pairing remotely is no big deal: mildly annoying, not quite as awesome as pairing face-to-face, but still viable. if you're *not* already a skilled pair, what's likely to happen is that you'll block on pairing.
>
> i've paired with many noob teams over many years. by way of analogy, let me tell you about their "pairing stations". they tend to be, well, laptops in cubicles with tables that have the only fat part in a corner, suitable for a single individual. they tend to use 4-point fonts. and the second person is sitting 3 feet away because of the corner. and -- with the best will in the world -- you know what that usually results in? "Never again! Pairing is bad. Agile is bad. XP is bad."
>
> a remoting environment can do the same thing.
>
> now don't get me wrong, pairing remotely is fine when you know what you're doing.
>
> consider a counter-proposal: bring them together for a couple of months, face to face, with serious pairing stations. they can find their "pair-legs" together. they can learn what slight changes of voice mean. they can learn all the ways pairing can go wrong in addition to the ways that it rocks. *then* we go to remoting. i can almost guarantee you better results.
>
> cheers,
> geepaw
>
>
>
>
>
> --
> _________________________
>
> @jonathanpberger (Twitter, Github, Skype, etc)
> http://www.jonathanpberger.com
> 718.930.2165
>
------------------------------------
Posted by: Larry Brunelle <[email protected]>
------------------------------------
To Post a message, send it to: [email protected]
To Unsubscribe, send a blank message to: [email protected]
ad-free courtesy of objectmentor.com