Content
View differences
Updated by Klaus Zanders 10 months ago
As a project manager, program manager and portfolio manager
I want to see the sums of the budgets of my projects to be related to each other in the project list
So that I can have a better overview of where the money is distributed don't need to do this manually.
**Acceptance criteria**
* We allow to set a fixed amount on a budget without planning material and labor costs. This allows for an easier allocation of money. For example on the top-level budget we do not plan explicit labor, but instead we just assign a lump sum of money.
* We can define relations between a project's budget with other budgets from the project hierarchy.
* Top-down approach: The parent budget has money in it and money is taken out of that parent's budget and allocated into the child budget.
_This can be used when we know the budget for the entire project hierarchy in advance and want to distribute money to its sub-projects._
* Bottom-up approach: The parent does not have any money allocated to itself. Instead the money that is "in" the parent budget is the calculated sum of the children's planned budgets.
_This can be used when we know the budgets for each individual sub-project but do not know the overall budget._
* Those approaches can also be combined. (_TBD: Add a screenshot that visualizes this_)
* In the project lists there are additional columns:
* `Budget`
* `Total budget` (including sub projects)
* `Costs`
* `Total costs` (including sub projects)
* `Percentage complete`
* `Total percentage complete` (including sub projects)
* `Work`
* `Total work`
* `Remaining work`
* `Total remaning work`
**Out of scope**
* New permissions
* Sub totals in the project lists
<br>
> For <mention class="mention" data-id="65732" data-type="work_package" data-text="##65732">##65732</mention> , we need to show information about , among others, budgets inside the portfolio/program. Right now, budgets are isolated inside projects, so we need to aggregate information about them.
> e.g.,:
> \- Inside a program, aggregate spent budget vs total budget
I want
So that I can have a better overview of where the money is distributed
**Acceptance criteria**
* We allow to set a fixed amount on a budget without planning material and labor costs. This allows for an easier allocation of money. For example on the top-level budget we do not plan explicit labor, but instead we just assign a lump sum of money.
* We can define relations between a project's budget with other budgets from the project hierarchy.
* Top-down approach: The parent budget has money in it and money is taken out of that parent's budget and allocated into the child budget.
_This can be used when we know the budget for the entire project hierarchy in advance and want to distribute money to its sub-projects._
* Bottom-up approach: The parent does not have any money allocated to itself. Instead the money that is "in" the parent budget is the calculated sum of the children's planned budgets.
_This can be used when we know the budgets for each individual sub-project but do not know the overall budget._
* Those approaches can also be combined. (_TBD: Add a screenshot that visualizes this_)
* In the project lists there are additional columns:
* `Budget`
* `Total budget` (including sub projects)
* `Costs`
* `Total costs` (including sub projects)
* `Percentage complete`
* `Total percentage complete` (including sub projects)
* `Work`
* `Total work`
* `Remaining work`
* `Total remaning work`
**Out of scope**
* New permissions
* Sub totals in the project lists
<br>
> For <mention class="mention" data-id="65732" data-type="work_package" data-text="##65732">##65732</mention> , we need to show information about , among others, budgets inside the portfolio/program. Right now, budgets are isolated inside projects, so we need to aggregate information about them.
> e.g.,:
> \- Inside a program, aggregate spent budget vs total budget