Using Agile

Using Agile

What are the Effects of Deleting a User Story

If you are assigned to a product as a team member, you can delete a user story. When a user story is deleted, the following user story details are also deleted:

• Dependencies the user story requires
• Acceptance criteria
• Tasks that are part of the user story
• Comments

Deleting a user story has the following effects on Burndown charts:

• Any hours reported for tasks belonging to the deleted user story are deleted.
• The burndown chart guidelines are adjusted to reflect the hours or the deleted points. The adjustment is effective from the day the user story was deleted.
• The actual burndown and burnup lines show any points or hours for the deleted user story and its tasks.

How to Edit Multiple Backlog Items

On the Backlog page, you can update more than one item at a time. Updating in bulk is useful for editing a specific attribute across multiple user stories or issues instead of updating each item individually.

For example, use the bulk update to assign multiple items to a sprint or release. You can also use it to select an owner for multiple items at the same time.

When using bulk update, you can:

• Use Shift or Ctrl on your keyboard to select the backlog items to update.
• Select a maximum of 250 user stories or issues to update at a time.
• Assign an issue to a maximum of ten fix releases and ten affected releases.
• Select either user stories or issues for the bulk update. You cannot combine both types of items.
• Leave an attribute value as blank or as Select a Value to avoid updating the field for all the selected items.
• Change a field value to Unselected for all the selected items. For example, if you select Unselected for the Release attribute, no release is specified for any user stories or issues in the bulk update.

Follow these steps:

1. Click Agile, and from Planning, click Backlog.
2. Select the product name from the Product drop-down list.
3. Select multiple user stories or issues.
4. Right-click the selected items, and click Bulk Update. You can also click the Bulk Update button.
5. Edit the required fields.
6. Save your changes.

   The fields for each backlog item display the updated values.

How to Work with List Page Filters

List page filter lets you control what you view on the page. All filters that are created for a list page appear in the Filters drop-down list for selection. The current filter in use on the list page shows in the Filters field.

You can set up filters on the following pages: Home Page, Backlog, Epics, Themes, Teams, Products, Releases, Requirements, Features, Sources, and Personas.

For example, you can set a filter on the Backlog page to view only the unassigned and open stories.

Note the following points about filters:

• When you filter, the selection criteria remain in effect for the list page. If you leave the list page and return, the list is prefiltered with the selection criteria from the filter.
• You can create and save multiple filters. Any filter that you create is automatically saved.
• You can edit and remove filters that you have created.
• To override the filter criteria for the list page and show the entire list, click Clear Filter.
• Filters are saved across sessions per browser. If you switch to a different browser, reselect a filter to apply it.
• Filters are saved across sessions for each browser. If you switch to a different browser, reselect a filter to apply it.

Follow these steps:

1. Open the list page that you want to filter.
2. Click Add/Edit Filter, and select Create a new filter.
3. Define the Filter Name, and the filter criteria.
4. Click Add to define additional criteria.
5. Click Filter when you are done.

   The list page is filtered using the criteria that you defined, and the filter is saved automatically.

Note: To edit a filter, click Add/Edit Filter, select Show Existing Filters, and edit the filter criteria. Click Delete to delete a filter.

How to Configure and Edit List Pages

The list pages allow you to set up and manage your products. The setting for the number of records to display on a list page is persisted for each browser and for each user. If you view the same list in a different browser, set this value again.

You can add or remove the columns that are displayed on list pages. If you added custom fields (attributes) for an object, the custom fields are available to add to the list pages as columns.

For example, if you add custom fields for releases, the custom fields become available for the releases list page.

Review this information before working on list pages:

• Adding custom fields to a list is a customization. The changes are available only for the logged-in user across sessions.
• You can configure the list pages for each view. When configuring, the attributes are filtered based on the selected product. You can select from default and product-specific attributes.

Follow these steps:

