(Originally published by Lv Yi on June 8, 2019) This is the first article in a series about “number of backlogs and multi-learning”. It introduces three common team structures in product development organizations.

(Originally published by Lv Yi on Sep 22, 2018) The number of backlogs is the ultimate lever for agility. This is the insight we gained from the systems modeling exercises in my recent CLP course. I used to think of two main designs from LeSS: 1) one product backlog, and...

The Essence of Scrum Unfortunately, many so-called Scrum adoptions keep missing the essence of Scrum. They are too preoccupied with the mechanics of Scrum; process, roles, meetings, and certifications. Or, even worse, they are obsessed with non-Scrum practices such as stories, points, velocity, task boards, or product boxes.

(this article is part of the upcoming “97 Things every Scrum practitioner should know” by Gunther Verheyen (editor)) When applying Scrum to a product with more than one Development Team, there is really little guidance in the Scrum Guide. The Scrum Guide seems focused on one-team Scrum for the most...

(Originally published on Odd-e’s blog) It is natural that people specialize in various things, but when they do it too much, it becomes over-specialization. Over-specialization wastes our potential. We shall try to understand why it happens, and how the adoption of LeSS avoids it.