One of the videos I've enjoyed recently over at Kanban School is this one with Pawel Brodzinski.
Pawel makes the point that Kanban does not replace software development methodology or project management methodology. I agree.
In the video he said it's more of a change management process (I think that's what he said) and I don't think he meant it quite like that.
To me, Kanban is a method of execution. On my teams, it's about the day-to-day execution and all the benefits that come with the Kanban process for that execution. The visualization really makes continuous improvement possible, almost inevitable.
So what do you think about all this? If you are new to Kanban, check out Kanban School.
Kevin HartfordProject Manager| Olgoonik Specialty ContractorsArlington, Va, United States
I agree that Kanban is more of an execution methodology than a PM or development methodology. I always view Kanban as something that is done within the process, rather than the process itself.
Josh NankivelEngineering Project Manager| AppleSioux Falls, Sd, United States
I see what you mean, it's more like a meta-process or framework your other processes can live in.
"There is a theory which states that if ever anybody discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable.
There is another theory which states that this has already happened."
