As an independent consultant, I have done a wide variety of jobs for a number of clients.  They usually entail setting up a development environment including source control and revision control, then adding product features.

Sometimes I work with the client's staff.  I teach them how to write software requirements documents so that everyone knows WHAT is going to be built.  Right after that, we do design documents to explain HOW it is going to be built.

This is not some huge bureaucratic institutionalized process I use.  It's simple, easy to use, and very effective in getting the thinking done BEFORE the coding starts.

After that, we go over which patterns are best suited to the task at hand and how we apply them.  This is often where most of the organizational change happens.  When people start thinking in patterns and use simple documentation, they find that their projects move along a lot faster, require less re-work and meet the needs of their customers on the first try.

Add to that a little test capability, some REAL source control and you have a nicely functioning organization.

When I am working on a project where I am the only one writing code, I still use these same processes.

Some of the projects I have done as the sole developer are shown on my Software Projects page.