The setup is pretty easy and might take one week.

Resource education is sometimes complicated. The most difficult thing to do is control or assign resources and it is especially complex for very long projects. If you have many resources for the same activity or concurrent activities with  overlapping resources, then fixing the allocations is very difficult. Some users avoid assigning resources because of this issue but resource assignment an important step. 

I rate setup a seven out of ten. 

When using the solution on my personal computer, I just installed it and began to use it. And at my company, I just told our help desk to install the solution remotely on my office computer.

The setup is based on the business requirements. It's not too difficult. 

The deployment takes four to six weeks.

We activated the license and then, to use MS Project, we have to create a whole project plan, and that requires manual data entry. Then, once we have that, everything moves quickly.

We do not need any technical people to maintain the product. It's very user-friendly and maintenance is very minimal. 

The installation is easy. Setting up a project takes a little bit longer. It's not as intuitive as Smartsheets, but it's relatively easy. You have to have a base knowledge to use either product, but I would rate Smartsheets eight out of 10 for ease of use, while Microsoft Project is maybe five out of 10 because it's not as intuitive. 

In the setup of Microsoft Project, the process was a bit challenging initially. The main reason was that I was not sure where to start in a safe and secure manner. Microsoft frequently updates its software and resources, but it can be difficult to find the necessary documentation for a specific solution. It is crucial to have some prior experience with similar products to effectively locate the necessary information. For someone who is just starting out and does not have the proper training, guidance from an instructor, or hands-on experience, the setup process can be quite complex.

The implementation of the solution was swift and effortless. The amount of time it took to deploy would largely depend on the specificities of your project and what features are required or optional. From my personal experience, creating the project was simple and straightforward, and did not require a significant amount of time. The deployment process was smooth and efficient.

The initial setup is straightforward. It hasn't changed in years. You add your tasks and have your dependencies and resources. That's a kind of basic functionality in Microsoft Project. Then it drops your Gantt chart on the right, and you get that created. Then you can add the percent complete and track the progress. It's like an office product like Visio, Word, or Excel. You open the application and create your schedule. It's essentially a scheduling tool.

Our deployment process follows standard procedures, often dictated by project requirements. We allocate two personnel for installation and project requirements. Currently, we have nine to ten projects.

Our IT department handles the deployment of the solution. I can tweak it on a per-project basis. However, the implementation or installation of the software is done quickly.

When we started working with the solution, the setup was somewhat difficult. Once you gain knowledge, you slowly see that the solution is easy to use. 

The product's initial setup phase is easy.

The deployment is not at all complicated since our company only had to download the product from the solution's official website, after which we enabled the licenses to use it.

It takes a while to build, but it will probably depend on the project size and all the dependencies. So, it isn't exactly straightforward, but it also depends on the size of the project or the scope of the project.

The initial setup of the Microsoft Project is straightforward. However, it was a Team's deployment and Microsoft Project is part of that suite. It took us approximately six months for the complete deployment.

The setup can be both complex and easy. I'd rate it 3.5 out of five, with five being an easy setup.

Deployment involves usually implementing the new tools and then adopting and having people use it. Implementation took about three months and then the adoption took another six to eight to nine months of training and making sure people use the tool.

We have admins and that's one or two folks that can handle any maintenance requirements. It's not a high-maintenance product.

Project is essentially an extension of an Excel sheet. You need to configure a lot of things to get your project management done correctly, and the use case scenario is different for each customer. Some require Project for certain needs, which may not be the same for the next customer. We need to understand the customer's work requirements, and we will build a solution on Microsoft Project.

The initial setup of Microsoft Project was straightforward.

Microsoft Project's installation process took around two hours.

The solution is deployed on-premises.

Only one junior engineer is required to deploy and maintain the solution.

The initial setup of Microsoft Project is complex.

The deployment took one day.

The initial setup is straightforward. You download, install, and use the product, and you get set up your projects. That's it.

The initial setup was a bit complex. It wasn't overly simple. 

The initial setup is very simple and straightforward. 

It is quick to set up. It took about an hour to deploy.

We have five people that are able to handle deployment and maintenance tasks. Typically, we have two or three available. 

In my organization, it is already packaged and available. 

The solution’s initial setup is straightforward.

The product has a simple, straightforward implementation process. It's not overly complex. 

I did not handle the initial setup. Our IT team handled that part of the process for the company. I just open it up and create a new project schedule. Therefore, I cannot speak to how difficult or straightforward the process is.

