Asana vs Microsoft Project

• Cross-team communication is always a challenge, but Asana helps make information transparent and accessible to all members of the team.
• It's easy to share with individuals outside of the organization and still control the flow of information.
• Being able to link in other design resources like InVision prototypes is a huge time saver.
• Integrating with Slack makes much of our necessary communication automatic.

Read full review

• Microsoft Project allows users to input a large and varied amount of detail pertinent to a specific project and then creates numerous varied out reports, as per the specific needs of a certain user working on that project.
• Microsoft Project is very flexible in relation to the familiarity of a specific user with the Project. Someone with very little knowledge of Project can still input some data and receive some useful reports, without using the whole capability of the package.
• Project allows a varied types of data to be inputted, such as definition of various subtasks related to the project, time information about the original estimates for tasks and the actual figures, monetary information about the cost of all items required to complete a project (such as rate per hour of specific participants working of a project, cost of equipment to be bought or rented, cost of materials required for project execution, etc).
• A Project Manager very conversant with Project can get a very large number of reports, each one for a specific need.

Read full review

• Nothing to note, really. We love it!

Read full review

• The Project software package, while being very powerful, it also has a rather lengthy learning curve. A fresh Project Manager which didn't use Project before (due to being in a different role, or using until now a different project management tool) and put in charge of a project having as a requirement the utilization of Microsoft Project for a new project starting very soon, will have a hard time to assimilate all aspects of the package, if he wants to take advantage of Project's full capabilities.
• While not being exaggerated, the cost of the software package is relatively high (around $650.00) This is maybe not a lot for a company needing one or two packages, but is relevant to a company needing to procure 20 packages.
• I would like to see more specialty books pertinent to Project. 'Leaning Microsoft Project Step-by-Step' issued by Microsoft themselves and used by me when I started learning Project is a bit cumbersome, unlike other books in their series for Word, Excel, Powerpoint, etc.

Read full review

• I'm not sure how this impacts our ROI. We are able to manage our workload better and see the workload we have.

Read full review

• Microsoft project has allowed us to better create estimates and proposals, while also helping track and manage the work in the same tool we developed our estimates with.
• We use Project Server for all of our document management and integrate it with our accounting software and CRM system via workflows to update and synchronize information.
• Our employees have found the integration with SharePoint, Visio and Office365 to be very straight forward and more of a powerful experience for a holistic solution to managing projects.

Read full review