About Duffbert...

Duffbert's Random Musings is a blog where I talk about whatever happens to be running through my head at any given moment... I'm Thomas Duff, and you can find out more about me here...

Email Me!

Search This Site!

Custom Search

I'm published!

Co-author of the book IBM Lotus Sametime 8 Essentials: A User's Guide
SametimeBookCoverImage.jpg

Purchase on Amazon

Co-author of the book IBM Sametime 8.5.2 Administration Guide
SametimeAdminBookCoverImage.jpg

Purchase on Amazon

MiscLinks

Visitor Count...



View My Stats

« My first Perl program... | Main| I only *thought* Ian was coming home today... »

Book Review - Crystal Clear : A Human-Powered Methodology for Small Teams

Category Book Reviews


While I like the general concepts behind agile development methodologies, sometimes they seem to be focused on speed with a disregard for any documentation.  Alistair Cockburn has an agile methodology that appears more palatable in today's environments...  
Crystal Clear : A Human-Powered Methodology for Small Teams.

Contents: Explained (View from the Outside); Applied (The Seven Properties); In Practice (Strategies and Techniques); Explored (The Process); Examined (The Work Products); Misunderstood (Common Mistakes); Questioned (Frequently Asked); Tested (A Case Study); Distilled (The Short Version); References; Index


The tendency to want to compare Crystal Clear (CC) to XP is something that can't be ignored.  In fact, Cockburn addresses this in the Questioned section.  He sums it up by saying that XP is stricter in several ways and more loose in a few.  XP wants shorter iterations, CC can be longer. XP calls for pair programming, CC permits it.  XP requires a customer to be an active member of the team, CC wants easy access to one.  XP requires no documentation, CC does.  It's probably that last point that makes CC an easier sell in a business environment.  Some methodologies are documentation-heavy (like RUP) and some are documentation-absent (like XP).  CC strikes a balance between documenting what needs to be known and remembered by the group, without having multiple binders of paper as a "product" to explain every last iota of code.  While XP is the methodology that has all the mindshare these days, I think I feel more comfortable as a developer using something like CC.  


If you're looking to slim down your development methodology or add some structure to a seemingly ad-hoc XP methodology, this book might be what you're looking for...

Comments

Gravatar Image1 - I'm using a lot of Crystal Clear in my projects since it is the closest fit to Domino I found so far. When customers have a stronge urge to change requirements frequently (justified or not) burn charts and Iceberg diagrams are invaluable. Also the shift from slipping release dates to slipping feature lists is a great tool.
I mailed some questions to Alistair and got fast, friendly and competent answers.
A must have on the working desk
stw

Post A Comment

:-D:-o:-p:-x:-(:-):-\:angry::cool::cry::emb::grin::huh::laugh::lips::rolleyes:;-)

Want to support this blog or just say thanks?

When you shop Amazon, start your shopping experience here.

When you do that, all your purchases during that session earn me an affiliate commission via the Amazon Affiliate program. You don't have to buy the book I linked you to (although I wouldn't complain!). Simply use that as your starting point.

Thanks!

Thomas "Duffbert" Duff

Ads of Relevance...