A lot of the answer here is going to depend on the organization and person.
Coming from a software development background, my sense is that you'll likely have a greater appreciation for the importance of keeping developers focused on writing code and removing as much overhead as possible when it comes to them participating in Scrum events like daily stand-ups, refinement and estimation, and sprint planning.
In my experience, this is where a lot of Scrum Masters get it wrong. Facilitating Scrum in a way that creates more overhead for the dev team isn't likely going to be met with a lot of support from the team, and over time will likely lead to frustration and negative sentiment. Finding that balance is going to be an essential to your success.
For what its worth, I haven't seen a lot of devs personally make this transition, but I think your perspective as a former developer could really help set you up for success in this type of role, and improve the odds your team will be successful with Scrum. Just my 2 cents, hope it helps!
Coming from a software development background, my sense is that you'll likely have a greater appreciation for the importance of keeping developers focused on writing code and removing as much overhead as possible when it comes to them participating in Scrum events like daily stand-ups, refinement and estimation, and sprint planning.
In my experience, this is where a lot of Scrum Masters get it wrong. Facilitating Scrum in a way that creates more overhead for the dev team isn't likely going to be met with a lot of support from the team, and over time will likely lead to frustration and negative sentiment. Finding that balance is going to be an essential to your success.
For what its worth, I haven't seen a lot of devs personally make this transition, but I think your perspective as a former developer could really help set you up for success in this type of role, and improve the odds your team will be successful with Scrum. Just my 2 cents, hope it helps!