Crystal Clear: A Human-Powered Methodology for Small Teams: A Human-Powered Methodology for Small Teams
©2005 |Addison-Wesley Professional | Available
©2005 |Addison-Wesley Professional | Available
This book introduces Crystal Clear, a better lightweight methodology for
building software. It describes the roles, teams, values, intentions, habits,
activities, policies and work products of a small software development team for
whom time-to-market and development costs are critical considerations.
Alistair Cockburn is one of the founders of the Agile software development
movement. He spells out proven best practices based on his extensive
experience helping organizations build software quickly and with less cost. The
author understands that small teams cannot be burdened by "process-heavy"
software methodologies. By advocating that developers stay close together and
remain in steady, good-will communication with customers and users, this
book teaches the reader how to develop software that not only does what it is
supposed to do, but also gets completed on time and within budget.
This product is part of the following series. Click on a series title to see the full list of products in the series.
Sample chapter is available for download in PDF format.
This material is protected under all copyright laws, as they currently exist. No portion of this material may be reproduced, in any form or by any means, without permission in writing from the publisher.
Introducing Crystal Clear, a new agile method proven to increase worker productivity while helping organizations deliver better software.
° More nuggets of wisdom from software engineering guru and best-selling author Alistair Cockburn
° Helps organizations eliminate the bureaucracy from software development by increasing emphasis on programmer input and job satisfaction
° Product launch at OOPSLA 2004 conference during October in Vancouver, BC
1. Explained (View from the Outside).
2. Applied (The Seven Properties).
Property 1. Frequent Delivery.
Property 2. Reflective Improvement.
Property 3. Osmotic Communication.
Property 4. Personal Safety.
Property 5. Focus.
Property 6. Easy Access to Expert Users.
Property 7. Technical Environment with Automated Tests, Configuration Management, and Frequent Integration.
Evidence: Collaboration across Organizational Boundaries.
Reflection on the Properties.
3. In Practice (Strategies and Techniques).
Strategy 1. Exploratory 360°.
Strategy 2. Early Victory.
Strategy 3. Walking Skeleton.
Strategy 4. Incremental Rearchitecture.
Strategy 5. Information Radiators.
Technique 1. Methodology Shaping.
Technique 2. Reflection Workshop.
Technique 3. Blitz Planning.
Technique 4. Delphi Estimation Using Expertise Rankings.
Technique 5. Daily Stand-up Meetings.
Technique 6. Essential Interaction Design.
Technique 7. Process Miniature.
Technique 8. Side-by-Side Programming.
Technique 9. Burn Charts.
Reflection about the Strategies and Techniques.
4. Explored (The Process).
The Project Cycle.
The Delivery Cycle.
The Iteration Cycle.
The Integration Cycle.
The Week and the Day.
The Development Episode.
Reflection about the Process.
5. Examined (The Work Products).
The Roles and Their Work Products.
Roles: Sponsor, Expert User, Lead Designer, Designer-Programmer, Business Expert, Coordinator, Tester, Writer.
A Note about the Project Samples.
Sponsor: Mission Statement with Trade-off Priorities.
Team: Team Structure and Conventions.
Team: Reflection Workshop Results.
Coordinator: Project Map, Release Plan, Project Status, Risk List, Iteration Plan and Status, Viewing Schedule.
Coordinator: Project Map.
Coordinator: Release Plan.
Coordinator: Project Status.
Coordinator: Risk List.
Coordinator: Iteration Plan ? Iteration Status.
Coordinator: Viewing Schedule.
Business Expert and Expert User: Actor-Goal List.
Business Expert: Requirements File.
Business Expert and Expert User: Use Cases.
Expert User: User Role Model.
Designer-Programmers: Screen Drafts, System Architecture, Source Code, Common Domain Model, Design Sketches and Notes.
Designer-Programmer: Screen Drafts.
Lead Designer: System Architecture.
Designer-Programmer: Common Domain Model.
Designer-Programmer: Source Code and Delivery Package.
Designer-Programmer: Design Notes.
Tester: Bug Report.
Writer: Help Text, User Manual, and Training Manual.
Reflection about the Work Products.
6. Misunderstood (Common Mistakes).
"We colocated and ran two-week iterations-why did we fail?"
"Two developers are separated by a hallway and a locked door."
"We have this big infrastructure to deliver first."
"Our first delivery is a demo of the data tables."
"No user is available, but we have a test engineer joining us next week."
"One developer refuses to discuss his design or show his code to the rest."
"The users want all of the function delivered to their desks at one time..."
"We have some milestones less than a use case and some bigger."
"We wrote down a basic concept and design of the system. We all sit together, so that should be good enough."
"Who owns the code?"
"Can we let our test engineer write our tests? How do we regression test the GUI?"
"What is the optimal iteration length?"
7. Questioned (Frequently Asked).
Question 1. What is the grounding for Crystal?
Question 2. What is the Crystal family?
Question 3. What kind of methodology description is this?
Question 4. What is the summary sheet for Crystal Clear?
Question 5. Why the different Formats?
Question 6. Where is Crystal Clear in the pantheon of methodologies?
Question 7. What about the CMM(I)?
Question 8. What about UML and architecture?
Question 9. Why aim only for the safety zone? Can't we do better?
Question 10. What about distributed teams?
Question 11. What about larger teams?
Question 12. What about fixed-price and fixed-scope projects?
Question 13. How can I rate how "agile" or how "crystal" we are?
Question 14. How do I get started?
8. Tested (A Case Study).
The Field Report.
The Auditor's Report.
Reflection on the Field and Audit Reports.
9. Distilled (The Short Version).
Pearson offers special pricing when you package your text with other student resources. If you're interested in creating a cost-saving package for your students, contact your Pearson rep.
|Online purchase price||$27.99|
Alistair Cockburn is a renowned software expert and accomplished instructor. He carefully separates advice to experts from advice to newcomers. Newcomers to agile development will find a step-by-step introduction to selected agile techniques previously not described elsewhere. Experts will see new strategies and techniques to try, as well as the contextual information they need for advanced decision-making.
© Copyright Pearson Education. All rights reserved.
We're sorry! We don't recognize your username or password. Please try again.
The work is protected by local and international copyright laws and is provided solely for the use of instructors in teaching their courses and assessing student learning.
You have successfully signed out and will be required to sign back in should you need to download more resources.