Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management.
$10,000
per year
Trello
Score 8.3 out of 10
N/A
Trello from Atlassian is a project management tool based on a Kanban framework. Trello is ideal for task-management in a to-do list format. It supports sharing boards and cards across users or teams. The product offers a free version, and paid versions add greater automation, collaboration, and administrative control.
I was not involved in the selection of ServiceNow. I am just an end user for this software. The other tools I have used were more directed toward project management, rather than issue tracking. At times, ServiceNow stacks up well, making it easy to address tasks assigned to me, …
I like Trello because it is simple and easy to use. I also like that the free version can do what I need it to do. Other options, such as LeanKit, JIRA, and ServiceNow are expensive and complicated. Trello does what I need it to do without being overly complicated. JIRA and Serv…
Trello wins in the quick to set up and easy to use scenario. It just makes sense. Kanbanize, on the other hand, requires a lot more initial setup, although boards can be much more customized with that product. In this case, personal task management was the target, with mobile …
Trello is very good for communicating plans between developers and management. It's much better than my memories of Pivotal Tracker, tries to provide better tools for agile methodology, but I found it rather difficult to use well. For initial planning within our team we use …
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
For teams or individuals with lots of individual tasks/details to track, Trello is perfect! It basically removes the need for a paper checklist. For those that need an overall project management tool that requires less tasks and more overarching goals, collaboration amongst various teams, and gantt charts I would suggest monday.com
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
I am very likely to renew Trello, because it doesn't cost anything to do so. I am also very likely to use Trello's upgraded features in the future because a lot of my team's data is stored on there and they have already gotten used to the platform. Trello is very easy for new team members to pick up, making the onboarding and usability very streamlined.
The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
Trello is incredibly intuitive, both on desktop and mobile right away. It is also full of helpful features that make it even easier to use, and is flexible enough to suit almost any organizational need. Onboarding for the software is thorough, but concise, and the service is frequently updated with even more QOL improvements.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
I haven't reached out to their support very often and their support is very limited anyway for the free users. They do have tons of great articles and videos in their Help Center and constantly send emails with updates and add-ons to the product. The fact that I've barely ever had to contact their support team means that they've developed a great product.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
For our small business, getting a few of us started well on Trello was the key, I think. As long as a couple of us were really comfortable with the interface, we could lead others and help them with any questions. From now on, anyone who works with us just naturally uses Trello for information sharing - it's just part of what we do.
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
Trello is more simple and not as "robust" as the other tools, but it's easier to use and manage and understand and ACTUALLY get stuff done with. It's simplicity is part of the beauty of using it. You don't need a million options that nobody uses, you just need to get stuff done.
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.
Trello keeps me organized, focused, and on track. I could filter the Trello board to only see my issues and understand what I needed to work on and when.
Trello helped our team implement an agile structure. It's a very simple kanban method of viewing all of your team's tasks and statuses. You can completely customize the columns to your team's specific workflow and create tags relevant to your work.
Trello helps reduce unnecessary communications between teams. When I want to request translations, I simply create a card on the localization Trello board -- no need to directly message anyone on the team, and I can watch the status of the card change from "in progress" to "in review" to "translated," all without having to directly ask for updates.