(total # of resource hours allocated to project/total # of technical resources to be assigned to project/projected start date/projected end date) For instance, from a technical standpoint: If you can get everyone on the same page and using your documentation system for determining all of these aspects of the management cycle, then you could use the comments section at a high level to delineate timelines, resources, and whatever else you can fit into your abbreviations. If you simply MUST use Asana, my best advice would be to develop a syntax/system for adding comments to Asana tasks that are meaningful to time, resources, etc.
ASANA AND OMNIPLAN FREE
Free for teams of up to 10 team members - This one only offers a free 60-day trial, but is one of the best I've ever used
There are some great free options that might get you closer to where you want to be than Asana. My honest opinion would be, if possible, use another agile project management tool other than Asana. Its tools for resource allocation and management are also almost nonexistent.
However, it lacks features that make it a great tool for keeping track of a very high-level view of pending, current, and past projects. Asana really excels at tasks creation and outlining, especially when you've already honed in on a specific project. In my opinion, Asana is a great tool for keeping track of TASKS, but not terribly robust at keeping up with project management requirements as a whole. I have used Asana, as well as several other tools, on multiple projects. With Asana at our core, how can we manage resource allocation and project stacking at a high level for an effective master project schedule? Unfortunately, while the "Notes" section of each event is flexible, it does little to remedy calculating effective scheduling. I'm currently using a "Master Project Schedule" Calendar on Google Calendar to outline the project roadmap using tags such as "" for projects we are waiting to get signed. However, these are too detailed for our agile and lean work environment. I've played around with OmniPlan and have experience in MS Project. It's worked so far, but as my team grows, it may not be the best long-term solution. As a result, our team is reliant on input from team members as to how projects will stack. The need for this is important since we do multiple projects at the same time. However, as project coordinator, Asana has poor support for overall project management features specific to resource allocation and stacking. We love the flexibility and ease-of-use Asana offers. We're very agile and lean focused and therefore our project plans are changing all the time. My team uses Asana for all of our project communications and task management.
0 kommentar(er)
