Creating roadmaps consists of the following topics:
- Must have a type value assigned to them
- May only have parents of the next-higher type in the
, you cannot skip levels
- May only have children of the next-lower type in the hierarchy; if there is no lower type of portfolio item, then children must be
- Cannot have defects,
suites, test cases, tasks, or other associated
except for attachments and discussions
Create a New Portfolio
If you are creating a new portfolio that you have not previously modeled using CA Agile Central's
hierarchy, here are a few options to help you get started quickly:
- Import portfolio items from a CSV file
- The CSV import for portfolio items does not allow automatic parenting—use the bulk chooser in the
Tools menu to multi-select.
- Create portfolio items from the Portfolio Items page for each type
- Create portfolio items from the Portfolio Items page for the highest type, then add children going down the hierarchy until you reach the lowest type in the hierarchy
Once you have created your portfolio item hierarchy, you may create new user story children from a portfolio item of the lowest level type, or you may parent existing user stories to a portfolio item of the lowest level type. You may bulk parent a group of portfolio items. Learn more.
Your portfolio is administered at the
level. You cannot share a portfolio or its contents across workspaces.
Portfolio items, projects, and custom fields cannot be shared or rolled up across different workspaces. We recommend that you limit the number of workspaces you create.
Create Portfolio Items
You can create a portfolio item from most pages within the Portfolio
Follow these steps:
- Select the Portfolio tab, then select Portfolio Items.
- On the Portfolio Items page, select +Add New.
- Do one of the following:
- Enter a description in the New Theme field, then select Add. You can add details later.
- Select the Add with Details button.
- On the Create Portfolio Item detail page, complete all required fields.
- Complete any of the optional fields on the detail page.
- Select Save & Close.
Create a Portfolio From an Existing User Story Hierarchy
If you are creating a portfolio that you already modeled in CA Agile Central's user story hierarchy:
- Import portfolio items from a CSV file or create portfolio items from the Portfolio Items page for upper-level types.
- Convert a user story to a portfolio item of the lowest level type. The conversion process will move user story children to the portfolio item, and will keep the original user story in its pre-conversion schedule
along with any associated defects, defect suites, test cases, and tasks.
- Associate the newly converted portfolio item to its appropriate portfolio item parent.
- Ensure that only a single level of child user stories exist beneath your lowest level portfolio items. Do not use parent-child user story hierarchies when using a portfolio hierarchy.
Bulk Choose User Stories and Portfolio Items
Assign multiple user stories or portfolio items to a parent portfolio item in a single action with the bulk chooser. The chooser allows you to search by FormattedID, Name, and Parent fields. Bulk choosing allows for automatic parenting.
Follow these steps:
- Do one of the following:
- For user stories: On a lowest-level portfolio item detail page, select User Stories from the Collections ribbon.
- For portfolio items: On any level of a portfolio item detail page (except the highest level), select Children from the Collections ribbon.
- Select the Choose button.
- On the chooser, you can search by keyword or ID. You can also select your project by the drop-down menu to further refine results. Press Enter to search, or select a project from the drop-down menu to automatically filter results.
The search does not support wildcards.
- Select the checkboxes of the stories you wish to add and select Done.
If you do not have editing
to a user story or portfolio item, it will not be added. A brief message displays, listing the work items that could not be added.
If you choose a large number of children, it may take a few moments to load. You can monitor the progress of a large bulk selection from the number of user stories indicated in the ribbon.
Manually Rank Portfolio Items
If you have manual ranking set up in your workspace and you
a portfolio item on the
board in either the same column or across columns, CA Agile Central shows you where that card will automatically fall according to its manually entered
For example, if you have a portfolio item that is ranked second in the column according to its manual rank and you try to drag it up or down in the column, a green bar displays between the first and second cards—the only place it can land regardless of where you drop it in the column.
Drag-and-Drop Rank Portfolio Items
From the Portfolio Item summary page, you can drag-and-drop rank portfolio items.
Block Portfolio Items
You can block a portfolio item if you need to. When you a block a portfolio item, the portfolio item displays as blocked, but the associated work items remain unblocked. Blocking a portfolio item has no affect on the work items associated with that portfolio item, including parent portfolio items. When you block a portfolio item, you are prompted to enter an explanation for the block.
You block a portfolio item when viewing a card view such as Portfolio Item Kanban or
or a grid view like Portfolio Items. The following steps assume you are using the
Learn more about blocked work.
Follow these steps:
- Select Portfolio, Portfolio Kanban.
- Hover over the portfolio item card you want to block to view the editing options.
- Select the Block icon and enter an explanation for why the item is now blocked.
User Access and Permissions
There are no special permissions for CA Agile Central Portfolio Manager. Instead, user permissions for projects enable CA Agile Central users to create and change portfolio items, or to see portfolio items associated with user stories.
Consider creating a new project for your portfolio items if you do not want to co-locate them in a project where development teams have editing privileges (although this is no different than restricting access to organizing user stories in your user story hierarchy).
If you wish to create a new project for your portfolio items, make sure to locate it above the team projects in the project hierarchy so that users in lower projects can easily
up in the project tree views. If you have portfolio managers or other users who only want to track status and progress of portfolio items, give them view permissions for this project.
Portfolio Item Fields
||A system-assigned value. Select the ID of a portfolio item in the summary view to go to the detail view. You can change the portfolio item prefix.
||Enter a unique, meaningful name for the portfolio item. This is a required field.
|Portfolio Item Type
||Select a type for the portfolio item from the drop-down menu if the portfolio item has no parent or children. Otherwise, CA Agile Central will assign this value for you. For information on how to edit these values, see Manage Roadmaps. This is a required field.
||Select one or more tags to associate to the portfolio item. Assigning tags helps with sorting,
, and reporting.
||Enter a meaningful description to help other users understand the purpose of the portfolio item. Use the rich text editor to apply fonts, formatting, links, and more. You can copy and paste images in this field.
||Select Browse to upload any attachments, such as images or .pdf files that help describe the portfolio item.
||Specify the owner for the portfolio item. This value defaults to the user who creates the portfolio item, but can be changed at any time.
||Specify the project within CA Agile Central to which the portfolio item is assigned. This is a required field.
||From the detail page, select the Discussions link in the Collections ribbon to add or view discussions. Discussions has a rich text editor.
||From the detail page, select the Revision History link in the Collections ribbon. Revisions include a revision number, detailed description, date stamp, and author.
||Select the magnifying glass icon to assign a parent portfolio item. Select the red X to unassign a parent. A parent may not be assigned to a portfolio item of the highest type. A portfolio item can only have a portfolio item parent. A user story may have either a portfolio item parent or a user story parent.
||From the detail page, select the Children link in the Collections ribbon to view or add children to the portfolio item. Portfolio items of the lowest level type will see a User Stories link instead, since they can only have user stories as children.
||Use the Release attribute on the lowest level of portfolio item (typically referred to as 'Feature') to schedule a feature into a roadmap timeframe.
||Use this drop-down to filter portfolio items as they display on summary pages or Kanban boards.
|Tracking Indicators (summary page)
|% Done by Story Plan Estimate
||The value of this field is calculated by dividing the number of accepted points by the total user story points for user stories associated with the portfolio item.
|% Done by Story Count
||The value of this field is calculated by the number of accepted user stories divided by the total number of user stories associated with the portfolio item.
Hover over either of the % Done fields to see the number of accepted points and user stories. If these fields have a red warning flag in the upper-left corner, the callout describes the warning.
|Actual Start Date
||The earliest date an associated user story is moved to an In-Progress schedule state.
Actual Start Dates for portfolio items with work-in-progress before 11/19/2011 will be null until another associated user story goes into progress, then the Actual Start Date will reflect that user story's in-progress date.
|Actual End Date
||The latest date the final associated user story is moved to a Accepted (or later) schedule state.
||Specify the status of a portfolio item. This value also determines which state column on the Portfolio Kanban Board a portfolio item is located.
|State Changed Date
||The date on which a portfolio item moved from its previous state to its current state. If a portfolio item already has a state prior to 4/28/2012, the value is set to the current system date until the state changes again.
||Gauge the size of a portfolio item during planning.
||Enter an updated estimate during capacity planning as more is known about the features being planned.
||Assign portfolio items to an investment category to ensure they align with your organization's goals.
||Enter the value this portfolio item could bring to a feature or initiative. Use a score determined by your organization.
||Enter the potential risk to deliver the portfolio item. Use a score determined by your organization.
|Planned Start Date
||Enter the date you intend to begin work on this item.
|Planned End Date
||Enter the date you intend to finish work on this item.
||The Weighted Shortest Job First (WSJF) Score is a prioritization method that many Program Managers and PMOs use to choose which features to schedule soonest.
||Enter any relevant notes that will help team members understand the progress of the portfolio item. Notes display on callouts.