(Russian Article) Explains lots of various PM-related stuff. Includes: use PERT to estimate tasks and risks; method to prioritize bugs based on "value/risk rectangle" ("квадрат риск-приоритет"), and others.
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.
Short (but to-the-point) explanation of how to use PERT approach to estimation of tasks. What's important, it gives a formula to calculate confidence level.
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.
(Russian article) Raises a valid question: how do we statistically interpret PERT deviation? Can we use it to estimate confidence level? Author thinks it is too much inaccurate, from pure statistics point of view. Proposes alternative approach (based on 2 point estimations, min & max, and Normal distribution.
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.