Skip to content

Consolidate Data Development handbook page to have 2 data development approaches.

Israel Weeks requested to merge master-patch-6e3d into master

Why is this change being made?

This MR consolidates our data development processes from four, down to two. We just need an Ad-hoc and Trusted Data development processes to align to how we actually develop data and how we will serve data in Tableau.

We currently have 4 data development approaches which is too many, confusing, and doesn't align to the current or target state of how we develop data at GitLab. The Business Insights data development was applicable at a time when many major business processes were not in the EDM. That is not the case today. We have the majority of the Release to Adoption and Order to Cash business processes modeled in the EDM. The remaining big gaps in the EDM are the People Data sources and the Engineering data sources which have very low EDM maturity at this time. The explorational data development flow can be consolidated with the ad-hoc data development. We can think of ad-hoc and explorational in the same context. We can think of Business Insights and Trusted data in the same context.

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