InfoQ Homepage Kanban Content on InfoQ
-
Mike Cottmeyer's View Inside The Lean/Kanban Conference
The first organized conference focusing on Lean & Kanban was held in Miami during the first week of May. Mike Cottmeyer was present and used his popular blog 'Leading Agile' to provide a relatively comprehensive play-by-play look into what occurred there.
-
Presentation: A Kanban System for Software Engineering
David Anderson presents a brief history of the kanban system through case study reports from teams at Microsoft and Corbis. Kanban acts to limit work-in-progress and focus the team on achieving a continuous flow of value to the customer and innovates on accepted agile management practices by providing an iteration-less process with a regular release cadence.
-
Kanban as Alternative Agile Implementation
Kanban systems for software, derived from the Toyota Production System, are an iterationless approach for scheduling work. Instead of using a time boxed iteration and planning meeting, the pulls stories from the backlog only when it has completed its previous work. Dave Nicolette thinks that its important to expand our repertoire beyond the basics become familiar with other tools like Kanban.
-
Presentation: Future Directions for Agile
In this presentation filmed during Agile 2008, David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile does not stand in just having a practice, but in finding ways to implement the principles contained by the Agile Manifesto.
-
Scrum-ban Paper Adds Kanban to Scrum
Corey Ladas has written an interesting paper titled "Scrum-ban" in which he describes how a Scrum team might introduce the lean practice of kanban. He goes on to describe an evolutionary process, which if taken far enough, replaces most of Scrum. Even for those who don't want to scrap Scrum and go lean, the paper provides a useful view into what kanban is and how it can augment Scrum.
-
Results of Agile Adoption Survey 2008
In February 2008, Dr. Dobb's conducted a survey on Agile adoption and the success rate of Agile software development. The survey revealed some interesting results on various parameters, including: adoption, scalability, iteration length, and team location.
-
Are Iterations/Sprints Waste or Value to Agile Teams?
Although many people consider iteration to be a key characteristic of agile software development, some question whether or not they're important, and add value to an agile method, or if they're superfluous, or even wasteful. InfoQ has assembled a roundup of arguments on the subject, to help agile teams decide if iterations are important for them.
-
Agile Kanban: Visual Tracking Beyond the Team Room
In the beginning Agile was largely a developer-driven initiative, sometimes improving development processes only to find the real bottlenecks lay outside developer control. In his latest InfoQ article, Kenji Hiranabe analyses Lean manufacturing's "Kanban" visual tracking tool, how it differs from the Agile taskboard, and how it helps identify more far-reaching improvements.
-
InfoQ Article: Lean Kanban Boards for Agile Tracking
"Big Visible Charts" aren't unique to Agile - Lean manufacturing also has its Kanban Boards. "Kanban" roughly means "card or sign," and each Kanban card is "pulled" onto the board only when the work represented by an "in progress" card is retired. In this InfoQ article, Kenji Hiranabe proposes using Kanban Boards to track Agile project status (Time, Task, and Team) to enhance collaboration.
-
Incremental Software Development without Iterations
David Anderson described how his team is using a kanban system for their sustaining engineering (maintenance and bug fixing) activities. Iterations have been dropped although software is still released every two weeks. Work is scheduled, monitored, and run via a "kanban board" and daily stand-up meetings.