@ - A - B - C - D - E - F - G - H - I - J - K - L - M - N - O - P - Q - R - S - T - U - V - W - X - Y - Z
A record of all actions made on a task. Activity is ordered by date/time and lists the resource who made the change.
A code used to identify an application or user used for authentication when integrating applications.
Billable time and expenses
The hard or soft allocation of resources to a project.
Burn up chart
The process of forecasting the gap between supply and demand to determine if you have sufficient resources to take on or complete a project at an organizational level.
The budget type of a project that has an associated revenue cap which exerts a revenue constraint from the Program to the projects.
Someone you are doing a project for. This can be internal stakeholders, departments or external clients.
A resource or user who is no longer active within the platform.
The process of measuring the number of resources required to meet the demand for various types of work.
A horizontal bar chart devised by Henry Gantt that is used by project managers worldwide to visualize project schedules. It includes all of a project’s tasks, milestones, and deadlines, and illustrates task dependencies.
Users with limited platform access that must be invited and fall under a client's profile.
An allocation type that represents the confirmed need for a team member. Hard allocations will be taken into account when calculating the team member's availability and utilization.
The visual representation of your resource utilization (Schedule People) or your project scope (Schedule Projects).
A bill or list of detailing services provided with a statement of the sum due.
The third highest level of user access. Manager's can view/edit their team's work, time registrations, schedule, and reports. Managers can also view revenue but do not have access to costs in financials.
Manual Revenue Recognition
A feature within Revenue Recognition that allows users to input their own revenue recognition amounts per month and in turn re-calculate the estimated percentage complete of the project
Registered time that is not directly linked to a specific project. Some examples could be, sickness, vacation, meetings, workshops, etc. Non-project time is also known as non-billable time.
The person responsible for creating and managing a project or a task.
The level of access assigned to a particular Forecast user. There are 5 default permission profiles: Admin, Controller, Manager, Coordinator, and Collaborator.
A phase is a phase of the project where a specific and significant event occurs. Any given project will always have at least one phase. In agile projects, a phase can also be used to define dates for releases. Releases typically happen when one or more sprints have resulted in the product having enough value to outweigh the cost to deploy it. Phases can also be referred to as Milestones.
A visual representation of all the stages a project goes through from start to finish.
A placeholder represents a generic resource demand on a project, is defined at the role level, and is used instead of allocating a team member to a project until the project is won.
A program is a group of projects that accomplishes strategic business goals by enabling the user to view overarching financial information for the projects that fall under.
The user responsible for creating and managing Programs.
A user who can only view but not interact with Programs.
An endeavor that is undertaken to create a unique product, service, or result. A project has a defined beginning and end in time, and therefore defined scope and resources.
The manager of a specific project.
A project stage defines where the project is in its life-cycle. In Forecast, the possible stages are pre-defined as Planning, Running, Halted and Done.
A system of identifying projects by applying color to visualize the state of the project. Project status can be identified using the R-A-G acronym (Red, Amber, Green) making it very easy for the projects at risk or in trouble to be identified and action taken.
The remaining time of a project or task based on the forecast setup, supported by Forecast's machine-learning technologies.
An individual or member of your project team or organization.
The way in which you acquire and allocate individuals as required for a project.
Revenue recognition is a generally accepted accounting principle (GAAP) that stipulates how and when revenue is to be recognized. The revenue recognition principle, using accrual accounting, requires that revenues are recognized when realized and earned, not when cash is received.
The name of the position assigned to a resource that is defined by skillset and job requirements.
A list or display of all projects, phases, allocations and tasks. Forecast has two schedules. Schedule People and Schedule Projects.
The range of requirements. These include both functional and non-functional customer requirements, as well as technical team-generated requirements.
Show/Hide (Eye icon)
The specific traits or competencies of an individual.
An allocation type that represents a tentative need for this team member. Soft allocations are not taken into account when looking at a team member's availability in the scoping or sprint pages but will appear in the heatmap calculation.
An iteration (cycle) of work. Typically 1-4 weeks.
An X-Y axis graph that shows the number of tasks that need to be completed (on the vertical axis) versus the time remaining (on the horizontal axis).
A meeting about what the team will do during the next sprint.
Anyone with an interest in the project’s success, including your boss, customers, team, investors, etc.
An additional step inside of a task.
A piece of work that needs to be completed. A task may also be referred to as an issue.
An overview of all tasks created.
A member of the organization, and / or a member of a project.
An overview of registered time on each task.
A feature available for tasks in Scoping to allow bulk task updates.
A label or reference that can be applied to identify a task. Forecast tasks include 4 indicators: High Priority, Bug, Non-billable or Block.
A graphical representation of a sequence of events. In Forecast, a project's Timeline is represented by a heatmap.
The amount of time logged or entered on a task to record work that has been completed.
The record of hours worked by an individual or by the organization.
A budget type associated with a Program. A program of this type does not have an associated overarching budget.
A user is a person who is able to login to Forecast.
This is your personal view of what's up front. It includes all of your tasks, sorted by overdue, this week, next week, and future.
The total amount of work assigned to a resource as compared to their availability/working hours.
An overview of the workload of all resources for a given time period. Utilization report is based on task or project allocations made in Schedule People.
An analysis of the speed at which the project actually progresses compared to the estimates. A velocity of 1.00 or 100% means that it is going according to the plan. Below 1 means it's going slower, while above 1 means it's going faster.
A "mock" or "ghost" team member that is primarily used for planning, testing, integrations.
A percentage assigned to an opportunity stage project based on the chance the project will be won.
The indicator of where a task stands within the project. Forecast offers 3 standard workflow status: To Do, In Progress and Done. Users can create additional, custom workflow statuses to suit their process and working style.
Article is closed for comments.