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 Vikas Hazrati on Jan 19, 2010
A lot of times teams and organizations would like to evaluate their way of working with their competition. They would like to focus on their areas of improvement and incorporate feedback to do better. Comparative Agility assessment is an assessment tool which suggests that the results would help guide the organizations in planning the next set of Agile initiatives.
Mike Cohn mentioned that initially he thought that it is not worthwhile to compare to competition. One should keep improving everyday towards perfection. However, now he thinks in a different direction. According to Mike,
It took me awhile, but I eventually realized the flaws in my thinking. A business does not need to be perfect; it needs only to be better than (and stay ahead of) its competition. Google is the dominant search engine today not because the results it shows are perfect but because its results are usually better than those shown by its competition.
Thus, being more agile than one’s competitors is indicative of the organization’s ability to deliver better products. This led Kenny Rubin, Laurie Williams and Mike Cohn to create the Comparative Agility assessment (CA). When a survey is taken, the survey responses are compared against the entire database and an organization can compare against similar organizations. For example, a team can compare against all teams doing web development, all companies that are about six months into their agile adoption efforts etc.
CA approach assesses agility on seven dimensions:
Currently, there is a database of 1123 surveys and you can register to take the survey. The survey is meant to be completed by an experienced ScrumMaster, coach, or consultant on behalf of a team or company based on interviews or observation.
Reacting to the tool Pasi Kantelinen suggested that instead of comparing Agility with the competition, one should answer the question, “How good results do we achieve?”. He added that the question could be extended to
"How good results do we achieve
- compared to what we achieved earlier? or
- compared to competitors? or
- compared to the best of the bread? or
- compared to excellent results?"
On similar lines, Julie agreed that just comparing Agility would not server the purpose as there are many teams who are using Agile practices but not going any faster in terms of speed or productivity.
Thus, though the end goal is delivering business value, however if you would like to know where your competition is then it might be a good idea to do the comparison.
Transforming Software Delivery: An IBM Rational Case Study
Agile Maturity Model Applied to Building and Releasing Software
Case Study: IBM's Agile Transformation
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!
It's important to compare with your competitors in order to know where your position is. This comparison should also make you understand which are the results you have to archive and where your company should be improved. Also a manager can compare the stuff within a company.
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