Manage the definition and development of large products through project portfolios.
A portfolio is a new iceScrum workspace that will help you manage the development of a big product with several teams. In particular, it is relevant when the product cannot be divided into valuable sub-products that could be managed independently.
Portfolio teams must be “feature teams” that are able to complete features independently. Each feature team is associated to its own iceScrum project and the projects are aggregated under the portfolio.
If you have any doubt about the relevance of the portfolio in your context or the meaning of the words used in the previous sentence, please refer to the dedicated documentation.
All the portfolio features are packaged into a single App that is enabled by default if you have a Business Cloud subscription or an Enterprise / Corporate On-Premise license. Business and Enterprise plans are limited to 1 portfolio / server, while the Corporate license gives access to unlimited portfolios.
You can create a portfolio from scratch, in which case you will be offered to create the associated projects and teams in the portfolio wizard.
You can also add existing projects to a portfolio. To do so, you must be either Product Owner of the Project, or Owner of the team the project belongs to.
A project can only belong to zero or one portfolio. A portfolio can’t have more than 10 projects for its functionalities to be usable under proper conditions.
Portfolios are always private: they can only be seen and updated by their explicit members.
Members of a portfolio can have on of these two roles:
Business owner: full permissions on the portfolio.
Stakeholder: read-only access on the portfolio.
The portfolio roles grant permissions on all the projects of the portfolio:
Business owner: get Product Owner permissions on all the projects.
Stakeholder: get Stakeholder permissions on all the projects.
To learn about the details of these permissions, read the dedicated documentation. If the portfolio members already have explicit roles on the projects and their teams, these roles are not changed. The permissions of their team / project roles will be merged with the ones granted from their role at the portfolio level.
The main business item manipulated at the portfolio level is the feature. In a regular iceScrum projects, features are ordered by the Product Owner according to the current business priorities. However, when the project is part of a portfolio, such decisions are taken at the portfolio level. That is why a regular Product Owner cannot update the order of the features in a project that belongs to a portfolio. They need to be Business Owner of the portfolio to do so.
The portfolio dashboard allows adding custom widgets in the same fashion as your user home. The widgets that list projects will be limited to the projects of the portfolio.
The “features” view of the portfolio shows all the features of each project, each project being associated with its own feature team.
Portfolio members can thus get a good overview of the distribution of features across the feature teams. Business owners can create feature inside projects and reorder features inside each project in order to materialize their business vision.
The feature details give access to the stories of each feature. Thus, you can good as deep as needed in the business item trees.
The Portfolio workspace it still at its early stages. We have a lots of things in our backlog:
Feature sandbox: suggest and order features in a sandbox before they are dispatched to a feature team and affected to a project.
Release train: synchronized sprints and release across the projects of a portfolio.
More widgets in the dashboard with portfolio specific functionalities.
Shared Definition of Done across the projects of a portfolio.
We would be glad to here any feedback about the current portfolio features, the ones in our backlog or maybe some we did not think about! Please write to our support email address.