IBM asked Alistair Cockburn in 1991 to develop a methodology for object-oriented project development. He didn’t know much about project management at the time and knew this would be a challenge. He decided to interview the project teams to get their views on the project. He discovered that successful teams share the same patterns and techniques, even though they don’t use any particular project methodology. He concluded that successful teams shared the same patterns and techniques without using any particular project methodology. He then created a family of methodologies, named Crystal. Project Management Frameworks and Methodologies
This article is only a small portion of the story about project management. We cover it in great detail in our flagship ebook. We appreciate you subscribing. All newsletter subscribers can download this (and many other ActiveCollab Project Management Guides). Download the Ebook We are unable to subscribe you at this time. Please double-check your email address. If issue still persist, please let us know by sending an email to [email protected] Try Again What is Crystal Method?
Crystal method is an agile software development methodology that focuses more on people and their interactions than on processes and tools. Alistair believed that people’s talents and communication skills have the greatest impact on the project’s outcome. Crystal Method is built on two fundamental assumptions. Teams can streamline their work processes and become more efficient.
Projects are unique and highly dynamic. They require specific methods.
Cockburn suggests that product development should be viewed as a game. It should encourage everyone to get involved, to think creatively, and to come up with brilliant ideas. Cockburn suggests that instead of focusing solely on “is our model accurate?” he should focus on “Is the product meeting the customer’s needs?” Or “Do our goals align as a team?” Teamwork is a natural part of large software projects. We have short, medium, and long-term goals. Our goal tracking will indicate if certain parts of the software are not working in sync. Everyone should work together to support one another and stay on the same page. “– Kalila Lang,DigiSomniCrystal method family members
Cockburn discovered that project properties change depending on how critical the project is. A smaller team can manage and build the product with minimal paperwork and status reporting, but larger teams are more likely to need to communicate important information. There is no single Crystal method. There are many Crystal methods for different types and types of projects. To make this categorization easy to understand, Cockburn named the methodology Crystal and categorized it along the two dimensions – size and criticality – that matching those of minerals – color and hardness.Essentially, Cockburn developed these families to point out that each project may require a particular set of policies, practices, and processes in order to meet the project’s unique characteristics. Cockburn explained this by calling Crystal “a collection of samples that you adapt to your circumstances”. The three dimensions that will determine which approach is best for your projects are: Team size
Criticality
What is the priority of the project?
They are generally characterized by their color.
