Content
View differences
Updated by Rosanna Sibora 3 days ago
**Outcome**
Adopting structured planning practices in OpenProject stops being a configuration task and becomes a one-click decision. Teams who would not have invested time in setup can now benefit from the same board-based planning that more experienced users have configured manually. Best practices are embedded in the product, not locked in individual users' institutional knowledge.
**Use Cases** Use Cases
* Usage of pre-configured whiteboards for planning session.
* Adding pre-configured whiteboards to dashboard, e.g. risk management.
**Background**
A powerful, flexible board is only valuable if people actually use it. For many users, the blank-slate configuration experience is the barrier. They know they want to do PI planning or a risk review, but they don't know which attributes to map to which axis, what filters to apply, or how to label their lanes. The result is that they fall back to external tools — spreadsheets, whiteboards, sticky notes - and the planning outcome never makes it into OpenProject.
Pre-configured templates solve this by encoding the answer to "how do I set this up" directly into the product. A team lead who has never run a PI planning session in OpenProject can select the PI planning template, point it at the right projects, and have a working whiteboard in front of their team within a minute.
Adopting structured planning practices in OpenProject stops being a configuration task and becomes a one-click decision. Teams who would not have invested time in setup can now benefit from the same board-based planning that more experienced users have configured manually. Best practices are embedded in the product, not locked in individual users' institutional knowledge.
**Use Cases**
* Usage of pre-configured whiteboards for planning session.
* Adding pre-configured whiteboards to dashboard, e.g. risk management.
**Background**
A powerful, flexible board is only valuable if people actually use it. For many users, the blank-slate configuration experience is the barrier. They know they want to do PI planning or a risk review, but they don't know which attributes to map to which axis, what filters to apply, or how to label their lanes. The result is that they fall back to external tools — spreadsheets, whiteboards, sticky notes - and the planning outcome never makes it into OpenProject.
Pre-configured templates solve this by encoding the answer to "how do I set this up" directly into the product. A team lead who has never run a PI planning session in OpenProject can select the PI planning template, point it at the right projects, and have a working whiteboard in front of their team within a minute.