Detailed and well-thought-thru article on brainstorming. But, as I see it, it is only author's opinion on the effective brainstorms. I have seen/participated/led brainstorms which violated some of the rules he proposed, and they still provided good value outcome.
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.
(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.
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.
(Russian article) Explains psychological things: why developers think managers are idiots, and why managers thing that developers are spoiled kids. And what manager can do to fix/avoid this problem.