Just a little rant today:
Scrum has 3 roles. Scrum Master, Product Owner, and the Team. I believe in a team of doers and performers (probably the same thing).
I, in general, don’t believe in putting a data modeler on a team, or an architect on a team, or any specialized role on a team. It’s not to say I don’t believe in having a data modeler or architect on the team, as long as they can view themselves as a member of the team willing to do work and get work done.
I believe the team needs a team data modeler if the team says, “These data relationships are pretty complex, we really do need a data modeler”, then we start talking about a data modeler (or architect, or whatever). However, in many cases, the team members can really model their own data or architect their own systems.
Often, we use a DBA service, or operations service. They provide a service to the team, but not a part of the team.
There may be some exceptions to the rule. When you want to create an organizational consistency, you may have an enterprise architect or data architect, but they usually work with the team as a guide or provide service. If you’re on the team, you’re on the team, skin in and all.
Anyways, just a bit of a minor rant today, no real coherent thought to it.