Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • 1
    By suggesting that perhaps the sizing should be increased for a paired story, you seem to make the implicit assumption that pairing will slow you down compared to going it alone, or that adding an additional person reduces overall capacity. What's the evidence for that? Commented Aug 22, 2013 at 23:43
  • Based on comments from the devs. It seems the general consensus from them is that it's not always as productive as two people working on two tasks and catch up frequently, rather than one person sitting there watching. My gut feel was that a 2-point story is a 2-point story, but it was something they raised I wanted to see what other people thought, to validate my gut feel! Commented Aug 23, 2013 at 0:57
  • @JasonTrue: In my experience pairing does slow down in general. Of course, it has the advantage that knowledge about the code is spread among the developers. So, you have an advantage and you have to pay a cost for it. Commented Aug 23, 2013 at 3:41
  • In my experience, pairing removes gumption traps and increases velocity on complex problems. I've only found it to slow me down on trivial problems. Commented Aug 23, 2013 at 4:16
  • 2
    Developers often raise this issue in environments where story points and velocity are being misapplied as an individual performance metric instead of measuring project variance. You might want to re-evaluate the perception of these numbers within the team and the outside organization. Commented Sep 2, 2013 at 18:33