You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Persona-based journeys through TeamForm features and the options for usage with links to config to set things up according to the option selected.
https://teamform.atlassian.net/wiki/x/4wBwQg
https://teamform.atlassian.net/wiki/x/AYDeng
https://teamform.atlassian.net/wiki/x/FQDrQg
| TeamForm Feature | How it helps | Reference Guides |
---|
1 | Simple tags | “Move to” and “Added” tags - To indicate who both at a person and team level has moved around since the baseline snapshot was taken Role & skill tags - Shows who has what roles and/or skills so that it becomes easier for supply leads to assess who is best situated with the right skill sets to be allocated out against the various demand requests
| |
2 | Tags with attributes | |
3 | Placeholder Roles | | |
4 | Financials | Budgets can be loaded against supply teams based on the budget/target they give to each of the demand teams Rate Cards - Daily rate cards against capability teams can be applied to provide a high level view of how much a particular request and/or team structure costs
| |
5 | Configurations | Planner search bar configurations - gives flexibility to control whether users can search how the Planner looks between baseline vs future members Requirement box - a configurable box that can specify to demand leaders the specific type of request information they need to provide when submitting the demand request
| |
6 | Planner | | |
7 | Team Builder | | |
8 | Forecast | | |
9 | Data Integration | Rates and budget importers can be used to allow drag and drop of data files to update rates and/or budgets Approved requisitions can be brought into Planner and be included in the baseline so that demand and supply leads can have the latest information on what has already been pre-agreed
| |
10 | Reporting & Dashboard | | |
11 | Notifications | | /wiki/spaces/CBA/pages/2692612097 |