<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sun, 19 May 2013 08:37:43 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Wil Sinclair's Blog: Process Patterns]]></title>
      <guid>http://www.phpdeveloper.org/news/15655</guid>
      <link>http://www.phpdeveloper.org/news/15655</link>
      <description><![CDATA[<p>
On the Zend Developer Zone today there's <a href="http://devzone.zend.com/article/12887-Wil-Sinclair-talks-about-Process-Patterns">a new post</a> mentioning something from <i>Wil Sinclair</i> about something he calls "process patterns" in software development.
</p>
<p>From <a href="http://wllm.com/2010/12/28/process-pattern/">Wil's post</a>:
<blockquote>
I need a word for several engineers working on the same project that isn't 'team'. Why? Because most engineers working on the same project aren't working together as a team. This is why I believe in process patterns. Note: I didn't say that I believe in processes, because I don't. [...] You name a methodology, and I don't believe in it. But I do believe that there are some process patterns that can dramatically improve team productivity.
</blockquote>
<p>
These patterns are things that are common to several of the processes common to software development - like backlogs, test driven development, etc - but don't have to be considered as something that only comes with XP or Scrum and shouldn't be used outside them. There's even <a href="http://www.ambysoft.com/processPatternsPage.html">a whole other site</a> dedicated to defining these patterns and where the ideas came from. Oh, and don't forget to add <i>Wil</i>'s new word to your vocabulary - "hackle", two or more engineers working together on one project (not necessarily as a team).
</p>]]></description>
      <pubDate>Thu, 30 Dec 2010 08:34:01 -0600</pubDate>
    </item>
  </channel>
</rss>
