Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

SDLC - Scrum process data model

Log in to subscribe to topics and get notified when content changes.

SDLC - Scrum process data model

See the relationship diagram and table below for a data model of the Agile Development plugin.

Scrum process relationship diagram

The Agile Development plugin adds several new tables to the existing SDLC Scrum tables.

Figure 1. Relationship diagram

Scrum tables and relationships

The following table describes what data the Agile Development tables contain as well as their relationships to other tables.

Table Description and Relationships
Application Model [cmdb_application_product_model] Contains whole products whose releases are being managed. A product can have related releases, themes, epics, and stories.
Theme [scrum_theme] Contains themes, which can represent either a tangible product (such as a trading application) or an abstract goal (such as performance tuning). A theme is always associated with a product and can have related epics and stories.
Release Product [m2m_product_release] Contains all products and their associated releases.
Scrum Release [rm_release_scrum] Contains release records which associate a list of sprints with a time range in which those sprints must be completed. A release can have one or more:
  • Release teams
  • Sprints
  • Stories
Team [scrum_pp_team] Contains the release teams, the people who work on scrum tasks, and stories during releases and sprints.
Team name [scrum_pp_team_name] Contains the names of release teams.
Release team member [scrum_pp_release_team_member] Contains release team members who work on scrum tasks and stories during a release.
Sprint team member [scrum_pp_sprint_team_member] Contains sprint team members who work on scrum tasks and stories during a sprint.
Epic [rm_epic] Contains epics, which allow you to group related stories or requirements that you have not yet transformed into stories. You can associate an epic to a product, a theme, or a configuration item.
  • An epic can have one or more child epics.
  • An epic may be associated with one or more epics.
  • One or more epics may be associated with a theme or a product.
Sprint [rm_sprint] Contains sprints, which are the backlog items to be addressed during a given time period. A sprint can be associated with one or more releases and stories.
Story [rm_story] Contains stories, which describe self-contained pieces of work that can be completed within a sprint. A story can contain one or more scrum tasks and can be associated with:
  • A product
  • A release
  • A sprint
  • A theme
  • An epic
Scrum task[rm_scrum_task] Contains scrum tasks, which describe a discrete amount of work for a story carried out during a sprint. A scrum task can be associated with a single story.