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 ?