Have questions about Pluralsight Flow before you make a decision?
Here are common questions and answers that can help you—or your boss—choose how to move forward.
Traditionally, engineering has relied on narrative and subjective metrics like story points and tickets cleared to demonstrate business value.
Flow is an organizational tool, pioneering a different way of measuring and communicating about productivity in software engineering. Imagine the airplane pilot who has been flying by feel, finally having the instrumentation to make the flight more predictable and reduce risk.
Flow provides engineering leaders with metrics in context to ask better questions and advocate for the team with substantive data:
- How much of your team's burn is going to refactoring old code?
- Did the change to our sprint cycle have a net-positive effect?
- How do Wednesday all-hands meetings affect productivity?
- How well do we share knowledge in code reviews?
- What did engineering accomplish last week?
By mining data in Git, we are able to increase visibility about team contributions, see where the biggest impact is being made, identify areas to give concrete feedback, and help teams understand how process changes impact the team’s effectiveness.
Flow is designed for leaders of software developments teams, including CTOs, VPEs, Directors, Engineering Managers, and Team Leads.
Basically, it's for anyone who is responsible for leading a software team—and tired of the interruptive shoulder-tapping, narrative accounts, and subjectivity of the past.
Managers tend to 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?
This is why we built Flow—to finally 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.
Pricing tiers are based on the number of people actively contributing to your codebase, and the number of repos that we process.
If your team doesn't fit neatly into one of the tiers, that's fine—all exceptional pricing is handled on a case-by-case basis.
Flow works with your current process, so there's nothing to change in your workflow.
All of our reporting is automatically generated when your developers check in code. No more bothering people to update tickets, or interrupting people to ask what they working on.
Flow works with any Git repository, no matter where you host it.
If your repos are available in the cloud or behind a firewall we will be able to connect to your codebase.
Flow is fully integrated with the following Git Hosts:
If you host your code in any of the below Git hosts, we will ingest your commit data, pull request data and tickets/issues.
- GitHub cloud
- GitHub Enterprise
- GitLab cloud
- GitLab Enterprise
- Bitbucket cloud
- Bitbucket Server
- Azure Devops (VSTS)
- Team Foundation Server (TFS) Setup
Flow also works with the following vendors via HTTPS or SSH:
Yes, we offer an on-prem solution for enterprise customers. Learn more about Flow Enterprise Server here.
- Lets you install Flow into your data center or private cloud to protect it behind a firewall
- Never sends information about your source code or metrics outside your infrastructure
- Is completely self-contained
- Allows you to integrate with GitHub, GitHub Enterprise, BitBucket, BitBucket Server, and GitLab Cloud
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. 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 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.
If you need help, please email email@example.com for 24/7 assistance.