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 Apr 20, 2007
VersionOne, the maker of Agile Enterprise, one of the leading agile tools for team organization and project management, has released two significant versions of their platform within the past few months: a free five-user community edition and 7.1 of their Agile Enterprise software.
The latest release adds integration with Subversion and Fitnesse, as well as a new Taskboard view. Taskboards are a common agile approach to project and task management, wherein tasks, often represented as index cards, are moved around on a board, like a whiteboard or corkboard. Agile teams may find this a valuable way of seeing and interacting with the high-level status of their project, from daily standups to task management. Integration with Fitnesse and Subversion makes feature-related FIT test results and subversion changesets visible when using VersionOne, allowing it to act as an integration point for the various tools used in the development process. Full details on these features as well as retrospectives and more are available in the release notes.
The community edition allows smaller teams to explore and use Agile Enterprise at no cost with up to five users, as long as support and automatic upgrades are not required. In order to install and use the community edition, you'll need a Windows 2000/2003 server on which to run IIS and SQL Server.
In addition, VersionOne has commercial hosted (SaaS/subscription) and deployable licensing models which do include support and upgrades. Pricing is relatively clear and well-published.
InfoQ caught up with Paul Culling of VersionOne to discuss these releases in detail. On the subject of the VersionOne API, and how it's used:Customers use the API for integration with tools from IBM (Eclipse/Clearquest) and HP (Test Director) and we have created the implementations with Visual Studio and open source tools FitNesse and Subversion both for our customers that use these tools and as reference implementations for guiding customers that do custom integrations.
We have also created a new open source customer request submission tool that works with the API. Although VersionOne has the most comprehensive reporting of any Agile tool in the marketplace, many of our customers are using the API for custom reporting – these are generally large enterprise customers that have specific historical reporting needs (generally non-Agile metrics/reports). We have a customer that pulls data out to do very specific earned value reporting. Another customer has integrated VersionOne with their time-billing system.
On the subject of features that differentiate VersionOne:
For more information, follow InfoQ's coverage of VersionOne, or artifacts and tools. Read more about this and other agile tools (ScrumWorks, XPlanner, Rally, etc.) in the Agile Tooling Survey results.
Agile Development: A Manager's Roadmap for Success
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!
The problem with VersionOne is that i need .NET framework etc on my machine, which i dont want. Wish it could run on JRE.
Likewise.
Isn't this just the opposite?
There's certainly some Agile proponents who argue against high-tech toolsets. I've got mixed emotions about them myself, having worked with and without. Valuing one over the other doesn't mean that, for instance, processes and tools don't have merit, just that the emphasis is on individuals and interactions.
Usually even those people who don't choose these tools for their own projects will accept that larger, possibly distributed teams, may need this sort of thing (even if some Agile methods may not be ideally suited to those kinds of teams).
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