A fellow trainer pointed me to this post from David Anderson: “EXTENDING THE FIVE CORE PRACTICES OF KANBAN” 

As I’ve identified in presentations and key note speeches I gave in 2010, 2011 and earlier this year, the biggest oversight is leadership. Small acts of leadership from any member of the team need to happen regularly. It is these acts of leadership that make change happen.

So the 6th practice is: Leadership - give permission for ideas and encourage process innovation from any and all team members.

Sounds like building a team ;-)

There is also a need for explicit feedback loops. The Kanban book identifies these at two levels:

• the daily standup meeting at the team and individual contributor level
• and the operations review at the organization and inter-team or across services level

So the 7th practice is: Implement Organizational Feedback using Quantitative Measures of Demand and Capability

Sounds like having short feedback loops is a good thing

http://agilemanagement.net/index.php/Blog/extending_the_five_core_practices_of_kanban/

Nice article from fellow Scrum Trainer about the differences between “Scrum” and the “Kanban Method”

1. You are applying Kanban to the incorrect context.
2. Kanban is modeled more after the assembly line and manufacturing.  Scrum is modeled more after creative product design.
3. From a Complexity Science view, Kanban is for ‘complicated’ work while Scrum is for “complex” work.

Make sure to understand the difference between “Kanban” and “The Kanban Method”

Full article
http://scrumcrazy.wordpress.com/2013/02/04/kanban-vs-scrum-kanban-is-not-for-software-development-but-scrum-is/

Great post from Jason Little about 4 stages that you go through learning a new process.

“I like to use the competence/consciousness model to describe what I see when any new process or change is introduced.”

http://www.agilecoach.ca/2012/07/09/kanban-isnt-the-point/

Nice job Jimdo people!

See the video.
http://de.jimdo.com/2012/07/03/besuch-von-mr-kanban-himself

Blog post in German.

We as devs are obsessed with #Agile, #Lean, #Kanban always looking for an excuse to solve our problem, instead of concentrating on the problem

Great quote from Hadi Hariri

Now go and solve the problem (or write an app) 

Nice article about Kanban VS Scrum
Best bits: 

Highly innovative products are not often created via a production line

Innovation is not something that you can enforce. Scott Berkun has a nice lecture about that. The Myths of Innovation: Scott Berkun Lecture

However the impact of having to constantly react to the latest crisis would be flagged and highlighted very quickly. The root cause would be analysed, made transparent and addressed.

The 5 Whys is a popular technique here

Full article from Edwin Dando

3 reasons to choose Kanban over Scrum
http://www.clarus.co.nz/blog/three-reasons-to-choose-kanban-over-scrum-1.html

Since you are here, you really should do this test
How Agile are you?
http://www.allaboutagile.com/how-agile-are-you-take-this-42-point-test/  

Great presentation to “grasp” Kanban. It shows how to adapt Kanban in a development project.

Interesting idea. I think it comes down to, that you forget about the process at all, since you are in a “self organizing flow state”.