The Data Vault Handbook - Concepts and Applications

4.3. ROLES In any Data Vault project, roles play a key part in ensuring smooth collabora- tion and successful delivery. It’s important to note that roles are not the same as positions. A role is a function someone assumes in a particular context, and it can shift as the project evolves. One person might fulfill multiple roles, and conversely, a single role may require the contribution of several individuals. In this way, the responsibilities of roles remain fluid, depending on the needs of the team and the context in which they operate. In a traditional Scrum team, there are three primary roles: Product Owner, Scrum Master, and Developers. However, in the context of a Data Vault project, the roles within the Developer group can be further specified to address the specialized needs of a data team. While Scrum typically includes a Scrum Master to facilitate team coordination and remove obstacles, in a Data Vault project, this role might be filled by a Team Lead. The Team Lead not only guides the team’s work but also plays an active part in facilitating collaboration, managing timelines, effort estimation, and en- suring the team stays aligned with project goals.