Re: Pair Programming
- --- In email@example.com, Mark Saffell <masaffell@...> wrote:
>Mark, these kinds of posts waste people's time.
> why should one read the book? did the person whom wrote the book read the book?
- You, a scrum guy, went to a pub with an XP guy!
Shame on you! You should know better than that.
On Feb 19, 2008, at 7:33 PM, Michael James wrote:
> I just went to a London XP pub night and met with a hardcore
> XP guy who claims to dislike Scrum. This wouldn't be notable
> except that it's happened before.
> I queried him on what practices he found useful, and it
> sounded a lot like Scrum to me, plus the engineering
> practices we usually recommend learning ASAP to
> avoid technical debt: (TDD, refactoring, continuous
> integration, pair programming....). He agreed that
> many teams fail to adopt these practices without
> a full-time mentor, learning them incrementally
> makes sense, and that Scrum is often the path
> people take to discover this.
> He also agreed with everything we've been
> talking about on this group: the importance of
> story "done" rather than task hours expended,
> getting the customer in the loop, fixed iterations,
> retrospectives.... I really couldn't find any
> contradiction with Scrum.
> As I see it, Scrum is XP's biggest ally. So where
> is this resentment coming from?