Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

Agile Development tables

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

Agile Development tables

The Agile Development application uses the following tables to manage the scrum process.

  • Application Model [cmdb_application_product_model]: represents whole products whose releases are being managed.
  • Release Product [m2m_product_release]: represents all managed products.
  • The following tables represent releases.
    • Scrum Release [rm_release_scrum]: represents all available releases. Each release contains a list of sprints with a time range in which the stories in those sprints must be completed.
    • Sprint [rm_sprint]: stores sprints, which are the backlog items to be addressed during a given time period.
  • The following tables represent product backlog items to be included in the sprint.
    • Team [scrum_pp_team]: represents who will complete Scrum tasks and stories during releases and sprints.
    • Epic [rm_epic]: represents stories or requirements that you have not yet transformed into stories.
    • Theme [scrum_theme]: represents either a tangible product (such as a trading application) or an abstract goal (such as performance tuning).
    • Story [rm_story]: represents self-contained pieces of work that can be completed within a sprint.
    • Scrum task [rm_scrum_task]: represents a discrete amount of work for a story carried out during a sprint.
    • Defect [rm_defect]: represents a deviation from expected product behavior.
    • Enhancement [rm_enhancement]: represents an improvement to an existing product.
Figure 1. Agile Development table structure
Table structure
Feedback