The Impact Analysis view shows you the impact of changing a group of element, of a whole project.
Scores and explanations
Impact Score (per project)
Shows the impact of ‘branching’ an element
Another project, or projects are thinking about changing this element as well. Action: You should talk to those projects to find out why you are both thinking about changing the same thing.
Newer planned version
Another project has already created a ‘planned’ version of this element.
Action: you should branch from that newer, planned version.
In the Impact Analysis view, in the left hand pane, choose ‘Replace with newest planned’ and the Implemented element will be replaced with most recent planned version. If you are branching, PM will then create a branch from this planned element.
Branched to retire in another project
Â Another project is thinking about retiring this element.
Action: You should talk to someone on that project before creating a branch: they are thinking about retiring something, and you are thinking about changing what’s there already. Maybe remove the element from the list.
Planned to retireÂ in another project
Another project has a plan to retire this element.
Action: We strongly suggest you don’t create a branch. Instead, in the right-hand pane, choose ‘Remove from list’ and no branch will be created. If you do create a branch, Portfolio Manager will warn you that you are branching from a version of the element which will soon be out-of-date.
Shows the impact of ‘promoting’ an element
Branched by project
Another project has a branch o this element.
Action: If you go ahead and ‘promote’ this element, then that project’s branch will be from the older version. It should be part of your project process to tell that project what you have done, before they discover it for themselves using the Impact Analyzers on their own project.
Planned by other project
You are trying to make ‘planned’ an element which already has a planned change. As this would create two parallel ‘planned’ elements, Portfolio Manager will not allow this.
Branched to retire
Another project has a ‘branched-to-retire’ version of this element. You should talk to them before you promote this element
Planned to retire
Another project is planning to retire this element.
PM will not allow you to promote this element.
Shows the impact of implementing these elements
Planned element branched in another project
Another project has already taken a branch of the element you are going to ‘implement’.
This is fine: the branch will still be connected with the newly implemented element. Shown as an impact just for information