Crystal clear destilled

Cockburn the man of the use cases and the crystal methodology, in his wiki says...

(Extract from Crystal Clear: A Human-Powered Methodology for Small Teams) Alistair Cockburn, 2004

At the end, it is time to roll it all back up again: What is the core of Crystal Clear, and what are the add-on practices that get the team farther into the safety zone? This chapter is very short.

Crystal Clear is a highly optimized way to use a small, colocated team, prioritizing for safety in delivering a satisfactory outcome, efficiency in development, and habitability of the working conventions. The brief description of Crystal Clear for level-3 practitioners is just this:

The lead designer and two to seven other developers ... in a large room or adjacent rooms, ... using information radiators such as whiteboards and flip charts, ... having easy access to expert users, ... distractions kept away, deliver running, tested, usable code to the users ... every month or two (quarterly at worst), ... reflecting and adjusting their working conventions periodically.

The people set in place the safety properties below using the techniques they feel appropriate. The first three properties are required in Crystal Clear; the next four get the team further into the safety zone.

1. Frequent Delivery
2. Reflective Improvement
3. Osmotic Communication
4. Personal Safety
5. Focus
6. Easy Access to Expert Users
7. A Technical Environment with Automated Tests, Configuration Management, and Frequent Integration

All the other pages in this book only expand on this page.

More info about crystal clear ?

Software metrics references

I'm looking for documentation about use cases points measurement and found that:

Wikipedia
A short definition an explanation...
Not a wikipeida like stuff :P

PDF Document
From the instituto tecnologico de buenos aires, talk about cocomo 2, function points and use cases points...
Is hard to read.

Also at our google group: Estimacion y Riesgos.pdf

The Yarbam Structure

The YARBAM project (Yet Another Rock Band Manager) is organized in 3 layers.

First we have a google project svn hosting where resides the source code, the wiki with the official documentation of the stable release and the issue tracking system.

Next layer is the yarbam developers google group, where developers discuss about new functionalities, changes in the project trunk and branches. Here goes the last news about the project state.

Finally the bottom layer is this blog, where gonna be documentation about new functionalities at the development version, tutorials, examples adn code, code and code.

So you want to visit the blog when need code examples and quick guides. You want to view the project home when need to get the source code, look at the issues and read the official documentation. Finally you want to ask the developers mail-list to give new ideas and discuss with developers.

A fourth layer may appear in the future as a yarbam users mail-list, where you as a user may ask the community for help and more.