InfoQ Homepage Pair Programming Content on InfoQ
-
/articles/pair-programming-no-panacea/en/smallimage/logo-agile.jpg)
Pair Programming Is No Panacea
Is pair programming all that it's cracked up to be? Contrary to popular belief, pairing can lead to a decrease in creativity, groupthink, inappropriate feedback, and can be demoralizing. Wes Higbee explores why it definitely shouldn't be mandated, and why you should consider other options where it could be beneficial.
-
/articles/why-wont-pair/en/smallimage/LOGO.jpg)
Why Won’t They Pair?
Pair programming is one of the core techniques of eXtreme Programming and has been shown to be effective for knowledge sharing as well as code quality, but it is a practice that is often not used, even in the most agile of organizations. Linda Cook explores why that is and provides some advice on how to encourage teams to try the practice.
-
/articles/no-hotfix-deployment/en/smallimage/logo-agile.jpg)
The Way to No-Hotfix Deployment
Hot-fix redeployment is a waste of time and effort at best, and often a source of further regression, Adam discusses some ready-to-use techniques that helped he and his team reduce the frequency of hot-fix deployments to almost zero.
-
/articles/change-practices-principles-values/en/smallimage/agile-logo.png)
Why We Fail to Change: Understanding Practices, Principles, and Values Is a Solution
There’s no reward for being a Scrum or kanban shop if we are not delivering value to customers. We see virtually no impact of agile or lean on the bottom line of success rates of improvement initiatives, because organizations often look for recipes. We need to change our mindset, and focus on the principles that people follow and values they share and the bigger whole: organizational culture.
-
/articles/mancuso-software-craftsman/en/smallimage/logo-caftsman.png)
Q&A with Sandro Mancuso about The Software Craftsman
In the book The Software Craftsman, Professionalism, Pragmatism, Pride Sandro Mancuso explores how craftmanship plays a role in agile software development. The book contains stories, examples and practical advice for software developers and other professionals involved in software projects to achieve technical excellence and customer satisfaction.
-
/articles/revisit-p-collective/en/smallimage/logo.jpg)
Revisiting XP: be a thoughtful programmer by exercising more collective ownership
Frequently developers cause and face regular frustration often due to a lack of consideration for those who come after them. This article explores the approach of programming more thoughtfully by revisiting one of the most simple (yet often misunderstood) XP rules: collective ownership
-
/articles/introducing-pair-programming/en/smallimage/logo-2.jpg)
Introducing Pair Programming
Why don’t more teams use pair programming? Why should they? Pair programming can increase quality, velocity and even job satisfaction, if it is implemented well. If you have ever been curious about pair programming, loved or hated pair programming, wished you were pair programming or tried and failed to introduce it to your team, this article examines how to make it work and how to get started.
-
/articles/measure-improve-productivity/en/smallimage/ShowCover.jpg)
Measuring and Improving Software Development Productivity
The book Improving Software Development Productivity contains practices, models and case studies to quantitatively support adoption of agile software development. An interview with Randall Jensen about measuring and improving productivity, contribution of agile to productivity, benefits from pair programming and teams, knowledge retention in maintenance and commandments for communication.
-
/articles/agile-pair-paining/en/smallimage/logo.jpg)
Pair Painting
Victoria was painting her kitchen last week and it got her thinking about pair programming. She and her partner have painted rooms together before, and they've ended up with something they've been really proud of, but when she did this alone, even though she has the skills and the knowledge, it didn't end up as good. She wondered why?
-
/articles/agile-defense-industry/en/smallimage/logo.jpg)
Agile in the Defense Industry
The Defense Industry is often viewed as a very “non-Agile” culture. Teams, organized along strict hierarchical boundaries, seldom collaborate freely and are forced to communicate through the handoff of contract-specified artifacts. In this article, Jeff Plummer shares his experience with successfully applying Agile principles and practices to his team working in the Defense Industry.
-
/articles/dealing-with-change-evolving-world/en/smallimage/anniversary.jpg)
Naresh Jain: Dealing with Change in an Evolving Contextual World
Naresh Jain won the Gordan Pask award in 2007. He writes about the need to adapt our processes and build on top of agile practices, one size doesn't fit all and processes must evolve as we tackle more and more complex problems. He examines some of the key elements from the Lean Startup movement and shows how they are the logical next step for many agile implementations.
-
/articles/adopting-pair-programming/en/smallimage/pair-on.png)
Successfully Adopting Pair Programming
Jay Fields takes a look at pair programming from an adoption perspective. This article is for you if you already know what pair programming is and guidance on how to get to the point of successfully practicing pair programming. Jay goes over everything from an optimal seating arrangement, to effective coaching techniques, to calling out common mistakes to avoid.