Skip to content

Add BIOps Workflows, BIOps Roles and Responsibilities to the Tableau Handbook page and update the Project Folder Architecture.

Israel Weeks requested to merge master-patch-1f5c into master

Why is this change being made?

  1. Add BIOps Workflow overviews and BIOps Roles and Responsibilities to the Tableau Handbook page.

  2. Add Team Member Sub-Project. This folder will be used to publish cross-functional Team Member content such as the Headcount dashboard.

  3. Remove the 3rd layer of the Project Folder Architecture that created folders for Trusted Data and Business Certified in the Tableau Production Project. This is a nuanced and somewhat confusing set-up since we do not have a concept of Business Certified in the handbook nor do we have a data development method that aligns to Business Certified. Business Certified is largely a result of technical debt and data work in the backlog not being completed yet. To strike the right balance of rigor with Trusted Data Development and not being a bottleneck in the Production folder, we can use the Certified Stamp to brand and certify trusted data content in Production. Content that is still SSOT, production grade content used to run the business, but does not currently pass all of the TD standards can still be published to Production without the certified stamp on a case by case basis. This non-certified content should have an issue with a project plan to promote the content to TD status overtime. The target state is to raise the maturity level of the data infrastructure over the next year as we deprecate the legacy schema and build new trusted data models and have the majority, if not all, of the content in production with a certified stamp.

Author Checklist

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Edited by Israel Weeks

Merge request reports

Loading