In order to use Tabsters correctly, it is important to understand how Tabsters structures your projects.
Tabsters enables you to manage your data simply and intuitively, in real time, with the various players involved in your project.
To help you manage your projects correctly, Tabsters offers a 5-level project representation.
These different levels are represented in Tabsters by the different icons you'll find on each card(see images below).
These icons give you an indication of the level you're at.
The highest level of project representation is the Business line (or project portfolio), which corresponds to a grouping of projects.
This is followed by the Project level, the workpackage which is a grouping of actions, but which is also the only level in Tabsters' project representation that is optional, i.e. you don't need to add a workpackage to your project if you don't need all 5 levels.
Then there's the Action level, which corresponds to deliverables and which can replace the workpackage level as a direct child of your project if you don't wish to have one, and finally the lowest level, which is the Task level, which can be controlled by a resource in order to inform the burned on it as part of time tracking management.
In addition to these 5 levels of project grouping, there are other levels for grouping these different elements along a transverse axis.
This axis can be the location of your project, its nature or even its type.
This transverse grouping provides a matrix vision of your projects, ordered according to the criteria mentioned above, among others.
There are also global axesproject portfolio global, projet global...), enabling you to group together different portfolios, projects, etc. without them necessarily being part of the same grouping.
The values of these axes can be defined by yourself within the application if you have the rights to access the Environment module (unitary right only given to key users).
Last but not least, Tabsters also lets you manage your various project stakeholders by grouping different resources into teams, corresponding to the different project stakeholders.
These teams and resources can also be grouped according to the cross-functional axes mentioned above.
