Transition - Yeret Agility

Patterns for getting to a lower WIP level in a system – The Freeze, No New Work, Limit Later, and some Mashups…

By Yuval Yeret|2011-07-30T08:59:45-04:00July 30, 2011|Blog, Export, kanban|

Some of us have the luxury of designing processes for greenfield systems meaning there is no history/legacy to deal with. Typically though, we are dealing with Brownfield/Legacy systems - This usually means there is some work in the system already, there are outstanding commitments, and some existing queues between steps in our processes. I'm working with several clients that decided to start using a Kanban system to manage their work, and believe Limited Work in Process is key to improving [...]

Why I think slack is highly important during an Agile/Kanban transition

By Yuval Yeret|2010-09-15T23:12:01-04:00September 15, 2010|Agile, kanban|

(Note, this post is about slack the concept not Slack the collaboration platform. Though Slack the platform is great as well. We use it at AgileSparks and love it, although it eats up some of our slack time...) Actually, the title is wrong. I think slack is highly important during any change initiative where you expect continuous improvement of the process and practices. The importance of slack is not new. Not in manufacturing, and not in the Software Engineering world. [...]