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) 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.
Discusses principles behind Kanban vs. Scrum. States that Kanban is built on principles (which is good), and Scrum is built on practices (not that good).
Discusses principles behind Kanban vs. Scrum. States that Kanban is built on principles (which is good), and Scrum is built on practices (not that good).
(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.
(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.