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

RE: [XP] Re: Pair Programming problem: 3 pros 2 cons. What to do?

Expand Messages
  • Charlie Poole
    Also, do *not* just decide to pair and do it without some in-depth discussion of how to do it. Developers tend to think it s obvious but it isn t always so.
    Message 1 of 42 , Jun 9, 2009
    • 0 Attachment
      Also, do *not* just decide to pair and do it without
      some in-depth discussion of how to do it. Developers
      tend to think it's "obvious" but it isn't always so.

      Charlie

      > -----Original Message-----
      > From: extremeprogramming@yahoogroups.com
      > [mailto:extremeprogramming@yahoogroups.com] On Behalf Of banshee858
      > Sent: Tuesday, June 09, 2009 10:31 AM
      > To: extremeprogramming@yahoogroups.com
      > Subject: [XP] Re: Pair Programming problem: 3 pros 2 cons. What to do?
      >
      > >
      > > PP was suggested by Scrum master and team agreed to try it
      > for awhile.
      > > On a retrospective meeting 1 month later majority of the
      > team members
      > > agreed to keep this practice. But now 2 developers criticize PP.
      > >
      > It sounds like you began the process with a consensus
      > decision making process and then changed the rules to allow a
      > majority vote without identifying you were switching your
      > decision making process. I am not surprised that you are
      > having problems with the minority. They feel like they got
      > shafted. I'd work to revisit the decision with and return to
      > consensus.
      >
      > Carlton
      >
      >
      >
      > ------------------------------------
      >
      > To Post a message, send it to: extremeprogramming@...
      >
      > To Unsubscribe, send a blank message to:
      > extremeprogramming-unsubscribe@...
      >
      > ad-free courtesy of objectmentor.comYahoo! Groups Links
      >
      >
      >
      >
    • Charlie Poole
      Also, do *not* just decide to pair and do it without some in-depth discussion of how to do it. Developers tend to think it s obvious but it isn t always so.
      Message 42 of 42 , Jun 9, 2009
      • 0 Attachment
        Also, do *not* just decide to pair and do it without
        some in-depth discussion of how to do it. Developers
        tend to think it's "obvious" but it isn't always so.

        Charlie

        > -----Original Message-----
        > From: extremeprogramming@yahoogroups.com
        > [mailto:extremeprogramming@yahoogroups.com] On Behalf Of banshee858
        > Sent: Tuesday, June 09, 2009 10:31 AM
        > To: extremeprogramming@yahoogroups.com
        > Subject: [XP] Re: Pair Programming problem: 3 pros 2 cons. What to do?
        >
        > >
        > > PP was suggested by Scrum master and team agreed to try it
        > for awhile.
        > > On a retrospective meeting 1 month later majority of the
        > team members
        > > agreed to keep this practice. But now 2 developers criticize PP.
        > >
        > It sounds like you began the process with a consensus
        > decision making process and then changed the rules to allow a
        > majority vote without identifying you were switching your
        > decision making process. I am not surprised that you are
        > having problems with the minority. They feel like they got
        > shafted. I'd work to revisit the decision with and return to
        > consensus.
        >
        > Carlton
        >
        >
        >
        > ------------------------------------
        >
        > To Post a message, send it to: extremeprogramming@...
        >
        > To Unsubscribe, send a blank message to:
        > extremeprogramming-unsubscribe@...
        >
        > ad-free courtesy of objectmentor.comYahoo! Groups Links
        >
        >
        >
        >
      Your message has been successfully submitted and would be delivered to recipients shortly.