Early in my journey, I operated under many assumptions. One particular one (embarrassing now) was that having exact processes and workflows with good documentation would be enough. Ah, silly me, depending so heavily on best practices. Thank goodness for the patient mentors and co-workers that have helped me learn better …

Every system – particular a complex one like a cross-functional development team – has constraints. Somewhere along the way from “Ready” to “Done” something impedes productivity and flow, be it drag or turbulence, viscosity, or excessive effort. Some folks call these issue bottlenecks, blockers, setbacks, obstacles, impediments, obstructions or waste. …

The Sprint Review, just like the iteration retrospective, is one the most important feedback loops in a Scrum team’s toolbox. According to “The Scrum Guide,” the purpose of the Sprint Review is to “inspect the increment and adapt the backlog as needed.” Let’s unpack that a bit. During the review the team and their stakeholders …