1. Open a list page.
2. Follow these steps to complete the tasks:
   • Configure:
     • Click Configure, and move the required columns into or out of the Selected list.
     • Drag-and-drop or use the arrow keys to reorder the fields.
   • Restore Configuration Defaults:
     • Click Configure, and click Restore Defaults.
   • Edit List Page:
     • Click a list page field to edit inline.

     Note: When you change a field value, a small red triangle appears in the upper left of the field indicating the updated value.

3. Save your changes.

Note: Fields that cannot be edited in-place include fields that have more than one value. If you sort or group by a column field with multiple values, the sort function sorts for each of the values in the column field. You cannot edit the value of the field in-place because the changes affect multiple objects.

How to Recover Deleted Items

If you accidentally delete an item on a list page, you can recover it from the Recycle Bin.

Follow these steps:

1. Click Setup
2. Click Home and go to the Recycle Bin.
3. Select the desired items and click Undelete.

What are the Effects of Deleting a Team

A CA Clarity™ Agile user who has super user privileges can delete a team. When a team is deleted, the following changes take place:

• Team members are removed from the team.
• Any open user stories that are assigned to members of the team become unassigned.
• The team is no longer available to assign to items in the product.
• The team cannot be selected in the filter for velocity and burndown charts.
• Any team member whose only assignment was on the deleted team can no longer participate on the product (the product becomes view only).

You can view in charts the work the team members perform before deleting the team by selecting All Teams. You can still view detail pages for completed user stories and tasks.

What are the Effects of Removing a Scrum Team Member

A CA Clarity™ Agile user can remove a scrum team member, who is a member of the same product. After a team member is removed, the following changes happen:

• The team member does not display in any lists the scrum team filters and the member was removed from.
• For any burndown charts based on the owner, the guidelines and actual burndown calculations are adjusted to reflect the removal of the team member. Team burndown calculations are unaffected.
• Any user stories or tasks that were assigned to the team member become unassigned. The user stories and tasks that are already closed are not affected.

The team member cannot edit or manage user stories and tasks that are assigned to the scrum team from which they were removed.

What are Planned and Actual Values

Planned value is the estimated value for the scheduled work and actual value is the factual value for that effort. You can see planned and actual values for a product, release, or feature.

The following values are displayed on the list pages and on individual detail pages:

• Planned Cost
• Actual Cost
• Planned vs Actual Cost
• Planned Effort
• Actual Effort
• Planned vs Actual Effort

This information is aggregated from the planned and actual values present for the requirements that are associated with the product, release, or feature. The aggregated values are read-only and cannot be edited.

What is Feature Hierarchy

You can view the requirements that belong to each feature in the Feature Hierarchy view.

Follow these steps:

1. Click Requirements, and from Detailed Planning, click Features.
2. In the View field at the top of the list page, select Feature Hierarchy.

   The list of features displays with any associated requirements.

3. Click Expand All to display the requirements that are associated with the feature.

What is the difference between Requirements and Features

You can consider feature as a parent for the requirements. The requirements are the content that drives the feature.

For example, the product supports Japanese is a feature. The requirements will include details such as need to support double-byte characters, needs to support Japanese-formatted keyboards, online-help should be in Japanese.

How to Change the Product Owner

When you create a product, you are the owner of the product by default. You can however, change the ownership of the product to another user or add additional owners. The new owner gains the right to change the product details. Only a current owner or the creator of a product can change the details of a product.

Follow these steps:

1. Click Requirements, and from Detailed Planning, click Products.
2. Click Details in the Actions column for the product you want to work with.
3. Click Browse in the Product Owners field, and select a new product owner.
4. Save your changes.

How to Define a Competing Product

You define a competing product in the same way you define a product for your company. When a product is marked as a competitor, it becomes available for selection as a competitor you can associate with one of your products.

To define a competing product, create a product and make sure the Competitor check box on the Product Details page is selected.

What are the Effects of Deleting a Sprint

