As a Scrum Master should I decide or the team decide whether they need a tester?


  • QA Engineer

    As a Scrum Master my team is already on the big side:

    • Product Manager
    • Associate Product Manager
    • Business Analyst
    • User Researcher
    • Interaction Designer
    • Content Designer
    • Developer
    • Developer
    • Developer
    • Developer
    • Architect

    The team used to have a tester but she left the team for a while but now she apparently wants to rejoin the team.

    The team seem to be handling testing fine without her and this is the direction of the org ie for each team to collectively own testing. Which is my preference.

    My question is should I take this to the team for them to decide if they want a tester or should I leave the team as is?

    I am sure the team will say yes to having a tester, but this goes against building cross-functionalists.



  • A lot of comments are made about the size of the team and the roles within it, so I'll skip that.

    My advice (with most questions, issues or whatever): Take it to the team

    The team is doing the actual work and they can tell what they think they need or should do or whatever. Then you can have a discussion about the situation and come to a solution with the team.

    Do not talk about the team and their needs, talk with the team



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2