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 Apr 17, 2009
In the world of agile software development there is little agreement on which practices are "really" agile, and which ones are not. Likewise, people don't agree on which agile practices are most important, and nobody knows which practices are actually applied in how many projects.
In an attempt to gain insight into the current state of the community, Jurgen Appelo is running a survey that could give us answers to these questions if a sufficient number of people participate.
Even though a number of other surveys have already been published before, most notably those of VersionOne and Scott Ambler, Jurgen's survey is the first that does not focus on coarse-grained methods (like Scrum or XP), but on 66 fine-grained individual agile practices. The results are going to be interesting if enough of the community participate.
18 agile and lean practices for effective software development governance
Case Study: IBM's Agile Transformation
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
The idea to isolate the practice and ask people whether certain practice is "Agile" or not is simply absurd.
Take an example, asking whether "Product Vision / Vision Statement" is an Agile practice or not makes no sense at all.
One can have product vision regardless of what methodology he/she uses. It has nothing to do with Agile or not, while having "Product vision" (or any other SINGLE practice) won't guarantee agility (even employing all practices without sharing Agile values won't).
I doubted what "Agile" means here, and what "Agile" means to the owner of the survey.
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.
1 comment
Watch Thread Reply