Besides working on Fez, I've been putting together a kind of hybrid ticketing / CRM system that is taylored to Liaison Librarians. The project is called Liaison Profile because "Liaison Database" sounded too boring and my suggestiong of "Liaison Tracker" was thought to have Big Brother connotations.

There are no plans to release Liaison Profile as an open source project but it's not out of the question if there is interest in it.

The project has been running for a long time which is probably due to me trying to be 'agile' and using the prototype software as the spec. What this meant is that everytime I've showed it to the focus group, they have thought of lots of things they'd like it to do differently and we've never settled on when the project will be officially 'finished'. So I've had to resort to the old-fashioned and boring technique of writing a requirements specification and seeking agreement on that.

My approach to requirement specs is to try and be workflow oriented so that I'm describing what the users will be trying to do rather than what the software does. In my opinion, this makes the spec easier to read and understand and possibly allows you to identify what the important things are.