[edem]

I worked for a company (subsidiary of Siemens) who adopted that horrendous Scrum methodology.

It was the absolute __worst__ year of my life. I had to pair with people non-stop even when __fixing bugs__. There were zounds of stupid rules which did not make sense whatsoever.

Perfect example of forcing a methodology on a company where it will never work.

I really like Pivotal products though. RabbitMQ is superb, and although Spring Boot is really slow and has its problems I use it on projects where performance is not important.

[cbryan]

It's not Scrum. It's Extreme Programming. It works fantastically well, even when you're __fixing bugs__. The whole idea is that you need to be paired so that two people can understand and problem solve around the bug. You end up with twice the understanding that you had before. It's worth it.

[mephitix]

Here's a radical thought - maybe Extreme Programming (I still think this is a genius marketing name :) works for some people and doesn't work for others?

After trying so many of these methodologies I've come to realize that people just work differently. It's self-defeating to try to push Extreme Programming or whatever on someone who prefers and is efficient at working alone.

Maybe adopt some of Scrum/XP/whatever that can be adopted at a high-level, but trying to push it through a team composed of people with different personalities and different ways of working just defeats the entire purpose.

[edem]

My thoughts exactly. I just __hate it__. I was super bored, super frustrated, and it was a complete waste of time. I resigned after a year of struggle.

[brobinson]

It worked extremely well results-wise for the few months we did it. I went home at the end of the day mentally exhausted, though. You are essentially having a conversation for 9 hours straight, 5 days per week.

[edem]

I could have done 10x work working alone. I speak from experience. In my current company we use Kanban, and I am super productive. We only do things which are useful for us.

[amorphid]

I dunno. Sometimes it's easier to simply stare at a problem & noodle your way through it. That's hard to do when forced to jibber jabber. Is the ol' stare & noodle a pair-friendly activity?

[tyingq]

I haven't done pairing myself, but I suspect it's highly variable based on the two specific individuals. Certainly I've noted smart and capable people I work with well, and some that I don't. Not every smart/capable pair is going to mesh. Just because I respect you doesn't mean I can work well with you, especially in such an intimate set up.

[amorphid]

Fair enough. I definitely enjoy pairing with some people & not others.

[tyingq]

It works better though, if you start from zero and hire people that drank the Koolaid.

It's hard to shoehorn it into an existing team where some portion of the team doesn't believe the premise. For example, some people (introverts, Asperger's spectrum, etc) will just never be comfortable with pairing.

Pivotal doesn't have this problem because developers that don't believe wouldn't ever apply for a job there.

But, that doesn't help Pivotal in their consulting practice. Very few of their clients would have the same advantage.

[edem]

No it __is not working fantastically well__. I speak from experience. There are also numerous studies (I can link to them) which detail why pair programming wastes time if not used for the right problem (mentoring or super-difficult task).

[Huggernaut]

Seems fair to say in some cases it works fantastically well, in others not at all?

[edem]

Yes. Pair programming works well if someone is being mentored or you are facing a very hard problem. In other cases it is a waste of time. You can read a lot of studies about this topic.