Lone Developer Project Management

PairProgramming is not always possible, and many developers are still "alone in the night"

A lone-developer project suffers from many of the same problems as multi-person projects, such as delays, budget overruns, ScopeCreep, GoldPlating, unrealistic expectations, lack of indicators, etc. What methods for managing larger projects can be used efficiently in a lone developer project?

Some suggestions:
See also:

View edit of August 14, 2010 or FindPage with title or text search