Pair Programming

Share on facebook
Share on twitter
Share on linkedin

In PairProgrammingMisconceptions Martin Fowler makes some very good points and I agree with everything that he writes. However, I think that there is an important point that he has not mentioned: what are the alternatives?

In traditional software engineering projects, there has been widespread use of peer review (design reviews, code inspections, code walkthroughs etc.) as a means of improving code quality. Pair Programming provides a more efficient means of reviewing both design decisions and code.

Over the last few years I’ve noticed a tendency in many organisations to dispense with code reviews without replacing them with anything, let alone pair programming. If developers don’t think that anyone else will have to read their code, code quality in terms of defect density and ease of maintenance will suffer.

Leave a Reply

Your email address will not be published. Required fields are marked *

On Key

Related Posts

Perspectives on Agile vs Waterfall

Having been a trained and qualified project manager for several years before joining ScrumCenter, the world of Agile and Scrum was entirely new to me.

All training moved to live-online, free online coaching and mentoring available

Due to the current COVID-19 crisis, all in-person coaching and training has been cancelled. Instead, we are offering live-online Certified Scrum training and online coaching and mentoring.

Initial coaching sessions are free and our team is there to support you with any agile related topic.

Please use the menu items or buttons to access our course schedule and book online coaching.