Rachel Davies' and Mike Hill Workshop on Informative Workspaces
- Team memory
- Visible status (keep it fresh)
- Automation - light and sound
- Hawthorne effect
- Track "puzzles"
- Root cause analysis
- Positive focus
Themes: Ownership: Own the space; collective ownership of communication, accountability.
More from the Agile 05 conference...
Delivering APIs in an Agile Context, John Major
John Major described a project that was doing custom programming of lab workflows as part of the Human Genome Project. This was an environment with lots of churn: biology, instruments, J2EE.
- Stable APIs vs. agile change
- General features vs.
The "North American Simulation and Games Association" (NASAGA) is having their annual conference October 5-8 in Manchester, NH, USA.
This group is mostly made up of people who use simulations and games as instructional tools. This is one of my favorite conferences.
The Agile '05 conference was July 24-29, 2005, in Denver, Colorado, USA. There were about ten or twelve tracks at all times, so this report is necessarily only a limited bit.
Fit for Developing Software, by Rick Mugridge and Ward Cunningham.
[My bias disclosure - I know both Rick & Ward, I was a reviewer, and
I've written for their publisher myself. This review is substantially as posted on the agile-testing group.]
Fit (see http://fit.c2.com) is a testing framework that Ward Cunningham developed.
A RowFixture is used to test that a set of items is as expected. The fixture flags surplus or missing items.
ColumnFixture is an easy fixture to understand from the user's point of view: each row is a test case, with some columns being inputs, and others being outputs:
Martin Fowler posted a good article on the idea of Language Workbenches, followed up by some nice links and more reading:
National Games Week is Nov. 20-26, 2005. See www.NationalGamesWeek.net.
Yes, it's an event focused on non-electronic games, but those still have a lot to teach us about interaction and play.
JUnit 4 is out for JDK 1.5. Gunjan Doshi summarizes the changes here.
It uses the JDK 1.5 "attribute" feature, so you label tests with "@Test" rather than following the convention of naming them "testSomething()".