Business stakeholder role for Agile Development 2.0

  • Release version: Xanadu
  • Updated August 1, 2024
  • 2 minutes to read

    • Use the business stakeholder role to read and retrieve data from any table of the Agile Development 2.0 and Scrum Programs applications to generate reports.

    When you activate the Business Stakeholder plugin (com.snc.business_stakeholder) in your ServiceNow instance, the Read only roles for Agile 2.0 plugin (com.snc.agile_read_roles) is also activated. This plugin provides a business stakeholder role (sn_agile_read) with which you can access all the tables of Agile Development 2.0 and Scrum Programs applications. You can assign this role to any user in your organization who is a business stakeholder.

    Plugin availability

    If you are a new customer, the Read only roles for the Agile 2.0 plugin (com.snc.agile_read_roles) is activated on zBoot. However, the business stakeholder role (sn_agile_read) is available only when you activate the Agile Development 2.0 plugin (com.snc.sdlc.agile.2.0).

    If you are an upgrade customer, you must manually activate the read-only roles for Agile 2.0 plugin (com.snc.agile_read_roles).

    Agile Development 2.0 tables accessible by users with the business stakeholder role

    When both the Read only roles for Agile 2.0 plugin (com.snc.agile_read_roles) and the Agile Development 2.0 plugin (com.snc.sdlc.agile.2.0) are active in your ServiceNow instance, the user with the business stakeholder role (sn_agile_read) has read access to the following tables.

    Table 1. Agile Development 2.0 tables
    Table Description
    Product Assignment Group

    [m2m_product_group]

    		 Stores relationship between products and groups.
    Release Assignment Group

    [m2m_release_group]

    		 Stores relationship between releases and groups.
    Application Model

    [cmdb_application_product_model]

    		 Represents a whole product whose releases are being managed.
    Release Product

    [m2m_product_release]

    		 Represents all managed products.
    Story Dependencies

    [m2m_story_dependencies]

    		 Represents all related stories (prerequisite and dependent) to an existing story.
    Scrum task

    [rm_scrum_task]

    		 Represents a discrete amount of work for a story carried out during a sprint.
    Sprint team member

    [scrum_pp_sprint_team_member]

    		 Represents the list of users who are part of a sprint.
    Team

    [scrum_pp_team]

    		 Represents who completes scrum tasks and stories during releases and sprints.
    Team name

    [scrum_pp_team_name]

    		 Represents the name of the scrum team.
    Theme

    [scrum_theme]

    		 Represents either a tangible product (such as a trading application) or an abstract goal (such as performance tuning).
    Scrum release

    [rm_release_scrum]

    		 Represents individual versions (releases) of the product. 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 together during a given time period.
    Epic

    [rm_epic]

    		 Represents related stories or requirements that you have not yet transformed into stories.
    Story

    [rm_story]

    		 Represents self-contained pieces of work that can be completed within a sprint.
    Defect

    [rm_defect]

    		 Represents a deviation from the expected behavior of a product.
    Enhancement

    [rm_enhancement]

    		 Represents an improvement to an existing product.
    Table 2. Scrum Programs tables
    Table Description
    epic_backlog_definition Stores the filter criteria that is used to create the epic backlogs.
    scrum_program_m2m_group Stores the relationship between a scrum program and its teams.