If you need assistance in setting up CA Agile Central Portfolio Manager, consider investing in CA Agile Central onsite services.
CA Agile Central Portfolio Manager Overview (Video)
CA Agile Central
Portfolio Manager Overview
Plan for Portfolio Management
Before you do any portfolio management in CA Agile Central, there are some important concepts to discuss with your organization. Understanding how your organization models your portfolio and identifying the terms you use to talk about it are essential for producing your portfolio in CA Agile Central.
Cultural and Organization Changes
What agile portfolio management needs from upper levels of the organization is leadership. The first change necessary to transition the organization culturally is to move away from command-and-control management and allow teams to self-organize. See this blog for more information.
For example, internally at CA Agile Central, large mother strategies are presented to the organization each year. Desired outcomes for the business are planned and shared company-wide. The departments and teams analyze what portfolios of
and projects can be proposed to achieve our goals. Teams trust that leadership around strategy will be provided, while the upper levels of the organization trust that teams will provide execution.
Design your Portfolio Process
Acting on new information enables your business to exploit opportunities, mitigate risks, and maximize value delivered. Portfolio steering helps your organization to easily shift
, adjust focus, and even stop initiatives that are no longer the best investments.
Modeling your portfolio in CA Agile Central may involve redesigning all or part of your portfolio management process to emphasize value delivery, strategic alignment, and smart steering. CA Agile Central coaches can help you implement these process changes and can help you facilitate your portfolio planning and steering events. CA Agile Central's coaches can guide you in this process and helps you reflect it in CA Agile Central Portfolio Manager. Contact your sales representative for details.
Contact your CA Agile Central account representative at [email protected] to schedule an Agile Portfolio Steering workshop.
Set up CA Agile Central With Your Administrator
Your organization has its own terms for categorizations and levels of strategic work and sizing. In CA Agile Central, we represent a specific initiative or
. When you are ready to begin using CA Agile Central Portfolio Manager, you will need to name and configure some aspects of portfolio items and projects with your administrator.
Set up Your Project Hierarchy
Important! Before you create a new
, carefully consider the fact that rollups and reports are performed within a specific workspace. The information to rollup or
on—such as projects,
(including portfolio items), and fields— must be stored in the same workspace. For that reason, CA Agile Central strongly recommends you limit the number of workspaces you create.
There are two types of projects:
For product companies or Independent Software Vendors (ISVs), use a strategy project to represent a product or an area of a product.
For Information Technology (IT) organizations, use a strategy project to represent a system, subsystem, or a multi-year
Create portfolio items in strategy projects.
Use an execution project to represent a scrum team, a
team, or a group of such teams.
The portfolio item hierarchy models your portfolio where each level represents a different type of strategic goal. The higher types of the hierarchy represent goals to bring to market over a longer period of time. The lower types of the hierarchy represent more discrete items of market value.
The two default portfolio items types are Initiative and Feature. You can create additional types but we recommend no more than three types.
The lowest level always represents what fits in a delivery
). If you follow the Scaled Agile Framework, that level is Feature. If you follow other scaled agile processes, you can rename this level to fit your taxonomy.
If delivering a marketable value typically takes less than a development release in your organization, then we recommend keeping the default two levels of portfolio items.
If delivering a marketable value typically takes longer than a development release in your organization, or if you want the option of accelerating marketable value by having multiple teams work on delivering the market value within a delivery timebox, then you want to add a third portfolio item type, and your portfolio item hierarchy would look something like:
Marketable Feature (or Minimal Viable Feature, or Minimal Marketable Feature)
In that case, the level above the Feature level tracks marketable features may take several releases to deliver market value, each release implementing pieces of marketable features.
is a budget or investment area that a portfolio item supports. Define a list of investment categories possible for a portfolio item. Each portfolio item can be associated with one investment category.
field represents the size that you think your portfolio item may be. You may identify as many sizes as you like, and for each you must provide a name and numeric value. CA Agile Central coaches advise using relative point sizes. These values will be used in future planning features to help you schedule portfolio items into a timeframe.
You can specify a value or
for each portfolio item. The
is a number that indicates the worth of the portfolio item. The risk score is a number that indicates the chances you will take in bringing the portfolio item to market.
The numbers you use for value and risk scores should have meaning for your organization. Consider using numbers that may be multiplied or graphed in a CA Agile Central
to provide more insight in prioritizing portfolio items. You can use a
to track textual risk assessment.
As with other CA Agile Central work item types, you may add custom fields to portfolio items. These fields display in the editor for each portfolio item regardless of its type. Consider the information that is essential to track for your portfolio that isn't already part of the portfolio item structure.
Ensure that users in your projects have the correct permissions, so they may view and edit work items as needed.
For PMO, program managers, and product managers:
Set editor permission on strategy projects (where portfolio items are created)
Set view permission on execution projects
Set editor permission on execution projects
Set view permission on strategy projects you want engineering to see
Note that once a Level 1 portfolio item is accepted to flow through a team, you want to relocate that Level 1 portfolio item to be in the execution project. The execution team can then add user stories to the portfolio item. This applies to any project tree structure.
Use the hierarchy apps for a way to manage hierarchies using
Adopt Portfolio Kanbans
Portfolio Kanbans visualize the value creation workflow at the Feature level, and track your governance and investment planning at higher levels. The Kanban displays the rank and progress of portfolio items, each column mapping to one of the portfolio item
values. You can also add the Portfolio Kanban app on your dashboard or create a custom page that contains multiple boards and other information. You can
and compare new portfolio work with the app.
Need more help? The CA Agile Central Community is your one-stop shop for self-service and support. To submit feedback or cases to CA Agile Central Support, find answers, and collaborate with others, please join us in the CA Agile Central Community.