Ritesh Mehrotra says he’s a developer and a Scrum Master; both at the same time. He never stops thinking about code nor about agile practices.
He suggests focusing on gaining skills and being close to teams. Ritesh also shares his story when his retrospectives were not going well and how they tried to resurrect it.
This is part of a series of conversations around my research on the topic: Future of the Scrum Master role.
Add your voice to this research study: