Maximizing Efficiency in Scrum with Sprint Goals

When a card gets pulled to work on, that should mean that the team is committing to not only starting it but also (and more importantly) finishing it.

Now, we all know that it's not always that simple. Blockers happen, new priorities come down the management pipeline, and, unfortunately, cards in progress are forgotten or pushed backward into the backlog.

But at the end of the day, your team is judged on the work they finish—not the work they start. And that's why the commitment to finishing should be the highest priority rather than the commitment to start something.

In this episode, Host Phil Ledgerwood talks about why cards get started but not finished and how to avoid ending up in this situation in the first place.