This document will walk you through how to utilize LinearB in your daily workflow.
1) Identify Unreviewed Pull Requests:
Identify pull requests that have been merged without review. Pull requests that are merged without review increase quality risk, decrease efficiency, and slow new value delivery.
Navigation: Activity → Pull Requests → Predefined Filters: “Merged Without Review”
2) Proactively Address Risky Work in Branches
Detecting risky work in branches allows for proactive quality risk management. Identify risky branches early and ensure proper inspection and review.
Navigation: Dashboard → WIP → Predefined Filters: “High Risk or High Rework”
3) Contributor Workload (WIP)
Identify contributors that are overloaded with WIP. Having contributors overloaded with work will decrease your cycle time, increase risk for late iteration delivery, and increase risk for contributor burn out.
Navigation: Contributors → Sort by “WIP”
4) Long Living Pull Requests (Stuck PRs)
Identify pull requests that have been open for too long. Pull requests that have been open for too long degrade in quality, decrease cycle time, and increase risk. Find them and push them forward.
Navigation: Activity → Pull Requests → Predefined Filters: “Long Living”
5) WIP vs. Completed Work
See how much work your team has in progress and how much work your team has completed. Compare your WIP to your remaining iteration time to improve iteration predictability.
Navigation: Dashboard → WIP / Done