Handling Stakeholder’s Review / Sprint Review in Kanban

“How do you handle Sprint Reviews in Kanban?” — This is a common concern during Kanban implementation in the IT industry.

The Sprint Review has been famous since 1995. Yet, most Scrum implementations struggle to do this. They struggle due to the complexity of development. It can become more complex in complex hierarchical organizations. The Kanban Method helps you think “out of the box.” But first, let us look at the history of the Sprint Review.

History of The Sprint Review

Sprint Review was introduced in 1995, and its definition and expectations have evolved.

1986: Hirotaka Takeuchi and Ikujiro Nonaka ]in “The New New Product Development Game.” — “Encouraging engineers to go out into the field and listen to what customers and dealers have to say.”https://hbr.org/1986/01/the-new-new-product-development-game

1995, Sutherland and Schwaber, the OOPSLA Paper mentioned -“Each Sprint is followed by a review”. “Review covers functional, executable systems that encompass the objects assigned to that team and include the changes made to implement the backlog items” http://www.jeffsutherland.org/oopsla/schwapub.pdf

1998, Sprint Review was called a “demo”.