<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pairing on Daniel Pomfret</title>
    <link>https://pomfret.uk/tags/pairing/</link>
    <description>Recent content in Pairing on Daniel Pomfret</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>© Daniel Pomfret</copyright>
    <lastBuildDate>Wed, 26 Jan 2022 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://pomfret.uk/tags/pairing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Further thoughts on pairing during software development! (Part 2)</title>
      <link>https://pomfret.uk/posts/further-thoughts-on-pairing-during-software-development-part-2/</link>
      <pubDate>Wed, 26 Jan 2022 00:00:00 +0000</pubDate>
      <guid>https://pomfret.uk/posts/further-thoughts-on-pairing-during-software-development-part-2/</guid>
      <description>&lt;p&gt;While being a Lead/Senior Developer on several agile development teams, I&amp;rsquo;ve seen the ups and downs of pair programming. I&amp;rsquo;ve tried to introduce pairing into new teams with different levels of success - so I thought I&amp;rsquo;d write down some of the experiences I&amp;rsquo;ve had - and the potential was of working that can make pair programming less painful.&lt;/p&gt;&#xA;&lt;p&gt;In August 2020 I wrote an article about &lt;a href=&#34;https://pomfret.uk/posts/some-thoughts-on-pairing-during-software-development-part-1/&#34;&gt;Some thoughts on pairing during software development.&lt;/a&gt; Where I talked about :&lt;/p&gt;</description>
    </item>
    <item>
      <title>Some thoughts on pairing during software development! (Part 1)</title>
      <link>https://pomfret.uk/posts/some-thoughts-on-pairing-during-software-development-part-1/</link>
      <pubDate>Tue, 04 Aug 2020 00:00:00 +0000</pubDate>
      <guid>https://pomfret.uk/posts/some-thoughts-on-pairing-during-software-development-part-1/</guid>
      <description>&lt;p&gt;Over the past few months, I&amp;rsquo;ve been pairing (pair programming) with other Software Engineers when working on stories during our sprints. It&amp;rsquo;s been fun, and the first time in a while I&amp;rsquo;ve enjoyed and felt rewarded while &amp;lsquo;pairing&amp;rsquo;. While I&amp;rsquo;m sitting in the sun, on a beach in Wales enjoying our holiday with my family, I look back and consider it hasn&amp;rsquo;t all been plain sailing&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;My first exposure to pair programming came as I was working on a team that was writing API&amp;rsquo;s for some of our business services. It was a relatively new formed team with a range of mid to junior level Software Engineers, a Business Analyst, a Product Owner, a QA tester and a Scrum Master.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
