How to Run Retrospectives That Actually Improve Things
Learn how to run retrospectives that improve things: data-first prep, a 60-minute agenda with timings, one owned experiment per retro, and a review loop.
Category
Engineering delivery is the process side of shipping software: planning work, sizing it, prioritising it and getting it to users on time. It covers project kickoffs, roadmaps, Scrum and Kanban practices, handling competing urgent requests and retrospectives that change how the team works. Good process stays light and leaves engineers long stretches of focused time.
4 articles
Learn how to run retrospectives that improve things: data-first prep, a 60-minute agenda with timings, one owned experiment per retro, and a review loop.
Learn how to run a project kickoff that works: a charter, a 90-minute agenda with timings, an assumptions…
Learn how to prioritize when everything is urgent with MoSCoW, cost of delay, WSJF scoring, and an intake…
Learn the difference between delivering value vs shipping features, with a comparison table, outcome metrics, and a plan…