Crystal Methodology

This presentation focuses on all the crystal methodologies thoroughly.
Provides a perceptive outline.

1. Prepared by: Muhammad Asim PH#  [phone]

2. Crystal Methodology

3. Crystal: Derived from gemstones Lightweight Methodologies Non-jealous

4. Crystal: Crystal methods are part of the crystal family developed by Alistair Cockburn in the mid-1990’s Based on o bservations of many teams that did not follow formal methodologies yet had successful projects

5. Crystal: Crystal methods focus on: People Interaction Community Skills Talents Communications

6. What is Crystal Methodology? It is a subset of agie methodology because use iteration and incremental development same as agile model

7. Crystal family: Crystal clear lightweight, not critical Crystal Yellow Crystal orange Crystal orange web Crystal Red Crystal Maroon Crystal Diamond Crystal Sapphire heavy, critical

8. Crystal clear: Lightest weight methodology Supports fixed price contracts Requires documentation Focus on people,not process or artifacts Project safety Small teams

9. Crystal Yellow: 7 to 20 team members Easy communication Clear owner ship of code areas Feedback Mission statement Monthly improvements

10. Crystal Orange: Incremental development The idea is for agile development New release after 3-4 months Each released is called “increment” Designed for medium size projects

11. Crystal Orange web: Used in projects that have a continually evolving code base that is being used by the public Used for category D40 projects Used in teams with 21-40 members

12. Crystal Orange web: Consists of a set of conventions grouped into five categories: Regular heartbeat with learning Basic process Maximum progress , minimum distractions Maximally defect free A community , aligned in conversation

13. Crystal Properties: Frequent delivery Reflective improvement Close or osmotic communication Personal safety Focus Easy access to expert users Automated tests ,configuration management , frequent integration

14. Frequent Delivery Iteration release regularly Delivery cycle shouldn’t be more than four months so problem find and fix early Customer ensure The team gets to debug their development and deployment processes

15. Reflective Improvement Developer dedicate time Reflection Workshop held every weak Iterations help process is working or feedback at the end of iteration

16. Osmotic Communication Developer team must be in same room Aids communication Information flow quickly Communication overhead reduce

17. Personal Safety Team members speak freely share their views without thinking about what others think about their views .

18. Focus Focus on a task long enough for progress Clear definition and goals of the project

19. Easy access to expert users Developer work with experts Improvement base on experts Communication 2 hours in one weak and reachable by phone

20. Automated tests ,configuration management , frequent integration Support Errors and problems Done regularly configuration management system and run automated system tests

21. Comparison: Crystal Crystal is much tolerant More likely to followed Crystal end-users participate in all of the incremental releases Face-to-face meetings happen in Crystal Extreme programming Xp is much disciplined Productive End user actively involved in XP informal daily stand up meetings happen in XP

22. Advantages: Effective team communication and this facilitates learning amongst team members from each other This methodology can be adjusted as per project type and team size Crystal Clear is an agile methodology for projects with small teams, less than about 10 people in size . It supports fixed price contracts Crystal Clear is not mutually exclusive with other methodologies

23. Disadvantage: The planning & development are not depended on requirements  May not work well for distributed teams . Moving from one flavor of Crystal to another in mid project doesn't work Crystal was not designed to be upward or downward compatible. varying by project size and criticality