Only a person with super-user privileges or product owner can delete a sprint (the Delete button does not display for other users). Deleting a sprint has the following effects:

• All sprint data specific to the sprint is deleted.
• Any user stories that are assigned to the sprint become unassigned.
• Any teams that are assigned to the sprint are removed.
• The sprint does not appear in the list for burndown chart rendering.
• The sprint does not display in burndown charts.

How to work with the Virtual Wall

When planning and managing a sprint, team members generally manipulate cards representing user stories and tasks. The cards are tacked to a wall or large board and manually moved around to update status and details. The Virtual Wall enables you to manage your tasks graphically. Team members can view all user stories and tasks that are committed for the sprint. You can also view the user stories and tasks that are specific to the team and task owners.

User stories are shown in the ascending order of ranking and include task details and any impediments. The location of the card from left to right on the page shows the task status to the viewer. The default can be one of the following options:

• Planned
• In Progress
• Closed

Note: System Administrator can customize the task status from the Setup page.

The default card color is green, but each team can color-code their task cards by mapping them on the Team Detail page. Tasks that have impediments display the impediment icon with details in the tooltip.

Manage Tasks on the Virtual Wall

As a product owner or a product team member, you can create tasks on the Virtual Wall. If you are not a product team member, you can only view the Virtual Wall.

Follow these steps:

1. Click Agile, and from Sprint Tracking, click Virtual Wall.
2. Click New Task for the user story to which you want to add a task.
3. Enter the requested details.
4. Save your changes.

   A new task card is created on the virtual wall.

Note: To edit, delete, or create new impediment on the virtual wall, click the arrow on the task card, and click Edit, Delete, or New Impediment.

The Virtual Wall enables you to drag-and-drop tasks to update their status. Dragging a task to a new status changes only the status. Edit the task to update the hours that are completed on it to reflect the burndown accurately. However, when you drag a task to a Closed status, any remaining hours on the task are zeroed out automatically.

Set Virtual Wall Colors

When tasks display on the Virtual Wall, they are green. You can color-code the task cards on the Virtual Wall to display in different colors for each task status, or task type. You can map colors for only one set of criteria. Color mapping is team-specific and is set on the Team Edit page.

Follow these steps:

1. Click Agile, and from Resources, click Teams.
2. Click Edit for the team you want to work on.

   The Team Edit page appears.

3. In the Virtual Wall Colors section, select a color criterion: Status or Type.

   The values and current color sample for your selection appear. For example, for Status, a color sample appears for each task status (Planned, In Progress, Closed).

4. Choose new colors for your values.
5. Save your changes.

   Note: To see your new color settings on the Virtual Wall, be sure to set the Team filter to display the team you set the colors for.

How to work with Chatter

Chatter lets you communicate with others in your organization and exchange information in real time. Using Chatter, you can do the following:

• View your information, status updates of people you follow, updates to records you follow, and updates to groups in which you are a member.
• Create a chatter group that allows members to post updates and communicate with each other privately.
• Add attachments or links to a posting.
• Determine whether you want to follow a user or a record that has been enabled for Chatter.

You can modify the Chatter setup. For complete information about using Chatter, see the Salesforce.com Help & Training. This documentation is available if you click the Setup link to bring up Personal Setup. Then click the Help link.

Turn Following On or Off

You can follow information about the following CA Clarity™ Agile items using Chatter:

• Products
• Releases
• Requirements
• Features
• Sources
• User stories
• Tasks
• Issues

The Following option is enabled by default for items that you create. If you are not the creator of an item, the Following option is deactivated. But you can manually activate it.

You can tell if an item is followed by looking at the Following column on the list page.

Follow these steps:

1. Open the appropriate list page and locate the specific item in the list.
2. In the Follow column of the list item, choose one of the following options:
   • To follow the list item, click the green icon to the left of the word Follow.
   • To turn off the Following option for the list item, click the icon to the right of the word Following.