Thinking about being a Scrum Master? Have you thought about: 1. What is your motivation and do you think you are the right fit? 2. Would you like it to be a career choice? 3. What is in it for you? Is this role really attractive for you? What kind of growth are you looking for? 4. What does this role mean to your organization? If you have thought about any of these questions and chose to be a scrum master, you are among the few scrum masters I have come across, who had the chance to do so. In many cases I have come across, being a scrum master has been a matter of chance, many times imposed, rather than a matter of choice. To me that is an indication of how much (lack of) thought we devote into our role in a team setting as we probably should. As a result, we have multiple cases of job done badly, the role being viewed as "just" an administrative role, or something so easy that "anyone" can do, etc. Before you jump into the Scrum Master Role Here I list a few things...
High Performance Engineering Culture | Software Development