Crystal Clear: A Human-Powered Methodology for Small Teams

Crystal Clear: A Human-Powered Methodology for Small Teams

4.03 of 5 stars 4.03  ·  rating details  ·  39 ratings  ·  7 reviews
Author Alistair Cockburn distills the secrets shared by successful small teams on what works and doesn't work in their development processes. The result is Crystal Clear, a new Agile LL2 methodology designed to help teams with two to eight members develop and release more functional software, faster.
Paperback, 312 pages
Published October 19th 2004 by Addison-Wesley Professional
more details... edit details

Friend Reviews

To see what your friends thought of this book, please sign up.

Community Reviews

(showing 1-30 of 107)
filter  |  sort: default (?)  |  rating details
John
Some aspects of this book were totally awesome. I love the basic methodology, the focus on communications, personal safety, reflection workshops, importance of keeping methods lightweight, etc. Unfortunately, the book suffers from a bit too much of trying to be something for everybody. Huge swaths of material were skimmable at best for me. For instance, examples of requirements documents and design diagrams. I've seen thousands of such examples and seeing new ones in this context provides nothin...more
Sami Poimala
This is a book about the idea, that there should not be a methodology for a company - but a methodology for a project!
Depending on the project size and criticality, you should tailor the process that suits exactly that project. Of course, this isn't true on small projects but any project involving more than 10 developers and taking more than - say - 6 months to build, deserves a fit-for-the purpose methodology.

This book will give you ideas for that. Actually 'Clear' in the name means that the pr...more
Russ
My first Agile book, this was a good introduction to the Agile concepts. It drags a little (as technical books do) but the illustrations of the value of Agile are clear and understandable.
André Gomes
Lot's of good ideas, simple and fast to read, goes directly to the point.

7 Properties:
1. Frequenty Delivery
2. Reflective Improvement
3. Osmotic Communication
4. Personal Safety
5. Focus
6. Easy Access to Expert Users
7. Technical environment with automated tests, configuration management, and frequent integration.
Coby Randquist
Read Chapter 9 - if nothing else.
Tony
Sep 10, 2007 Tony rated it 4 of 5 stars Recommends it for: software developers
decent methodology, but it always comes down to theory vs. practice, doesn't it!?
Otis Chandler
Jun 05, 2009 Otis Chandler marked it as to-read
If selly says so...
hailbringer
May 10, 2013 hailbringer marked it as to-read
John Kavadias
Apr 24, 2013 John Kavadias marked it as to-read
Robert Postill
Apr 23, 2013 Robert Postill marked it as to-read
Shelves: agile, wishlist
Tejas
Apr 11, 2013 Tejas marked it as to-read
Shelves: software
David
Feb 21, 2013 David marked it as to-read
Chris
Feb 07, 2013 Chris marked it as to-read
Krzysztof
Jan 29, 2013 Krzysztof marked it as to-read
Robert
Dec 04, 2012 Robert added it
Marek Tihkan
Nov 01, 2012 Marek Tihkan added it
Shelves: grabcad
Brendan Powell
Oct 19, 2012 Brendan Powell marked it as to-read
Shelves: to-read-for-work
Andy Brandt
Oct 08, 2012 Andy Brandt marked it as to-read
« previous 1 3 4 next »
There are no discussion topics on this book yet. Be the first to start one »

Goodreads is hiring!

If you like books and love to build cool products, we may be looking for you.
Learn more »
Writing Effective Use Cases Agile Software Development Surviving Object-Oriented Projects Use Cases Effektiv Erstellen Agile Software Entwicklung

Share This Book

Your website