Skip to main content
Table of Contents

Role Based Path - Engineering Manager

This guide is for Engineering Managers who need a simple, reliable way to run healthier sprints and improve team flow. It focuses on the views that help you spot bottlenecks early, reduce unplanned w…

heather.hazell
Updated by heather.hazell

This guide is for Engineering Managers who need a simple, reliable way to run healthier sprints and improve team flow. It focuses on the views that help you spot bottlenecks early, reduce unplanned work impact, and align on one small improvement per iteration.

Time Required: 6–10 minutes to orient, 15 minutes to set a sprint rhythm
Difficulty: Easy

TL;DR

  • Use Teams → Iterations (Current) for live sprint risk and scope signals.
  • Use Teams → Iterations (Completed) for planned vs. unplanned and carryover patterns.
  • Use Metrics → Delivery to understand where flow slows (coding, pickup, review, merge).
  • Use gitStream (if enabled) to reduce review friction with low-noise guardrails.
  • Use Developer Coaching (if enabled) to support workload balance and reduce knowledge risk.

What you likely care about

  • Are we on track for this iteration?
  • What’s causing carryover and scope instability?
  • Where are PRs getting stuck?
  • Is workload sustainable?

Where to spend time in LinearB

Teams → Iterations (Current)
  • Use for standups and mid-sprint scope checks.
Teams → Iterations (Completed)
  • Review planned vs. unplanned patterns and carryover themes.
  • If AI Iteration Summary is enabled, use it to accelerate your retro narrative and action items.
Metrics → Delivery
  • Identify the slowest stage trend and focus improvements there.
gitStream (if enabled)
  • Adopt low-noise PR hygiene and safe change patterns.

Metrics to prioritize

  • Cycle Time with stage context.
  • Planned vs unplanned and carryover.
  • PR size and review-friction patterns where relevant.
  • Unlinked work signals (when your team relies on PM linking).

Recommended EM operating rhythm

  • Weekly: Use Current Iteration + Delivery trend checks to spot early risk.
  • End of sprint: Review Retro Iteration patterns and pick 1–2 improvements.
  • Next sprint: Validate changes by checking trend shifts.

Recommended next articles

How did we do?

Role Based Path - Director of Engineering

Role Based Path - PMO & Delivery Operations

Contact