Project Management & Agile··1 sources verified
Retrospective Actions Stall When They Depend on People Outside the Team
Summarised by Relevant News AI · Read time: 3 min
A Scrum.org practitioner column argues that retrospective actions often fail because they need changes outside the team or because the work never reaches Sprint Planning. It cites Easy Agile's State of Team Alignment 2026 survey of 419 engineers, product managers and project managers, which found 69 percent complete less than 60 percent of their retro actions. The survey attributed 28.9 percent of stalled actions to changes outside the team's control and 20.5 percent to actions that never entered Sprint Planning; the author notes the vendor's method is opaque, so the figures are rough.
Why it matters: Scrum teams that want retrospective actions to stick need a way to handle outside demands like shadow work, so they should check whether their improvement items reach Sprint Planning and who can approve cross-team changes.
All sources