Asana vs Microsoft Project

• The best tools of Asana are found once we start a project, since the calendar that is integrated into our mail is super easy to use and we use it as a small agenda.
• The management of projects is incredible, the monitoring provided is one of the best in its category, since it facilitates group work.
• The creation and assignment of tasks, notifications and that each person can enter to work no matter where it is since it has a good mobile and web interface.

Read full review

• It is part of Office365 subscription. The look and feel is similar to other tools like excel. Helps in creating project plans, Gantt charts, work break down structures etc.
• Helps in resource allocation and tracking the projects. There is an option to use it to capture timesheets too.
• Helps project managers in producing weekly status reports and integrates well with other collaboration tools like Skype, sharepoint etc.

Read full review

• I wish it implemented easier with Outlook or Gmail. I would like for it to be easier to send tasks from email to Asana.
• I think there's room for improvement in terms of how easy it is to make new Section Headers for tasks and lists.
• I'd like for more aspects of the interface to be customizable.

Read full review

• Remote work can be challenging - as Project must be downloaded to a specific computer.
• Upgrading to the top of the line version can feel like a requirement. There is a lot of functionality that is not available unless in the most expensive pay-tiers.
• Microsoft Project can be extremely expensive on a per user basis. Other tools can be much more cost-effective - especially for more basic project management needs.

Read full review

• We went from disorganized to having our processes fully documented. This allows for projects to be duplicated and started faster, increasing my margins.
• Less opportunity for missed tasks or confusion.
• Progress checking always available and easy to use (for our clients)

Read full review

• On the projects that I dealt with, Project had a positive impact on the overall business objective, allowing realistic estimates of the duration, personnel, equipment and materials extremely important for the preparations of responses to RFQs (Request for Quotations), ensuring that the company is not capturing a contract for work that the company is very well capable of performing, however, due to a bad quotation, is not going to realize any profit.
• Once a contract is awarded, Project again had a positive impact, by allowing the construction of a correct WBS (Work Breakdown Structure), the personnel requirements, the identification of critical paths, the budget to be allocated and the creation of work orders (WOs) used by team members for weekly reporting of the hours expanded on the project , the purchase of equipment sufficiently in advance of the date when it will be needed and the identification of specific personnel required to be assigned to the project team, as per they specific skillset, and also when each member must start working on specific segments of the overall Work Breakdown Structure.
• Once the project started, Project was invaluable in monitoring the actual progress of the project in comparison with the very initial schedule and its milestones, the identification of slippage and enhancing an early advance for the formulation of solutions required in order to pull the schedule back.
• Project also was highly beneficial in creating practically automated financial reports of expenditures to date, such reports being of high on the priority list of higher up management.

Read full review