Common Objections

A few reasons you may not need an engineering intelligence platform

Don't worry you are not alone, we answer the common ones here

#
Isn't analytics provided within the tool, like Github analytics or Jira reports good enough?
Github / Jira was always designed to be more operational in nature, which helps you in achieving a set of tasks but their primary purpose isn't to understand your process and find out possible bottlenecks and suggest ways to improve it. And that is exactly why we build AnalyticsVerse.

How are we different from Jira reports?

Jira reports will give you things like a burndown chart and what is the status of every story in the sprint. We go miles ahead and give you a complete view into the following things:
  1. Relate all your commit and MR work at a sprint level, and give you aggregated metrics about how much and what type of work was done along with tracking deployment metrics in a particular sprint.
  2. We have detailed views for each of the metrics, along with a timeline view on each issue showing you all activities (commits, issue state changes, merge requests, deployments) that happened on the issue
  3. A view on how you have performed in a particular sprint as compared to your previous sprints on any metric, which we believe is crucial for taking actions to actually improve.
The entire platform has 8+ dashboards covering different aspects of your processes, out of which Jira has a few metrics which are a subset of one of the dashboards (sprint report) we discussed above.
Sprint report
Sprint report dashboard


How are we different from insights provided by repository tools?

Github will provide you with basic contributor and commit activity, Gitlab does that along with merge requests activity analytics (in the ultimate plan which is priced at $99 per dev month) and deployments activity insights. Bitbucket will not provide you with any insights by default, you will have to add plugins to even watch a simple activity chart of your commits on the repository level. Ways AnalyticsVerse can assist your team in a much better way:

  1. We believe in value stream analytics and not repository analytics, that's how every metric will be visualized, which means you have to way group repositories into value streams and have a singular view into all metrics on your set of repositories.
  2. On AnalyticsVerse, you will see metrics like long pending, risky, and rubber-stamped merge requests, which point out potential requests that need extra attention. (All anomaly calculations are designed to happen on your historical data, so we adapt to your team dynamics on day 1).
  3. We also go further and have advanced metrics like lead time of a commit, risky commits and deployment frequency which actually gives you a holistic view of your development and deployment activities.
  4. We also analyze your team's health based on the amount of work the team has been historically doing and point out potential overburdened team members to actually prevent burnout.
  5. On every metric that we compute across the dashboard you can also create your own visualizations, save them as dashboards and share it with your team.

Again, AnalyticsVerse was built to optimize processes and all metrics revolve around that ideology, and we know a heatmap of commits is never enough to understand what's happening within your team.
AnalyticsVerse project creation
Value Streams



I don't believe a tool can help in measuring and increasing developer productivity.
That's awesome because neither do we! The purpose of AnalyticsVerse is never to measure or try to improve developer productivity. We have and always will focus on optimizing processes within your teams and projects. In fact "Optimize processes, not people" is the first ideology on which we built AnalyticsVerse. There are a lot of factors to an individual's performance which no tool can ever analyze, there's always a human aspect involved when evaluating a human and we never intend and are neither capable to do that for you. What we can help with is "data" at the right time and right place available readily for you to take apt decisions.
Project risk dashboard
Project risks dashboard



Whatever we are doing currently is working for us, why change that?
Yes that is absolutely true, and I am sure when you say it's working for you, it may actually be working wonders for your team, but to believe that there is no room for improvement will plateau out the growth of your team. And there is never an absolute best, all we are saying is if there is the will to continuously improve, one needs to commit to changing processes. With your team growing, the type of work you do change, your processes also need to change. And that change cannot be driven by you sitting for a 2-hour long meeting with your team, the change will come gradually if you head in the right direction. And we just want to be the ones assisting you to reach there.



We are a really small team yet, why do I need a visibility tool when I am already aware of most of the things.
Every big thing starts small, and so will your team. If you are below 5 developers in your team, the value you will see out of our platform will be lesser, but if you try to incorporate a few things within your processes from the start, example figuring out how long it takes for a commit to reach production will help your team have much more streamlined processes in the future. If you are a team planning to grow in the future, irrespective of your current size you will need a tool that helps you improve your processes as you grow.



How can there be a one size fits all platform especially for engineering teams?
The first thing you are required to do, as soon as you sign up on our platform is define your value streams, trying to capture different ways your team maybe using task tracking tools and git repositories. Once you have defined these value streams, we take several hours to show you your first reports, what we do behind the scenes is auto configure things for you, a few of them are the way you use story points, or what statuses a task can be in, what branch you use as your primary branch for development.

Apart from default configurations we also rely on the historical data of your teams to understand the dynamics in which you work. You also get to customize things like how do you make releases, and how you track production defects, which lets you tailor the platform to your needs.

Along with adapting to your processes we also have a very strong customization use case, called Custom dashboard which lets you create your own views on the metrics we compute and save and share it across your team.
Custom dashboard
Custom Dashboards



I like the ideologies and metrics, why can't I build it myself?
Absolutely yes, there is no doubt you can replicate what we have built, if you assign a team to it, this can be achieved in a few months. But from our experience building it is just 20% of the job, the bigger effort will be to evolve that platform with your processes. Where we as a team will specialize in this domain, to give you metrics and reports that are meaningful and actionable for your teams. A big concern for you also might be whether you want to really build something you won’t sell?



Do I really need to believe in everything you say?
Absolutely not, this in our minds is genuinely not a sales pitch, this is us talking to you on what ideologies we have built AnalyticsVerse, and even if our ideologies resonate with you, don't take our word for it. We want you to take a look for yourself and see what value we can provide, which is why we have a no-questions-asked free trial.
And pay your first dollar to us only if and after you see the proof of value.



We Integrate with the tools you rely on

Github Logo
Jira Cloud Logo
Gitlab Logo
Jira Server Logo
#

Ready to dive in?
Try it out for free. No credit card needed.