Pluralsight Flow Reviews

Code metrics - The industry average and where an individual stacks up to others

Organization wide metrics for comparison

Player card - one stop page for viewing all metrics related to a developer (Date range selection feature is very good)

Spot check

Team Processes has be to improved a lot. Features like knowledge sharing, review collaboration, project timeline feel like unusable metrics. One can't make any decisions based on these metrics. Some of these dont make any sense at all.

It is a great tool for any organization wanting to track code and team fundamentals. It gives a birds eyeview of your developers with industry standards.

Organization wide tracking of code fundamentals.

How various teams stack up with each other and their code performance.

One stop place for all analysis

Budgeting and management of teams

Provides excellent visibility into the team's workflow efficiency. It helps in identifying bottlenecks and improving overall productivity. Its analytics engine provides concrete data and insights into the agile delivery process.

The number of parameters that go into generating a workflow report is a tedious process. Very expensive in terms of pricing. Though it looks at the number of lines of code as a metric, the quality of code as a metric is not captured.

Pluralsight Flow helps me with efficient data tracking - get insights into team performance, identify and evaluate individual performance, and effectively improve customization across teams.

The tool gives us the feasibility to track the commits and can monitor the stucking points.

The tool needs to improve towards tracking individual members' detailed reports to show their working and coding practices

The tool gives an idea of the sprint flow as well as tracking the member's commits .

The amount of insights and flexibility of building reports that drive conversations around efficiency and improvements.

The UI can be a little difficult in some areas.

SDLC efficiency insights and the ability to drive conversations around areas to improve.

Pluralsight has a wide variety of reports which are parameterized and have scales to judge the health of the work of a team or an organization. The visuals are also very helpful.

In some areas, the terms are a bit hard to understand, like JITTERS, but still, the information and data provided in support is handy for understanding the topic.

Pluralsight Flow is helping in getting the exact picture of how frequently the team is developing and putting in the commits. Also, if the quality of the code is maintained.

The wide variety of reports and the granularity of the metrics it gathers and provides. As an Engineering Manager, it's been an invaluable tool to help guide my developers to better coding practices and to gain insights on how well they are doing as a whole. I love how it gives me the insights to try to catch performance issues early to better work with my developers.

Nothing really comes to mind... It's intuitive, the documentation is FANTASTIC and it has a LOT of data it grabs. Sometimes the developers are missing or the merge suggestions are wrong but that's very minor.

Without clear and concise visibility into how your development teams are doing, you can't make as great of management decisions. It's very manual to pull github stats and jira stats and this tool allows us to save time, gain even more insights than we could have gotten on our own and allows us Managers to better help our teams.

Pluralsight allows us to access detailed analytics and data that helps us find issues and improve the team workflow. It is completely customizable and can allow us to customize the entire workflow as per our team needs.

Pluralsight is a quite complex platform and it has bit steep lurning curve in the beginning for new teams. also I found the integration process with other some tools is a bit complex

Pluralsight Flow solves our project workflow and project delivery process and helps our dev team to work and collaborate efficiently. It is an overall a complete package for development process for our teams.

Simply plugs into your code base and brings out actionable insights to improve delivery, quality and collaboration, all these three are must haves for any business

Some newly introduced metrics such as Jitter and backlfow are useful but are poorly designed but I am sure the team will improve upon them, Also the UI should allow export of data

It helps us read the cultural aspects of the team which was impossible to measure before, for example we can now tell where the bottlenecks are in our workflow and also if teams are just doing reviews as a compliance checkpoint or really deriving value from the review exercise , we could also learn if team members have a key person dependency and if team has a culture of sharing knowledge

Increased visibility: Pluralsight Flow provides a comprehensive view of the software delivery process, allowing me to see exactly how work is progressing across my entire team.

Data-driven insights: With Pluralsight Flow, I can access detailed metrics and analytics that help me identify bottlenecks, improve team performance, and make data-driven decisions about how to optimize our software delivery process.

Seamless integration: Pluralsight Flow integrates seamlessly with other tools and platforms that my team uses, such as GitHub and Jira, making it easy to incorporate it into our existing workflows.

Customizable workflows: Pluralsight Flow allows me to customize our workflows to meet the specific needs of our team and our projects, ensuring that we're working as efficiently and effectively as possible.

Actionable recommendations: Pluralsight Flow provides actionable recommendations for improving our software delivery process, based on data and analytics, helping us continuously improve and optimize our workflows.

Complexity: Pluralsight Flow can be quite complex, especially for users who are not familiar with data analytics or software delivery processes. It can take some time to learn how to use the tool effectively.

Limited customization: While Pluralsight Flow does allow for some customization of workflows, some users may find that the tool is not as flexible as they need it to be, particularly if they have very specific requirements for their software delivery process.

Cost: Pluralsight Flow can be quite expensive, especially for smaller teams or organizations with limited budgets. This may make it difficult for some users to justify the cost of the tool, especially if they already have other tools in place that are providing similar functionality.

Integration issues: While Pluralsight Flow does integrate with a wide range of tools and platforms, some users may experience issues with integration or find that the integration process is more complex than they anticipated.

Pluralsight Flow is designed to solve several problems related to software delivery, such as:

Lack of visibility: Pluralsight Flow provides a comprehensive view of the software delivery process, allowing users to see exactly how work is progressing across their entire team. This helps to eliminate blind spots and increase visibility into the software delivery process.

Inefficient workflows: Pluralsight Flow helps to optimize workflows by identifying bottlenecks, dependencies, and other issues that may be slowing down the delivery process. This helps users to improve their workflows and reduce delivery times.

Poor quality: Pluralsight Flow helps to improve the quality of software by providing data-driven insights into code quality and other factors that impact software performance. This helps users to identify and address issues before they become major problems.

Lack of collaboration: Pluralsight Flow promotes collaboration by providing a shared view of the software delivery process and enabling users to work together more effectively. This helps to improve communication and reduce misunderstandings.

Limited scalability: Pluralsight Flow is designed to be highly scalable, allowing users to easily manage large teams and complex projects. This helps to ensure that software delivery processes can grow and evolve as needed.

Overall, the benefits of Pluralsight Flow include improved efficiency, better collaboration, increased visibility, and higher quality software. By solving these problems, Pluralsight Flow helps users to deliver software more quickly, more reliably, and with less effort.

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.

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.

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.