(Russian article) Interesting idea for sustaining long projects: while working on bugs/features in a long project, you get to know its problems, deep architectural problems. So, spend some time and work on the "ideal" architecture, the one you'd build from the very beginning if you knew everything you know now. Knowing this "ideal" architecture will help you drive the project in the right direction.
An approach to Project Management (and the tool to implement it), where the entire process is completely transparent, and all the decisions are made by team itself.
V-Model (one more project lifecycle model). Steps similar to waterfall, but, unlike Waterfall, allows going back to earlier stages -- if a problem found on latest stage and needs to be corrected.
Spiral lifecycle. Was invented by a particular company in their specific project environment. As far as I know, has no wide applications in other teams.
Simple advice on how to do esimates, schedule, and how to later control the schedule execution. Most probably "as is" it can only be used on smaller projects.
Also, highlights a few cool features of MS Excel, which can be used for the proposed method, and for other tasks.