Flow Pros and Cons

It has easy dashboards to use to review the behavior of the team mattes. You can perform a follow on each teammate or even review the team as one. You can easily check metrics like commits per day, or response and easily compare an individual against the team. Review collected by and hosted on G2.com.

It is something that they are trying to enhance, but I would like to have better goals. Currently, the goals are difficult to set per member or user; it will be cool to have some more "engagement tools", like send it emails to encourage you to accomplish the previously set goals and etc. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

La manera de como se ve organizada la informacion Review collected by and hosted on G2.com.

solo demasiadas opciones que aveces uno se pierde Review collected by and hosted on G2.com.

The amount of insights and flexibility of building reports that drive conversations around efficiency and improvements. Review collected by and hosted on G2.com.

The UI can be a little difficult in some areas. Review collected by and hosted on G2.com.

The innumerable amount of insights that the tool provides is the main positive point.

Simple integration with repository and ticks. Easy configuration of teams and goals. Review collected by and hosted on G2.com.

Frequent changes in the layout and arrangement of information make it difficult to use it consistently and standardized across teams, requiring constant training.

Many functionalities are made available incompletely, making it unfeasible to use and without a detailed description of what the problem is. Some of them we are interested in using, but rarely work right away. We need to keep an eye on it for a few weeks until we notice that it has started to work. Review collected by and hosted on G2.com.

Pluralsight Flow is a powerful tool designed for software development teams to help them visualize their workflow and optimize their processes. As a language model, I don't have firsthand experience with Pluralsight Flow, but I can provide an overview based on what I know.

One of the key benefits of Pluralsight Flow is that it provides teams with detailed metrics and insights into their development process. This includes information on things like cycle time, lead time, and throughput, which can help teams identify bottlenecks and areas for improvement. The platform also provides real-time visibility into work in progress, making it easier for team members to stay aligned and coordinate their efforts.

Another advantage of Pluralsight Flow is that it integrates with a wide range of other tools commonly used in software development, including GitHub, Jira, and Trello. This means that teams can easily track their progress across different systems and tools, and get a more comprehensive view of their development process.

Pluralsight Flow also has several features that are designed to promote collaboration and teamwork. For example, team members can use the platform to leave comments and feedback on specific tasks, helping to keep everyone on the same page and ensure that work is progressing smoothly. The platform also includes automated alerts and notifications to help teams stay up-to-date on important events and milestones.

Overall, Pluralsight Flow is a valuable tool for software development teams looking to optimize their workflows and improve their processes. Its combination of detailed metrics, real-time visibility, and collaboration features make it a powerful solution for teams looking to work more efficiently and effectively. Review collected by and hosted on G2.com.

relatively high cost compared to other similar tools, the learning curve required to fully utilize its features, and the fact that it may not be suitable for smaller development teams with simpler workflows. Review collected by and hosted on G2.com.

As a manager, it helps me identify whether the team needs help applying good coding metrics. Developers can also self-evaluate as those are available to everyone. Review collected by and hosted on G2.com.

The UI is hard to navigate; buttons aren't clear where they will take you; sometimes, it takes many clicks to get to where we want to go, like seeing a single person's metrics, for example. Review collected by and hosted on G2.com.

I use it for my own motivation. I like seeing that there is a tool that validates that I'm doing lots of work, whether that's reviewing other merge requests, making comments, or pushing commits.

It helps with best practices. It's good to create short commits that are atomic and small, and the graph makes you want to do that. Review collected by and hosted on G2.com.

It's a little but clunky.

But, setting that aside, sometimes I forget to check it. I don't have a reason to check in very often. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

When working properly, the product can provide valuable insight into finding talent within your organization. It can also help find developers that struggle and improve their coding and code review practices.

The product is in constant evolution. Review collected by and hosted on G2.com.

The operational overhead to manage users, teams, repositories and git forks is unbearable. They really need to fix their git alias matching system. The user roles and groups are not integrated with other Pluralsight products like SKILLS which doesn't help.

Over the years, we faced multiple outages that caused the users to question the validity of the data. It is difficult to use as an input for performance when people question the reliability of FLOW. Efficiency is a metric that cannot be used reliably and coding days get impacted by normal operating practices like squashing commits and deleting branches.

Pluralsight has a pricing strategy that is not really compatible with the SaaS model. They had us commit in a multi-year contract and refused to revisit the license count for SKILLS and FLOW. Review collected by and hosted on G2.com.