Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Really good to provide feedback and inputs for your performance review
What do you like best about the product?
It is not bulletproof but gives you a very good overall understanding of your team's performance. It has a nice UI to identify gaps for your developers.
What do you dislike about the product?
It doesn't handle co-author from git, so there will be missing data if that's something common in your teams
What problems is the product solving and how is that benefiting you?
Performance for my teams
- Leave a Comment |
- Mark review as helpful
Metrics for modern engineering management
What do you like best about the product?
Flow provides metrics useful for large distributed engineering organizations that both apply to individual achievement and team collaboration. It offers fundamental metrics such as coding days, impact, and time to merge that teams need to be able to improve. The investment categories report is very useful for reporting on where the team is actually spending their time, and DORA metrics can help accelerate time to shipping code. Unlike a lot of tools like this Flow offers hierarchical team structures that are useful for large groups.
What do you dislike about the product?
Flow integrates tightly with Git, and is dependent on the flow teams use to be able to capture some information. For example, if individuals do most of their work in private forks, and then squash and merge their changes, some data is lost and certain metrics will not be accurate without a larger administrative overhead, such as setting up multiple Github connections to read individuals' private spaces. Related to this there are issues around merging identities to make sure work is attributed to the right person that can become a burden at the scale of hundreds of engineers.
What problems is the product solving and how is that benefiting you?
Flow provides operational metrics that we use to improve our agile process and collaboration between teams. This helps us optimize our software delivery, which gives us more accurate estimates for the business, and a better return on our engineering investment.
We have immediate information about the productivity of our team and can improve our dev process.
What do you like best about the product?
The automatization of the information of each team member. The graphics are useful once you understand them. Also we can share the information with our developers.
What do you dislike about the product?
It is confusing at the beginning, where the information come, how can we read the graphics and guide the developers to read their data. If we don't have git development, then the information won't be shown.
What problems is the product solving and how is that benefiting you?
The follow-up of the quality and velocity of the developer's performance, as a group, how can we manage our process and metrics. It helps with the 1-1 meetings giving information to discuss (data).
Great tech-centric learning platform for larger organizations
What do you like best about the product?
The content is thorough and great for bridging into certifications and the oversight is excellent. The courses are very thorough and fleshed out as well which makes it great for communicating this to your team.
What do you dislike about the product?
Pluralsight is a very expensive platform and locks you into a contract. This makes it very unfriendly towards small businesses who may be better off utilizing a free platform or one of many cheaper options.
What problems is the product solving and how is that benefiting you?
Flow had insight into commits and churn etc. but honestly wasn't any more useful than what DevOps or a similar platform already offers. Flow also wasn't the most intuitive to use so while it was helpful for breaking out certain information better than others, it had issues.
Helpful tool to track efforts
What do you like best about the product?
Helps us track our impact on the team and how efficient we are with our work which I believe will help us improve by setting a benchmark for ourselves.
What do you dislike about the product?
I believe it would be more flexible if we could have metrics to compare the quality of code as well rather than just quantity.
What problems is the product solving and how is that benefiting you?
It is generally hard to keep a track of how impactful you are to the team and Plural Sight provides metrics which helps us identify it.
Interesting at first but not so after a while
What do you like best about the product?
Code analysis - Churn rate, efficiency analysis in comparison to industry average
What do you dislike about the product?
Pluralsight flow focuses more on lines of code written
What problems is the product solving and how is that benefiting you?
Developer efficiency - at first it helps identify potential existence of bottlenecks
Pluralsight flow offers a unique insight in development work
What do you like best about the product?
It is a good way to observe data when comparing it to your intuition. It's a great dashboard for git and Jira work. It's also a place you can go to learn your work patterns as you try to improve yourself. As a leader, it is also a helpful guide to identifying who and what to mentor. It's also easy to spot top performers, as you
What do you dislike about the product?
It's just data, as it lacks context. Current work may be more research or learning-oriented which changes commit patterns. Don't make personal decisions just on this data.
Wish it we also track confluence work, as we plan our development using conflunce.
Wish it we also track confluence work, as we plan our development using conflunce.
What problems is the product solving and how is that benefiting you?
Trust that remote work is occurring was why product was selected. This was before the pandemic when most of us used to work in the office. The benefits now are
Recommendations to others considering the product:
Use it with human context
Excellent Matrics and analysis
What do you like best about the product?
Number of coding days, Analysis like refactoring and other features.
What do you dislike about the product?
I don't think something to dislike for now.
What problems is the product solving and how is that benefiting you?
Code quality metrics, Coding day metrics, User coding standards etc
Recommendations to others considering the product:
Very good product with predefined metrics for user coding performance.
very complete platform
What do you like best about the product?
The platform allows evaluating the impact of each developer by project, technology, team, among others. Not only at the development level as such, but also in how it shares knowledge
What do you dislike about the product?
What I like least is that the metric used for days of code is not so clear, if a commit is mixed with another, the history that was advanced is lost.
How to measure that metric could be better configured.
Also the date filters are not so clear (last month maybe should be the last month from the current day, not the previous one)
How to measure that metric could be better configured.
Also the date filters are not so clear (last month maybe should be the last month from the current day, not the previous one)
What problems is the product solving and how is that benefiting you?
The tool has allowed us to measure the impact of each member of the team and generate incentives to meet goals that we set for ourselves as a team. We have improved the consistency in which we upload codes since everyone cares that their work is reflected on the platform
good amount of insight to my services
What do you like best about the product?
the ability to use trends and see how the developers are doing on their productivity
What do you dislike about the product?
there isn't as much DevOps types of insights like deployments per timeframe or test results
What problems is the product solving and how is that benefiting you?
while working with dev teams we are able to see the workload of those teams and determine lead times for services to production
showing 61 - 70