Software Project Management

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.

Examples of project document and status report for small projects (e.g. under 100 man-hours).

(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.

Short howto on using PERT in Microsoft Project.

Prototyping lifecycle model.

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.

(Article in Russian.) Expirienced PM explains how you could customize MS Project to get the maximum value from it.

Analysis of a Kaban applied in a particular software organization. Analytics. Numbers.

Analysis of a Kaban applied in a particular software organization. Analytics. Numbers.

Highlights some aspects of Kanban, and gives some tips on application of it in Software. Some notes on the origin of the Kanban (production plants).

Highlights some aspects of Kanban, and gives some tips on application of it in Software. Some notes on the origin of the Kanban (production plants).

Deeper analysis of Kanban applicability to Software. Lots of interesting details on the origin (Toyota production). Provides several possible models of Kanban for Software. Good references list.

Deeper analysis of Kanban applicability to Software. Lots of interesting details on the origin (Toyota production). Provides several possible models of Kanban for Software. Good references list.

A very good summary on the Kanban. Highlights Kanban strong sides. Comparison to Scrum.

A very good summary on the Kanban. Highlights Kanban strong sides. Comparison to Scrum.

Another article on Scrum vs Kanban. Has a very good high-level descriptions of both Kanban and Scrum, and then gives pros and cons for each of them.

Sample of Kanban board for software development.

Kanban basics. Explained really well. Great idea.

Motivation tips.

Interesting point of view on distinctions between engineers and managers. Looks very reasonable.

Статья про то, как можно эффективно построить управление IT-проектом по ГОСТ.

(Russian article) Explains basics of how the project management & documentation was done according to USSR standards.

(Russian article) An approach to project planning, using timelines, quite a simple but powerful notation.

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).