This article explains the different use cases for plan types in OnePlan. Your organization may follow the examples here, or your plan types may be completely unique. Plan Types are important in OnePlan as the different tools can be utilized at each plan type or level.
When creating a new plan, you will first select the plan type. The form and which features are available will be based off the field type selection.
The first method is to have a flat hierarchy, where the plan types are not related to each other. For example, Enterprise Project (where perhaps the budget is over 1 million dollars) and Small Project (which have budgets less than 1 million).
The second method is to build out a hierarchy of plans where there is a parent to child lookup relationship between the plans. This structure is useful for tree grid visibility & data roll up. For example, Portfolios and then under the portfolios, we have children Value Streams, and then under the value streams, we have children Epics, and then under the epics, we have children Features.
The third method is to have a blend. You may have a hierarchy, such as Portfolios & Programs, and then at a child level have multiple different plan types that are equal in their level to each other. Such as Waterfall Project (for projects managed with traditional waterfall scheduling & details), and also Agile Project for project teams who follow an agile or lean management process).
When creating a new plan, you will be prompted to first select plan type. If there is a hierarchy of plan types, you would go to the parent plan type in the Portfolios page and select a child plan type.
Each plan type may have a different form, and in each form, there may be different sections, fields, stages/steps, and different planning modules enabled or not (i.e. Financial Planner, Resource Planner, Scheduler, etc.)
Please sign in to leave a comment.