Home » Agile, Project Management

Kanban Side-Effects

12 April 2012 No Comment

Learn how Kanban, as an alternative to top-down approaches, can be used to support introduction of best software development and organizational practices using a few real-life examples.

Kanban is the simplest commonly used approach to software development and project management. With such a simple tool, which in terms of required practices prescribes close to nothing, we don’t expect much change of the way we work. After all, we are advised to start without changing our process much when introducing Kanban. The interesting thing which is observed in Kanban teams is something which is called emergent behavior: best practices are seamlessly introduced without much conscious effort. The funny thing is that exactly the same practices were resisted when introduced by direct management action before.

Video Producer: Agile Central Europe Conference

Related Videos:

Comments:

Add your comment below, or trackback from your own site. You can also subscribe to these comments via RSS.

Be nice. Keep it clean. Stay on topic. No spam.

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

This is a Gravatar-enabled weblog. To get your own globally-recognized-avatar, please register at Gravatar.

*