Draft: Change Certify Group Categories Title

Why is this change being made?

Certify Group within Plan Stage is currently composed of two categories, Requirements Management and Quality Management. This Issue and associated MR is proposing a change to a singular category entitled Requirements and Traceability Management.

The reasoning for this change includes the following:

Quality Management is not synonymous with the testing capabilities associated with the category and its relationship with requirements. Joining the two categories creates an interconnected framework between requirements and testing. Ideally, our requirements users will leverage test cases and sessions alongside their requirements work item type, and will have a clearer understanding of their linkage via a singular category model.

Market leaders in the requirements space do not have separation in their categories. This change puts GitLab on par with market competition. Examples Includes:

Jama Software: Requirements Management and Traceability Solution Modern Requirements: Requirements Management Tool IBM DOORS: Requirements Management Tool

Each above Competitor has Traceability capacity in their solution, but only Jama has a "Traceability" in its primary marketing descriptor. I have identified Jama as the leader the category though, which is why I believe an appropriate name for the category in GitLab is Requirements and Traceability Management.

This name change emphasizes the long-term focus on traceability management in GitLab. Work items are central to traceability and this indicates to our customer base our intention to focus on development in this category. Traceability also aligns closely with our vision for a singular platform for DevSecOps. One of our greatest unfair advantages is allowing the user to develop from plan to release all within one place. Creating an emphasis on tracing accurately throughout that entire release cycle provides great value, especially to GitLab stakeholders and champions.

Existing Category Name(s)

Requirements Management Quality Management

Proposed Category Name

Requirements and Traceability Management Additional Context

• Related Issue and Issue

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.

---