I only use the solution. I did not have to set it up. I can't speak to how easy or difficult it is to do this as I am just an end-user in the company.

Microsoft Project's initial setup is straightforward.

I'm not sure how the setup was. I just used it. It was already on my laptop, and I just started using it for my work, so I can't speak to how it was implemented or how long it took to do so. My understanding is that you don't need a lot of people to handle the installation process.

The setup was straightforward and not as complex as Primavera or any other project management tool.

When it comes to the on-prem deployment of the older versions, you don't usually get the results, you don't find it online. They are not readily available. We need to get into the third party applications and download the third party results. From there on, it's a marathon to install. The cloud version is easier. 

There's not really any maintenance needed. 

Setting up Microsoft Project in our company was relatively straightforward, taking a short amount of time.

The solution is simple to set up. It's not overly complex. Especially now, after working with it for so many years, it's very easy.

It's an online tool. From that perspective, there is no maintenance needed.

The initial setup is a bit more complex than I would have hoped for or that I am used to. Again, it is possible that it's a lack of know-how and education with this product.

Installation is automatic and simple, we had no issues.

It's easy to set up the solution. It's not a complex process. 

We only need one person to deploy and maintain the product. They are an admin.

I wasn't around, but it would have been pretty straightforward for the person who did it.

The initial setup is complex.

The solution’s setup is very easy.

The solution is very straightforward and simple. It's not as complex. You can connect the license in less than 30 minutes on a desktop.

The tool's deployment is very straightforward. 

It's very easy to install and use. It doesn't take a long time to deploy.

We have about 1000 people using it in our operations department.

It's a straightforward deployment. If you're going into a Project Online, you don't have to do any setup. It's just the basic configuration, which I will be connecting to your active directory to pick up your resources, and I will be configuring the environment for role security permission and stuff. Then of course, the custom information like your verticals, your divisions and stuff that you want to align your projects with. So the configuration is very easy. Of course, only if you want to bring your own workflows and customization into the environment. That's the development rule, but even those development periods are not very long. Like four months, five months is max that we get into. After that, just mostly support and enhancement.

The packaging of Microsoft Project Professional for enterprise use is relatively straight forward. The end-to-end enterprise implementation with Project Server is complex. Most of the complexity is on the people and process side of set-up for an enterprise rather than for a single project.

In terms of the initial setup, if you're using it as a fairly basic tool, it's fairly straightforward. When you start getting into the more complex tools and the features of the product, it becomes harder to use. That's to be expected. You have to have knowledge of the tool to be able to use it properly.

Installing Microsoft Project is effortless. The initial installation took me about two or three days. It was easy to install after I took the online courses. I didn't need an integrator or a consultant. 

The initial setup isn't complex. The implementation is easy due to the fact that the user interface is so good.

I would rate the initial setup of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best. It's not very complicated. Even if you download and use the application for the first time, you can easily find your way.

The initial setup was straightforward. I didn't do it. Our IT guys did it, but once they got the process done, it took less than an hour.

It was pretty straightforward. Essentially, you should have taken classes in it and worked with it in order to understand some of the nuances of it. It can have a little bit of a learning curve.

The solution's initial setup was straightforward.

The setup was very straightforward and took about fifteen minutes. I'd rate the ease of setting up four out of five.

The setup was straightforward. It took us about three hours to do so. 

Its initial setup is simple.

The initial setup is very simple and quite straightforward. 

The deployment is very easy. Follow the instructions, and you can easily install the application.

The initial setup is straightforward. It's just downloading the initial file version, and it can be done on the same machine. It took me half a day to deploy it. 

The installation for doing the Waterfall methodology is easy. You do not need a lot of training, but if you want to do advance operations, such as Excel, you need to be trained. There are many pieces of training online on platforms such as YouTube and Udemy, people can easily learn. You do not need a special course or to have a certificate.

The solution's initial setup is easy. It takes a few hours to complete.

It was quite complicated. It needed consultants that were specialists in it to help with the implementation. Most of it was done before, but it wasn't widely used. So, we took that implementation and built on it.

In terms of maintenance, because it's a cloud-based solution, it's real-time.

Being a SaaS solution, it comes ready to be used. The deployment took a few minutes.

We have our own implementation team that took care of the setup. I was not personally involved. I know that the deployment time takes roughly three weeks.

The initial setup is straightforward.