Once your team is planning well and your stakeholders are aligned, two questions keep coming back: how do you know the team is doing well, and what do you do when something breaks? As a manager you are responsible for answering both, with evidence rather than gut feeling.
You'll start with engineering metrics: what measures such as DORA actually tell you, where they mislead, and how to use them to improve a team without turning them into targets. From there the module looks at incidents, including how to run an effective incident response and how blameless postmortems help a team learn from failure instead of hiding it.
Once you can measure your team's work and respond well when things go wrong, you'll be ready for the next module, Career Growth & Org Design, which looks at how to grow the people on your team and shape the structure around them.
A recorded webinar where panelists discuss how engineering leaders can measure and improve team performance using three well-known frameworks.
Allen Holub argues that DORA metrics don't tell the whole story of developer productivity, which is a useful counterpoint before you adopt any measure.
An overview of incident management as the Google SRE book teaches it, from the first alert through to the blameless postmortem.
John Allspaw explains why focusing on people instead of systems after an incident hides the real causes, and what a useful postmortem looks like instead.
A look at how Meta runs incident reviews across a very large product organization so that response stays effective and the same problems don't repeat.