Crystal Method

Source: Presentation - The Crystal Methods, or How to make a methodology fit, Alistar Cockburn @2003

Seven principles

Interactive face-to-face communication is the cheapest and fastest channel for exchanging information
Weight is costly
Heavier methodologies for larger teams
More ceremony for more criticality
More feedback & communications, fewer intermediate deliverables
Discipline, skills, understanding counter process, formality, documentation
Efficiency is expendable at non-bottleneck activities.

Crystal Orange

Crystal Orange : roles & teams

Roles: Sponsor, Business expert, Usage expert, Technical facilitator, Business analyst/designer, Project Manager, Architect, Lead designer/programmer, Designer/programmer, Design Mentor, Reuse Point, Writer, Tester, UI designer.
Teams: System planning, Project monitoring, Architecture, Technology, Functions, Infrastructure, External test.

Crystal Orange : standards - Policy:

Delivery increments every 3 + 1 months
Tracking by milestones, not by work products
Mandatory regression testing of application function
Direct user involvement
Ownership model for work products
2 user viewings per release
Use cases completed down to failure cases
Single, common object (not analysis & design models)
Downstream activities start as soon as upstream is "stable enough to review"

Local standards (set and maintained by team):
Work product templates, Coding style, UI style
Regression test framework

Crystal Orange : products

Ownership assignment is negotiable
Every product has an owner.

Crystal Orange : tolerance

Policy standards are mandatory, but equivalent substitution are permitted
any technique allowed
Tolerance on work products
Minor deviation from templates permitted

Crystal Orange : activities & milestones

Mid- & post-increment methodology review
Each work product
Each work product, Iteration deliveries, Test cases, Final delivery
Each work product stable enough to review and Application correct enough to deliver.

Crystal Clear

Crystal Clear : roles & teams

sponsor, senior designer, designer/programmer, user (part-time)
coordinator, business expert, requirements gatherer
single team of designers/programmers
single big room, or adjacent offices

Crystal Clear : Products and Milestones

Products:Release sequence, Schedule of user viewings, deliveries;Actors-goals list & Annotated use cases; Design sketches & notes as needed, screen drafts; Common object model Running code, Migration code, Test cases; User manual
each
each
Methodology (pre- and mid-increment)
Requirements stable enough to design to
UI stable enough to document to
Application correct enough to deliver.

Crystal Clear : Policy

Delivery increments every 2 + 1 months
Tracking by milestones, not by work products
Requirements in annotated usage scenarios (use cases)
Mandatory regression testing of application function
Peer code reviews
Direct user involvement
Ownership model for work products

Crystal Clear : Standards (up to the team):

Coding style
UI style
Regression test framework

Crystal Clear : tolerance

Policy standards are mandatory, but equivalent substitution are permitted
any technique allowed
Quite wide tolerance on work products
Assess the Quality of the communications, not the quality of the work products (except Test Cases).

Frequent Delivery of Usable
Code to Users (required)
Reflective Improvement (required)
Osmotic Communication Preferably by Being Co-Located (required)
Personal Safety
Focus
Easy Access to Expert Users
Automated Tests
Configuration Management
Frequent Integration

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License