The out-of-the-box setup is straightforward if you follow the guide. 

ServiceNow has very clear guidance on how to set it up correctly. It wasn't difficult, it just took some time to set up.

I would rate the setup as seven out of ten.

It's not complex, but it's all about adaptability. The organization-level change management takes a little bit of time when we try to integrate ServiceNow ITBM with other systems, such as SuccessFactors. We are using SuccessFactors internally to take care of our core HR functionality. I would rate its setup a four out of five in terms of ease.

The setup is a bit complex. It depends on the organizational needs, and sometimes, we make customizations based on those needs. 

However, it can be challenging during upgrades due to the customizations. There are various features, configurations, occasional server errors, and complex module setups. Adapting the out-of-the-box features to the organization's requirements can also be a little complex.

So, the setup's complexity is okay, but it is not straightforward.

The initial setup was fairly complex.

We thought we could have everything ready in six to eight weeks' time. However, it literally took us almost six months.

In all fairness, there are some things we also realized afterward. We are premium partners. We realized that, while we say out-of-the-box, it is not actually out-of-the-box. If you are staffing an organization from scratch, it is okay. However, we were already using Clarity and, obviously, spreadsheets. One of the issues which we face was a mindset from people who suddenly had to start using it when they already had methods. 

Discounting that fact itself, many of the customizations and all those modules, configurations, parallel runs, and then going live and cutting over took us more than we thought. 

The configuration of the product takes time. What happens is, while ServiceNow claims everything is out-of-the-box and everything can be easily achieved, many times, for some customizations, we had to raise a ticket with the actual ISVs, or the vendors and then add that. And we have an in-house ServiceNow team. We are not beginners.

We know ServiceNow pretty well. In spite of that, if you have to refer to ServiceNow, it means it's still not that user-friendly compared to others. They're in that space, they're evolving. However, it's more from the configuration perspective where you run into issues. I'd rate the initial setup at a or 2.5 to three out of five. It's not easy. There's a moderate amount of difficulty. 

If you understand the CSDM, a framework of ServiceNow, it could take around three or four months to learn. It is not the easiest because you need to tie into the other data structures of the platform. Therefore, it is not the most straightforward topic for any developer, but you must access the platform. You need to understand the data structure, do some analysis, and know where it fits into the puzzle. You need to understand the CSDM well before leveraging the best of those capabilities. Deployment takes anywhere from one to two quarters, depending on the scope of the implementation. If you are covering multiple products, etc., it will take longer. If you have the necessary information to leverage, your application and technology portfolio will be much easier to integrate. It takes time, typically between one and two quarters or around three to six months. From an implementation perspective, we need a team of around five to six people for deployment. From a stakeholder perspective, we need a team of around ten people. I rate the solution’s setup a four out of ten.

The installation is quite easy.

The initial setup is quite complex. It's not easy. I would say its implementation is on the complex side, since, unlike other modules, these are pretty much concept-oriented, and having a successful implementation is a pretty tedious task. It took four to five months to deploy the product.

The tool's deployment is difficult. I rate it a four out of ten. Integrating and setting up the basic system took a long time, about eight months. We started in December 2022 and finished in July. There were many complex scenarios and options, making it difficult. Understanding and configuring everything properly was a challenge, especially compared to setting up a similar system with Zendesk, which only took a month.

My team and I were involved in our design team. Four developers, one analyst, and two QA guys were on the ServiceNow Strategic Portfolio Management implementation side. So, in total, there were six people on our IT team. It took them about eight months to configure everything for us.

The initial setup is of a medium difficulty level. It is not easy or complex. However, it is clunky. The user interface is difficult to find features and navigate around. The forms are generic and the solution was primarily developed as an incident management tool which it is good at, but project management is something they developed later. It feels like it was an afterthought.

I rate the initial setup of ServiceNow Strategic Portfolio Management a five out of ten.

On a scale of one to 10, with one being the worst and 10 being the best, I would rate the initial setup a seven. 

The initial setup is straightforward.

It took three and six months to complete the deployment.

The solution is provided to us, we didn't do the setup so I'm not sure about how difficult it was. I assume it's not difficult. I'm a user of the product, and we're on a development operational organization model. The product is managed externally and the service provided to us. 

The complexity of the initial setup can vary depending on the amount of data that needs to be migrated.

I find found the setup to be quite easy.

The initial setup is straightforward. It's easy to implement. An average deployment takes about two months. CAPPM, in comparison, would take about four months.

All the processes of project management have to be very well defined. When these requirements aren't defined, we have to approach that first before we can implement the solution. It's very important for the success of deployment.

The initial setup of the solution was simple and user-friendly.

The initial setup was quite easy. It’s almost similar to setting up a Facebook account. It’s not difficult like other solutions. There is a lot of media that you can use to help your team deploy into the system. Deployment is rather quick and takes about 40 to 45 minutes to set up in total.

The initial setup is straightforward. We took two weeks to deploy the solution. It is an agile process. The product is cloud-based.

The initial setup is complex, especially when you are implementing it for multiple branches. It normally takes a few days to deploy.

The initial setup was very simple, and we implemented it very quickly.