(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.
One more tool. Commercial again :( But this one, they support Kanban board, integrated into the overall system. With bug tracking and effort tracking. They say you can use it for Kanban, Scrum, or whatever your process is.
(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.
(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.
A variation of burndown chart which allows to visually identify how fast the team is resolving the items, and also, what is the rate of adding new work items in the middle of the work.
A variation of burndown chart which allows to visually identify how fast the team is resolving the items, and also, what is the rate of adding new work items in the middle of the work.