Content
Updated by Niels Lindenthal 4 days ago
**As** a project manager, portfolio manager and program manager
**I want to** see the budgets on my Overview page
**so that** I easily get an overview of the financial plan and status.
**Motivation**
* Understand how much budget was planned, spent and is available.
* Make the project overview more useful and engaging.
* Improve onboarding
* Reduce churn
**Acceptance criteria**
* Widget shown only if Budgets module is activated in the project.
* Case 1: Single project only
* Total actual costs (€)
* Total planned budget (€)
* Spent budget (%)
* Remaining budget (€)
* Budget by cost type (€/pie chart)
<img class="image_resized op-uc-image op-uc-image_inline" style="width:269px;" src="/api/v3/attachments/785565/content">
* Case 2: Aggregation for portfolios, programs and sub-projects
* Show the number of sub-elements (34 projects in this portfolio, 10 projects in this program, 5 sub-projects in this project)
* To be evaluated: Can we use stacked bar charts to illustrate information for multiple projects
* What happens with very many projects?
* High difference between large projects and small projects?
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/785564/content">
**Technical notes**
* We stick to the chart libary chart.js <br>
**Permissions and visibility considerations**
* _We use the existing permissions._ _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* Changes to the budget module.
* Include this information in the API (separate work package).
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** see the budgets on my Overview page
**so that** I easily get an overview of the financial plan and status.
**Motivation**
* Understand how much budget was planned, spent and is available.
* Make the project overview more useful and engaging.
* Improve onboarding
* Reduce churn
**Acceptance criteria**
* Widget shown only if Budgets module is activated in the project.
* Case 1: Single project only
* Total actual costs (€)
* Total planned budget (€)
* Spent budget (%)
* Remaining budget (€)
* Budget by cost type (€/pie chart)
<img class="image_resized op-uc-image op-uc-image_inline" style="width:269px;" src="/api/v3/attachments/785565/content">
* Case 2: Aggregation for portfolios, programs and sub-projects
* Show the number of sub-elements (34 projects in this portfolio, 10 projects in this program, 5 sub-projects in this project)
* To be evaluated: Can we use stacked bar charts to illustrate information for multiple projects
* What happens with very many projects?
* High difference between large projects and small projects?
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/785564/content">
* We stick to the chart libary chart.js
**Permissions and visibility considerations**
* _We use the existing permissions._
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* Changes to the budget module.
* Include this information in the API (separate work package).
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._