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 Mark Levison on Mar 18, 2010

The Agile Skills Project is a wiki providing an inventory of skills that a good Agile Developer should have. The project was started after a meeting in Chicago in the spring of 2009, attendees of that meeting agreeing that: “High productivity in Agile software development requires excellence in these areas: Product, Collaboration, Business Value, Supportive Culture, Confidence, Technical Excellence, and Self Improvement.”
In the first post to the mailing list, Ron Jeffries said:
We're here to begin to come up with an approach to improving developer skills for Agile / Scrum / XP projects. The Scrum Alliance is thinking of there being a new developer-focused certification (CSD?). I think we all have a basic agreement that whatever we do should "have teeth", and that developers and hiring managers alike should come to respect the rating or ratings that might come about.
From those initial ideas the project has grown to encompass the following goals:
- Establish an evolving picture of the skills needed on Agile teams
- Encourage life-long continuous learning
- Establish a network of trust to help members find like-minded folks, and to identify new mentors in the community
In support of those goals the group has created:
The skills inventory currently includes sections for: Business Value, Collaboration, Confidence, Product, Self Improvement, Supportive Culture and Technical Excellence.
It even has a list of things to look for in an Agile organization:
The Agile Skills project is looking for people to ask questions, participate in the discussion and describe skills.
Previously on InfoQ: “The 'Agile Developer Skills Workshop' Is Underway” and “Looking Inward To Stop An Agile "Decline And Fall"”
18 agile and lean practices for effective software development governance
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!
This tentative clearly fall on the fallacy of "Others have failed, but we're not like them, we are better!"
And it's a bold goal, change/certify a mindset of continuos learning?
This tentative clearly fall on the fallacy of "Others have failed, but we're not like them, we are better!"
Not quite sure I understand: "This tentative clearly fall on the fallacy" - but I will attempt to respond. The group doesn't make any claim that it will create great certifications. It does claim that it can do a good job of documenting many of the skills required to be a great Agile Developer. Is it starting to meet that claim? You be the judge.And it's a bold goal, change/certify a mindset of continuous learning?
Agreed a bold goal but even if it fails it will still have pushed the boundaries of understanding a bit further back.
Cheers
Mark Levison
Agile Pain Relief Consulting
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.
2 comments
Watch Thread Reply