<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>ProjectLocker Blog: Tag practices</title>
    <link>http://blog.projectlocker.com/articles/tag/practices</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description></description>
    <item>
      <title>ProjectLocker joins the Agile Alliance</title>
      <description>&lt;p&gt;&lt;img src="http://www.projectlocker.com/images/Agile-logo-4c-corp.jpg" alt="ProjectLocker is an Agile Alliance Corporate Member" title="ProjectLocker is an Agile Alliance Corporate Member" width="220" height="160" /&gt;&lt;/p&gt;&lt;p&gt; It&amp;#39;s no secret: we like Agile Software Development here at ProjectLocker.&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;We&amp;#39;re not dogmatic about any one particular methodology over another.&amp;nbsp; As a company, we&amp;#39;ve always focused on supporting the most efficient ways software developers can save time, save money, and build better software.&amp;nbsp; But if you look at the &lt;a href="http://agilemanifesto.org/" target="_blank" title="Agile Manifesto"&gt;Agile Manifesto&lt;/a&gt;, I think you&amp;#39;ll see some things that we might agree with:&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;em&gt;&lt;strong&gt;&amp;quot;Individuals and interactions over processes and tools&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;em&gt;&lt;strong&gt;Working software over comprehensive documentation&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;em&gt;&lt;strong&gt;Customer collaboration over contract negotiation&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;em&gt;&lt;strong&gt;Responding to change over following a plan&amp;quot;&amp;nbsp;&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;With that in mind, especially given that supporting Agile teams is the &lt;em&gt;raison d&amp;#39;&amp;ecirc;tre&lt;strong&gt; &lt;/strong&gt;&lt;/em&gt;for &lt;a href="http://www.projectlocker.com/scenario/startup" title="ProjectLocker Lite"&gt;ProjectLocker Lite&lt;/a&gt; as well as our long-standing partnership with the Agile &amp;amp; Scrum experts at &lt;a href="http://www.3back.com/" title="3Back"&gt;3Back&lt;/a&gt;, we felt it was time to make it official:&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;ProjectLocker is now a corporate member of the &lt;a href="http://agilealliance.org/home" title="Agile Alliance"&gt;Agile Alliance&lt;/a&gt;.&amp;nbsp;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;For all of our current users who are Agile practicioners: I&amp;#39;d encourage you to take a moment and see what resources the alliance can offer to enhance your current project.&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;And if you&amp;#39;re an Agile practicioner or Alliance member who&amp;#39;s not using ProjectLocker yet, I think you&amp;#39;ll like what you see. &lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;

</description>
      <pubDate>Wed, 25 Jun 2008 10:25:00 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:933cadad-e8b1-48aa-98f0-5d555dac866c</guid>
      <author>Damon Young</author>
      <link>http://blog.projectlocker.com/articles/2008/06/25/projectlocker-joins-the-agile-alliance</link>
      <category>hosted</category>
      <category>subversion</category>
      <category>SVN</category>
      <category>trac</category>
      <category>agile</category>
      <category>alliance</category>
      <category>manifesto</category>
      <category>scrum</category>
      <category>development</category>
      <category>practices</category>
      <category>3Back</category>
      <category>ProjectLocker</category>
      <category>Lite</category>
    </item>
    <item>
      <title>Source control best practices for teams with multiple projects</title>
      <description>&lt;p&gt;While we&amp;#39;re very big proponents of &lt;a href="http://subversion.tigris.org/" title="Subversion"&gt;Subversion &lt;/a&gt;here at ProjectLocker, we also recognize that even the best tools and, consequently, the teams that use them can be crippled by the wrong development processes.&amp;nbsp; With that in mind, here is an excellent article by &lt;a href="http://www.crisp.se/henrik.kniberg/" title="Henrik Kniberg"&gt;Henrik Kniberg&lt;/a&gt;, a Certified Scrum Master with &lt;a href="http://www.crisp.se/index_en.html" title="Crisp"&gt;Crisp&lt;/a&gt;, a Stockholm-based Agile consulting firm.&amp;nbsp; In it, he proposes a methodology to most effectively make use of your version control tool when applying Agile best practices in an environment with multiple &amp;amp; distinct teams working from common code base.&amp;nbsp; Notice that he never mentions a specific version control tool, just a set of procedures and team protocols to help optimize the process.&amp;nbsp; More details at the link below:&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;em&gt;&lt;strong&gt;&lt;a href="http://www.infoq.com/articles/agile-version-control" target="_blank" title="Version Control for Multiple Agile Teams"&gt;&amp;nbsp;&amp;quot;Version Control for Multiple Agile Teams&amp;quot;&lt;/a&gt;&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Watch this blog for more posts in the future on best practices and other development resources we think will help you build better software. &lt;/p&gt;

</description>
      <pubDate>Thu, 10 Apr 2008 14:08:00 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:6ca62caf-d802-4e42-8c3b-f1599eea50a4</guid>
      <author>Damon Young</author>
      <link>http://blog.projectlocker.com/articles/2008/04/10/source-control-best-practices-for-teams-with-multiple-projects</link>
      <category>subversion</category>
      <category>hosted</category>
      <category>SVN</category>
      <category>agile</category>
      <category>scrum</category>
      <category>best</category>
      <category>practices</category>
      <category>software</category>
      <category>development</category>
      <category>lifecycle</category>
      <trackback:ping>http://blog.projectlocker.com/articles/trackback/9</trackback:ping>
    </item>
  </channel>
</rss>
