LinearB Pulse correlates and analyzes Git activity, matching project issues, and team interactions creating the ideal project delivery board for dev teams.
Pulse shows the project issues and related Git work for each team member to help you run a faster, more dev-friendly daily stand-up meeting. The Pulse daily devboard automatically:
- Shows completed work and WIP for each dev so you spend less time on status updates.
- Flags high-risk branches and blocked PRs so you can get help for everyone who needs it.
- Visualizes progress, risks and blockers for dev work in the context of the relevant project issue so you can predict if you’re going to hit your delivery deadlines.
Here’s 16 tips for using LinearB Pulse to run your most efficient stand-up ever:
Look for the ⚡️LIGHTNING BOLT⚡️ symbol for advanced tips.
How to use LinearB before your stand-up
1) ⚡️Get updates from the last 24 hours
Open Pulse for five minutes before your stand-up each day to review progress from the last 24 hours. Use the “Done” filter to see work that has been completed and the “WIP” filter to see work in progress. This will allow you to spend less time in the stand-up discussing status updates and more time focusing on who needs help and who needs to connect after the meeting.
How to use LinearB during your stand-up:
2)⚡️Start with high-risk code and blocked PRs
Start your meeting on the “Team Dashboard” to see “Notifications” about branches with high-risk code and blocked PRs.
LinearB analyzes Git logs to predict future production quality issues. We also flag PRs merged without review, PRs that have not been picked up for review, PRs with abnormally high review time and PRs with abnormally high back and forth interaction.
Reviewing these notifications at the beginning of your meeting ensures status updates don’t take time away from discussing who needs help.
3) ⚡️ Check your WIP balance across the team
While you’re in the Team Dashboard, you can see how many active branches each team member has, how many reviews they’ve done in the current iteration and how many days they’ve been active. You can easily see when workload is not balanced across team members or when one of your devs is at risk for burnout.
Knowing when team members are over or underutilized helps you understand risks to your delivery deadline.
4) Announce the number of days left in your iteration
Announcing the number of days left in your iteration at the beginning of the daily helps focus your discussion around “are we going to deliver on time?” Click in to Pulse and you’ll see this in the top left corner of the screen.
5) Look at issues and the related Git work for specific team members
Click the avatar to filter by “Member” and see just the issues and Git Activity Timeline for that specific team member.
6)⚡️ Check for context switching
Context switching can hurt your devs ability to go deep into specific customer use cases and may stop them from doing their best work. The Git Activity Timeline helps you visualize if someone is bouncing around between work or has too much work. Look for the following possible warning signs:
- Git activity dots across multiple issues in the same day or week.
- Git activity dots in issues that are not central to your core iteration success criteria.
7) ⚡️ Look for dependencies between developers
The “Member” column helps you see how each team member’s work relates to projects (e.g. features and bugs). When clicking through each team member and hovering over specific branches and PRs, pay attention to the other team members working on the same issues to uncover dependencies that could lead to delays.
8) Review “Git Activity Timeline” to see recent progress
The hover feature helps you see details for branches and PRs correlated to project issues. This allows you to see actual dev work and not just project issue status. Blue dots represent branch commits and green dots represent PR reviews and merges. These dots help you visualize how your team is working together to ultimately deliver the features and fix the bugs you care about.
9) Find outdated project management statuses
You can easily see when your project management tool status is not up to date by comparing the project status to the Git activity status and Git Activity Timeline. For example, if an issue is marked “Selected for Sprint” but you see dots on the timeline, that means work in Git has actually started and your project management tool is outdated.
Ready to start using LinearB Pulse for your daily?
10) Update your project management status directly from LinearB
When you see a discrepancy in status, you can update your project management tool directly from LinearB with two clicks. Use “Pulse Actions” to update your “Project Status” directly from LinearB.
11) Look at completed work and work-in-progress
Filter by “Done” and “WIP” to see completed work and work in progress. Issues marked as “Done” in your project tool are highlighted in green so can spot them easily even when the “Done” filter is not engaged.
12) Filter by “To do” to see issues that have not been started
Quickly see issues that have not been started and compare against the number of days left in your iteration and the amount of WIP across the team so you can communicate early with your business if you need to remove items from your iteration.
13)⚡️ Find priority issues that aren’t getting attention
“In Progress” state in your project management system doesn’t always mean an issue is getting the full attention it needs from the team. Use the Git Activity Timeline to visualize where your team is really spending their time and if your priority issues are getting the focus they need.
How to use LinearB after your stand-up:
14)⚡️ Enable Slack alerts to see high-risk and blocked work in real-time
Don’t wait until your stand-up to find out your team needs help. Activate LinearB Slack alerts, get notified about high-risk code and blocked PRs in real-time and jump in to help with one click.
Did someone say automated high-risk code Slack Notifications?
We did! Enable high-risk Slack Alerts with a LinearB free account.
15) See how non-planned items are impacting your iteration
Use the “Type” filter to drill into specific issue types like bugs to see how these (typically) non-planned items are affecting your delivery scope and how much effort is allocated there.
16) Keep your Product Manager up to date
Help your product management team and business stakeholders stay up to date with your team’s progress by inviting them to LinearB and linking them to the Pulse devboard each day. They’ll get the information they need to make decisions without interrupting your devs.