What approach/methodology are you using for one-man software development -

you can find thousands of questions out there how develop software , methodology best one. these targeting medium large teams, people having different roles , responsibilities.
i'm interested in methodology using one-man-shows? steps doing, documents creating things want develop clear , document well, share community?

especially, i’m interested in following questions:
_are using structured approach you’re developing on own or no @ all?
_what phases using?
_which documents writing before , after coding?

and if have “your” standardized approach, can share templates using?

thanks in advance, cheers gerry

personally think matter of making decisions when comes development process (solo). in case wouldn't recommend setting massive development process pick elements prevent problems have earlier had. approach small applications (in right order):

• always write down going make , not going make (define scope) - think of functional requirements (functional design)
• (oo only) make class diagram displays relations between classes. (technical design - sequence diagrams, while usefull, take massive amounts of time make)
• write program according have written down (or part of it).
• refactor , redesign application (once in every x hours, write 1 down)
• repeat step 3 4 until result wrote in functional design.
• walk through every corner of application find every single path , write down in testdocument. identify possible problems in paths , test them.

when comes big applications (or assignments else) prefer using "medium large teams" approach. brings guarantee not meeting problems.