This image belongs to www.innolution.com
Of course, I know that there is not any ceremonies in Kanban except for Daily meeting but you have to inspect and adjust your process.
What did I think of it?
Well, it was thanks to a nice lady (I believe that only for chatting with her because I hadn’t got the pleasure to know face to face).
Who is that girl?
She is Manisha Mahawar who works at Zanox AG as Lean Delivery Agent in Berlin at this time.
If you want to reach her, you can do it at twitter @mmahawar
She told me that she has several stakeholders in one project (following Kanban’s approach) that want to check the product before its release on production so she thought on Sprint Review but she hesitated about implementing Sprint Review because of course she knows the Sprint Review is not part of Kanban. However, after we were chatting I suggested her that it would be to do it in order to engage the stakeholders.
In addition, we have another discussion about when will be the best moment to do the Sprint Review. I recommend her not to do each week because the stakeholders would introduce many interruptions to the team.
Basing on different points of view, we agreed that the best time will be when team members finish a feature because the idea of Sprint Review is to deliver an increment of the product but it has to get real value to the stakeholders.
Second and minor issue was what should have the name of this “Sprint Review in Kanban”. There were many name such as Kanban Flow Review, Product Review (it sounds very similar to Scrum so we decided not to use it), Weekly Workflow review and others such as building blocks reviews, Or MmF review or PI review. We decided to adopt the last one, PI Review (Product Increment Review).
I haven’t said anything about this article to Manisha in order to get a great surprise to her (I hope so). Writing this article was thanks to her and her issue so I would like to give the credit of the idea and of course her help to do a brainstorm about what would be the best approach to deal with the Sprint Review.
At this moment, I will publish the article on Linkedin and then on my Agile blog (waiting for Mannish Mahawar’s comments and observations) www.mariolucero.cl