Anh Chi Nguyen, AKVA Group
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; because I wished 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, lofty my aspirations, it was a tough mission.
As a developer, you mostly work alone at your desk. But I quickly realized that I could not do things on my terms anymore. Rather, I needed to collaborate with people and look for solutions which could work for all. Rather than “ME” 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 or testers who may be considering transitioning to a Scrum master.
Key takeaways include:
- Understand human psychology to decode team behaviors.
- Select communication methods that could help your team to solve collaboration problems.
- How to measure and interpret work progress in your team and spot out where to improve.
- How to make Agile work for your team and organization