The entire Tempo platform is aimed at people: plan for people, reports on how people perform etc..
What I'm looking for (and suggest) is to extend the planning to include capabilities. Take the regular demand cycle: You get a new request in and you need to evaluate it. In early stages you'll want to plan the capabilities needed for an demand request: I need 4 man days of API programming, 3 man days of the infrastructure team, 7 days of front-end programming, etc....
In the current Tempo system one can only translate this to people that have a specific role. But for long term planning this is not optimal. As it might be that the person you thought of for the task is no longer available or even works for your team (company).
My suggestion is to extend the planning to capabilities which later on can be mapped to actual users that have these capabilities at the time you're actually ready to start implementing the demand request.
Thanks!
Jacques Schoofs
Senior Certified Atlassian Consultant
atSistemas
Jacques Schoofs
| Tempo Products | Tempo Planner |
| Tempo Platform | Cloud, On-Premise |
We Will be using T-I-177 to provide updates on Server version of this feature.
After a successful trial period in our TempoLab Early Access Program, we’re excited to announce a new feature for our Planner cloud customers - Generic Resources. This new feature allows customers to assign generic (unnamed) resources to tasks and plans, either as a standalone placeholder in Planner or as part of Tempo Teams, when the owner has yet to be identified.
This much-requested new feature makes planning future activities more accurate, even when full details are still to be decided.
You can read more about assigning generic resources in our Help Center.