In Portfolio Manager terms, moving EA project elements from branched to planned is a significant step. It is the point at which the solution goes from ‘we’re just thinking about it’ to ‘this is probably going to happen’.
Promoting to planned can be done for a complete project, or for individual elements. When elements are promoted to planned they are moved from the project package into the model staging package. Elements that were ‘branched to retire’ will also be moved into staging, and be promoted to ‘planned to retire’.
Impact on your project
When elements are promoted to planned, then you are confirming that modeling of these elements is complete. We think that is a good time to put them under change control.
Change control means that any future changes you need to make to these elements will be modeled in a new, ‘change’ project, with it’s own project package and new branches taken from your planned elements. The ‘change’ project will then progress through the complete Portfolio Manager lifecycle. This is our recommended approach.
However, if instead you move these planned elements out of staging and back into your project to continue changing them, you may cause problems for other projects – particularly if they were prompted to branch from your planned change – see below. Chaos may well ensue. You have been warned!
Impact on other projects
When your project changes become planned then all other projects that have branched the same baseline elements that you are changing will see that they are now working on out-of-date information. They will be advised to use your planned elements instead of the baseline elements that will be replaced.
The go-live (implementation) date for planned elements is shown in generated Portfolio Manager views. Element roadmaps and time machine diagrams are based on this date information and show how your project changes will impact the model at future dates.