This is the documentation for an older version of Folio and has been moved to the Tempo instance.
Please view the Folio Category in the Tempo Products Wiki Categories for all versions of Folio's Documentation.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

The 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 chart.

Categories

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 classify expenses in their appropriate category so that you can later get relevant information about the categories themselves, like the total planned cost for all capital expenses.

Operational expenditures (OPEX)

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. 

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.

Financial expenditures (FINEX)

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

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 the Expenses page for more information on expenses and how they are calculated.

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

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.

Scope Inspector

The scope inspector allows you to view the breakdown of the Folio's scope by issue type (user stories, bugs, etc.) and see if the planned positions have a capacity that matches the effort required for that scope. It will help you answer questions such as:

  • Are the planned salaries sufficient to implement the planned features of our 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?

Clicking the Scope button brings up that information in the details panel on the right.

 

Details
Scope Inspector

Shows or hides Scope Inspector.

XHides the Scope Inspector.

Inline Help. Clicking on the icon opens up an inline dialog containing definitions of elements displayed in section.

Saved filterClicking on Saved Filter link displays all JIRA issues included in your Folio's scope
Capacity per PersonA single person's capacity in terms of regular working hours given the Folio's timeframe and the Working Schedule configuration.
Planned positionsTotal number of positions currently planned
Planned EffortTotal number of working hours currently planned
Breakdown By Issue Type
Issue TypeType of issues (User Story, Task, Bug, etc.)
CountTotal number of issues by type
Earned Value Field

Sum of the Earned Value Field for all issues of given type. Will not be display if earned value field is Original Estimate.

Original EstimateSum of Original Estimate for all issues of given type.

 

 

  • No labels