| Table of Contents |
|---|
...
2. On the right of the toolbar, click the Configure Data Sources icon. The data sources configuration opens.
...
3. In the Data Sources Configuration window, in the Data Sources tab, select Rally Software. The Step 2. Configure Source pane opens.
...
1. Configure credentials
The following information must be provided:
...
| Tip |
|---|
API Token vs. Password To ensure security you can use the "API Token" instead of a password for Rally Cloud. If a token is used login field should stay empty. How to generate API Keys in Rally - https://github.com/RallySoftware/rally-oauth-examples#api-key. |
...
Default credentials
If you enter an URL that coincides with any URL from Default Credentials, no password/login is needed. For more information, see PERF Administration.
Check connection
...
2. Distribute workflows
Workflows represent processes on your project and give you control over the project's progress. PERF simplifies workflows by distributing each of them into three different buckets.
At this step issue statuses pulled from Rally Software project are to be distributed into 3 buckets: To Do, In Progress, and Done.
To Do: for statuses meaning the item is not ready for development.
In Progress: for statuses meaning the item is in development.
Done: for statuses meaning the item satisfies the "Definition of Done" criterion in a project.
...
Change is applied immediately, data load is unnecessary.
For more details, see Include Sub-Items into Metrics Calculation.
Workflow updates type
Rally workflows could be changed and then a new status could be added or removed the existing one. To manage changes in the configuration you can choose between automatic and manual workflows update.
Workflow Updates Type | Description |
|---|---|
Automatically | If any Rally workflow was changed, then the PERF application after next data load does the following:
|
Manually |
|
...
3. Configure scope management
This section describes how to configure scope management for Rally data source.
Definition of ready
Is used to configure what work items are considered to be ready for development for the project, so the affected metrics are calculated correctly.
...
| Expand | ||||
|---|---|---|---|---|
| ||||
|
Definition of work buckets
Configure what issues are considered as features, defects and debts on the project.
...
| Expand | ||
|---|---|---|
| ||
5. Configure on-time delivery targets
This step is necessary of you wish to use metrics to monitor commitments fulfilment, e.g. all critical bugs are fixed within 24h after reporting.
...
PERF Attribute | Default Rally Software Field | What It Affects | ||
|---|---|---|---|---|
Epic | Parent | Capacity widget: roll-up of reported time to the epic level in the report for downloading | ||
Estimation in Original Hours | "Estimate" as an original estimate, "To do" as a remaining estimate. Assumption | Metrics measured in hours: Effort variance, Workload, Velocity: Committed vs Completed in hours, | ||
Estimation in Story Points | PlanEstimate Applicable for: Defect, DefectSuite, UserStory (HierarchicalRequirement). Non-applicable for: Tasks, Portfolio Items. | Metrics measured in story points: Velocity in story points, scope metrics, | ||
Fixed release | Release | Metrics by release: Velocity by release, scope metrics by release, Bug Growth by release, | ||
Priority | Priority (applicable only for Defects) | Target Fulfillment charts by priority, Open Bugs Over Time by Priority | ||
Severity | Severity (applicable only for Defects) | Target Fulfillment charts by severity | ||
Sprints | Iteration | Metrics by sprint: Velocity by sprint, scope metrics by sprint, Bug Growth by sprint,
|
Specific features of Rally entities
...