The world of work is constantly changing. Agile work processes in particular are becoming increasingly popular. Even large companies are trying to introduce agile working methods. For many, the Scaled Agile Framework (SAFe) is the right solution for their agile teams. However, implementing SAFe with all its features such as providing reports, visualizing dependencies and automated documentation is not always easy in reality. Many companies spend a lot of time and money searching for the right…
N/A
ServiceNow Now Platform
Score 8.8 out of 10
N/A
The ServiceNow Now Platform is a digital workflow building and extension tool for ServiceNow featuring a number of low-code / no code tools.
N/A
Pricing
Agile Hive - SAFe in Jira
ServiceNow Now Platform
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Agile Hive - SAFe in Jira
ServiceNow Now Platform
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Agile Hive - SAFe in Jira
ServiceNow Now Platform
Features
Agile Hive - SAFe in Jira
ServiceNow Now Platform
Project Management
Comparison of Project Management features of Product A and Product B
Agile Hive - SAFe in Jira
7.8
1 Ratings
3% above category average
ServiceNow Now Platform
-
Ratings
Task Management
7.01 Ratings
00 Ratings
Resource Management
8.01 Ratings
00 Ratings
Gantt Charts
7.01 Ratings
00 Ratings
Support for Agile Methodology
9.01 Ratings
00 Ratings
Visual planning tools
8.01 Ratings
00 Ratings
Agile Development
Comparison of Agile Development features of Product A and Product B
Agile Hive is used for our value train within a SAFe setup. Every quarter we organize a so-called Product Increment (PI) Planning, where we plan all Features and Enablers in Agile Hive. Based on the priority of the Product Manager all teams plan their Features and Enablers accordingly to the sprints that are determined by the Release Train Engineer and set up in Agile Hive. The teams then create User Stories and estimate them and based on their sprint velocity (defined in Agile Hive) Product Owners can see how many Features and Enablers are realistic in one quarter (Product Increment). Further, dependencies across teams can be defined and made visible in Agile Hive, so that the plan is feasible. Without Agile Hive it would be hard or impossible to plan across several teams within a value train and to manage all dependencies. Additionally, with Agile Hive the plan is more realistic, so what can be achieved within one quarter in product development.
ITSM is straight forward creation of Incidents and Requests. It can get more confusing as you layer more modules on top of it with event management, risk, project, etc. It also becomes more costly as everything is a different license. Integration between other external applications is very easy to do with their API. You can easily create endpoints for external apps to talk to or create REST messages for the platform to reach out directly.
Providing admins/devs with easier mechanisms for providing businss stakeholders with self-service admin capabilities across the platform
Tutorials on how to be the best at reporting in servicenow
Guided tour functionaltiy is a bit rigid and could use more workflow capabilities
Making it easier to push form variables to the user so there is more context when providing an approval. The out of box approval UI/form is terrible in my opinion.
While we are very likely to renew, we are also assessing if we should renew all of what we currently subscribe to as we try to reduce costs. Some parts of the business feel there may be a better tool out there to fit their process requirements. We are currently working with them to identify what those requirements are to see if it makes sense while also pointing out a reduced cost of tooling is not always the best fit if we have an increased cost of customization and maintenance between tools.
It has in general a good usability, but there are some downsides, the big picture view of the entire product increment is too static, so there is no zoom in or zoom out. Mostly throughout planning it is necessary to zoom in to a sprint level and manage the user stories there. Also, the pig picture view has some limitations, because you cannot read the entire user story name (boxes are too small).
It provides a lot of modification options which is wonderful for certain team usage but becomes too much of a job when it comes to the Service Desk. Also on the app support side, since too much information can be carried, it affects the GUI and makes it complex.
The platform is provided as a SaaS solution and support from the vendor has been good. There are regular software releases with bug fixes, new features and enhancements, and furthermore we are given the opportunity to fully test these before rolling these new releases out into the production environment to minimise the risk of business disruption
We went through a re-implementation last year with a partner and were very pleased with the outcome. We looked at several partners and chose one that was able to provide an entire scope and cost upfront of what would be required to complete our requirements. We worked very closely with the dedicated team assigned to our project throughout the process and they fully delivered on all of our requirements that we presented in the initial scope.
With Jira Software alone it is also possible to plan a SAFe product increment planning, but it would be nearly impossible to see the overall big picture of all product teams involved in a release train. So, the planning on sprint level for one team would be more efficient, but the planning for a whole quarter with all dependencies across teams would be not feasible to present. Therefore, Agile SAFe enables value trains an efficient way to plan a product increment.
ServiceNow is by far a better tool over Remedy. Its ability to integrate so seamlessly to so many tools allows for plenty of opportunity to streamline and improve processes. Servicenow has intuitive flows that allow you to quickly pivot if process change. Its adaptiveness is what makes it far better solution over Remedy
Our base managed service MSA is very clear and focused on our use of ITSM (ITIL role license). Other parts of the platform use some sort of transaction count licensing. This type of pricing does not work for an implementation of our scale.
Very easy to use. Capture more data from the Incident and problem management. Easier to escalate and following the change management process to resole the issues.
Fast implementation of our Sales & Operation/Projects controls and process - tool adapted to our needs, not us to adapt to the tool.
Once we are a consulting/implementation company, our customers are happy to see that we use what we sell, and it is easy to show them how this platform/tool can have an impact on our own business.