I have questions before I purchase a Flow business subscription

Pluralsight Flow is a highly customizable software engineering analytics platform that provides concrete data and insights into your software delivery process. Configure Flow to provide the data you need for your unique business practices. Use Flow’s data to discover how you can evolve your workflow to create and support healthy work patterns. 

How does Flow work?

Flow connects to githosts like Gitlab and ticket vendors like Jira to pull in data and visualize it in reports. Flow pulls data from solutions across the software development life cycle and gives you data that reflects the real work your teams and individual engineers are doing. Flow visualizes your data across reports so you can understand where teams get stuck, who might need guidance, which practices are going well, and how you are progressing toward your goals. 

Engineering leaders use Flow’s data to:

• Get on the same page with engineers during 1:1’s. 
• Visualize your workflow and analyze work efficiency.
• Gain deeper insights into how teams really work during a sprint. 
• Better understand your teams’ needs and bottlenecks.
• See where you can improve your practices in ways that work best for your team.

Flow is designed for leaders of software development teams, including CTOs, VPEs, Directors, Engineering Managers, platform engineers, and Team Leads. 

Managers can lose the intuition and visibility as their teams scale. The larger the team, the harder it is to answer questions like:

• What did we deliver yesterday?
• How much burn went toward paying down technical debt?
• Why is the release running late?
• Did the process changes make things better?
• How do I know when someone is struggling, and how can I help?

Flow answers those seemingly impossible questions. Flow is the tool of choice for data-driven leaders and helps software teams reach their highest potential.

Our pricing plans are described on the pricing page (opens in new tab).

Pricing tiers are based on the number of people actively contributing to your codebase.

For most Flow reports, you won’t need to change your workflow. Flow report data is generated when your developers check in code, update tickets, create PRs, and more.

But every engineering team is unique and approaches their work differently. Flow provides powerful configuration options to help make Flow work better with the unique aspects of how you work. Once Flow is configured, you’ll get to spend less time bothering people to ask what they’re working on.

With changes to your workflow and new features being added to Flow, you’ll want to spend time regularly to keep Flow configured the best way for you, your workflow, and your team’s uniqueness. This will not only enable you to have the most accurate data, but also let you take advantage of new and updated Flow features.

Flow works with Git repositories and ticket vendors.

If your repositories are available in the cloud or behind a firewall, Flow can connect to your codebase. Learn more about using Flow with an internal server or behind a firewall.

Flow integrates with the below Git hosts and ticket vendors:

If you host your code in any of the below Git hosts, Flow ingests your commit data, pull request data and tickets/issues.

• GitHub cloud
• GitHub Enterprise
• GitLab cloud
• GitLab Enterprise
• Bitbucket cloud
• Bitbucket Server
• Azure DevOps Services (VSTS)
• Azure DevOps Server (TFS)
• Jira

Flow also works with the following vendors via HTTPS or SSH:

• Assembla
• Beanstalk
• Kiln

We are language agnostic, so any coding language checked into a Git repo will work.

Well, sure you count lines of code, but why would you want to do that?

As demonstrated by this story from the early days at Apple, managing by lines of code is kind of ridiculous (opens in new tab). And it's not even clear how you would do it if you wanted to.

Reductionist metrics like lines of code are incomplete ways to think about software engineering. After all, writing more lines of code isn't the same thing as forward progress, and doing more with less code—or removing code—is often the goal.

We believe your data has a far more interesting story to tell. For example, we think that Impact is a better way to think about codebase change. The metrics in Flow have accounted for this false path and we do not emphasize lines of code as a meaningful metric.