Allocation
The actual or planned workload of the individual resources or a Team. The effort expressed as the time or number of Story Points required to complete a task is evenly distributed over the task's duration.
...
The App uses them to replace non-issue Jira entities (like Components, Versions, and Projects), which it cannot recreate in Jira while cloning the scope.
Box
The most essential element of the App. Boxes are high-level task containers arranged into a hierarchy.
A Box is a container for tasks - tasks can come from external tools, such as Jira and Trello. Basic tasks are native to the App and don't exist anywhere outside of it.
Each Box has its configuration (security settings, scope, modules). Boxes lets you perform various actions and visualize data depending on the setup.
Box hierarchy
A tree structure consisting of a Box root (parent node) and Boxes (nodes). Each node can potentially have a different Box type.
The hierarchy is presented in the Hierarchy and Timeline modes of the Overview module and the Box Switcher.
How the hierarchy can be arranged depends on Box type settings - possible parents are defined for each Box type. Additionally, scope type settings validation is performed when a Box is created or moved. A box is a customizable structured space (container) where you organize and visualize your project, program, and portfolio elements, such as tasks, deliverables, resources, risks, and even other boxes (sub-boxes).
Boxes are equipped with all the essential tools for efficient management, allowing you to adapt seamlessly to various project management approaches, including Agile, scaled Agile, Hybrid, and Waterfall. You can also customize them to support unique methodologies that do not fall into any of those categories.
Each box can be customized based on the specific tools (modules) needed for your project, the scope of work, and the security roles required for viewing and managing the box.
...
Box hierarchy
Box hierarchy is a structured system for organizing and managing the various elements of projects, programs, and portfolios.
At the top of the box hierarchy is the Home (root) box, which acts as a container for all the boxes created within your organization. Boxes created under the root can also house additional boxes (sub-boxes).
All those boxes form parent-child hierarchies, allowing you to view and aggregate project, program, or portfolio data at both high and low levels. You can view the entire box hierarchy in the Overview module using the Hierarchy and Timeline modes.
By default, only specific box types can serve as parents to other box types. However, you can redefine the parent-child relationships between your boxes and sub-boxes to create custom hierarchies that align with your business needs.
The sub-boxes can inherit specific settings from their parents or have a separate configuration.
...
Box type
Box template, which defines the most relevant characteristics of a Box (node), such as:
types of parent Boxes under which a Box of a given type can be nested
default module configuration and names
default column view of different modules
default card layout
default Period mode
Box types can be defined by BigPictures administrators. Read more here.
...
Box module
The following modules are available in BigGantt:
Overview
Gantt
The following modules are available in BigPicture:
Overview
Gantt
Risks
Roadmap
Board
Calendar
Resources
Teams
Most of the modules can be preconfigured using Box types.
Box switcher
...
The box switcher, located in the upper-left corner of the application, displays the name of the current Box you are viewing. When you click it, a drop-down list containing the Box hierarchy tree is displayed. You can then select a specific Box from the hierarchy to switch to.
...
The Box switcher is displayed in the Apps header for each module and in the WBS Widget and Skill Widget, which can be added to the issue screen.
Box status
...
The status of the box determines your ability to modify the box details or adjust the box configuration.
...
Not started - gray
In progress - blue
Done - green
Capacity
The App calculates individual and team capacity.
The capacity of your resources is calculated based on Workload Plans and non-working days resulting from Holiday Plans and individual /wiki/spaces/BIGGANTT/pages/315393385. It reflects the workload resources are capable of after everything has been considered.
Column views
Column Views allow you to add different fields as columns to the task list and configure their display and aggregation settings, which determine how data is presented in the Gantt and Scope type module's task list.
...
Original Estimate Mode - this mode shows the planned workload versus the resource capacity.
Remaining estimate mode - use this mode to show workload history (Spent time) and the remaining workload versus the resource capacity.
Story points mode - use this mode to show the planned workload versus resource capacity expressed in Story Points.
Gadgets
Thanks to the Gadgets, you can add dynamic content to a Confluence page or the Jira application dashboard to monitor the health of projects, departments, or specific processes. This means that you can have your favorite Gantt charts and Risks all in one place and thanks to the auto-refresh all up to date.
There are three Gadgets available:
Holiday plans
A calendar that reflects the non-working day reduces the capacity of Teams or individual Resources (Team members).
Inheritance mode
When creating a new Box type or moving a sub-Box to a different parent Box, thanks to the Inheritance mode, the Box type configuration can be passed on from the upper-level Box type to the sub-Box type.
...
Any Jira issue with the "Risk probability" and "Risk consequence" field values.
"Risk consequence" and "Risk probability" fields must be added to your Jira screen configuration scheme.
Risks module
The risks module consists of two main elements:
Customizable risk heat map
Customizable risk list (register)
You can configure a risk heat-map. The heat-map can be used to show the level of risk resulting from the risk assessment by considering the category of probability or likelihood against the category of consequences or severity.
You can define a name for the Risks axis and set the corresponding custom in the Configuration of the App.
Scenario mode
With the Scenarios feature, you can quickly try out different variants of your plan, compare the results, and find the best one.
All task changes are stored in the Scenario history, and you can easily undo them. When you create a scenario, changes made to your tasks are synchronized with Jira or other connected tools, such as Trello, only after merging.
Scope
A defined collection of tasks makes up the Box Scope. In general, tasks can be manually added to the scope or automatically synchronized with Jira or connected tools such as Trello.
In "Scope definition," you can specify what range of tasks is included in the scope of a given Box - those are the tasks you will be able to work within the Application (visualize them on a Gantt chart, manage Risks, distribute workload, etc). The App gives you much flexibility; you can include multiple Jira projects, simultaneously include tasks from different external tools (such as Trello and Jira), or include only some tasks that meet your particular specifications. The flexibility of the setup ensures that a Box can be configured to contain precisely the tasks you need to fit your work.
...
A short guide to security settings, access, and roles can be found here.
Skills
The skills are defined at:
The task level - skill required to complete a task. The related effort is used to calculate the skill demand and is evenly distributed over the task's duration. The skill demand will be displayed in the Resources module's Skill panel.
The resource level - skill acquired by the resource. The resource’s time is allocated across different skills. Skills weigh most in the "Perfect match algorithm," which is approximately 80%.
Each skill has a start and end date so that you can plan the skill development over time.
Skills Panel
Skills Panel is a part of the Resources module. It displays a comprehensive li ‘ of skill.’ Only the tasks displayed on the Resource Grid (within the visualized period) are considered. The skill effort is included in the calculation for any task that is at least partly displayed.
...
Any Jira issue, Trello card, or Basic task (native to the App).
Team
The team module lets you group individual users into teams, enabling effort-based planning.
The concept of teams is used mainly in the Resources, Objectives, and Board modules, but since the information about the team can be stored as a label or a custom field, it can also be displayed using the Gantt, Scope, or Risks module by adding it to the Column View or Card View.
You can create global teams and assign them to multiple Boxes. Once created, you can easily give them to individual Boxes (a team is inherited and can't be edited on a Box level) or duplicate them in a personal Box (a team configuration is duplicated and can be further edited).
Team Capacity
The capability to achieve a set amount of productivity within a single day is calculated as the sum of Team members' capacities. Team capacity factors in the existing manpower are known to readily possess the necessary skill set and the number of hours in a workday.
Calculating individual capacity considers team members' availability across all teams they're a part of.
Team code
Team code identifies teams by the App's modules and, when synchronized, the Host and connected platforms. Depending on the configuration, the Team code is stored as the following fields:
...
Team Member Availability
You can set availability for each team member (what percentage of their working hours is assigned to the team). Availability impacts the capacity - if a team has four members, and each is given 50% of their eight-hour day to the team, the team capacity for a day is 16 hours (if no other non-working days detract from capacity).
Timebox
Timeboxes define consecutive timeframes used for work planning. It helps to think of them as, e.g., sprints, iterations, increments, or stages.
...
A calendar that reflects specific working hours of an individual resource and is the basis for capacity calculation of Teams or personal Resources (Team members). Workload plans are used to define exact working hours. You can create as many as you like and assign them to your resources separately.