The budget page allows you to enter all expenses and all team positions you expect the folio will require during its lifespan. Expenses are added to one of three main categories: Operational expenditures (OPEX), Capital expenditures (CAPEX) or Financial expenditures (FINEX). The section on categories explains each one in detail. Planned expenses can be single occurence or recurrent ones. Positions are the team members you will need to accomplish the work, such as developers, testers, team leads, etc. and are added to the operational expenditures. Information entered here will be used to provide project health metrics on the Overview page and shown as a reference on the Forecast charts.

Expenses

Expenses correspond to amounts spent to attain the objectives of the portfolio. They can belong to any of the three categories described in section Categories: OPEX, CAPEX or FINEX. Expenses can be single occurrence, or they can be recurrent. Recurrent expenses can also be amortized; in which case the amount associated with the payment will be evenly split on the payment period. Expenses should represent all money that you plan to be spent during the folio's time frame, such as rents, maintenance contracts, software license purchases, loan financing costs or mortgages.

See Budget Expense for more information

Positions

Positions are the salary expenses you plan the folio will incur at one point or another. They are operational expenditures. Positions are grouped by title (e.g. Developer, Architect, Q&A). You can collapse (or expand) a group of positions by clicking the triangle icon ( ) next to a position title.

Example of positions could be J2EE Developer 1, System Architect, Test Automation Specialist, etc.

See Budget Position for more information

Scope Inspector

The scope inspector allows you to view the break down of the portfolio's scope in user stories, bugs and other types of issues that your project is associated with and see if the budgeted positions match the effort required for that scope.
It will actually answer questions such as:

Are the budgeted salaries sufficient to implement the planned features of our cool application?
How much required effort has been estimated for the planned scope? How much to fix the known bugs?
What's the maximum effort a person can possibly provide given the current portfolio's time frame?

In the Budget page, clicking the scope Inspector button brings that information in the details panel on the right.

Details
Scope Inspector	Display portfolio scope panel
X	Hide the scope panel
	Clicking on information icon will show you online definitions of elements displayed
Saved filter	Clicking on Saved Filter link display the all JIRA issues included in your portfolio
Max. Effort/Person	Indicates the maximum regular hours for a single person within the portfolio's dates.
Planned positions	Indicates the total number of positions currently planned in the budget
Planned Effort	Indicates the total number of hours currently planned in the budget
Breakdown By Issue Type
Issue Type	Issue Type
Count	Total number of issues by type
Earned Value Field	Total number of earned values by issue type Note that this column will not be display if earned value field is "Original Estimate"
Original Estimate	Total original time estimate by issue type

On this page:

Categories
Expenses
Positions
Scope Inspector

Related pages:

Browser not supported