Flow Academy is an educational resource for customers getting started with incorporating analytics about the development process into their team’s standups, retrospectives, one-on-ones, and more. By leveraging data in their regular workflows, engineering teams can map initiatives to outcomes, identify and eliminate blockers in real-time, have more productive and actionable conversations, and adjust processes with confidence.

Course Overview

Using the player card in 1:1s

Summary Recap

For further information, see  1_1s with Developers.pdf.

Learning Check

Which report is the most useful in 1:1s with developers?

• Project Timeline.
• PR Resolution.
• Player Card.

Before we start using data as a starting point for discussion in 1:1s for the first time, what should we do? 

• Coach team members on what the different reports are showing and help get them comfortable with the data.
• Bring the reports into the discussion and start asking questions about different metrics or trends.

An engineer recently joined your team and is beginning to ramp up. How do you know?

• Their Active Days per Week and PR Involvement are beginning to rise.
• Their Influence is increasing and Review Coverage is decreasing.
• Their Unreviewed PRs metric is beginning to rise.

See LC M1_ 1_1s with developers.pdf for correct answers.

Course Overview

Using the code fundamentals in Retrospectives

Using the PR resolution in Retrospectives

Using the review & submit fundamentals in Retrospectives

Using the review and collaboration

Summary and recap

For further information, see Retrospectives.pdf.

Learning Checks

What two metrics in the Review & Collaboration report help us understand “speed of feedback”? 

• Unreviewed PRs and Influence. 
• Responsiveness and Reaction time. 
• Influence and Review coverage. 

What two metrics in the Review & Collaboration report help us understand “thoroughness of feedback”? 

• Unreviewed PRs and Influence. 
• Responsiveness and Reaction time. 
• Influence and Review coverage. 

What is the difference between the Review fundamental metrics and the Submit fundamental metrics? 

• The Review fundamentals look at how team members are handling their own work in the code review process, whereas the Submit fundamentals look at how team members are handling others’ work in the review process.  
• The Submit fundamentals look at how team members are handling their own work in the code review process, whereas the Review fundamentals look at how team members are handling others’ work in the review process.  

Which two metrics in the PR Resolution report are most commonly used in team retrospectives? 

•  Time to First Comment and Time to Resolve.
• Time to First Comment and Avg. Comments per Review.
• Avg. Comments per Review and Number of Follow-on Commits.

See LC M2_ Retrospectives.pdf for correct answers.

Course Overview

Using the work log in Daily Standups

Using the review workflow in Daily standups

Using the Daily Update in Daily standups

Summary and recap

For further information, see Daily Standups.pdf.

Learning Checks

How is the Daily update report most commonly used in Standups?  

• To help the team quickly surface discussions around code-level blockers. 
• To find team collaboration patterns. 
• To visualize commit, ticket, and PR activity in one unified view. 

What does the Review workflow report show? 

• A visualization of team work patterns over time. 
• A unified view of all the team’s open PRs over the selected time period. 
• A set of metrics that give a high-level view of how the team is leveraging the code review process. 

What are the defining characteristics of high-activity pull requests? 

• PRs that are seeing a lively discussion, likely with a number of reviewers participating, but the discussion has continued for a while and doesn’t seem to be driving toward a resolution.
• PRs that are larger in size, with a higher level of Review coverage. 
• PRs that have a higher than average number of follow-on commits. 

What are the defining characteristics of long-running pull requests?

• PRs that were submitted near the end of a sprint after the main PR was approved. 
• PRs that have been open for a while, where there was some back-and-forth discussion between team members that was followed by silence. 
• PRs that have been open for a while but haven’t received any comments or an approval. 

See LC M3_ Standups.pdf for correct answers.

Course Overview

Using the player card in 1:1s with your manager

Using the Project timeline in 1:1s with your manager

Using code fundamentals in 1:1s with your manager

Summary and Recap

For further information, see  1_1s with Managers.pdf.

Learning Checks

How is the Player Card most commonly used in 1:1s with Managers? 

• To help managers keep a pulse on how things are going, proactively make the team’s work visible, and advocate for specific team members. 
• To give an overview of what every individual on the team is working on. 
•  To provide a high-level view of team collaboration trends over time. 

Your team decides to allocate an entire sprint to cleaning up older areas of the codebase. Which report should you use to make the work your team is doing visible? 

• Code Fundamentals
• PR Resolution
• Project Timeline

See LC M4_ 1_1s with Managers.pdf for correct answers.