Most of you have probably heard that the words we use are strongly related to our thoughts as well as our lifestyle. When your thoughts begin to change, that can be observed in your language too or when your language begins to change, also your mindset begins to change. We, ourselves, are the reflection of the words that we frequently use.
When we consider thinking of Scrum Guide at a similar point of view, the most critical points in terms of artifacts, events, roles, and values are Development Team (89*), Product Backlog (61*), and Increment (45*). Although the most widely mentioned and discussed roles are Scrum Masters or Product Owners everywhere, it is often overlooked that the Development Team is actually the heart of Scrum.
Given the fact that the main purpose of Scrum is to create value for the customer; when we consider a scenario that exists only the Product Backlog which can be prioritized by the Development Team and the product vision can be created by them, also the value can be represented with a high quality or without impediments, other members lose their functionality to a great extent. Neither the Product Owner, who gives the vision to the product and the sole accountable of Product Backlog; nor the Scrum Master, servant leader and the protector of Scrum Framework, or the Sprint Backlog, which shows the details of how to create a DONE Increment, sustain their former criticality or functionality. Even though we all know that our journey is not just on happy paths, sometimes the purpose of the work or the value created by the people at the coalface can be overshadowed by the means.
It should be never forgotten that Scrum or other approaches are just tools for creating value for the customer, and the people that use these tools differentiate the value created.
*Number of uses in the Scrum Guide.
