Skip to main content

Hi 

I’m interested in how users of the legacy CRI functionality are capturing their portfolio level risks, that are not connected to programmes or projects? 

We have a requirement to capture Portfolio level risks, which could be stand alone risks to the portfolio, and escalated risks from programmes and projects. Currently we're only using the legacy CRI functionality and keep portfolio level risks in an excel outside of Planview, which means that we need to manually collate the full portfolio risks.

We’ve considered having a project entity that represents the portfolio, to allow us to capture risks but this doesn’t feel like a good long term solution. 

Has anyone else achieved this in Planview Portfolios? 

Many thanks

​@Louise Goodsir CRIs can only be associated with a Project/Work Entity, so you proposal to use a dummy project is the only option.
Logbook addresses this limitation by allowing you to have a “Logbook” and create Logs (CRIs, etc.) at any level in Strategy.

Appreciate that some customers are waiting for Logbook to have a workflow/process management capability, but there is already big value in Logbook over CRIs and today Logbook gives you the ability to see the whole history of changes to attributes and fields, like Status.

Reply


Terms of UseCookie settings
All Data Subject Access Requests (DSARs), and requests of “Do Not Sell My Personal Information” according to the CCPA, must be submitted through the Planview DSAR portal located here

Planview has appointed a Data Privacy Officer (DPO) to be responsible for overseeing our Privacy Management Program and related privacy compliance measures. DPO can be contacted at privacy@planview.com