title: Is there such a thing as a process smell?
body: <p>We're generally familiar with <a href="https://stackoverflow.com/questions/114342/what-are-code-smells-what-is-the-best-way-to-correct-them">code smells</a> here, but just as damaging if not more so are when the business side of things - as much as it falls within our domain - is  going wrong. </p>
  
  <p>As examples, the inverse of anything on the Joel test would be considered a major process smell (i.e. no source control, no testers) but those are obvious ones and the point of "smells" is that they're subtle and build into something destructive. I'm looking for granularity here.</p>
  
  <p>To start off with here's a couple (which can be turned into a list as the answers come in)</p>
  
  <hr>
  
  <ul>
  <li><p>Writing code before you have a signed contract with the client</p></li>
  <li><p>Being asked for on-the-fly estimates (<em>"just a rough one will do"</em>) for anything which will take more than a day (a few hours?)</p></li>
  <li><p>Ancient cargo-cult wisdom prevails (personal example - VisStudio sourcesafe integration is banned)</p></li>
  <li><p>You've stopped having non-project specific group meetings (or lack any similar forum for discussion)</p></li>
  </ul>
  
  <hr>
  
  <p><strong>So what are some other process smells, and just how bad are they?</strong></p>