Got inspired this morning and diagrammed my (present) software process. Yes, it actually boils down to code-and-fix, but I've actually got eight defined nodes in the graph, with arrows going every which way. Three of the nodes even have a box around them to show that they are sort of a combined requirements and planning phase.
Looking at this diagram, I actually feel confident that I might be able to make small improvements to my process. It's so frustrating working at an ad-hoc level, for me and my users.
Got busy with Dia and diagrammed the whole thing after drawing it out on paper. I'm trying to get up the courage to carry this to software engineering class tonight and show my professor.