In this post, I will focus some terms and explanations on the “Scrum Guide 2017” which I believe is so important to understand the Scrum.
The Scrum Guide defines the Scrum as
A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
It is easy to understand “productive, creative, highest value” terms. But, you may have such questions: “What are the complex adaptive problems” or “Aren’t all projects complex?”
Honestly, I accepted this term as it is for a while until I came across another framework called “Cynefin” in which the type of projects is explained so well.
This framework says, If unknowns are more than known ones it is a complex problem. In this type of problem, It is advised that firstly a)probe and b)get a sense and c)then respond. After examining this concept, “inspection”, “adaptation” terms in Scrum become more meaningful.
“Simple” and “Complicated” are such problem types in which knowns are more than unknowns. It is mostly the things that you did the same before.
“Chaotic” problems mostly consist of unknowns in which you really do not know exactly what to do next.
If we continue the Scrum guide, we come across the “Empiricism” term.
Scrum is founded on empirical process control theory or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Scrum employs aniterative, incremental approach to optimize predictability and control risk.
Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.
The Common language
The common definition of “done”
What is “done”? I understand it as a “checklist” which you should tick every after a PBI(Product Backlog Item) is completed. It is defined by the Scrum team and provides a common agreement.
When the values of commitment, courage, focus, openness, and respect embodied and lived by the Scrum Team, the Scrum pillars of transparency, inspection, and adaptation come to life and build trust for everyone.
Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback. Incremental deliveries of “Done” product ensure a potentially useful version of a working product is always available.
Product Backlog refinement(a.k.a. Grooming) is the act of adding detail, estimates, and order to items in the Product Backlog.
During Sprint Planning the Scrum Team also crafts a Sprint Goal. The Sprint Goal is an objective that will be met within the Sprint through the implementation of the Product Backlog, and it provides guidance to the Development Team on why it is building the Increment.
Also published on Medium.