Skip to content

GitLab Next

P
Product Intelligence
Closed
Opened by Mark Wood@mjwood🌀Developer

Capture Interactions with Requirements

Problem

As Category:Requirements Management becomes more mature, we want to transition from measuring success based on number of requirements created to interactions with requirements.

A general workflow for teams utilizing requirements would be as follows:

  1. Create high level requirements (requirements at a group level) - not yet implemented in GitLab
  2. Create low level requirements (requirements at a project level) - Implemented in GitLab %12.10
  3. Develop design / code / testing by referencing requirements
  4. Link appropriate design / code / test to requirements - Test linking MVC in %13.1

In short, the actual creation of requirements is only a small piece of capturing the benefits of having a requirements based development approach - the far greater measure of success is to measure the interactions with requirements - specifically viewing and tracing to requirements.

Proposal

After we are able to achieve requirement creation metrics via Usage Ping, we would like to plan out and implement the next steps as follows:

  1. Track requirement navigation changes - are users paging through requirements?
  2. Track requirements filter events - are users searching for requirements to reference them?
  3. Track linking events - are users linking both code and tests to requirements?

Result

Next steps (if any)

Edited by Mark Wood