Where Kanban Works Well - David Anderson Interview Part II
Where Kanban Works Well - David Anderson Interview Part II
Join the DZone community and get the full member experience.Join For Free
Discover how you can take agile development to the next level with low-code.
Kanban techniques have been successful in many different industries, especially ones that don't seem to fit with agile methodologies. IT application maintenance, media, games, and investment banking are just a few domains where Kanban has proven to be extremely effective. DZone recently got the chance to speak with David Anderson, who pioneered the use of Lean methodology in software development, now known as Kanban. Anderson explained why Kanban was especially helpful in certain industries. He also explained why Kanban can be helpful in just about any context.
The most commonly cited instance where Kanban is extremely successful is software maintenance. Anderson says this involves fixing production bogs and doing small incremental improvements. Kanban works well with software maintenance because such work isn't a natural fit for projects and one to four week sprints. Anderson says, "It makes more sense just to take the requests, work on them, and when they're ready, find some way of deploying them to production." Media companies are another space where Kanban works well, Anderson said. Since media schedules often don't run in one to four week cycles, Kanban is a good fit. Anderson adds, "Media companies often have a much wider range of demand and they need to be responsive and make small changes that happen in one or two days, and if they can deploy faster, often they can generate more revenue from advertising." There's a real business benefit in the media industry when reporters work on stories immediately and deploy them as quickly as possible instead of waiting until the end of an iteration. Anything that's calendar driven, where the dates on the calendar do not fit neatly into iteration boundaries, tends to be a domain where Kanban is catching on.
Another large industry where Kanban is extremely beneficial is game development. Game developers like Kanban for a reason that's different from the media companies. Anderson said, "Some online gaming companies for example, if they deploy something faster they generate more revenue, so it's similar to media in that respect. But the real reason why game companies are adopting it [Kanban] is that the games industry has a huge requirement for specialization, and a lot of the work involved in creating a game is production rather than software development." Production in game development involves the creation of data for graphics, animations, music, sound effects, and levels within the game. "The industry has a lot of specialists and a lot of hand-offs in the work flow," said Anderson. "So it doesn't fit neatly with the agile model of cross-functional teams and a generalist workforce. In fact, most of that agile advice just does not resonate with the games industry." Anderson said that while agile adoption in the games industry has struggled, they desperately need greater agility to meet demands from the market.
There is also significant Kanban adoption in investment banking, Anderson says. "Most investment banks are essentially software companies," he said. "All those fancy derivative products that were largely responsible for the bust in the economy (CDOs, CDSs) are basically just software programs, and every product that an investment bank offers is just a new program. That's also true for things like commodities trading. These programs tend to run on some underlying commodity trading platform, but for each incremental product it's just a small upgade, for example, if you added gold in London to oil in London." It's a small additional program that runs on top of the existing platform, he said. "Those types of features are very similar to software maintenance. Each one has an immediate business benefit. It doesn't make sense to batch them up into large projects. It doesn't make sense to build up 16 different commodity offerings and then launch them all at the same time," said Anderson. There's a major benefit to writing these pieces of software individually and deploying them as soon as they're ready. Once they're deployed, the bank has another investment product to market, and it can trade with that product immediately and start making money.
DZone asked Anderson if there were any areas where Kanban wasn't well-suited for adoption, or if there were any industries that would be negatively affected by Kanban. To directly answer the question, Anderson said, "I believe there will be areas where Kanban doesn't produce any significant improvement above and beyond what you would see with any established agile method. There are domains where an agile method will be perfectly good enough. My gut feeling is that in five years, when we look back at this decade, we'll find that there's a small number of domains and circumstances where agile proves to be good enough and Kanban doesn't make it any better." Anderson says that he has evidence for this theory from companies like Industrial Logic, a world famous eXtreme Programming shop that uses Kanban to enhance the XP approach. They use the XP practices, he says, but they've gotten rid of iterations and they use a Kanban approach for their project and release management. Case studies like these lead Anderson to believe that there are few circumstances where Kanban wouldn't make an agile process better. At the very least, he says, it would have a neutral effect and not a negative one.
"There are plenty of talking heads out there who like to sound intelligent an knowledgeable, and some of those people will say, 'Kanban's great for software maintenance, but you wouldn't use it on big projects,'" said Anderson. "Well, there are plenty of people using it on big projects and seeing significant benefits out of that. Other people will say, 'Well, some people are using it on big projects, but you couldn't possibly use it for program management.' Again, that's proving not to be true." Anderson says there is a small number of people applying Kanban techniques to an over-arching, multi-project level. Portfolio management of IT projects at the Motley Fool, an investment newspaper, was the earliest example, he said. Anderson also said that he'd talked to a program manager from a large telecom equipment manufacturer in Scandinavia recently who wanted to use Kanban at the program management level to integrate three projects together. Both of those organizations were already using Scrum. The Kanban community has plenty of experience and evidence showing that Kanban can be used in many different spaces along side agile methods.
Although Kanban has critics, Anderson says most of them have never used its techniques before. He says these types of critics show up in the kanbandev yahoo group periodically and get hushed up by the members who don't tolerate opinions without experience. Anderson admits there's still unexplored territory for Kanban, but he hasn't found an area yet where Kanban has had a negative effect. That's because Kanban can be adapted to a wide range of scales and situations. There's even a growing movement for personal Kanban, Anderson says, which is subtly different than Kanban for teams. "What we'll see also, is that program management Kanban will be subtly different from team Kanban, but many of the principles will be the same. It's just that the solution that evolves out of applying the principles to a particular problem space will create differences."
David Anderson is the Vice President at Lean Software & Systems Consortium and he also runs his own consulting firm, David J. Anderson & Associates. The first part of DZone's interview with Anderson is titled "How Kanban Got Hot - David Anderson Interview Part I". Much of the research and case studies for Kanban come from the community, which has forums at the Limited WIP Society website and the kanbandev Yahoo group.
Opinions expressed by DZone contributors are their own.