DevDynamics Reviews & Product Details

Before using Signals, sprint planning often felt like guessing, and halfway through, things would start to fall apart. I wouldn’t notice issues like too many pull requests (PRs) or team members being overloaded until it was too late to fix them. With Signals, I get instant alerts when something isn’t right, like PRs stacking up or someone having too much work.

One time that really stood out was when Signals showed me that one developer was handling most of the PR merges. It wasn’t something I would have noticed on my own, and it wasn’t sustainable. We spread the work out more evenly, and right away, things felt smoother and less chaotic.

Another big help is the mid-sprint email report. It gives me a clear view of whether we’re on track or if we need to make changes. Instead of dealing with problems after they’ve gotten out of hand, we can fix them early. The team is less stressed, and we have more time to focus on actual work. Review collected by and hosted on G2.com.

So far, looks pretty good. We are enjoying using it. Review collected by and hosted on G2.com.

As a developer, I’m mostly neck-deep in code or running around closing tickets. Tracking every single PR? Honestly, it’s not always in my head. But the Slack alerts? Total game changer. If a PR’s just sitting there, doing nothing for too long, I get an alert. Simple. I can jump on it right then. It’s like having a little helper who’s always on top of things, so I don’t have to keep checking every 10 minutes. Review collected by and hosted on G2.com.

I mean, it’s great, but sometimes I wish I could adjust the alerts more like, you know, mark certain PRs as more important than others. But ya, even without that, it’s saving so much time. Not something I’d really complain about. Review collected by and hosted on G2.com.

Before I started using DevDynamics, tracking our velocity and quality metrics felt like a full-time job. I spent a lot of time trying to piece together data from Jira, GitHub, and spreadsheets. With my involvement in multiple projects, finding the right information was time-consuming. DevDynamics made it easy by setting up a weekly email report for me. I once wanted a report with some changes, and the team got back to me pretty quickly with a new report format.

A lot of time which went into figuring out where things are stuck got reduced with the weekly reports which has allowed me to act faster on issues. Overall the time to detecting bottlenecks and getting insights has reduced so that has overall helped us get faster. Review collected by and hosted on G2.com.

I can't say. The team has been pretty approachable. Review collected by and hosted on G2.com.

To get any meaningful insight into a project and identify bottlenecks, I typically need to check at least five tabs: GitHub, Jira, Sonar, Slack, and spreadsheets. What I really value about this platform is the instant clarity it provides. Having everything in one place allows me to see the status of the tasks and projects being completed. It has saved me countless hours that I would have otherwise spent searching for issues; now, I can focus directly on solutions. Review collected by and hosted on G2.com.

I haven't encountered any significant issues yet, but I would appreciate it if the weekly AI reports you send via email were also accessible on the platform. That would make it much easier to reference them later. Also, a handy mobile app could help the top management. Review collected by and hosted on G2.com.

DevDynamics makes it really easy to integrate with tools like Git, Jira, and other development platforms. The interface is intuitive and easy to use, and their customer support team is always super helpful. The platform works well for all engineering roles, giving great visibility into team workflows and efficiency. It’s been really useful for spotting bottlenecks and helping us improve productivity overall.

The best thing is that it gives granular data which each manager can interpret and action based on their unique project / team / ecosystem dynamics.

The feature to track investment in KTLO vs New features is also great which helps in estimating for capacity planning. Review collected by and hosted on G2.com.

It would be nice if there was a section to store all the reports that were generated previously, so it’s easier to find them later.

Also it would be good to have comparisons over standard time periods such as q-o-q or m-o-m.

Ability to remove spikes due to anomalies would also make the data less noisy. Example: at times if the Program team decides to clean up JIRA, the counts can become anomalous. Review collected by and hosted on G2.com.

Dev dynamics helped us to get feedback and improve month on month basis how as a team we are delivering our commitments via varous metrics from GitHub,Jira and monitor improvent areas closely. Not just self monitoring it has some great features ex configuring alerts if certain metrics which we all as a team comitted and we miss to deliver those it reminded us to make sure we work continuously on those and improve. Review collected by and hosted on G2.com.

User management can be improved as sometime same user metrics comes under different ids. Review collected by and hosted on G2.com.

One big challenge in identifying bottlenecks is figuring out exactly where in the SDLC the issue happened. When did it open, why is it stuck, and who’s holding it up? It was manual and time-consuming.

I really appreciate the PR and issue lifecycle feature. It makes things so much easier by showing exactly where and why an issue is getting delayed. No more back-and-forth or guesswork! Review collected by and hosted on G2.com.

It would be really helpful if the PR lifecycle report could be exported as a PDF. That way, we can easily share it in meetings and have proper discussions around it. Right now, we have to take screenshots or manually prepare something, which is a bit inconvenient. Review collected by and hosted on G2.com.

Earlier every sprint felt fine in the first few days, then suddenly some PRs stuck, someone overloaded, one feature half done, and then last min scramble starts. Now mid-sprint only I get to know ki bhai ye problem hone wala hai… PRs taking longer, too much work on one dev, code quality issue in one place. We saw one guy merging most PRs alone, fixed it, and our merge times improved. No more last min panic. Review collected by and hosted on G2.com.

It’s damn good at telling me what’s wrong right now, but would be killer if it could also predict next sprint. Like tell me today if my next sprint will be a mess. Review collected by and hosted on G2.com.

Tracking capitalizable development costs has always been a manual, frustrating process. Every quarter, finance would ask for numbers, and we'd be stuck pulling data from Jira, estimating based on story points, and just hoping we got it right. This feature eliminates the guesswork. Simply set capitalization rules once-by epics, labels, or contributors-and DevDynamics does the rest. Now, instead of spending hours trying to reconcile numbers, we get clear, structured reports that finance actually trusts Review collected by and hosted on G2.com.

It's still in beta, so there's room to grow. Review collected by and hosted on G2.com.

We were searching for a tool to track various engineering metrics that could enhance our productivity and highlight weaknesses in our processes. Dev Dynamics has proven very helpful in this regard. It was extremely easy to integrate Dev Dynamics with our tools such as GitHub, JIRA, and Jenkins. The entire implementation took less than a week. Additionally, Rishi and Prasad have been very supportive whenever we needed assistance with Dev Dynamics. Review collected by and hosted on G2.com.

I haven’t noticed any significant drawbacks with Dev Dynamics. Review collected by and hosted on G2.com.