If you are confused because you are not a software developer, please don't complain about this article. Just stop reading. The question is by a developer and for developers. It obviously should have had more context so to help non-developers know that.
If you are confused because you ARE a software developer, but don't know what scrum is, or don't understand the scrum jargon, stop complaining and go read up on scrum right now. Agile and scum are part of the culture now. Whether good, bad, or ugly, they're here to stay, just like OO, client-server, and waterfall. You only make yourself sound stupid when you make comments of the variety: 'I've never used it, so it must not be imporant, but I did skim the wikipedia article and it sounds like a stupid idea.'
With that out of the way, let me say the least dysfunctional team I have ever worked on used scrum. The engineers chose to use scrum. It was not forced on us by management. The reason we chose scrum was that we'd all been around the block a few times and understood that process just gets in the way. There is no way to avoid schedules, deadlines, and status meetings altogether. But we wanted to spend as little time as possible on that stuff. We chose scrum as the least intrusive process. The manager pretty much ignored us, we did things in a way that made sense, and we got a lot of work done.
So, to answer the original poster, in your next sprint retrospective you should say '${SCRUMMASTER} has turned into a glorified spreadsheet jockey. That's not good because he used to be our most productive coder. We need to find a way to get him back in the game.' Either the team will adjust the role of scrummaster to make it work within your organization, or you're not doing scum right.
Hint: Hiring a beancounter to jockey the spreadsheets is not the right answer. I've seen that tried, and the results were not pretty. Not only did the beancounter do a bad job with the spreadsheets, but he tried to be the boss.