(Presented as Part 3 in the Scrum Alone is Not Enough series.) As mentioned in the introduction to the Scrum Alone is Not Enough series, Scrum is simply the framework and, to work best, other tools and patterns need to be incorporated to build the most effective systems. Portfolio Management is one of those things […]
Kanban
Kanban Portfolio View – continued
(Continued from Kanban Portfolio view and the 3 core rules. This is the conclusion of Part 2 in the Scrum Alone is Not Enough series.) 2. Limit Work In Progress We know from queuing theory, psychology of multi-tasking, and empirical evidence (Rally study, my summary of the Rally Study) that more Work in Progress means less work gets done overall. […]
Kanban Portfolio View
(Presented as Part 2 in the Scrum Alone is Not Enough series.) Do you know what projects your Team is working on? Do you know what the Teams around you are working on? Does everyone in your organization know? In almost every organization that I visit, the answer is a resounding no. Scrum may have been […]
Scrum Alone is Not Enough
To be successful with Scrum in the long term you need more than the basic framework. This is intentional. Scrum provides the structure as a starting point, but it’s designed to work well when applied with other effective patterns. Like the Design Patterns movement of the late ’90s, a pattern can be used by itself […]