InfoQ Homepage Kanban Content on InfoQ
-
Tracking Schedule Progress in Agile
The challenge of knowing whether we are on track to deliver haunts projectmanagers and developmentmanagers at various levels as their organizations take on agile approaches to product and project development. Driving towards smaller work items and lower work in process brings the benefits of both better project risk management as well as more effective agile execution and learning.
-
Applying Lean Thinking to Software Development
Lean’s major concept is about reducing waste, meaning anything in your production cycle that is not adding value to the customer is considered waste and should therefore be removed from the process. Steven Peeters explains how you can apply Lean principles in an IT environment.
-
InfoQ Interviews David J. Anderson at Lean Kanban 2013 Conference
If they were to carve a new Mt. Everest into the mountains surrounding Silicon Valley, then alongside Dijkstra, Kernighan, The Three Amigos and The Gang of Four they would need to make room for David J. Anderson, father of Kanban in the software development industry. The Lean Kanban Conference took place in downtown Chicago last week, and InfoQ interviewed Anderson.
-
Implementing Kanban in Practice
At the Lean Kanban conference, InfoQ asked Dr. Arne Roock how a team can evaluate whether Kanban is the right tool, and how to kick it off. Dr. Roock offers some prescriptive advice.
-
Kanban Pioneer: Interview with David J. Anderson
David J. Anderson, pioneer in Kanban for software development, recently came to Brazil. A group of InfoQ Brasil editors interviewed David about Lean, Agile and Kanban. See the highlights of the interview.
-
Using Kanban to Turn Around Distressed Projects
This case study describes how Kanban and lean development techniques were used to rescue a distressed project that had violated its budget, schedule, and quality constraints. The article presents a detailed account of how the techniques were introduced mid-project to establish control over a chaotic project environment, and is supported with several charts that show the team’s progress.
-
Kanban for Skeptics
As a change agent, you constantly need to reassure people that the path we follow is worthwhile traveling. Kanban raises much harder questions on a management and leadership level. This article summarises the most common arguments raised against Kanban and discusses how to tackle them, with links to a free e-book that Nick wrote.
-
Organizational Culture and Agile: Does it fit?
Recently, Agile Coach Michael Sahota has been exploring the impacts of organizational culture on Agile transformations. We caught up with Michael and asked him to answer a few questions for our readers.
-
Doing Kanban Wrong
Kanban as a tool to support lean software development continues to increase in popularity all the time. However, like countless tools before it, Kanban will be unfairly blamed for many project failures by people who are doing Kanban wrong. This article discusses some ways the author has tried to give Kanban a bad name. Hopefully these examples will keep you from falling into similar traps.
-
Use of Kanban in the Operations Team at Spotify
In this article, InfoQ spoke with Mattias Jansson, Operations Engineer at Spotify (an online music streaming service) about the adoption of Kanban by the Spotify Operations team. Jansson offered a lot of detail about the choice to adopt Kanban as well as the experiences that the Operations team at Spotify has gained while implementing a Kanban-based approach to dealing with their workload.
-
The Current Direction of Agile
This article focuses on some of the recent trends within the Agile community by briefly describing some alternatives to today’s well known Agile processes. Particularly focusing on estimation, forecasting deliverables and the increased impact Lean manufacturing has had on the Agile community.
-
Visualizing Agile Projects using Kanban Boards
In the spirit of "information radiators and “big visible charts” Kenji Hiranabe proposes using Kanban Boards to organize three viewpoints (Time, Task, and Team) so the whole team understands the current status of the project and can work in an autonomous, motivated and collaborative manner.