2024 December Release

Scrum CenterPermanent link for this heading

The scrum center allows defining general settings that apply to all subordinate scrum projects. Additionally, the team members of a scrum center either have special access rights on the scrum projects or can be assigned to the scrum projects as team members.

DashboardPermanent link for this heading

The dashboard is divided into following areas:

  • Scrum Projects
    Shows all scrum projects that belong to the scrum center.
  • Product Versions
    Shows all product versions of the scrum center. Product versions can be assigned to backlog items. Navigate in the widget to create a new product version.
  • Forms and Categories
    Shows the available forms and categories.
    Note: To be able to store forms and categories from a different context, you must adjust the Restrict Shortcuts Within Teamroom field in the configuration settings accordingly.
  • Processes
    Shows the available custom processes.
  • Templates
    In the create dialog (e.g. “New” context menu command in a Teamroom) the templates are displayed according to the grouping by the template categories.
  • Text Modules
    The defined text modules can be inserted into Word documents.
  • Report Templates
    Shows the available report templates. Report templates can be defined as BIRT or Excel reports. The Scope of Analysis field defines where the action for generating the report is displayed and which data can be included in the report.
  • Thesauri
    Shows the thesauri in which terms for tagging of scrum artifacts can be managed. At least one thesaurus has to be created so that the tagging can be used. The default thesaurus for new terms is defined in the settings of the scrum center. Thus, new terms can be created directly in the tagging process. If no standard thesaurus is specified, only the predefined terms in the thesauri can be used.

SettingsPermanent link for this heading

A scrum center provides following settings.

“General Settings” TabPermanent link for this heading

  • Name
    The name of the configuration.
  • Subject
    Defines an additional description of the configuration.
  • Mindbreeze InSpire Service
    Defines the Mindbreeze InSpire Service that is used for classification.
  • Access Protection
    Defines the access protection of the scrum center.
    • Default: Only the defined scrum center members can access the scrum center and its content.
    • Generally readable: Everyone can read the scrum center and its contents, but searching is not possible.
    • Restricted: Only scrum administrators and privileged users have access to the members of the scrum center. Typically, this setting is used, if the scrum center contains several scrum projects of different partners. This way the partners cannot see the users who are defined in the scrum center.
  • Restrict Shortcuts Within Teamroom
    Defines which type of shortcuts may be stored in the configuration.
  • Restrict the Downloading or Opening of Content on the Device
    Allows to restrict team members who can open or download content at the device.
  • All Team Members May Add Members
    Defines whether all team members can add users to the team or only team members with full control.
  • Restrict Team Members
    Defines the organizations, organizational units, teams and external organizations whose members may be added to the configuration.
  • Enable Advanced Mode
    Advanced mode includes, for example, working with multiple shelves, as well as managing templates and presettings.
  • Main Administrator
    Defines the user who will receive the automatically generated e-mail messages concerning the configuration. Otherwise, all scrum center administrators receive the e-mail messages. The user is also listed as contact in case of missing permissions.
  • Support Team
    The support team handles the organization-internal management of support requests in the respective context.
  • Activate Trace Output
    For example, if you are a form designer using expressions for calculation or validation, it can sometimes be difficult to identify errors in the expressions. To simplify analysis, you can write trace output to the web browser console cooobj.Trace("string"); or cooobj.Trace("string", value);).
  • Organization
    Shows the organization the scrum center is assigned to.

“Scrum Center” TabPermanent link for this heading

  • Short Form
    The short form is used as prefix for the backlog item ID. If left empty, it is enforced that each scrum project defines its own short form.
  • Take Over Product Versions From Scrum Projects
    Defines whether product versions that are created in scrum projects are automatically added to the scrum center. This applies only to product versions created after enabling the setting.
  • Use Product Versions Only From the Scrum Center
    Defines whether only product versions that are defined in the scrum center can be used in backlog items. Specific scrum projects can be excluded.
  • Projects With Own Product Version Management
    Defines projects that may specify their own product versions, if Use Product Versions Only From the Scrum Center is correspondingly configured.
  • Allow Story Points for Defects and Impediments
    Enables the Story Points field also for defects and impediments.
  • Prevent Changes of Closed Backlog Items
    Defines whether the contents of closed backlog items can be changed.
  • Require Unique ID per External Application
    Defines whether the ID for external applications has to be unique.

