- Basics of Agile and its manifesto
- Definition of Scrum
- Scrum and its three pillars (qualities)
- Scrum Guide and its history
Basics of Agile
Historically, Waterfall model was used in software development projects which is a sequential (non-iterative) design process. Waterfall model is a predictive method in which you need to define and plan as much as possible in advance.
On the other side, changing market conditions, evolving technology, unpredicted challenges, emerging customer requirements are leading to an understanding that some problems can not be fully understood or defined in a predictive or planned manner – accepting the need of an adaptive design process.
To find the answer of such an adaptive design process, a group 17 different independent thinkers met on February 11-13, 2001, and formed The Agile Alliance to offer a manifesto as a better way to develop projects. You can read more about Agile Manifesto at: http://agilemanifesto.org
Here are 12 principles behind Agile Manifesto: http://agilemanifesto.org/principles.html
Note: Agile is an adaptive product development methodology. And, Scrum is a process framework to manage development (it is not a process or technique for building products) within which people can employ various process and techniques.
Definition of Scrum
Scrum is an iterative and incremental agile software development framework for developing and sustaining complex products.
As per the definition mentioned in Scrum.org Scrum Guide:
Scrum (n): A framework within which people can address complex, adaptive problems, while productively and creatively delivering products of the highest possible value.
Qualities of Scrum:
- Lightweight – Little documentation of Scrum framework make it quick
- Simple to understand – Easy, quick and less jargons make it simple to understand
- Difficult to master – It is short and simple but that is what makes it difficult to master as people and companies are still evolving and working to understand new ways of software development
Scrum and three pillars
Scrum follows empirical process control theory, or empiricism. Empiricism mentions that knowledge comes from experience and making decisions based on what is known.
Using Scrum, below three pillars are part of every implementation of empirical process control:
Transparency: This pillar ensures that there is a common understanding by defining common standards to ensure significant visibility during the process. E.g. common language for communication and common definition of “DONE” to perform and accept work
Inspection: It is an important part to monitor progress and detect any variances in the process. Frequency of inspections by skilled inspectors should be reasonably planned i.e. not too many and not too less.
Adaption: Once a variance is identified by an inspector then an adjustment must be made as soon as possible to minimize further deviation.
Scrum Guide and its History
Ken Schwaber and Jeff Sutherland developed Scrum, written and provided Scrum Guide. Find latest version of Scrum guide at http://www.scrumguides.org