DevDynamics Reviews

As the Head of Engineering, I was looking at enhancing the efficiency and well-being of our teams. We recognized early on that despite our teams' constant efforts, our projects were not progressing as quickly as we hoped. To address this, we used DevDynamics, to analyze project data and track team velocity. They gave us insights into the varying progress rates across our projects, enabling us to identify and address the underlying causes of delays effectively.

Simultaneously, we were mindful of the importance of our developers' well-being and job satisfaction. DevDynamics introduced DevEx surveys . These surveys allowed us to be mindful about early signs of burnout and maintain a healthy, positive work culture.

All in all as a leader, this tool gave me an analytical view on how the team is being run.

Nothing that I can think at this point of time.

DevDynamics has helped with efficient resource and team management at Apna. Their platform has helped us improve the quality of work and velocity of our work.

I have been involved in engineering metrics and was using another tool before this. DevDynamics is more comprehensive because I get the popular metrics like DORA but also get access to other features like activity log and goals to drive improvement in my teams.

The data from DevDynamics has helped me have better conversations with non-technical leaders from my org. It’s helped others understand how engineering time is spent and the tradeoffs needed to assign more devs to important projects.

Not much. I had some feedback about some features and they shipped those pretty fast.

I started using it for tracking engineering metrics and am using the reports for my monthly conversations with the leadership team.

With DevDynamics, it's easy to understand activities in Github. I find the DORA metric view and PR analysis useful. This helps us understand how we are doing as a team.

Certain configurations, such as merging contributors and setting up teams can be made easier. Although the DevDynamics team provided assistance, I believe the product should have the capability to handle these activities in bulk more efficiently.

As a fully remote team, it used to be challenging to help the team with the issues related to the PR cycle. DevDynamics offers valuable insight into where our team is investing their time and helps identify development bottlenecks.

We started working with engineering metrics for the first time so the team had a lot of questions. The DevDynamics team was very helpful with everything from how to set up our Jira/Gitlab and which metrics would be more helpful for our company. They helped us make the process more actionable so that our teams could start improving. We were running pilots with 2 different vendors and the difference in the engagement was quite clear.

We are now starting to go beyond just metrics and also look at where our teams are focused and how we can change this to help meet more business goals.

The setup ran into some problems, mainly because of how our tool permissions were configured but the DevDynamics team got on a call to walk us through the process.

We started a program to connect engineering performance to business goals, and improve KPIs for the different teams.

We connected DevDynamics with our Jira and Github and started receiving insights very soon. We get alerts in our team Slack channel which tell us about any misses on best practices like PRs merged without review etc. We’ve seen our review rate increase since we’ve started measuring and discussing the relevant metrics in the team.

The number of metrics can be overwhelming at first. I think it would be good to get a smaller selection based on the team.

Our goal was to get visibility into our team and how we can improve our engineering process to match with the best teams out there.

I’m able to see how much time at the team and org level is being spent on new features, maintenance, QA etc. We’ve used this to make decisions about automation for repetitive low value work so that our devs can spend more time on new feature development. The ability to look at how different teams are doing on metrics or practices has also led to better conversations with the team leaders about what can be improved. This has led to an overall improvement in the metrics that we are using for understanding engineering performance.

The team also spent some time with us to set up our CI/CD metrics since we really wanted to track deployment data for different teams. Also, the initial integration was quick and the support provided by DevDynamics team was great.

I want to see more high level reports that can be shared with other stakeholders across different functions in the org.

As a CTO, it has given me much better visibility into the engineering organization and how to get heuristics inputs directly from this tool rather than discussing it with every engineering manager on those inputs. It helps me identify the teams that need more input and feedback to become better in terms of their various aspects like delivery timelines, velocity, and general sprint processes

I lead a distributed engineering team and DevDynamics gives me visibility into the work without doing too many status update meetings. The insights have been useful to figure out where we may need to improve our focus. We recently switched from Github and Jira to Azure Devops and the transition was smooth for us. We were able to get the same level of metrics and analytics as before.

I get weekly reports but I would like to configure it to suit my needs.

We are mainly using it for our distributed team.

DevDynamics help me understand what developers are working on, which development process taking more time, and who is getting burned out. I especially like their working agreement module, it helped us in improving our PR cycle time and process hygiene.

Help docs are missing. Though the DevDynamics team is very responsive without help doc sometime it's difficult to configure the product as per our needs.

It helped us in improving efficiency and deliver faster.