The planned cost Planned Costs 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 occurrence 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 Costs Forecast chartschart.

Anchor
BudgetCategories BudgetCategories

Categories

Folio FOLIO uses a classic categorization of expenses to better structure your budget. Every expense planned in a budget belongs to one of three main categories: Operational expenditures (OPEX), Capital expenditures (CAPEX) or Financial expenditures (FINEX).  Each of these categories will be shown only if it holds at least one expense in it for a given budget. Once a category is displayed on screen, you can collapse it or expand it by clicking on the triangle icon ( ) next to the category name.

You should define classify expenses in their appropriate category so that you can later get relevant information about the categories themselves, like the total planned cost planned for all capital expenses.

Anchor
OPEX OPEX

Operational expenditures (OPEX)

 Operational Operational expenditures are all non-capital expenses incurred during normal operation.  They are the day-to-day expenses required during the execution of a project, such as the salaries, rent, insurance, electricity, and computer maintenance contracts. They do not include physical assets or loan financing for example.  All positions added to a budget are automatically added to the OPEX category. 

Anchor
CAPEX CAPEX

Capital expenditures (CAPEX)

Capital expenditures are used by an organization to acquire or upgrade physical assets with a useful life extending beyond the taxable year.  Examples of capital expenses are purchase of a computer, photocopier or building.

Anchor
FINEX FINEX

Financial expenditures (FINEX)

Financial expenditures are usually interest expenses, such as loan financing, credit card interest, etc. 

Anchor
Expenses Expenses

Expenses

Expenses correspond to amounts spent to attain the objectives of the Folio.  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 Planned Expense the Expenses page for more information on expenses and how they are calculated.

Anchor
Positions Positions

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 Planned Position the Positions page for more information on positions and how their cost is calculated.

Anchor
IMPORT IMPORT

Import / Export

FOLIO Allows you to import or export your data in CSV (comma separated values) format.

Importing Planned Expenses

To import data from an

existing CSV file, click on the

...

button and select

Import data

. Alternatively, you can

type the keyboard shortcut

i to open the import dialog. See Importing Data from CSV and Planned Costs Importing Tips to

learn more about importing

Planned expenses.

Exporting Planned Expenses

To export data to an external

CSV file click on the

...

button and select

Export data

. Alternatively, you can

type the keyboard shortcut

x to instantly export Planned Expenses. Exported CSV file includes both budgeted positions and expenses.

See Planned Costs CSV Export Detail

to learn more about Planned expenses export.

Anchor
SCOPE SCOPE

Scope Inspector

The scope inspector allows you to view the break down breakdown of the Folio's scope in by issue type (user stories, bugs and other types of issues that your project is associated with and , etc.) and see if the budgeted positions match planned positions have a capacity that matches the effort required for that scope.
It will actually help you answer questions such as:

• Are the budgeted planned 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 Folio's time frame?

In the Planned page, clicking the scope Inspector Clicking the Scope button brings up that information in the details panel on the right.

Image Modified

Details
Scope Inspector	Display or hide Folio scope panelShows or hides Scope Inspector.
X	Hide the scope panelHides the Scope Inspector.
	Inline Help. Clicking on information icon will show you online the icon opens up an inline dialog containing definitions of elements displayed in section.
Saved filter	Clicking on Saved Filter link display the displays all JIRA issues included in your folio	Max. Effort/Person	Indicates the maximum regular hours for a single person within the folio's datesFolio's scope
Capacity per Person	A single person's capacity in terms of regular working hours given the Folio's timeframe and the Working Schedule configuration.
Planned positions	Indicates the total Total number of positions currently planned in the budget
Planned Effort	Indicates the total Total number of working hours currently planned in the budget
Breakdown By Issue Type
Issue Type	Issue TypeType of issues (User Story, Task, Bug, etc.)
Count	Total number of issues by type
Earned Value Field	Total number of earned values by issue type Note that this column will Sum of the Earned Value Field for all issues of given type. Will not be display if earned value field is "Original Estimate".
Original Estimate	Total original time estimate by issue typeSum of Original Estimate for all issues of given type.