Jira Software vs Jive-x (Discontinued)

• Manages Epics (projects) very well. Tasks can be adjusted easily along with their corresponding Story Points. The Backlog can be easily managed by moving Tasks around as needed.
• Notifications can be automatically sent out (if setup) to the Developer when new work is assigned.
• Epics/Tasks/backlog items can be managed through an easy to use drag and drop process.
• Agile. Easy to work with (very intuitive)

Read full review

• I write these from the perspective of the Community Manager - You can choose your level of moderation on Jive to match the policies of your organisation. From full on content pre-moderation to to completely reactive moderation, you can take your pick. We chose the latter end of the spectrum, trust your colleagues to be professional and you will be rewarded with professional content.
• The ability for users to set up their own groups very easily with out the need to revert to developers is great as this allows individuality. This allows for organic growth with out impact on the budgets of departments and teams to get their work done on Jive. The option is always there to get 'someone in to fancy it up a bit' however you will find that your own people will develop those skills themselves. Your users will also learn from each other and you should actively encourage stealing of best practice from across your organisation.
• The knowledge repository or Question and Answer features are the most value-adding for me. Having searchable history that allows your to get answers quickly so the next question can be asked is the reason why you should have a collaboration platform in the first place, Jive makes that easy.
• Single Sign On has been a excellent addition for us, if Jive does not make your colleagues lives easier then they won't use it.
• You can customize and brand Jive to reflect your company identity.

Read full review

• Make certain the full end to end processes are documented - changing flows will impact the lineage of your data
• Make certain someone on the team has JIRA experience or have a vendor support you in the implementation
• Look at full functions offered out of the box and understand additional plug-ins that may be needed.

Read full review

• No QA environment. It's cloud-based so you need to purchase another instance to set up a QA environment.
• The gamification system is not as user intuitive as you'd expect. The admin spends more time setting up opportunities than they should need to.
• Jive-x was bought out by three different companies in the last 2 years. There is an uncertainty of how long it will be supported and updated.

Read full review

• Sprints management is relatively simple and straightforward.
• As our organization matures, we will be able to take more advantage of JIRA's reporting tools to help us refine our processes.
• By keeping things relatively simple and transparent (everyone can view all tickets -- no crazy permission schemes), the entire org has visibility into our development process.

Read full review

• Hard to quantify the results...but I also left the company before we had built a mature instance of Jive in-house so the final results/impact were yet to be fully realized and measured.
• The use of Jive brought together multiple-departments for the first time in our 50+ year old company to truly build an "end-to-end" approach to our marketing/sales/fulfillment/customer service engine. It was truly phenomenal to watch how the internal life-cycle of a prospect-turned-customer literally transformed and unified our inter-departmental teams through the use of Jive Engage.

Read full review