“Feature Administration” TabPermanent link for this heading

  • Enable Capacity Planning
    Defines whether the capacity planning is enabled. If enabled, the effort for each task can be defined. Additionally, the amount of available hours of each team member can be specified per sprint.
  • Unit for Effort Tracking
    If the capacity planning is enabled, the unit for effort tracking is “hours”. If disabled, it is set to “man days”.
  • Enable Defects Reports
    Allows generating a daily defects report as PDF. In the Report Settings you can for example specify the generation time, the included scrum projects and the recipients.

“Predefined Values” TabPermanent link for this heading

  • Processing Stages
    A processing stage (e.g. “Implementation”, “Quality Assurance”, “Documentation”) can be assigned to a task. If all tasks of a processing stage are done the story will turn to the next processing stage. The order of the processing stages is defined by the order in this field.
  • Defect Severities
    Defects may be classified by their severities.
  • Affected Applications
    Affected applications may be assigned to backlog items.
  • External Applications
    Defines a set of external applications. Scrum artifacts can define an ID for these applications. Based on this ID external applications can process the scrum artifacts.
  • Environments
    Environments (e.g. Linux) may be assigned to backlog items.
  • Impact Areas
    Impact areas (e.g. GUI) may be assigned to backlog items.
  • Hierarchy Levels
    Hierarchy levels (e.g. software layers) may be assigned to backlog items.
  • Administrative Categories
    Administrative categories may be assigned to backlog items.

“Structuring” TabPermanent link for this heading

The defined terms in the following fields can be used to structure the corresponding scrum artifacts.

  • Topics for Structuring Backlog Items
  • Topics for Structuring Tasks
  • Topics for Structuring Sprints
  • Topics for Structuring Time Tracking Entries
  • Topics for Structuring Reasons of Defects
  • Topics for Structuring Causes of Defects

“Tagging” TabPermanent link for this heading

The defined terms in the following fields can be used to tag the corresponding scrum artifacts.

  • Terms for Tagging Stories
  • Terms for Tagging Defects
  • Terms for Tagging Impediments
  • Terms for Tagging Tasks
  • Terms for Tagging Sprints
  • Terms for Tagging Versions
  • Terms for Tagging Releases

“User Interface” TabPermanent link for this heading

  • Prevent Time Entry Editing
    Defines whether time entries can be changed later on.
  • Additional Required Fields
    Defines fields that are mandatory.
  • Additional Locked Fields
    Defines fields that cannot be changed.
  • Enable Checkboxes for the Following Fields
    Defines fields that only allow selecting predefined values.
  • Allow Single Selection Only
    Fields defined in Enable Checkboxes for the Following Fields can be restricted to allow selecting only one value.

„Logos“ TabPermanent link for this heading

The defined logos and background image are used for the scrum center and for all personal dashboards.

Note: If the personal dashboard is assigned to several configurations, the logos and background image will not be applied.

“Default Values” tabPermanent link for this heading

  • Default Thesaurus for New Terms
    If a default thesaurus is specified, new terms can be created directly during tagging.
  • Default Categories
    When an object is created, the specified category is assigned according to the defined object class. In the Apply to field, you can specify whether the setting applies to instances, templates, or both.
  • Default Processes
    When an object is created, the specified process is assigned according to the defined object class or category. In the Apply to field, you can specify whether the setting applies to instances, templates, or both.
  • Default Background Tasks
    When an object is created, the specified background tasks are assigned.

ActionsPermanent link for this heading

  • Create Scrum Project
    Creates a new scrum project. The settings in the scrum center will be inherited by the scrum project.
  • Translations
    The “Translations” action can be used to export or import a CSV file containing the multilingual names of the customizing objects. This enables an external translation.
  • Authorize Team
    Defines the users of the scrum center. A description of the different roles can be found in chapter “Roles”.
  • Settings
    Opens the settings of the scrum center.

Download PDF

Download PDF