--- sourceDocument: Zurich Strategic Portfolio Management sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-business-management Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich Strategic Portfolio Management ft:clusterId : - itbm bundleId : - itbm workflow : - Technology --- # Components installed with Agile Development 2.0 # Components installed with Agile Development 2.0 {#ariaid-title1} * Release version: Zurich * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Several types of components are installed with activation of the Agile Development 2.0 plugin, including tables, user roles, and properties. Note: The Application Files table lists the components that are installed with this application. For instructions on how to access this table, see [Find components installed with an application](https://www.servicenow.com/docs/access?context=find-components&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). Demo data is available for this feature. ## Roles installed {#components-installed-with-agile-2.0__section_wly_yyh_wdb} {#components-installed-with-agile-2.0__table_u1t_gb1_wdb__entry__3} | Role title \[name\] | Description | Contains roles | |-|-|-| | Scrum admin \[scrum_admin\] | A scrum admin has full control on the Agile Development 2.0 application. | * scrum_user * rm_product_admin * rm_task_admin * rm_test_admin * rm_doc_admin * rm_story_admin * rm_epic_admin * rm_releasescrum_admin * rm_sprint_admin {#components-installed-with-agile-2.0__ul_qwy_1t2_gkb} | | Scrum master \[scrum_master\] | A scrum master guides team members through a sprint and serves as a sounding board for issues that arise. A scrum master can move stories between a release backlog and a sprint. This user can create and manage: * Epics * Stories * Sprints * Team Members {#components-installed-with-agile-2.0__ul_qdw_dy4_cmb} | * scrum_sprint_planner * scrum_story_creator * scrum_user {#components-installed-with-agile-2.0__ul_rdw_dy4_cmb} | | Scrum product owner \[scrum_product_owner\] | Users with this role are responsible for the business value of a project and for maintaining the product backlog. A product owner can move stories between the product backlog and releases. This user can create and manage: * Themes * Epics * Stories * Products * Releases * Teams {#components-installed-with-agile-2.0__ul_tvc_21z_whb} | * scrum_release_planner * scrum_story_creator * scrum_user {#components-installed-with-agile-2.0__ul_uvc_21z_whb} | | Scrum release planner \[scrum_release_planner\] | Users with this role perform release planning activities. A release planner can create and manage: * Themes * Products * Releases {#components-installed-with-agile-2.0__ul_vvc_21z_whb} | * scrum_user * scrum_story_creator {#components-installed-with-agile-2.0__ul_wvc_21z_whb} | | Scrum sprint planner \[scrum_sprint_planner\] | Users with this role manage the sprint process. A sprint planner can create and manage: * Stories * Sprints {#components-installed-with-agile-2.0__ul_xvc_21z_whb} | * scrum_user * scrum_story_creator {#components-installed-with-agile-2.0__ul_yvc_21z_whb} | | Scrum story creator \[scrum_story_creator\] | Users with this role create the descriptive elements of a product. A story creator can create and manage: * Epics * Stories * Tasks {#components-installed-with-agile-2.0__ul_zvc_21z_whb} | * rm_scrum_task_admin * scrum_user {#components-installed-with-agile-2.0__ul_jq4_cbz_mmb} | | Scrum story editor \[scrum_story_editor\] | Users with this role have edit access to the Story \[rm_story\] table. | * scrum_user * rm_scrum_task_admin {#components-installed-with-agile-2.0__ul_f15_prb_1kb} | | Scrum team member \[scrum_team_member\] | Users with this role are the scrum users who work on a story in a sprint. A team member can create a scrum task, perform updates to a story, and log enhancement requests or defect reports. | * scrum_user * scrum_story_creator * scrum_story_editor * rm_defect_admin * rm_enhancement_admin * rm_scrum_task_admin {#components-installed-with-agile-2.0__ul_awc_21z_whb} | | Scrum task admin \[rm_scrum_task_admin\] | Scrum task administrator with access to \[rm_scrum_task\] table. | scrum_user | | Scrum user \[scrum_user\] | Basic scrum role that all other roles inherit. It confers read-only rights to the Agile Development application. A scrum user can view all elements of agile, but cannot create, edit, or manage records of any type. | cmdb_read | [ ] {#components-installed-with-agile-2.0__table_u1t_gb1_wdb} ## Tables installed {#components-installed-with-agile-2.0__section_s1x_dzh_wdb} {#components-installed-with-agile-2.0__table_AgileDev2.0__entry__2} | 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 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. | | Release team member \[scrum_pp_release_team_member\] | Represents the list of users who are part of a release. | | 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. | | Documentation Task \[rm_doc\] | Represents documentation tasks for the product. | | Enhancement \[rm_enhancement\] | Represents an improvement to an existing product. | | SDLC release \[rm_release_sdlc\] | Represents individual versions of the product. | | Testing Task \[rm_test\] | Represents testing tasks for the product. | [ ] {#components-installed-with-agile-2.0__table_AgileDev2.0} Note: Dashboards in Agile Development require a separate plugin to be installed and configured. For information about Agile 2.0 dashboards and reports, including burndown charts and cumulative flow diagrams, see [Agile Development process flow](https://www.servicenow.com/docs/XqIMvqpEIR7SpwM5FVZyqg "Learn the process that is used to manage product development efforts in Agile Development 2.0, such as creating a product or tracking a sprint or release.") and [Performance Analytics Content Pack for Agile 2.0](https://www.servicenow.com/docs/lcxOWHaxnaZFA~0iEsxO5Q "Improve your Agile processes and practices using preconfigured dashboards with data visualizations from the Platform Analytics Content Pack for Agile 2.0."). ## Properties installed with Agile Development 2.0 {#ariaid-title2} Properties are added with activation of Agile Development 2.0. Agile Development 2.0 adds the following properties. Note: All of these properties are located in the System Properties \[sys_properties\] table. To access the table, enter sys_properties.list in the navigation filter. {#properties-installed-with-agile2__agile2.0_properties__entry__2} | Property | Usage | |-|-| | Draw Burndown Chart ideal line as a linear straight line com.snc.sdlc.scrum.pp.burndown.ideal.linear | Draws the burn down chart ideal line as a straight line. * Type: true\|false * Default value: false {#properties-installed-with-agile2__ul_pwk_ty1_xmb} | | Stories in any one of the states specified in this comma separated list will be shown in the progress board (in the order specified) com.snc.sdlc.scrum.pp.progress.story.states | Specify the story states using a comma separated list that should be shown in the story progress board. The states in the progress board follow the same order as specified here. * Type: integer * Default values in their order: * -6: Draft * 1: Ready * 2: Work in progress * -7: Ready for testing * -8: Testing * 3: Complete {#properties-installed-with-agile2__ul_m3v_sdr_gz} {#properties-installed-with-agile2__ul_hcv_vy1_xmb} | | Tasks in any one of the states specified in this comma separated list will be shown in the progress board (in the order specified) com.snc.sdlc.scrum.pp.progress.task.state | Specify the task states using a comma separated list that should be shown in the progress board. The states in the progress board follow the same order as specified here. * Type: integer * Default values in their order: * -6: Draft * 1: Ready * 2: Work in progress * 3: Complete {#properties-installed-with-agile2__ul_pst_f2r_gz} {#properties-installed-with-agile2__ul_nft_5y1_xmb} | | Enable the Actual Hours field for scrum tasks com.snc.sdlc.scrum.pp.task_uses_actual_hours | Enable the Actual hours field in the Scrum Task form. Displays actual hours of tasks on the task progress board. * Type: true\|false * Default value: true {#properties-installed-with-agile2__ul_tkr_ty1_xmb} | | The default sprint length (in days) used if the length cannot be calculated from the sprint. com.snc.sdlc.scrum.pp.default_sprint_length | Specify a default sprint duration that should be used when creating a sprint, if the sprint length cannot be calculated from the sprint. * Type: integer * Default value: 14 {#properties-installed-with-agile2__ul_d3w_ty1_xmb} | [ ] {#properties-installed-with-agile2__agile2.0_properties}