<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>pair programming | Scrum Agile Project Management Expert</title>
	<atom:link href="https://www.scrumexpert.com/tag/pair-programming/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scrumexpert.com</link>
	<description></description>
	<lastBuildDate>Mon, 14 Aug 2023 16:00:05 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://www.scrumexpert.com/wp-content/uploads/favicon.png</url>
	<title>pair programming | Scrum Agile Project Management Expert</title>
	<link>https://www.scrumexpert.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>10 Tips for Digestible Pair Programming</title>
		<link>https://www.scrumexpert.com/videos/10-tips-for-digestible-pair-programming/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 13 Jun 2023 15:11:38 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[pair programming]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7546</guid>

					<description><![CDATA[Pair Programming is an Agile software development technique proposed by the eXtreme Programming (XP) approach. Software developers are aware of the fact that this technique can have some huge advantages. Pair programming is an efficient way to share knowledge, it gives you an almost instant feedback loop, and delivers higher quality, less error-prone code. Pair programming can be exhausting though. The constant conversation with a colleague and continuous flow of ideas and feedback can be extremely tiring and might result in a severe headache at the end of your workday. However, it doesn’t have to be this way. This presentation discusses some easy ways to improve the quality of your pair programming sessions. They will help to make it – in addition to being super useful – a lot of fun. Discover 10 tips to help you improve your pair programming sessions to make them digestible. Video producer: https://fullstackeurope.com/ Text reference: How to keep pair programming digestible Further reading: Will Pair Programming Really Improve Your Agile Project? (A critical look at the book Pair Programming Illuminated)]]></description>
		
		
		
			</item>
		<item>
		<title>You Must Be Crazy To Do Pair Programming</title>
		<link>https://www.scrumexpert.com/videos/you-must-be-crazy-to-do-pair-programming/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 14 Mar 2022 22:25:07 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[pair programming]]></category>
		<category><![CDATA[XP eXtreme Programming]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=6962</guid>

					<description><![CDATA[Pair Programming is probably considered to be the most extreme &#8216;Extreme Programming&#8217; practice, and a powerful technique for unlocking learning in a software development team. This video looks at this cultural practice that supports our ability to create better software faster in continuous delivery and DevOps teams. The presentation from Dave Farley provides pair programming examples, describes some pair programming best practices, and challenges some thinking about pair programming patterns and antipatterns. When Kent Beck wrote about Extreme Programming (XP) he described Pair Programming as one of the technical and cultural disciplines that helped to improve the quality and efficiency of software engineering. Few teams that practice it would go back to working without it. Video producer: https://gotocon.com/]]></description>
		
		
		
			</item>
		<item>
		<title>Pair Programming for Remote Teams</title>
		<link>https://www.scrumexpert.com/knowledge/pair-programming-for-remote-teams/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 26 Oct 2015 16:37:21 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Blogs]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[distributed teams]]></category>
		<category><![CDATA[pair programming]]></category>
		<category><![CDATA[XP eXtreme Programming]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=2899</guid>

					<description><![CDATA[Pair programming is one of the original practice of eXtreme programming, but it is also one of the least used by Agile software development teams. In his blog post, Alisdair McDiarmid explains how Customer.io uses pair programming with remote teams. Customer.io has been growing rapidly and its teams work in different location. Pairing has been used to allow people in different teams to work together virtually. Even if the technical aspects of pairing might be tedious, the practice has bring many benefits that include improved collaboration, quicker bug fixing and faster feedback. The blog post explains all the benefits of having two brains focusing on certain tasks. The most important benefit is that participants are learning quicker. Alisdair McDiarmid wrote &#8220;For me, whether remote or in person, the most important reason for pairing is an obvious one: learning. I’ve already learned a ton of things from my new colleagues, and I’ve been able to teach them a little of what I know too. This can be something as simple as a neat Vim trick, or as involved as the history of a collection of software components. Every time I pair with someone, I get a little better as a software engineer, and those tiny improvements add up to create a more effective engineering team.&#8221; Read the full blog post on http://customer.io/is-open/How-Pairing-Powers-Remote-Teams.html]]></description>
		
		
		
			</item>
		<item>
		<title>Pairing Programmers and Testers</title>
		<link>https://www.scrumexpert.com/knowledge/pairing-programmers-and-testers/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 06 Aug 2013 19:50:04 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Blogs]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[pair programming]]></category>
		<category><![CDATA[scrum team]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1603</guid>

					<description><![CDATA[Scrum requires that members of the team collaborate. One of the agile software development practice used to collaborate is pair programming. In his blog post, Erik Brickarp reports his experience when pairing a programmer and a software tester. He explains how he, as a software tester, paired with a programmer and also a domain expert to take the bugs out of a critical feature that was put in production without adequate quality assurance. In the results of this pairing, Erik Brickarp mentions: * having fun * quicker bug fixing after cooperation to discover the bug * they rarely worked the three together * there was a lot of learning for all participants * longer focus when working together than individually Read the complete blog post on http://erik.brickarp.se/2013/06/experience-report-pairing-with.html]]></description>
		
		
		
			</item>
		<item>
		<title>Can Pair Programming Work?</title>
		<link>https://www.scrumexpert.com/knowledge/can-pair-programming-work/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 22 Jul 2013 20:05:34 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Blogs]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[pair programming]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1589</guid>

					<description><![CDATA[Pair Programming is one of the eXtreme programming (XP) original practices. Continuously in surveys about Agile, it is one of the least used Agile practices. In this blog post, Dave Nicolette do an extensive survey of pair programming trying the question: &#8220;does pair programming work?&#8221;. He starts by exploring the meaning of &#8220;working&#8221; and if we could answer this question with a simple &#8220;yes or no&#8221; logic. He then discusses other issues around pair programming like physical constraints, management issues, nature of the tasks, learning curve or personality types. At the end of this exploration, Dave Nicolette provides his own opinion and reveals that he thinks that pair programming works. This practice provides a much clearer understanding of requirements and helps maintain self-discipline. Read the complete post on http://davenicolette.wordpress.com/2013/07/06/does-pair-programming-work/]]></description>
		
		
		
			</item>
		<item>
		<title>Pair Programming as a Good Practice</title>
		<link>https://www.scrumexpert.com/knowledge/pair-programming-as-a-good-practice/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 18 Oct 2012 17:40:56 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Blogs]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[pair programming]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1255</guid>

					<description><![CDATA[In this article, Gunther Verheyen explains that pair programming is a good software development practice. Even if Scrum doesn’t prescribe specific engineering practices, Scrum fully supports the agile principle that says “Continuous attention to technical excellence and good design enhances agility”. Pair programming is a good practices promotes by the eXtreme Programming approach. According to Gunther Verheyen, its main goal is software quality. Its success lies in the roles and the rotation of pairs. The article provides different type of roles implied in the pair rotation implemented by his company. There is the lead-partner association where the lead is the person that has the responsibility to implement a specific backlog item. The rotation occurs every half-day. There is also the driver-navigator roles. The driver writes the code and the navigator minds respect for the overall direction and design. These two roles are switched frequently during the half-day. The navigator checks in real time the code for standards, duplicate or reuse. This should be done anyway and this is why Gunther Verheyen thinks that pair programming is not more expensive than programming alone. Instead doing some activities serially, they are now performed in a parallel. Another great additional advantage of pair programming is knowledge sharing. This is why Gunther Verheyen concludes that pair programming should be part of a software engineer’s normal daily practice.]]></description>
		
		
		
			</item>
		<item>
		<title>Pair Programming Report</title>
		<link>https://www.scrumexpert.com/knowledge/pair-programming-report/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 30 Aug 2012 15:02:38 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Blogs]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[pair programming]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1199</guid>

					<description><![CDATA[Pair Programming is an Extreme Programming (XP) practice where two developers collaborate on the same code on one workstation. In this blog post, Yan Pritzker provides an experience report after his first nine months of pair programming. On the positive side of pair programming, he lists quick knowledge transfer, improved productivity and higher quality code. The disadvantage of this practice are a tired voices, difficulty to research and learn, need for space for creative activities, longer time spent on trivial tasks, possible issues with sharing the same configuration for the development environment. His conclusion is that &#8220;pairing coupled with an extremely pragmatic approach to knowing when not to pair is the key to success.&#8221;]]></description>
		
		
		
			</item>
		<item>
		<title>Four Antipatterns of Pair Programming</title>
		<link>https://www.scrumexpert.com/knowledge/four-antipatterns-of-pair-programming/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 23 May 2012 18:34:30 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[pair programming]]></category>
		<category><![CDATA[people]]></category>
		<category><![CDATA[scrum team]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1083</guid>

					<description><![CDATA[Scrum likes to rely the technical practices recommended by eEXtreme Programming to improve the software quality. Pair programming is one of these practices, even if surveys tell us that it is not used as much as other practices like test-driven development (TDD). In this article, Zee Spencer shares four common pitfalls of pair programming and tell us how to avoid them. These four common pitfalls are * Motive Mismatches * Competence Chasms * Disposition Dissonance * Semantic Squabbles The article explains us that each pitfall presents its own challenges, but it also offers potential benefits if you deal with it effectively. None of them can be solved by avoidance.]]></description>
		
		
		
			</item>
		<item>
		<title>Does Pair Programming Have to Suck?</title>
		<link>https://www.scrumexpert.com/videos/does-pair-programming-have-to-suck/</link>
					<comments>https://www.scrumexpert.com/videos/does-pair-programming-have-to-suck/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 07 Mar 2012 16:48:30 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[pair programming]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=984</guid>

					<description><![CDATA[Pair programming is sometimes the norm, and some developers really enjoy the collaboration, experiencing enhanced productivity. In other teams, pairing is shunned, avoided, or&#8230; faked. Angela Harms did a short survey about pairing attitudes and compared successful and unsuccessful pairing experiences. The survey produced some really clear results. Some factors most of us think are really important to a good pairing session turned out to be&#8230; meh. Other factors, though, stood out, hands down, as clearly separating good from bad pairing experiences. This video discusses these survey results and why pairing sucks or doesn&#8217;t suck. Video Producer: Ruby Midwest Conference]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/videos/does-pair-programming-have-to-suck/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Pair Programming Benefits</title>
		<link>https://www.scrumexpert.com/knowledge/pair-programming-benefits/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 09 Feb 2012 19:36:03 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[pair programming]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=936</guid>

					<description><![CDATA[Pair programming is an extreme programming technique that should help Scrum teams to build better software: two heads are better than one, they say, and thus two heads will usually produce a higher-quality system. This article presents the benefits of this technique for the team, the developers and the managers that will appreciate the value of a true team that works well together, collaborates and continuously improves the code base.]]></description>
		
		
		
			</item>
	</channel>
</rss>
