Wednesday, September 20, 2006

Crystal Clear

Crystal Clear is a member of the Crystal methodologies and is an example of a lightweight methodology. The Crystal family of methodologies focus on efficiency and habitablity as components of project safety. Crystal Clear methodologies are for development of systems that are not life-critical. Crystal Clear focuses on people, not processes or artifacts.

Team Description

There is only one team, generally consisting of up to 6-8 members, seated together in close proximity i.e. the same or adjoining offices.

Roles (requiring separate people)
  • Sponsor
  • Senior designer-programmer
  • Designer-programmer
  • User (part-time at least)
One of those team members may become project coordinator, one will become the business expert and either one or more may become requirements gatherers.

Policy Standards
  • Software is delivered incrementally and regularly (every 2 - 3 months).
  • Progress is tracked by milestones consisting of software deliveries or major decisions.
  • At least some automated regression testing of application function.
  • User has direct involvement.
  • 2 user viewings per incremental release.
  • Downstream activities start as soon as upstream is 'stable enough to review'.
  • 'Product and methodology tuning workshops' are held at the start and middle of each iteration.
Products Produced
  • Release sequence
  • Schedule of user viewings and deliveries
  • Annotated use cases or feature descriptions
  • Design sketches and notes needed
  • Screen drafts
  • A common object model
  • Running Code
  • Migration Code
  • Test Cases
  • User Manual
Team Internal Matters
Set and maintained by the team.
  • Templates for the work produced
  • Standards for coding and user interface
  • Standards and details of regression testing
Crystal Clear does require documentation to be produced. Just what documentation consists of is not spelled out by Crystal.


Agile Software Development, Alistair Cockburn; Addison-Wesley, 2002


Post a Comment

<< Home