Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown

joint scrummaster role

author & internet detective
Posts: 40035
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
On my team, we do not have a dedicated ScrumMaster. (It's currently about 15% of my job.) When having a joint ScrumMaster/other role, what do folks think it meshes well with.

Here's my current thinking:

Junior developer
Pros: Can focus on process, pigs (team) will not defer
Cons: Is likely to not have the experience to push back on process and to the product owner

Tech lead
Pros: Not a manager
Cons: Some issues with deferring to decisions made and merging tech lead vs ScrumMaster decisions

Project manager
Pros: Likely good at organization and process
Cons: Easy to turn into reporting and feeling like a status meeting

People manager
Pros: Likely good at organization and process
Cons: East to turn into reporting. Easy to have fear of openness because your manager is present
He's my best friend. Not yours. Mine. You can have this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic