title: Naming convention for new projects
body: <p>I've tried several times to come with an answer to this question. I'm not happy with how projects are named in my shop, they are usually random named after some of these items:</p>
  
  <ul>
  <li>the client</li>
  <li>some technology used/ or expected to be used inside the project</li>
  <li>some acronyms for the business case the project would relate to</li>
  <li>some names from the domain the project would be in</li>
  </ul>
  
  <p>I find several drawbacks with those approaches:</p>
  
  <ul>
  <li>the word pool quickly dries up when you have many similar projects</li>
  <li>having the client name inside the project makes it harder to have it abstracted to a generic product</li>
  <li>the acronyms usually sound horrific</li>
  <li>there are many projects that would not pass the prototype phase, and because of this they don't get a proper name</li>
  <li>it's hard to name a project before you know exactly what it does, so most of the time the name picked for the svn and issue tracking project are bad ones.</li>
  </ul>
  
  <p>Please tell me:</p>
  
  <p><strong>What is your naming convention in your shop, are you happy with it, and what would you choose if it were up to you?</strong></p>
  
  <p>Thank you!</p>