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 Aug 29, 2007
Danube technologies has delivered the Summer '07 release of ScrumWorks Pro, which includes Bugzilla and Jira integration, burndown charts with theme filtering and more options for projecting and trending, as well as a few more things.
ScrumWorks Pro can integrate with both Bugzilla and JIRA by importing items from either into ScrumWorks Pro as backlog items, where they can be manipulated like any other backlog item. These can be imported individually or in bulk, using searches to select the items of interest. InfoQ spoke with JD Aspinall of Danube Technologies about the nature of this feature, and how to use Bugzilla and/or Jira alongside ScrumWorks Pro:
I think the users that requested this feature were hoping to use the two tools alongside one another.
Many of our users track all their bugs as Product Backlog Items in ScrumWorks Pro. There are many others that for various reasons have chosen to utilize a different tool to track issues and only chose to import certain defects.
Burndown charts may now be grouped by theme; having organized your backlog in themes, ("akin to web 2.0 tags"), you may highlight or filter your backlog using themes and now filter the burndown using these same themes.
Users can also conduct some what-if analysis by altering the way the burndown chart trend lines are projected using one of:
Small, co-located teams seem best-suited to agile development, and these teams often prefer physical tools like whiteboards and index cards. However, with the increasing visibility of agile methods in the enterprise, many people are seeking to find ways to apply these methods in larger and distributed teams for whom the physical tools are less effective, and turning to agile project management software.
ScrumWorks was the third-most popular Agile project management tool in the Agile Tooling Survey 2006 used by ~10% of respondents, although the survey does not seem to distinguish between the Pro and Basic versions.
ScrumWorks Pro is available to existing license-holders at no cost. Licenses are priced at $249/user/year; floating and shared-user licenses are not available, although volume discounts and multi-year subscriptions are available. The server is supported on Windows XP/Vista/2003 Server, Mac OS X 10.4.2+ and Linux, the desktop client on Windows XP/Vista/2003 Server, Mac OS X 10.4.2+, and Linux KDE windows manager and the web client on Internet Explorer 6+, Mozilla/Firefox 1.5+, and Safari 2.0+.
There are few reviews of ScrumWorks Pro, so if you've had the opportunity to use ScrumWorks Pro on a software project, please add your voice. For more information on ScrumWorks, visit Danube Technologies' website and watch the introduction to the free ScrumWorks Basic tool. For more information on agile tools, read on in InfoQ's agile community.
Transforming Software Delivery: An IBM Rational Case Study
Agile Development: A Manager's Roadmap for Success
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!
Rather than risk confusing readers with a niche development phrase, I've changed "opportunity to use ScrumWorks Pro 'in anger'" to "opportunity to use ScrumWorks Pro on a sofware project".
Geoffrey, out of curiousity, what's the history of the "in anger" idiom?
As far as I know, it traces back to the 'Ant in Anger' article (although if someone has a more complete etymology, I'd be happy to hear it). It has come to mean "in a real setting" (e.g. production environments, serious for-pay projects) rather than something you've played with on your own time, or done a proof-of-concept in.
I don't think it's used outside of development circles, and I expect there are lots of developers who aren't familiar with the phrase, so I think the revised form is a lot more clear. I hope it didn't confuse anyone.
No, I'm pretty sure the phrase "in anger" meaning "for real" has been around for many years. I can't find an etymology, even in the Oxford English Dictionary, but I suspect it comes from the military, where a weapon used "in anger" has been used "for real".
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.
4 comments
Watch Thread Reply