InfoQ Homepage Kanban Content on InfoQ
-
US Scrum Gathering 2010 Kicks Off With a Day of "Deep Dives"
The 2010 US Scrum Gathering kicked off Monday in Orlando with a buzzworthy day of "deep dive" learning, collaboration, and healthy debate.
-
You Can Say No to 'Pull' in Kanban
Kanban places a lot of emphasis on the pull psychology. Most people who subscribe to lean ideas prefer pull systems as opposed to traditional push systems as they are deemed to be superior for performance and productivity. However, there might be situations where you would want to say No to a pull.
-
Minibook: Scrum and Kanban: Making the Most of Both
Scrum and Kanban are two flavours of Agile software development - two deceptively simple but surprisingly powerful approaches to software development. So how do they relate to each other? The new InfoQ minibook by Henrik Kniberg and Mattias Skarin, Kanban and Scrum - making the most of both, clears up the fog so you can figure out how Kanban and Scrum might be useful in your environment.
-
ScrumBan - Evolution or Oxymoron?
Kanban workshops, courses and conferences are springing up, and practicing Agilists are investigating what this method, adapted from Lean, offers their teams. Attractive benefits are cited, from revealing bottlenecks to happy teams experiencing more "flow". But thought leaders warn that Kanban's laid back approach is "kryptonite" to Scrum's call to resolve impediments immediately.
-
Wrong and Right Reasons to Apply Kanban
Kanban's aim is to minimize WIP (Work-In-Process), or inventory, between processes by making sure that the upstream process produces parts only if its downstream process needs it. Of late, Lean and Kanban are growing in popularity. More and more companies are setting up Kanban Boards, limiting WIP and eliminating Muda. Michael Dubakov investigated the wrong and right reasons for applying Kanban.
-
Observations on Lean in Action in Japan
What did a group of Agilists see when they "went to the gemba" in Japan to observe Lean in action? Here is a roundup of observations from bloggers and newsgroup writers on this spring's "Roots of Lean" tour to Japan, led by Mary and Tom Poppendieck. The tour visited both manufacturing and software organizations, and included Henrik Kniberg, Sune Gynthersen, & Gabrielle Benefield, among others.
-
James Shore With More On Keeping It (Agile) Real
In a casual interview, InfoQ got to talk with James Shore about some of the topics he's been most vocal about lately, including his Art Of Agile book, recent waves of watered-down agile, and how Kanban might be less than the whole picture.
-
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.