What is our primary use case?
Zoho Sprints is a defect-logging tool. Once we do the testing, the defect needs to be logged. We log it in Zoho Sprints so that we can track the time taken for resolution. We also use the solution for status because it goes through various stages. Once development is complete, it gets assigned to the testing team. When the testing team is completed, it goes for deployment, and so on.
What is most valuable?
Zoho Sprints is a defect-logging tool. Zoho Sprints is a more cost-effective solution than Jira. Other than that, everything is standard, including the logging of defects. You can change the status and track it through the different stages. Another useful feature is time logging, where the resources can log their time.
What needs improvement?
Zoho Sprints is a confusing tool, and you need to get used to it. It's not as simple as Jira, where everything is clear about what needs to be done.
What do I think about the scalability of the solution?
Since Zoho Sprints is a SaaS system, it is scalable. It's a web page. You create as many projects as possible and share them with the team members.
More than 50 users are using the solution. Currently, we are running around six projects simultaneously, and we plan to increase the usage. Scalability is addressed through the cloud. We use Amazon and Google Cloud to upgrade automatically.
How are customer service and support?
The solution’s technical support is excellent.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We previously used other tools like Jira and ClickUp. Jira is a time-tested tool that has been around for years, and many people and companies use it. ClickUp was something new but had some issues, so we dropped it and switched to Zoho Sprints.
How was the initial setup?
The solution's initial setup is very easy. The solution's deployment is immediate because it's a web version. The moment you create a project, it's all ready to go.
On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup a seven out of ten.
What about the implementation team?
Ours is a small entrepreneurial team, and everybody is a developer. We have three leads, and the rest are developers. The leads handle all the deployments.
What was our ROI?
The solution is good for tracking defects. People work in different time zones, and Zoho Sprints is an excellent tool for managing them well. The solution provides around 60% to 70% improvement in efficiency.
What's my experience with pricing, setup cost, and licensing?
Zoho Sprints is a more cost-effective solution than Jira.
What other advice do I have?
Zoho Sprints is a SaaS solution. We do backlog grooming through a spreadsheet with the corresponding executives from the client side. It's not done in the tools. We use Microsoft Excel for planning. We do have maintenance with all the customers. We use various tools. We use WhatsApp and other collaboration tools for high priority cases. Otherwise, we use Slack.
I would recommend the solution to other users.
Overall, I rate the solution an eight out of ten.
*Disclosure: I am a real user, and this review is based on my own experience and opinions.
