Agile request management
This section explains how to manage Dimensions CM requests in a Dimensions CM integration.
Note: Agile request management doesn't support external requests from other providers mapped in Dimensions CM.
Requests are used to track and approve the changes your team is making.
A request is a single unit of work, equivalent to a story in Agile planning, that can report a defect, suggest an enhancement, or detail other work for a particular product. You use story points to estimate the size of a request.
For details about using Dimensions CM requests, see Work with requests.
Each request type has a lifecycle assigned to it that determines which users may work on the request. For information about request lifecycles, see the Dimensions CM Administration Console online help.
The request catalog displays all the requests in a Dimensions CM product or stream. You can open a request and view its information. For details, see View the request catalog.
Backlogs enable you to organize your team’s work and group requests into a prioritized hierarchy of epics and features.
Backlogs are located at the product level in PulseUno. You can view a backlog as a hierarchy or a flat view.
An epic is a large unit of work that is typically broken down into smaller units of features and requests.
Epics, features, and requests can belong only to one backlog, but you can move them between backlogs. Epic and features are optional and you can plan a flat backlog that contains only requests.
The following figure displays the backlog structure with epics, features, and requests.
For details about backlog planning, see Plan and manage a backlog.
An iteration is one development cycle, commonly known as a sprint, which is typically a few weeks.
An iteration includes the requests your team are confident they can complete during the sprint. As an iteration progresses, the remaining effort required to complete the requests should decrease.
For details about managing iterations, see Plan and manage an iteration.
Iterations are located at the product level in PulseUno. You can view an iteration as a list or a card wall.
The Content tab displays the content of an iteration in a flat list and includes the following information:
- What requests are being worked on.
- For each request, its rank order in the iteration, title, effort, current state, and owners.
- The progress of the work; the effort, in story points, required to complete each request.
Tip: You can show or hide request labels and closed requests.
On a Card Wall tab, each card displays information about a specific request such as:
- Which team member is working on it.
- The request’s story points.
- If the request is blocked.
- The number of days the request has been in its current state.
- A badge indicating its review state and the health of the changes.
Cards are grouped in rows by request type with a separate column for each lifecycle state. Each request type displays the number of requests that are blocked, hidden, and unassigned.
A card wall also displays metrics about the progress of the current iteration:
|In progress||Story points remaining to be completed (as a number and percentage).|
|Iteration end||The number of days left until the iteration ends.|
|Done||Requests completed (as a number and percentage).|
|Burndown chart||Displays how much work remains to be done in the iteration and helps to predict when the work will be completed.|
|Burnup chart||Displays how much work has been completed and the total amount of work.|
For details about customizing the card wall view, see Use a card wall.
The History tab displays changes made during an iteration, for example, requests that were added.