Scrum Master? Transponster?

I love Friends. In one episode there is a scene where Rachel and Monica are competing against Joey and Chandler. If they know Joey and Chandler better than vice versa, they get rid of the duck. Or win the apartment. Don’t quite remember. Anyway, there was one question that I find especially funny:

Ross: Correct! What is Chandler Bing’s job?
Rachel: Oh! Oh gosh, it has something to do with numbers.
Monica: And processing!
Rachel: Oh, well… and he carries a briefcase!
Ross: Ten seconds. You need this or you lose the game.
Monica: It’s, um, it has something to do with transponding.
Rachel: Oh, oh, oh, he’s a transpons… transponster!
Monica: That’s not even a word!

I sometimes feel like Chandler. Hell, it’s hard even for me  to describe what do I do for living. So I decided to gather different kind of activities from past few weeks. As background information, my role is Scrum Master in a team which is building software(*). Half of the team and PO are located outside of Finland. So this is what I do:

  • Have one-to-one video calls with PO about XX
  • Have an initial planning session where we select a baseline story for estimation and arbitrary story point value for that
  • Have planning sessions with smaller groups of people
  • Have a three-way session where we try to solve a technical problem that one person is having
  • Create a single-pager about the sprint goal and stories and attach it near team room door
  • Create tasks for a user story with a smaller group of people
  • Go to Verkkokauppa to get a team room TV, conference microphone etc.
  • Going through backlog and modifying user stories by myself
  • Code a new feature
  • Create unit tests
  • Peer review other team member’s code and documentation
  • Preparing for sprint planning meeting by going through the assumed user stories
  • Write and update a bunch of confluence pages
  • Ad hoc discussions about testing in our project
  • Getting familiar with Git and bunch of other technologies
  • Ad hoc discussions about application architecture and technology choices
  • Have daily standups
  • Have knowledge sharing session where we go through one person’s code
  • Writing instructions about JIRA usage
  • Preparing for sprint review session
  • Facilitating sprint review session
  • Having a sprint retrospective with the team and coming up with a bunch of improvements
  • Participate in session where we go through user personas of the product we’re building
  • Have sprint planning meetings
  • Have sessions about the user interface of the product
  • Have Scrum of Scrum’s meeting
  • Participate on other team’s sprint reviews

…and most likely something that I cannot even remember. So based on this list my job is to talk with people and occasionally produce some code. We’re in quite early stages of the project, so if I would write this list in 6 months from now, the list would probably be a bit more compact.

*) Gosh this is boring as I cannot really tell what we actually are doing. Oh well, at least I can come back to this post after a couple of years to refresh my memories!

PS. Here is a totally not-related nice picture from Pyhä-Luosto 😉

Leave a Reply

Your email address will not be published. Required fields are marked *