SCRUM Master: I am the person in charge of facilitate and manage the correct implementation and continuity of the SCRUM framework.
I am supposed to know the framework perfectly and know as many necessary tools as I may need so the product owner or the development team can count on me if they are having troubles to accomplish any existing project goal shaped into SCRUM.
I know that SCRUM is based on the empirical process, therefore I know that its three pillars are: Transparency, Inspection and Adaptation.
Transparency comes from a team that trust to each other. It presents one of the largest challenges of SCRUM but delivers a great reward. Transparency makes it easy to get better results as it pushes the SCRUM team to show the facts as they really are. No matter how bad or good the increment goes, the development team and the product owner as well, should inform, as soon as possible, about any situation that may change the increment or the sprint goal itself. Finally, transparency opens the door to the next two pillars of the empirical process and allows them to perform the role that they are meant to play.
Inspection happens or must happen at least once during a sprint. Continuous inspection is one of the main issues of the SCRUM framework. To get an appropriate feedback, the product owner should show the product to the customer, most likely during the sprint review, so the customer can agree with the increment delivered or point corrections and/or changes, which the development team must receive as an improvement opportunity and work hand by hand with the customer, so they can get to the most accurate version together.
Adaptation is the main goal to achieve in projects full of uncertainties like SCRUM projects. One of the mandatory practices of the product owner should be the regular delivery of working product to the market so he/she can get the right feedback from its customer and final users and work on a more precise refinement of the product backlog to add value to the current and the next increment of product. We will know if we are going through the right way and successfully adapting if we can respond positively to these questions: “Is the team working better than the previous sprint? Is the product at the highest level it can reach for this sprint?”, if the answer is “Yes”, then keep going.
The empirical process teaches me that the more important things are facts. It makes me stay alert to the environment and what may cause an obstruction to the project to, it also gives more than one opportunity to correct and move forward to our main goal.
Check this essentials video from Scrum alliance:
José Gregorio Ortega G.
Give me your feedback and share this article if you liked it!