Metrics for Scrumban
I'm working with a team that has recently pivoted from using Scrum (zombie) to Kanban with Scrum ceremonies. The team management wants me to come up with the 'right' metrics to measure to show success and have advised that I sue the Goal-Question-Metric methodology to come up with a presentation which after they have reviewed and approved, can then be shared with the team. The whole idea of doing this without the team in the first place seems strange to me! And also, from my experience with Kanban, I have suggested that we use what's available out of the box initially, which is Control Chart, CFD and Throughput of work items over time. However, this doesn't seem to be cutting it with them and I am struggling to come up with something novel in the G-Q-M format. Has anyone any advice on this or on any other aspects that perhaps can satisfy the ask of 'what metrics are we going to measure'?
As you have rightly put the Goal first - so let's start with that...what are we (team management) really trying to achieve? So that we do not get lost in the myriad of questions. And then we can focus on limited questions derived from the goal. Also, give a thought on Impact Mapping with OKR.
I'm working with a team that has recently pivoted from using Scrum (zombie) to Kanban with Scrum ceremonies. The team management wants me to come up with the 'right' metrics to measure to show success
I'd suggest that your team has not pivoted at all, but given up on Scrum because it has proven too hard. The zombie problem is less visible but it is still there. Before you consider the "right metrics" to show some kind of "success", my advice is to think about how you will tackle this unfortunate loss of transparency.