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 Geoffrey Wiseman on May 23, 2007
In response to his "disquiet in the state of Agile", Brian Marick proposed a refocusing of the Agile Alliance. After Rachel Davies stepped down from being the chair of the Agile Alliance, Marick ran on the platform of following through on his proposal, and was elected.
He'll be working on "some derivative" of this proposal at the Agile Software Development Forum to prepare for a vote of the membership.
Briefly, the original proposal suggested a refocus with a two year span:
Focusing on helping the agile team succeed, rather than the organization/business as a whole:
'Members of the Agile team' is defined to be everyone who'd be expected to attend a team standup meeting: programmers, testers, user experience designers, Scrum product owners or XP Customers, technical writers, and so on.
Contribution to the agile community as a prerequisite for membership.
Funding small conferences dedicating to advancing the practice:
We hope to fund at least five conferences a year, in at least three continents. The Agile Alliance will choose conferences to fund based on bids by groups of volunteers.
Aiding members when they are unable to reconcile the interests of the members with the interests of individuals within their organization:
While the Agile Alliance is not a union, it will intervene on behalf of members, whether by providing a supportive outside voice, aiding exiting employees in job searches, removal of a company from a list of known-good employers, other methods we haven't thought of yet, or any combination of the above.
Spending down the Agile Alliance surplus over two years by soliciting requests from Agile user groups.
There will be a careful evaluation of whether the Agile Alliance has, in fact, improved the success rate of Agile teams over what it would otherwise have been. The evaluation will include people in the role of Devil's Advocate. Unless the evaluation concludes that the Alliance is making a substantial difference in the world, the Alliance will disband, distributing any remaining monies to user groups.
Brian Marick is looking for help to "stir things up". Join in the conversation, add your voice, and follow along at InfoQ.
Transforming Software Delivery: An IBM Rational Case Study
Agility at scale, become as agile as you can be
A practical guide to choosing the right agile tools
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