Components installed with Agile Development 2.0
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.
Demo data is available for this feature.
Roles installed
| 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 |
| 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 | - scrum\_sprint\_planner - scrum\_story\_creator - scrum\_user |
| 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 | - scrum\_release\_planner - scrum\_story\_creator - scrum\_user |
| Scrum release planner\[scrum\_release\_planner\] | Users with this role perform release planning activities. A release planner can create and manage: - Themes - Products - Releases | - scrum\_user - scrum\_story\_creator |
| Scrum sprint planner\[scrum\_sprint\_planner\] | Users with this role manage the sprint process. A sprint planner can create and manage: - Stories - Sprints | - scrum\_user - scrum\_story\_creator |
| 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 | - rm\_scrum\_task\_admin - scrum\_user |
| 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 |
| 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 |
| 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 |
Tables installed
| 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. |
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 and Performance Analytics Content Pack for Agile 2.0.
Parent Topic:Agile Development 2.0 reference
Properties installed with Agile Development 2.0
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.
| Property | Usage |
|---|---|
| Draw Burndown Chart ideal line as a linear straight linecom.snc.sdlc.scrum.pp.burndown.ideal.linear | Draws the burn down chart ideal line as a straight line.- Type: true\|false - Default value: false |
| 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 |
| 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 |
| Enable the Actual Hours field for scrum taskscom.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 |
| 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 |