What It Takes to Be a Successful Scrum Master

摘要

This paper focuses on the lessons learned along the way as I transitioned from Developer to Scrum Master. I'll share my own personal story in why I decided to take on this transition. My main desire was to help people. I wanted to help my fellow developers and product owners to solve daily Scrum communication problems and adopt an Agile mindset. However, with my lofty aspirations, it was a tough mission. As a developer at my organization, you mostly work alone at your desk. But I quickly realized that I could not do things on my own terms anymore. Rather, I needed to collaborate with people and look for solutions which could work for all. Rather than "ME", it is now a "WE". As a Scrum Master, my tasks have become more abstract and personnel related. In sharing my story, I'll discuss what I have experienced working in a Scrum Master role for more than 4 years. This includes my successes, challenges, and yes... failures. I hope that this can provide valuable insight (including tips and lessons learned) to other developers & testers who may be considering transitioning to a Scrum Master role. Some particular points I'll cover include: 1. Understand human psychology to decode team behaviors. Why is it that some team individuals behave in 'odd ways' that you can't understand on the surface? What's going on here?! 2. Select communication methods that could help your team to solve collaboration problems. Keep in mind, what works for you does not mean it will work for your team. Test it and adjust! 3. How to measure and interpret work progress in your team and look for team improvements. 4. Do Agile vs. Be Agile learned lessons