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 Amr Elssamadisy on May 13, 2008
Kim Gräsman asked a simple but thought-provoking question to the extremeprogramming Yahoo! group:
Hello all,
It seems incremental design has become a theme (if implicit) on the
list these past weeks -- does anyone have good references to reading
on incremental design?
Good question. There were some good recommendations made. Here are some of them:
The question then morphed into a discussion about adopting incremental design:
I'm just thinking about this in the abstract, I don't have an actual
question really, but it seems to me getting a team started with
incremental design can be difficult, and I've talked to people who
have tried without much success. So I think I'm trying to better
understand the practice before misguidedly attempting to use it.
To answer the question about how to adopt incremental design well, the age-old question of what IS good design reared it's head. This, of course, resulted in advice that was all over the map. One interesting point of view was presented by Ron Jeffries:
I believe that by most people's lights, a "good design"
automatically turns out to be evolvable. IOW, faced with a design
that is thought to be good, but not evolvable, we can quickly come
up with a design which is similar in essence, "better", and
evolvable. The making it "better" will make it more evolvable
without working directly toward that property.
But, one notable gap in the discussion was that the "how do I adopt incremental design?" was never directly addressed even though that seemed to be the main topic for a large part of the discussion. The group came at the issue from different angles but never directly. Is it difficult for us to discuss adoption? Or is it so obvious that we don't need to address it directly?
Case Study: IBM's Agile Transformation
Agility at scale, become as agile as you can be
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
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.
No comments
Watch Thread Reply