Home » Archives

Content tagged with: lean

[9 Nov 2012 | No Comment | ]

This session walk you through charts from real Kanban teams asking “what should be happening”?

[29 Aug 2012 | No Comment | ]

This presentation reviews the top 10 myths and misconceptions, along with a few neglected and important principles of Lean thinking that many in software development, including Kanban practitioners, neglect. I first learned about a Kanban approach to development from an apologetic agile practitioner concerned that they’d broken “the rules.” Although it’s common practice, fixed time-boxes aren’t a required strategy for agile development. Since Kanban’s broad adoption, I’ve continued to encounter a number of myths and misconceptions both for and against Kanban.

[27 Apr 2012 | No Comment | ]

As a full-service online-agency e-netconsulting KG ist specialized in technically sophisticated web- and mobile-solutions. Aiming for improvement of internal processes Kanban soon appeared as a suitable method. Kanban enables us to model the entire value-added-chain . Focusing on software-development led to high response time regarding inquiries and often did we not go the whole distance, i.e. documentation and similar tasks remained incomplete.

[12 Apr 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.

[10 Aug 2011 | No Comment | ]

This video discusses Programmer Anarchy, a development process where programmers are not just empowered to act but the driving force behind a product, leading to substantial increase in results.
http://www.infoq.com/presentations/Leaner-Programmer-Anarchy

[13 Oct 2010 | No Comment | ]

The method of Modeling in Color (MIC) has its foundation in object-oriented analysis and design; however, given today ís modern service oriented architectures (SOA), the approach is more relevant than ever. In any SOA, MIC can provide answers to difficult questions like: How are services properly designed? What ís the appropriate level of granularity for those services? Basic MIC techniques will be discussed and how to break a Color Model into discrete, loosely coupled components will be examined. How to convert the componentized model into XML schema and into XML …

[23 Aug 2010 | No Comment | ]

This session describes how Lean Production and Kanban has been applied to game development. Lean principles and Kanban tools have been used by a number of developers, including the presenter, to slash production costs by over 50%. As a complement, or replacement, to Scrum, Lean/Kanban provides predictability, transparency and optimization for complex game production.
http://www.infoq.com/presentations/kanban-video-game-dev

[11 Aug 2010 | No Comment | ]

This video presents how to surpass the limitations of some Kanban systems based on a sequence of phases by introducing work cells which involves using simultaneous phases grouped in two queues: what you are doing and what you are going to do.
http://www.infoq.com/presentations/Single-Piece-Flow-Kanban
Related article: Aspects of Kanban

[29 Jun 2010 | No Comment | ]

It is not uncommon in IT projects that you are required to learn something on the fly or you see an opportunity to introduce a new technique or tool that would bring great benefits to a project. In this presentation, John Stevenson discusses how Kanban can be used to manage a training schedule, for either personal development or for team skills transfer.
Watch this video on SkillsMatter.com

[10 Jun 2010 | No Comment | ]

Last year one of my client teams was looking for a better way to work following some problems while running fairly standard Scrum. One change appeared to be to combine Scrum with kanban – “Scrumban”. So we jointly decided to give it a go. This experience report explains how the team did it. It should help anyone interested in evolving their Scrum and other timeboxed iterative process to an interesting alternative. The talk will cover:
* Why evolve? A summary of how the team was working and the issues they were …