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