title: Which SDLC methodology to use?
body: <p>I'm moving to a new company where I will be the project manager/developer/tester/release management etc... for the projects I work on. Basically I'm everything. The programming manager doesn't care what you do as long as you deliver a product. So, I need to develop how I'm going to go about managing my projects. I also need to follow some methodology so that I'm not learning bad habits. </p>
  
  <p>So, basically what kind of methodology should I use? Is there some resources out there I might look at for the situation I'm going to be in? Should I adopt agile or scrum? These projects will be fairly small.</p>
  
  <p>As of right now, here is how I plan on doing things. Please comment on any of the following. </p>
  
  <ol>
  <li>gather requirements</li>
  <li>analyze requirements</li>
  <li>fix/change requirements...start over at 1</li>
  <li>design</li>
  <li>development</li>
  <li>unit testing</li>
  <li>load testing</li>
  <li>user acceptance testing/ fix bugs</li>
  <li>move to production</li>
  </ol>