You're right! In my first role as a Scrum Master/Project Manager, I faced challenges due to a lack of technical skills, which made it difficult to fully understand and support my development team's work and obstacles. After being laid off I decided back to school for a computer science degree (only because I already had so many college credits to apply to a computer science degree ). Now, with my enhanced technical knowledge, I am confident in my ability to bring more value and support to any Scrum team, helping them achieve success.

From a developers perspective, you have the utmost respect from me. That's really all we ask for. Curiosity. Interest. All too often, there's this mentality that software development is all about the "process", and everything else is just a lesser detail. And from a devs perspective, that's just disrespectful. Most of us have spent our lives becoming developers out of genuine curiosity. We spent most of lives swimming in these deep technical details in order to get where we are. And when we have someone who is supposed to be managing us and they choose to stay away from all technical details, there's a huge disconnect going on. You nailed it. You don't need to be a coder. We just want to work with someone who is curious. As developers, we have to understand the agile process to some degree so why shouldn't scrum masters have to have some level of understanding of the technical details they are managing? Trust grows immensely when that gap is bridged from both sides.

Hello, I am a new scrum master who just got off my first project. The project didn't make it out of discovery. Do you offer resume guidance etc for someone in this type of situation? Some not-so-agile experience, some related experience in past jobs.