Jesper Boeg on Priming Kanban
In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Floyd Marinescu on Oct 18, 2007
InfoQ's mission is to be the world's source for tracking change and innovation in the enterprise software development community. To maximize the positive impact of all the content we are putting out, InfoQ has been extending its service to communities where English is a barrier to learning. In April InfoQ China launched, and this October InfoQ Japan has launched and is operating at http://infoq.com/jp. InfoQ Japan is translating InfoQ's daily news & weekly technical articles and will be publishing original Japanese news & video interviews/presentations, building and connecting local community in Japan like InfoQ does for the rest of the world. Since it's launch, InfoQ Japan is already attracting an average of 3500 visits a day.
InfoQ Japan is launched in partnership with, and operated by, Component Square Inc (CSQ), a Japanese consortium aimed at improving software development & software component reuse in Japan. CSQ CEO Nagao-san commented on the motivations behind InfoQ Japan:
Currently in Japan, in order to obtain the latest information about IT, accessing overseas websites directly or gaining information which is published by Japanese media are the only options. However, few engineers can read overseas websites due to the language barrier; the rest have no option but to gain from Japanese media which is often very late and also filtered. Thus we have decided to launch InfoQ Japan because we see the tremendous significance and potential in offering authors’ unfiltered opinions to engineers in Japan in a timely manner, with no language barrier.Commenting on the need for greater skills & innovation in Japan, Nagao-San mentioned:
Although information may be published without distortion by Japanese media, we can not deny that sometimes information is biased by press’ interests. We believe that it is essential for engineers to be exposed to the information directly and make their own judgments.
Today in Japan the shortage of mid-level engineers is becoming an important issue. Also, the growing shortage of technical architects, mid-level engineers, and project managers is becoming more serious. We believe that InfoQ will play a significant role in resolving these issues. It will not only provide information to Japanese engineers but also offer the potential for engineers to experience ongoing technical revolution in real time, potentially triggering more innovation of their own.
In addition to empowering Japanese IT, Nagao-san also commented on the potential to bring more Japanese innovation to the rest of the world:
As innovation has been triggered with Ruby’s (developed in Japan) encounter with a framework called Ruby on Rails, there is a lot of hidden underlying potential and innovation in Japan that is not yet recognized globally. For instance, Seaser, the opensource DI container, and openthlogy which is hosted by the Requirement development alliance, could be valuable internationally.InfoQ Japan feature set is technically equivalent to InfoQ.com; it has its own personalized RSS feed system (grabbing the feed from InfoQ.com/jp automatically only has news from InfoQ.com/jp), and also its own thread commenting system - the same news posts in each language has independent discussion threads and are not mixed. From an English news post, the Chinese or Japanese translations (if translated) have urls that differ only slightly, such as:
In the meantime, we hope to introduce such innovation emerging in Japan internationally. We find the IT scene in Japan pretty interesting. For example, Kenji Hiranabe’s work on “visualization” has been introduced already on InfoQ: http://www.infoq.com/articles/agile-kanban-boards
As significant innovation occurs with all this coming together, we wish that the InfoQ community will develop and bring about greater innovation globally, and we feel fortunate to be able to contribute.
China: infoq.com/cn
Japan: infoq.com/jp
Congratulations.
infoq.com/in in the national language of Hindi probably won't work for the Indian audience. This is because all(!) of the software professionals currently in India can read English - in fact, they prefer to read English.
www.bbc.co.uk/hindi is an exception because it is the generic news.
Good job.
This is nice. Any chance that InfoQ will publish a case study of how InfoQ manages its site accross countries? If the architecture of InfoQ site itself could the included as well that'd be great. :-)
Congratulations Floyd, Alex and rest of the team.
Cheers.
Hello, Floyd,
I'm very glad you finally started up InfoQ Japan, and chose Nagao-san as a partner.
I had worked on an article with Deb, about "Kanban"(introduced in your quote above), and am working on more articles about "Ideas Agile can learn from Lean and Toyota Production System" Series(I just named it :-)
In the last Agile2007, I led a workshop with Mary Poppendieck "Learning Kaizen from Toyota", and there we collected a lot of ideas together with the attendees.
jude-users.com/en/modules/weblog/details.php?bl...
Another original from Japan was "Ruby x Agile" series which Sam introduced in the infoQ.
www.infoq.com/news/2007/08/ruby-x-agile-2
It is about the video in which Matz, Kakutani, and I am talking about Ruby and Agile.
Let's keep in touch.
I believe there was a talk at QCon that covered the behind the scenes of InfoQ. It would be nice if it appeared in the videos/articles section at some stage.
In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
4 comments
Watch Thread Reply