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 Abel Avram on Jun 18, 2008
The Fixture Gallery is an open cookbook for FIT/Fitnesse fixtures and version 2.0 has been recently released by Gojko Adzic. This version of the gallery adds Python code samples for those who program for the web in Python. FIT/Fitnesse is an acceptance test framework with a Wiki front end useful for both customers and developers to create and run acceptance tests.
Version 1.0 of the gallery offered examples of source code in Java and C#, but version 2.0 brings something new according to Gojko:
The most important change in version 2.0 is that it is now expanded to cover Python examples as well, for all fixtures and concepts explained in the document. FitLibrary fixtures section now has examples for ConstraintFixture, CombinationFixture, CalculateFixture and notes about SetFixture and SubSetFixture.
Gojko invites everyone interested to contribute to the gallery:
My intention with the Fixture Gallery is to start an open documentation project where other people can contribute their notes and ideas about how best to use FIT/FitNesse fixtures. The source code for the document and all examples is hosted on SourceForge. Please help to make this document better either by directly changing it on SourceForge or by modifying the live wiki version on FitNesse.info.
FIT, or Framework for Integrated Test, is a framework used for writing and executing acceptance tests originally developed for Java by Ward Cunningham. FIT is a collaboration tool allowing everybody interested in a project to run tests which verify if the code meets the product requirements. The difference from other types of tests is that the requirements are contained in HTML tables and documents and not Java or C# code. Fitnesse is a Wiki front-end to FIT allowing users to collaborate and communicate while building together an understanding of the domain and creating acceptance tests based on user stories.
A FIT test is a called a fixture. The fixture makes the translation between the acceptance test expressed through an HTML table or Wiki page and the actual code of the application, testing the code and showing the results. The Fixture Gallery is a set of fixtures coming in three possible forms: a print-ready PDF, an executable FitNesse Wiki, or a live web site. Gojko says about the gallery:
For each fixture type, this document explains the table format and fixture class structure and provides advice when to use and when not to use it. Each example is accompanied by the source code for Java, .NET and Python FIT implementations, in a form that can be easily copied and used as a template for similar fixtures.
Other important FIT/Fitnesse resources are: the FIT web site, the Fitnesse web site, and Ward Cunningham and Rick Mudgridge's book on FIT. This presentation by David Hussman adds valuable insight in the topic.
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
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
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