Define Budget for the projects
You can define Project Budget in man-hours in the Project card.
Screen #1– “Project info”
Go to Pipeline and navigate into project info, and define an Approved budget, all the rest (Burned, Remaining work, Total expected work, Remaining budget) will be calculated automatically according to the uploaded data from the external system.
Screen #2– Project card (budget)
Define Budget for a set of tasks in MSP
1.1. To use budgets in your project you must “enable budget processing”->
Open in the pipeline the project info card (see the previous point) and turn on “Enable budget processing” in Advance settings mode.
The default settings to search for budget tasks in the MS-Project file are the “name” column where Epicflow looks for task containing the phrase “budget” (not case sensitive) in its task name. All other text is not mandatory.
1.2. In the example below, we created budget tasks for the resource group Engineering. The first “Budget for Engineering” of 500 man hours is defined at the top level of the project, meaning that any task or sub-budget assigned to the resource group Engineering or one of its resources is using this buffer. “Budget for Engineering Module 01” is an example of a sub-budget since it is part of a summary task of this project. Any task in this summary task that is related to the resource group Engineering eats out of this buffer of 100 man hours. In this example, you can see that one task of 30 hours is assigned to the resource Anne de Jong of the resource group engineering, and the other two task of 20 and 40 man hours are assigned to the Engineering group itself. In total 90 man hours.
1.3 The Remaining and actual work values of a budget task in MS-Project are calculated by Epicflow and updates when syncing the project.
For a buffer task in MS-project:
– The “Remaining work” denote the remaining buffer left. (10 mh in our example)
– The “Actual Work” is used to denote how much of the man hours is used from this buffer. (90 mh in our example)
Manual adjustment of the remaining or actual work is overwritten by Epicflow for budget tasks. Only changes in the Work column are taken into account for budget tasks by Epicflow.
Screen #3– Budget (MSP)
Define Budget for a set of tasks in Jira
1.1. To use budgets in your Jira project you must “enable budget processing”:
Open in the pipeline the project info card and turn on “Enable budget processing” in Advance settings mode.
The default Epicflow column for of budget task for Jira is “tag”. The “tag” column in Epicflow corresponds with the “label” field in Jira. In this label field, Epicflow looks for the budget mark text, “#budget” in our example.
Instead of “tag” you can also use “name” as an identifier for budget tasks. In that case, you have to use the budget mark text in the task name. Similar as with MS-project budget tasks.
Screen #4– Budget Settings (Project Card)
You can also define this setting for all project at the import page:
Screen #5– Import Page
1.2 To mark a task as a budget task one has to define a “#budget” in the label field as displayed in the example below. The group this budget is allocated to is #WebDev.
Screen #6– Budget (Jira)
1.3. You can define budget tasks at different levels:
- At Project level by defining a budget task that is not linked to an Epic or a Story
- At Epic level by defining a budget task that is linked to an Epic but not to a Story
- At Story level by defining a budget task as sub-task of a story
Similar to MS-project you can add hierarchy to budget tasks. See the MS-project example above.
Budgets in the task list
1.1 In the task list of Epicflow you can filter on the budgets and its related task in the “budget” column. The budget column describes from which budget the task consumes its budget.
When filtering on a specific budget, then all tasks that are directly related to this budget are showed plus the budget task itself. The budget tasks are marked by an orange dot before their task name.
Based on out MS-project budget example, we now filter on the “Budget of Engineering module 01” budget, resulting in our three tasks with 90 mh of work in total and the budget task itself.
Screen #7– Budget (Tasklist)
Note that for the buffer task (the task with orange dot):
- The 10 mh in the remaining column denoted the buffer left.
- The 90 mh in the spend column denotes how much of the man hours are used from this buffer.
- Spend and remaining are calculated automatically, you are only allowed to change the Total mh.
- These values are synchronized with the MS-project file. You see the same values in our MS-project file example.
1.3 Hierarchy of buffer tasks. The related buffer of the buffer task itself is “Budget for Engineering”. When filtering in the “Budget” column for all task related to engineering, you can see the hierarchy. If a buffer task is is at the top of the hierarchy (so it can’t consume from any other buffer) then you see [Budget] in the buffer column. See the example below.
Screen #8– Hierarchy of buffer tasks (Budget)
Define Budget for a multigroup
If your multi-group is defined in the external system, then you can also define a budget for a multi-group.
In our example, we defined a multigroup “Production” consisting of “Electric” and “Assembly”
Screen #9– Multigroup (Resource Management)
The idea of a budget for a multi-group is that maybe at the start of the project you reserve a total budget for “Production” and in a later stage you will specify who will use which part of the budget.
In our MS-project example this looks like this:
Screen #10– Multigroup Budget (MSP)
At the top level, we have besides our “Engineering” budget a budget for “Production”. All task assigned to Assembly or electric or at one of its resource “eat” from this buffer.