Pluralsight Flow Reviews

Pros

As a manager, PSF helps me identify whether the team requires assistance in implementing effective coding metrics. It also allows developers to self-evaluate their performance as these metrics are available to everyone.

Cons

Navigating the UI can be difficult at times. Buttons aren't always clear about their destination, and it may require multiple clicks to access specific metrics, like viewing an individual's data.

Pros

Pluralsight Flow equips me with the necessary tools to understand my team's work and identify areas where they may require assistance.

Cons

Individually, any of the metrics can be misused. It requires multiple metrics to obtain a clear picture.

Pros

I spend most of my time on the weekly activity summary, which conveniently displays all the actions taken by team members over several weeks.

Cons

I find some metrics like "impact" and "daily commits" to have perplexing guidelines.

Pros

The team-based metrics and reports seamlessly feed into our sprint retrospectives and individual coaching plans.

Cons

The absence of DORA metrics means we have to rely on an additional tool to ensure we capture operational metrics.

Pros

In my fortnightly one-on-ones with my engineers, I rely on Pluralsight Flow. The metrics it provides are excellent for gauging my team's progress and identifying areas for improvement.

Cons

Some of the metrics are a bit challenging to comprehend. It would also be beneficial to have additional metrics related to my team members' comments on pull requests.

Pros

The tool enables visualizing all the commits and other contributions from the team.

Cons

Most of the time, this information is inaccessible behind the skill walls of Jira, GitHub, or Azure. Flow bypasses this barrier.

Pros

It provides valuable insights into the team's activities. The concise and easily understandable reports help me comprehend what is happening within my team. The PR's report is particularly helpful.

Cons

Care must be taken while using Flow as it can potentially misrepresent an individual if not utilized carefully. Data requires context, and without understanding the context, it could paint an inaccurate picture.

Pros

The tool's most significant strength lies in the countless insights it offers.

Cons

Integration with repositories and tickets is simple. Teams and goals can be easily configured.

Pros

Pluralsight consistently enhances and expands its flow services. While the initial version already provided me with basic insights into my team's performance, the latest version offers practical tips and advice based on the actual metrics provided.

Cons

Getting the proper data in Pluralsight requires some effort. Since our codebase tends to move around, we need to re-add it to Pluralsight. Although this process doesn't disrupt the metrics or cause issues, Pluralsight doesn't provide alerts when the data stops coming in.

Pros

I can gain valuable insights about my work and track my progress.

Cons

One benefit is that it automatically gathers data.

Pros

The dashboards in PSF are user-friendly, allowing me to easily review the behavior of individual team members or assess the team as a whole. I can effortlessly examine metrics such as daily commits or response rates and make easy comparisons between individuals and the entire team.

Cons

While they are working on enhancing it, I would appreciate better goal-setting options. Currently, it's challenging to set goals per member or user. It would be great to have additional "engagement tools," such as reminder emails to encourage achieving previously set goals.

Pros

Out of the box, Flow presents a plethora of information and metrics that can be utilized to enhance processes, quality, and productivity.

Cons

It's not always clear how the metrics are calculated. In my team, we have several part-time members, and most of the metrics, such as coding days, don't account for this.

Pros

Personally, I use it for motivation. It's gratifying to see a tool that validates my hard work, whether it's reviewing merge requests, providing comments, or making commits.

Cons

However, setting that aside, I often forget to check it. There's no compelling reason for me to check in frequently.

Pros

When functioning properly, the product offers valuable insights for identifying talent within the organization. It can also help identify developers who may be struggling and improve their coding and code review practices.

Cons

Throughout the years, we encountered several outages that raised doubts about the data's reliability. It becomes difficult to utilize Flow as a performance input when there are concerns about its validity. Metrics like efficiency can't be relied upon, and coding days are impacted by common practices like squashing commits and deleting branches.

Pros

It delves much deeper into software engineering metrics than the usual commits per day.

Cons

Managers need to understand that this tool doesn't provide the complete story. It serves as a useful conversation starter during one-on-one meetings and offers a way to gauge the pulse of the engineering team. However, it can be risky in the hands of individuals without a software engineering background.

Pros

It's fascinating how it correlates numerous engineering metrics, offering teams and leadership a more accurate view of performance at both individual and team levels. Having a streamlined method to combine all these different data points is fantastic.

Cons

There have been instances where certain dashboards weren't functioning correctly, but the support team has been excellent in assisting me and resolving the issues promptly. In other cases, configuration changes on our end unexpectedly broke the setup.

Pros

I appreciate the insights it provides on the team's throughput and delivery capabilities.

Cons

I'm dissatisfied with how it doesn't adapt well to our development flow, and I question its claim of being usable for coaching individuals.

Pros

It provides an appropriate measure of where teams currently stand and highlights areas for improvement.

Cons

Gathering excessive data across various aspects for developers makes the analysis process overly complicated.

Pros

While it's not foolproof, it offers a comprehensive understanding of my team's performance. The user interface is visually appealing and helps identify areas for improvement among developers.

Cons

It doesn't handle co-authors from Git, so there will be missing data if that's a common practice in your teams.

Pros

The insights go beyond superficial metrics like lines of code and uncover what truly matters.

Cons

The pricing is high. Ideally, it should cost about half as much.