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

, by Cockburn, Alistair

Write a Review

Note: Supplemental materials are not guaranteed with Rental or Used book purchases.

ISBN: 9780201699470 | 0201699478
Cover: Paperback
Copyright: 10/19/2004

eBook

Available Instantly

Online: 1825 Days

Downloadable: Lifetime Access

$30.59

Summary

Author Biography

Supplemental Materials

Introducing Crystal Clear, a new agile method proven to increase worker productivity while helping organizations deliver better software.

Preface	p. xiii
Explained (View from the Outside)	p. 1
Applied (The Seven Properties)	p. 17
Frequent Delivery	p. 19
Reflective Improvement	p. 22
Osmotic Communication	p. 24
Personal Safety	p. 29
Focus	p. 32
Easy Access to Expert Users	p. 34
Technical Environment with Automated Tests, Configuration Management, and Frequent Integration	p. 37
Evidence: Collaboration across Organizational Boundaries	p. 42
Reflection on the Properties	p. 43
In Practice (Strategies and Techniques)	p. 45
The Strategies	p. 45
Exploratory 360[degree]	p. 46
Early Victory	p. 48
Walking Skeleton	p. 49
Incremental Rearchitecture	p. 51
Information Radiators	p. 54
The Techniques	p. 59
Methodology Shaping	p. 60
Reflection Workshop	p. 65
Blitz Planning	p. 68
Delphi Estimation Using Expertise Rankings	p. 76
Daily Stand-up Meetings	p. 78
Essential Interaction Design	p. 79
Process Miniature	p. 91
Side-by-Side Programming	p. 92
Burn Charts	p. 94
Reflection about the Strategies and Techniques	p. 108
Explored (The Process)	p. 111
The Project Cycle	p. 117
The Delivery Cycle	p. 123
The Iteration Cycle	p. 126
The Integration Cycle	p. 130
The Week and the Day	p. 131
The Development Episode	p. 132
Reflection about the Process	p. 133
Examined (The Work Products)	p. 135
The Roles and Their Work Products	p. 138
Roles: Sponsor, Expert User, Lead Designer, Designer-Programmer, Business Expert, Coordinator, Tester, Writer	p. 140
A Note about the Project Samples	p. 144
Sponsor: Mission Statement with Trade-off Priorities	p. 146
Team: Team Structure and Conventions	p. 148
Team: Reflection Workshop Results	p. 151
Coordinator: Project Map, Release Plan, Project Status, Risk List, Iteration Plan and Status, Viewing Schedule	p. 153
Coordinator: Project Map	p. 154
Coordinator: Release Plan	p. 155
Coordinator: Project Status	p. 159
Coordinator: Risk List	p. 162
Coordinator: Iteration Plan to Iteration Status	p. 163
Coordinator: Viewing Schedule	p. 166
Business Expert and Expert User: Actor-Goal List	p. 167
Business Expert: Requirements File	p. 169
Business Expert and Expert User: Use Cases	p. 174
Expert User: User Role Model	p. 176
Designer-Programmers: Screen Drafts, System Architecture, Source Code, Common Domain Model, Design Sketches and Notes	p. 178
Designer-Programmer: Screen Drafts	p. 181
Lead Designers: System Architecture	p. 183
Designer-Programmer: Common Domain Model	p. 188
Designer-Programmer: Source Code and Delivery Package	p. 191
Designer-Programmer: Design Notes	p. 192
Designer-Programmer: Tests	p. 196
Tester: Bug Report	p. 199
Writer: Help Text, User Manual, and Training Manual	p. 201
Reflection about the Work Products	p. 202
Misunderstood (Common Mistakes)	p. 205
"We colocated and ran two-week iterations-why did we fail?"	p. 206
"Two developers are separated by a hallway and a locked door."	p. 208
"We have this big infrastructure to deliver first."	p. 209
"Our first delivery is a demo of the data tables."	p. 210
"No user is available, but we have a test engineer joining us next week."	p. 211
"One developer refuses to discuss his design or show his code to the rest."	p. 212
"The users want all of the function delivered to their desks at one time..."	p. 213
"We have some milestones less than a use case and some bigger."	p. 214
"We wrote down a basic concept and design of the system. We all sit together, so that should be good enough."	p. 215
"Who owns the code?"	p. 216
"Can we let our test engineer write our tests? How do we regression test the GUI?"	p. 217
"What is the optimal iteration length?"	p. 218
Questioned (Frequently Asked)	p. 221
What is the grounding for Crystal?	p. 223
What is the Crystal family?	p. 232
What kind of methodology description is this?	p. 235
What is the summary sheet for Crystal Clear?	p. 240
Why the different chapter formats?	p. 241
Where is Crystal Clear in the pantheon of methodologies?	p. 243
What about the CMM(I)?	p. 252
What about UML and architecture?	p. 256
Why aim only for the safety zone? Can't we do better?	p. 258
What about distributed teams?	p. 260
What about larger teams?	p. 262
What about fixed-price and fixed-scope projects?	p. 263
How can I rate how "agile" or how "crystal" we are?	p. 264
How do I get started?	p. 266
Tested (A Case Study)	p. 267
The Field Report	p. 269
The Auditor's Report	p. 293
Reflection on the Field and Audit Reports	p. 299
Distilled (The Short Version)	p. 303
References	p. 304
Index	p. 308
Table of Contents provided by Ingram. All Rights Reserved.

Please wait while the item is added to your bag...

FREE SHIPPING

Amazon no longer offers textbook rentals. We do!

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

Summary

Author Biography

Table of Contents

Supplemental Materials