Crystal Methods Flashcards
Crystal Objectives
1) Human powered
2) Focuses on team not on processes
3) directly tackle cooperative game of team invention and communcation
4) Aspires to be sufficient methodology
5) This game never repeats
Crystal attributes
1) Size and criticality
2) lighter color and hardness
Crystal family characterisation
Vertical axis - life(l), essential money(e), discretionary money(d), comfort(c)
Horizontal axis - team size
Crystal family characterisation
Methods are not compatible with each other
If size or criticality changes, change the crystal method
Crystal family genetic code
1) Design priorities
2) Project properties (what team is aiming for)
3) Design principles
4) Key techniques (specific tools)
5) Crystal methods
Design priorities
1) What to work on, what specific order
2) Project safety (project outcome)
3) Development efficiency
4) Habitability (comfortable to use, so that teams do not feel need to avoid it)
Project properties
1) Frequent delivery
2) Reflective improvement
3) Osmotic communication
4) Personnel safety (project team and end user)
5) Focus (priority items for team members)
6) Access to expert users and other users
7) Proper technical environment
Design principles
1) Face to Face communication
2) gauge method weight
3) Add weight
4) Add ceremony
5) Feedback
6) Discipline and skill
7) trade efficiency
Key techniques
1) Methodology shaping workshop
2) reflection workshop
Popular methods
1) Crystal clear (low criticality, small size)
2) Orange
3) orange web
Project safety
1) If all implemented, project safely reach end goal
2) delivered in reasonable period of time
3) 7 project properties (3 base properties, 4 not mandatory)
4) Project safety increases incrementally
Habitability
1) Creating convention, team can live with
2) Comfortable to use
3) team did not feel need to circumvent or avoid
4) includes tolerance for human variation
5) Maximum amount of freedom for team members
Development efficiency
1) eliminate waste
2) team members work continuously on the same project (static team)
3) short iteration (able to focus)
4) familiarity with requirements
Gauge methodology weight
1) Adds cost to the project, constantly monitored
2) less is better
3) Darker methods need more weight, frequent communication
4) criticality increases documentation and reporting
Trade efficiency
1) Non-bottle necks can be less efficient, so bottlenecks can become more efficient